Jim McLaughlin

Very helpful, and I wish I’d done that. I still haven’t figured out how to fix my browser, which is somehow blocking access to the site editor when not in debug mode. (Removing cookies doesn’t help. A never-ending saga.)

But many thanks, @wfpeter!

• This reply was modified 1 year, 11 months ago by Jim McLaughlin.

I set up the debug code in wp-config, and suddenly the problem goes away and there are NO errors in the log in wp-content/debug.log. Very strange behavior. There isn’t even a debug.log file. I think I’ll reinstall WP and see what happens.

Update: Doing the reinstall, and removing the debug code, returned to the same error. Possibly a theme error?

Update2: Viewing the site and admin page on my phone, I get no error and I can reach the site editor with no difficulty. Obviously, a browser cache issue now. So frustrating. Viewing on another user/browser instance on the same computer doesn’t show the problem, either. Crazy Chrome.

• This reply was modified 1 year, 11 months ago by Jim McLaughlin.
• This reply was modified 1 year, 11 months ago by Jim McLaughlin.
• This reply was modified 1 year, 11 months ago by Jim McLaughlin.

[Update: no errors now, though I can’t access site-editor.php for some reason.]

This is definitely a Wordfence migration issue. This error shows up often. Sorry for the bother.

For folks who got this far, when you deactivate WF, you will be walked through a series of steps that will remove WF properly, allowing for the director migration to happen. If I get other errors, I’ll update this, but assume that a proper deactivation of WF before migrating the directory works as WP says it does (which is quite easy, otherwise).

[Update: no errors now, though I can’t access site-editor.php for some reason.]

This is definitely a Wordfence migration issue. This error shows up often. Sorry for the bother.

For folks who got this far, when you deactivate WF, you will be walked through a series of steps that will remove WF properly, allowing for the director migration to happen. If I get other errors, I’ll update this, but assume that a proper deactivation of WF before migrating the directory works as WP says it does (which is quite easy, otherwise).

• This reply was modified 1 year, 11 months ago by Jim McLaughlin.

A bit of progress (and I uninstalled Wordfence before seeing this). Now the error is:

Warning: Unknown: failed to open stream: No such file or directory in Unknown on line 0

Fatal error: Unknown: Failed opening required ‘/home/corps/public_html/wp/wordfence-waf.php’ (include_path=’.:/opt/cpanel/ea-php74/root/usr/share/pear’) in?Unknown?on line?0

I got this after moving files to the root folder. This is a link to the original folder (wp) folder, but I don’t know where the link is being referenced. Hunting…

I saw a couple of firewall rules getting hit, but once I disabled them (for now), I still get the 500.

In /var/log/apache2/error_log, I don’t see anything pointing to this site, only a bunch of PHP eact-server.ini syntax errors (we’re running an old version of PHP on the server, but the site is using PHP 7.4).

I’m not much of an admin, so if there is a different error log I should be checking, I welcome the help.

Thanks, much.

• This reply was modified 1 year, 11 months ago by Jim McLaughlin.

I get stuck here: “Login to Wordfence.com…” It’s asking for a 2FA authentication. I need that turned off or reset somehow.

Thanks for sharing!

I appreciate the patience and guidance!

Appreciate all the help. Attempting this is a private browser and deactivating WordFence did not resolve the issue. I get no log errors within the WP file structure. If there is another place to look for an error description, I welcome the suggestions.

I get this error on all of the WP sites on this server, so I’m thinking there is some other general limit/restriction being hit.

Thanks. I appreciate the response. I’m doing as you do, but it shows up as a caption. I’ll keep trying!

I learned something.

As noted,too, “If you don’t see the Post Format module, then you are likely using a theme that does not use post formats.”

TT3 is pretty simple. I’m not surprised.

Good hunting.

Not a fix, but editing the HTML to wrap the image with a URL is a workaround. Here’s a reminder (keep everything but the square bracketed stuff):

This approach seems to run counter to the concept of a template, whereby a page layout (template) is saved and can be used/applied to other pages. If one can’t select a template in a page settings, it would seem to be a somewhat useless feature.