[Resolved] Types upgrade blanking out all forms on our site.

[Author]

Posts

[davidM-25]

Please read about the issue here -

https://toolset.com/forums/topic/cred-blanking-out-front-end-another-upgrade-failed-not-playing-with-types/

We were in the middle of a site update and URL change so we just backed down types to work. We want to move forward and upgrade toolset and I just tried again today on a test site and as soon as I update Types boom all of our CRED forms are blank.

This happens across 2 distinct sites on our server too. There has to be something we saved in the database a certain way or some upgrade path we took a while ago that is causing the issue. I can do a clean install of toolset and everything works so obviously it is a database setting causing this. I can provide details for login to our test site and anything else you need but this is very important to fix as we are running into issues with toolset things not working that have been fixed in the latest versions.

Please let me know what you need and what the next steps are. To be clear - once the CRED form starts everything on the page - even the non-toolset stuff and theme stuff - is completely wiped out. Just blank right at the start of the CRED form. This is not theme or other plugin related, as stated in other ticker we have tried turning all things off.

[davidM-25]

I can give example pages in a private message. Please let me know if you have any issues with the details. Feel free to switch themes or do anything else with the site as it is purely a cloned backup.

[Luo Yang]

Hello,

The problem you mentioned above is abnormal, if you see a blank wordpress page, it means there is PHP errors in your website.

In case it is a compatibility problem, please try this:

1) Backup your website first,

2) Make sure you are using the latest stable version of Toolset plugins, you can download it here:
https://toolset.com/account/downloads/

3) Deactivate other plugins and switch to wordpress default theme, and test again

4) Enable wordpress debug mode, and copy/paste the PHP debug logs here

PHP Debugging
In case you think that Types or Views are doing something wrong (what we call a bug), you should enable PHP error logging. Again, edit your wp-config.php file and add the following:

ini_set('log_errors',TRUE);
ini_set('error_reporting', E_ALL);
ini_set('error_log', dirname(__FILE__) . '/error_log.txt');
This will produce a file called ‘error_log.txt’ in your WordPress root directory. Make sure that the web server can create and write this file. If it cannot, use an FTP program to create the file and make it writable to Apache (normally, user www-data).

https://toolset.com/documentation/user-guides/debugging-types-and-views/

5) If the problem still persists, please provide a database dump file (ZIP file) of your website in below private detail box, also point out the problem page URL, I need to test and debug it in my localhost, thanks

[Luo Yang]

Thanks for the details, the function mb_convert_case() is a built-in PHP function
hidden link

so it should be a server problem, you will need to install PHP mbstring in your website, please check it with webserver provider for it, here is a document about
mbstring Introduction :
hidden link

[davidM-25]

We had a few issues. First we weren't getting good error reporting from PHP. I had to do a fresh install of the package and move to latest of 5.6.

When we did this we sent the results to you guys and I realized that the errors were mbstring issues. We initialized mbstring and was able to update the types package.

Now I am not sure what was in the release notes but you guys have to do a better job of advertising upgrade requirements. If a new server mod was required that this would be in big red bold before someone hit update now on their site. I mean this is a big deal.

What makes it harder to troubleshoot and I am sure your devs know why but we can install all new stuff clean without mbstring enabled and we didn't get the blank pages... This ticket, a couple others, and hours troubleshooting our site could have been fixed with a couple of lines in release notes.