• Hello guys,

    first my actual environment:
    Version WP: : 4.6.1
    Theme: Catch Evolution Pro 3.4 + Child theme

    MySQL Version : 5.5.52
    PHP Version : 5.6.29
    WP URL: http://www.astrolive.ch
    Debug File Permessi di scrittura : Writable
    PHP Memoria in uso: 56.92 MB
    Limite di memoria PHP : 256M
    Dimensione upload massima PHP : 2M
    Dimensione massima Post PHP : 8M
    Consenti URL fopen PHP : Disabilitato
    PHP Allow URL Include : Disabilitato
    PHP Display Errors : Disabilitato
    PHP Max Script Execution Time : 30 Seconds

    Plugins:
    All In One WP Security 4.2.4
    Catch Web Tools 1.9.1
    Category Posts Widget 4.6.2
    WordPress Contact Forms by Cimatti 1.4.4
    Widget Facebook like box 1.0
    Moon Phases 3.1.1
    Recent Posts Widget With Thumbnails 4.13.1
    Redirection 2.5
    Page Builder by SiteOrigin 2.4.21
    Smart Slider 3 3.1.2
    SiteOrigin CSS 1.1.2
    SiteOrigin Widgets Bundle 1.7.2
    WooCommerce 2.6.9
    Yoast SEO 4.0
    Zodiacal period 1.0
    ——————————————
    First of all, I followed Marius’s L. J. (Clorith) advises to avoid possible basic mistakes!

    Well, i try now to explain what happens:
    If I update from 4.6.1 to 4.7 the twin installation i have on the localhost , it will be done perfectly.

    If i try to do the same on the online-installation, it won’t be done correctly (i think).
    The final result is that i get a blank page with address: “www.astrolive.ch/wp-admin/about.php?updated”. If i try to re-login or to visit my homepage, the browser shows a blank page. I have no chances to achieve my site.

    I have tried to update first plugins and at the least the WP-version, nothing.
    I have tried to do it contrariwise, nothing too.

    Regarding the plugin “All in one WP Security” i resets all parameters to the original setting to avoid possible problems with access-permissions. No result!

    Fortunately, i created a backup and i can try to test a lot of “combinations” but
    in my opinion the problem is not in the update procedure inside.

    If you need, i can provide more information of course.
    Thank you very much in advance for your help.

    I wish you all Merry Christmas and an happy New Year!

    Regards
    Ernesto

Viewing 6 replies - 1 through 6 (of 6 total)
  • Moderator bcworkz

    (@bcworkz)

    If i try to re-login or to visit my homepage, the browser shows a blank page.

    This usually means there’s a PHP error somewhere. Edit your wp-config.php file so that WP_DEBUG is defined as true. Re-load the blank page. This time there should be error messages telling us what and where the problem is.

    Thread Starter erpico57

    (@erpico57)

    Hy bcworkz,

    thanks a lot for your suggestion.

    I have updated from 4.6.1 to 4.7 and later have changed wp-config.php as you told me.

    The complete result of debugging can you find at http://pastebin.com/8zQmygMW.

    Anyway, there is a new row in this report created after update. The remaining rows contain the same text like by 4.6 version-report.

    The new row is the following one:
    Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 86017 bytes) in /home/astroliv/public_html/wp-includes/pomo/streams.php on line 201

    I will wait on your feedback before do something…
    Thank you very in advance
    Bye
    Ernesto

    This row wasn’t

    Moderator bcworkz

    (@bcworkz)

    That other output are things that should be addressed, especially the Warnings. They would not stop your site from loading though. Warning level errors often indicate related code is not functioning as intended.

    Obviously a Fatal Error is what is crashing your site. pomo/streams.php is used to load translation files into memory. Translation files shouldn’t be so large that loading into memory would be a problem. Do you have any idea what file might be loaded that is so large as to overrun memory? Another possibility is some code is stuck in an infinite loop and the file load just happened to be the one operation that kicked the process over the limit. I’m guessing the latter.

    It’s not unheard of for problems to arise on hosted servers that were no problem on localhost due to differences in server configuration. We need to narrow down the source of the problem. This is normally done by deactivating all plugins and switching to the twentysixteen theme. Reinstating each, one by one, will eventually reveal the problem entity.

    Of course, since you cannot log in, that would be hard to do. We can disable plugins and switch themes through FTP or your hosting account’s file manager. Go to the wp-content folder and rename the plugins and themes folders. Create a new themes folder and copy (not move!) the twentysixteen folder and its contents from the renamed themes to new themes. Depending on your FTP client, copying may be difficult. You might have to download the twentysixteen files and upload back to the new folder. Renaming forces WP to use the only theme in themes and to deactivate all plugins.

    You should be able to login now. Your site will be messed up due the theme change and lack of plugins. Don’t worry, it’s temporary and better than the “White Screen of Death” aka WSOD 😉

    Once you’ve logged in, use FTP to rename the new themes folder, and rename the original folders back to their proper names. In the back end you can now restore your original theme. Reload your page. If your site doesn’t crash, proceed to activating your plugins one by one, most important first. Reload after each one.

    When your site crashes again, you’re going to need to do the whole renaming thing again. Make note of the last activated entity, you don’t want to activate that one again! You should be able to login and restore all of your previous setup except that one entity.

    Take up the site crash issue with the author of that entity, or find another one that works similarly, or do without, or debug the code yourself. Good luck!

    Thread Starter erpico57

    (@erpico57)

    Hi BCWORKZ,

    first, i wish you and all people a good 2017!!!

    I followed your suggestions and i could update successfully to v4.7.
    I should exclude 2 plugin (Child theme configurator and a Facebook widget)
    in order to run updates without crashes.
    The only thing i did, was to add in wp-config.php following line:

    define(‘WP_MEMORY_LIMIT’, ’64M’);
    i had this tip from “https://tutorials.hostucan.com/how-to-increase-php-memory-limit”

    Now the site runs fine but i have rcognized a strange thing:
    if i select “Appearance => Customize, the back-end of WP shows a blank page.
    In the address field is following path:

    http://www.astrolive.ch/wp-admin/customize.php?return=%2Fwp-admin%2F

    Anyway, i can back to the WP-Panel. Other functions run well.

    Have you got an idea what happens?

    Thanks a lot in advance!

    Ernesto

    Thread Starter erpico57

    (@erpico57)

    Hi BCWORKZ,

    related to my last post, I have sets on true “define(‘WP_DEBUG’, false);” and recalled “Appearance => Customize.

    The browser shows following error:

    Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 12288 bytes) in /home/astroliv/public_html/wp-admin/includes/post.php on line 1272

    It seems to be the same error like during the update of the version 4.7
    but every time i get this error, system shows another name of .php .
    I don’t see any logic and i have no idea how to follow/solve this kind of problem.

    Thanks a lot for your help.

    Regards

    Ernesto

    Thread Starter erpico57

    (@erpico57)

    Hi BCWORKZ,

    PROBLEM SOLVED ! System works now perfectly !

    The Host-provider added the file php.ini to my installation and following line in .htaccess:
    SuPHP_ConfigPath /home/astroliv/public_html/php.ini

    In php.ini following line was also added:
    memory_limit = 128M

    I’m afraid to cause this unnecessary engagement.

    Anyway, thanks a lot for your useful support!

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘After 4.7-update, site is lost, no chances to re-login’ is closed to new replies.