j Mar 26, 2018 · 12:31 am #9147 after updating the theme the page builder from siteorigin is not displaying.
checked in fiddler it’s throwing this error
Fatal error: Call to undefined function mime_content_type() in /home/lochinvarridgeco/public_html/wp-content/plugins/siteorigin-panels/inc/admin-layouts.php on line 94
0
j Mar 26, 2018 · 12:46 am #9148 The theme is Polestar free version
Andrew Misplon Puro Mar 26, 2018 · 4:42 am #9149 Hi 🙂
Is Page Builder up to date? Please, check that there isn’t an update for Page Builder waiting. If there is, please run it.
If the above doesn’t help you can roll Polestar back.
Will be online in a few hours to assist further.
j Mar 26, 2018 · 4:56 am #9150 Yes all are up to date, also tried disabling other plugins.
My temporary fix is that i commented out the
wp-content/plugins/siteorigin-panels/inc/admin-layouts.php
// get file mime type
$mime_type = mime_content_type( $file );
// skip non text files.
if ( strpos( $mime_type, ‘text/’ ) !== 0 ) {
continue;
}
is that ok?
Andrew Misplon Puro Mar 26, 2018 · 5:00 am #9151 That should be perfect, thanks.
Page Builder introduced hardening for this error in the last version but it clearly wasn’t enough. Thanks for sharing the info. I’ll pass this on and hopefully we can prevent it happening in future. We haven’t been able to replicate it so far which has made things harder.
I’ll update Polestar this afternoon to remove the layouts function till this is resolved.
Thanks for the help, much appreciated.
j Mar 26, 2018 · 5:10 am #9152 Thank you.
i don’t know if it has something to do in php version though
Andrew Misplon Puro Mar 26, 2018 · 5:15 am #9153 Thanks. At a glance it looks like there is support in PHP 7. Some users can switch versions in thei hosting control panel, if you can, that might be an option.
Andrew Misplon Puro Mar 26, 2018 · 5:24 am #9155 Any chance you know which version of PHP your server uses? Just so I can add that to the issue report? Thanks.
j Mar 26, 2018 · 5:33 am #9156 Does not work in live site PHP Version 5.6.34
but works in localhost PHP Version 5.6.24
Andrew Misplon Puro Mar 26, 2018 · 5:53 am #9157 Super, thanks for the update. I’ll pass this all on shortly. If you can upgrade to PHP 7, I’m sure it’ll help with other challenges in the future. PHP 7.2 is recommended for WP.
TheDoubleDavis Mar 27, 2018 · 2:04 pm #9171 Hello,
I also wanted to chime in to mention it is happening to one of our sites too. Same error, and everything is up to date. Front end of the site looks good, just the admin area isn’t displaying. I know this was created yesterday but I also wanted to wait for an update as well.
Thank you in advance!
Andrew Misplon Puro Mar 27, 2018 · 2:46 pm #9172 Hi, thanks for reaching out.
The issue is in PHP 5, some servers have an extension installed that resolves this and others don’t. If you can upgrade to PHP 7, the issue will be resolved.
Page Builder will rewrite this function in their next update to avoid this for servers unable to upgrade PHP.
I’ll push an update for Polestar this evening to remove the layouts folder until the Page Builder update is out.
Sorry for the hassle. Thanks.
TheDoubleDavis Mar 27, 2018 · 6:11 pm #9173 Thank you for the speedy response! We are up to PHP 7.
The error is gone, however the display in edit mode and add new is still not there (and only a button for visual and text).
Just wanted to update with that as the information may help.
We were also considering uninstalling page builder plugin and the widget bundle plugin that goes with it (both site origin), then reinstalling them both again. Though we are worried it will wipe the information on the pages.
Andrew Misplon Puro Mar 27, 2018 · 6:31 pm #9180 Super, thanks for upgrading PHP.
Page Builder has most likely dropped below the editors. When the tab fails like this it’s often due a JS conflict. Please, try a plugin conflict test. Temporarily deactivate all non-SiteOrigin plugins in one go. Is the issue resolved? If so, there is a conflict. Reactivate plugins one by one, test after each activation. If the issue does not resolve with all non-SiteOrigin plugins deactivated, it isn’t a plugin conflict.
TheDoubleDavis Mar 27, 2018 · 7:01 pm #9181 Hello again,
Thank you for the advice! We did the plugin conflict test and saw that once all non-SiteOrigin plugins were deactivated, the issue still remained.
Thank you for your support thus far by the way.