Update bug

I too have had to deactivate your plugin. 1.26 was stable, 1.27 is definitely not.

• This reply was modified 1 year, 1 month ago by Muette.

Hi @muette

I hope you’re well today!

I’m sorry to hear about the issue but we are not aware of any general bug that would take sites down. Usually such issues are specific to site configuration or server configuration/resources and that would need to be checked.

If you have access to some server PHP error log (or could ask your host to look into it) and you could share such log – entries from about time when this happened – it could help diagnose the issue.

As for rollback, simplest way is as follows

1. access your site via FTP, cPanel “File Manager” or similar way and go to “/wp-content/plugins” folder
2. delete “forminator” folder from there entirely (it will not remove any form data from site, only the plugin itself)

If Forminator update took the site down, site should get up after that (note: if there’s any server-side cache, you may need to purge it additionally)

You should be able to login to the site then just fine.

3. then you can download previous version of plugin from this page (form at the bottom):

https://www.ads-software.com/plugins/forminator/advanced/

4. and, finally, simply install it via the “Plugins -> Add new -> Upload” option in your site’s back-end.

This way you would retain all the forms and data that was already there.

Kind regards,
Adam

Thank you, have managed to rollback to previous version 1.26 which works fine. However, I tested this twice, both times 1.27 caused a critical WP error – and there were no changes to the rest of the environment in the intervening period so we are still unable to use 1.27. I have looked thru PHP error logs – nothing – and have put in a support request to the hosting company. May I reiterate also, I was not the only one who experienced this today – I noted another person with the same issue.

Thanks for the instructions.

I replicated the error and this points firmly toward a mismatch between your latest version and WP functions.php line 5905:

“Fatal error: Uncaught Error: Call to undefined function php_uname() in D:\Inetpub\vhosts\DOMAIN\wordpress\wp-content\plugins\forminator\library\mixpanel\class-mixpanel.php:151 Stack trace: #0 D:\Inetpub\vhosts\DOMAIN\wordpress\wp-content\plugins\forminator\library\mixpanel\class-mixpanel.php(64): Forminator_Mixpanel->super_properties() #1 D:\Inetpub\vhosts\DOMAIN\wordpress\wp-content\plugins\forminator\library\class-core.php(128): Forminator_Mixpanel->__construct() #2 D:\Inetpub\vhosts\DOMAIN\wordpress\wp-content\plugins\forminator\library\class-core.php(68): Forminator_Core->__construct() #3 D:\Inetpub\vhosts\DOMAIN\wordpress\wp-content\plugins\forminator\forminator.php(377): Forminator_Core::get_instance() #4 D:\Inetpub\vhosts\DOMAIN\wordpress\wp-content\plugins\forminator\forminator.php(106): Forminator->init() #5 D:\Inetpub\vhosts\DOMAIN\wordpress\wp-content\plugins\forminator\forminator.php(84): Forminator->__construct() #6 D:\Inetpub\vhosts\DOMAIN\wordpress\wp-content\plugins\forminator\forminator.php(505): Forminator::get_instance() #7 D:\Inetpub\vhosts\DOMAIN\wordpress\wp-includes\class-wp-hook.php(310): forminator() #8 D:\Inetpub\vhosts\DOMAIN\wordpress\wp-includes\class-wp-hook.php(334): WP_Hook->apply_filters() #9 D:\Inetpub\vhosts\DOMAIN\wordpress\wp-includes\plugin.php(517): WP_Hook->do_action() #10 D:\Inetpub\vhosts\DOMAIN\wordpress\wp-settings.php(495): do_action() #11 D:\Inetpub\vhosts\DOMAIN\wordpress\wp-config.php(86): require_once(‘…’) #12 D:\Inetpub\vhosts\DOMAIN\wordpress\wp-load.php(50): require_once(‘…’) #13 D:\Inetpub\vhosts\DOMAIN\wordpress\wp-admin\admin.php(34): require_once(‘…’) #14 D:\Inetpub\vhosts\DOMAIN\wordpress\wp-admin\upload.php(10): require_once(‘…’) #15 {main} thrown in D:\Inetpub\vhosts\DOMAIN\wordpress\wp-content\plugins\forminator\library\mixpanel\class-mixpanel.php on line 151

Notice: Function is_embed was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in D:\Inetpub\vhosts\DOMAIN\wordpress\wp-includes\functions.php on line 5905

Notice: Function is_search was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in D:\Inetpub\vhosts\DOMAIN\wordpress\wp-includes\functions.php on line 5905

There has been a critical error on this website.”

• This reply was modified 1 year, 1 month ago by Muette.

Hi @muette

Thank you for response!

Yes, I noticed another case as well afterwards but still – knowing about specific error is very important here.

And the error that you found is indeed saying a lot about the issue. It seems that, the php_uname() function is disabled by your host (either or purpose – assuming some security risk or just by oversight) the “php_uname()” function on the server. Most likely that happened upon PHP update/switch from 7.x to 8.x.

That doesn’t mean that there is a bug in Forminator but rather that it’s a server/hosting specific issue and so far it’s quite rare.

However, we care a lot about compatibility so I have reported it to our Forminator Team already and our developers will look into it to see how they can modify our code so it would no longer need that function (or at least didn’t fail if it’s not available).

I’m not able to give ETA on this as it’s a fresh discovery and needs to be fully investigated by developers, fixed and then also tested by QA team before release but they’ll work on it and fix would be included in one of future releases.

As for now, you could ask your host to see if they could allow the php_uname() function for you or, if they refuse, stick to previous version of the plugin until the fix is released.

Kind regards,
Adam

Thank you very much. I will pass that suggestion on to them. Hope it helps other people avoid this stress. Have already reverted to v 26.

They cannot allow that function since it is a shared tenancy. We will wait for your next (improved) version in the hope you can rectify this.

My host has that option disabled too for security so hope reverting to previews version will fix error on my end too

Agata

Hi, I just tried your latest update 1.27.0, and it’s still breaking my WP admin backend… sorry guys. Still stuck on 1.26.0

Hello @muette,

I hope you’re doing well today!

Our developers are still looking for possible workarounds to be implemented in the plugin, to make the latest versions work with as much hosting environments as possible. However, there’s no ETA, I’m afraid.

Meanwhile, if the hosting support can’t help with enabling php_uname function, you can try a workaround with defining it in a PHP snippet.

Please save the following code in as a PHP file, e.g. php-uname.php, and upload it to /wp-content/mu-plugins/ directory:

<?php

if (!function_exists('php_uname')) {
    function php_uname($mode = 'a')
    {
        $uname = array(
            'a' => php_uname('s') . ' ' . php_uname('r') . ' ' . php_uname('v') . ' ' . php_uname('m'),
            's' => 'Windows NT',
            'n' => 'Windows',
            'r' => '5.1',
            'v' => '5.1 build 2600',
            'm' => 'x86'
        );
        return $uname[$mode];
    }
}

This should make it run as a must use plugin.

Let us know if there’s still any issue!

Best Regards,
Dmytro

Thank you Dymtro I will try that. Do you think you will solve this problem eventually?

Hello @muette,

I see the request has been forwarded to the developers. However, I can’t guarantee that php_uname function can be completely omitted, or provide any ETA at this point, I’m afraid.

Please let us know if the above PHP snippet helped to make it work on your end. Your feedback can help our devs to make the right decision, (e.g. use a similar solution in the plugin).

Best Regards,
Dmytro

Hi @muette,

Since we haven’t heard from you for a while. I’ll mark this thread as resolved for now. Please feel free to re-open the thread if you need further assistance.

Regards
Nithin

Please if we can keep open till I have tried the snippet. Thank you.

Hi Forminator,

I followed your instructions and uploaded the php-uname.php file, then tried to update to 1.28 and got this!

Update failed: <?php if (!function_exists('php_uname')) { function php_uname($mode = 'a') { $uname = array( 'a' => php_uname('s') . ' ' . php_uname('r') . ' ' . php_uname('v') . ' ' . php_uname('m'), 's' => 'Windows NT', 'n' => 'Windows', 'r' => '5.1', 'v' => '5.1 build 2600', 'm' => 'x86' ); return $uname[$mode]; } } -1

So, I removed the php-uname.php file & tried the update again.

1.28 has now updated and so far, seems to be ok! YAY!

Will keep you posted. Thank you.

Muette