Theme related wsod in backend

  • Resolved rhagius

    (@rhagius)


    3 years ago

    after trying out all typical solutions for wordpress wsods i am at my wit’s end.

    I migrated my website from wordpress.com to a self-hosted solution using all-in-one-wp-migration, which looked to work fine, until a coworker wanted to use the backend and got wsod. After going through all the suggestions for fixing wsods and a few of my own, namely:

    checking every single plugin used
    checking memory (980m should be enough?)
    deleting and reinstating all saved accounts
    scrubbing the database off of old wordpress.com entries or deprecated urls
    running debug mode and not getting any logs from the wsod

    i of course landed on my self made theme as the issue. I went over the functions.php file to remove and clean up all custom additions that are not necessary for functionality. i used a theme check plugin to help me weed out most of the issues that come from being a beginner at this, but nothing looks to be related at all to backend.

    Especially irritating is the part where it works fine for me while using my pc, but any other device, like smartphone, tablet or other pcs can’t seem to get into the wp-admin version of the site while my theme is activated.

    Any input would be welcome, please help!

    P.S.: while the theme is active, backend functionalities like searching for new plugins or changing settings seem to not work right or lead to wsod even for me.

    The page I need help with: [log in to see the link]

Viewing 8 replies - 1 through 8 (of 8 total)
  • Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    Errors like this are logged. Check the error log on your server. If you can’t find the log, please contact your host.

    Meantime, enable wp_debug and wp_debug_log and after an error, look at wp-content/debug.log to see if anything gets logged there. https://www.ads-software.com/support/article/debugging-in-wordpress/

    Thread Starter rhagius

    (@rhagius)

    thanks for the reply, my server error-log does not show anything when this occurs, same with the debug log

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    hmmm… Did you set all three debug defines to true?

    Thread Starter rhagius

    (@rhagius)

    oh, i missed one, i only had wp_debug and wp_debug_log seen mentioned in a wsod-guide!

    Hope that helps clarify the situation, will report back!

    Thread Starter rhagius

    (@rhagius)

    Nothing showing up, still.

    Thread Starter rhagius

    (@rhagius)

    i think i managed to fix it: while guides mention empty space at the end of the functions.php file to be able to cause wsod, i did not expect EVERY single empty line within functions.php to trigger it, no matter the position.

    i hope anyone in a similar position will find this useful.
    thanks again for trying to help me out here!

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    If the empty lines are not within a <?php and ?> pair, then they’re output as HTML

    Thread Starter rhagius

    (@rhagius)

    i had multiple pairs of <?php and ?>, for visibility i separated them by an empty line. this worked without trouble on the older wp.com site, so i did not even think that it might be the issue.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Theme related wsod in backend’ is closed to new replies.

Tags