tark94

Hi,

Here’s a copy of the migration log: https://pastebin.com/5qQ5DQ0Y

Thanks

@maneshtimilsina Hey sorry I think I misidentified the plugin. Actually there’s a plugin with a very similar name to yours – different developer, nothing to do with yours ??

Yes wp-content is 755 and no, the problem never occurred with other plugins (incl. Cache Enabler) in the past.

Your question about the server user prompted me to get in touch with my hosting which explained they did correct the permissions of the user.

Version 1.8.4 is what I’m trying to upgrade to, and setting wp-content/plugins to 755 was the first thing I tried.

It appears they’ve moved the ‘Convert to regular block’ feature to a new at the top of the post. You have to hover the mouse over an icon that looks like a square (in that menu) to access the feature.

The ‘Convert to regular’ block feature used to appear but no longer. So I guess this lack of functionality is only confined to me.

In order to avoid theme updates erasing the filter code for disabling Yoast schema, is it best to create a custom plugin for this code?

• This reply was modified 3 years, 3 months ago by tark94.

@wfadam please disregard the last request – I found a way on WF to unblock the user.

Hi @wfadam, today WF has decided to block a user, despite me having whitelisted their IP address. I also updated the list on WF of Ezoic’s IP numbers in case Ezoic had updated one of their IPs, somehow throwing WF out of whack.

When I look on WF Live Traffic, I can see WF returning a 503 for the user. Sadly, the only button options are “block IP,” “run whois,” and “see recent traffic.”

It’s a pity there’s no button “allow access” to just override WF’s firewall and grant someone access.

• This reply was modified 3 years, 9 months ago by tark94.
• This reply was modified 3 years, 9 months ago by tark94.

Thanks @wfadam!

@wfadam it seems one of the scripts is causing problems with WordFence. Could you confirm this?

https://prnt.sc/xfahyw

__ez.queue.addFile('/tardisrocinante/css_onload.js', '/tardisrocinante/css_onload.js?gcb=9&cb=1', false, [], true, false, true, false);

@wfadam I can definitely confirm that WordFence still throws up that 503 error whenever I try to log out of my WP account.

Thanks @wfadam, yesterday I purged both the CloudFlare and Ezoic caches.

I have as well a plugin ‘Cache Enabler’ and I cleared that as well. As far as caching plugins are concerned, that’s the only such plugin I use.

Are there any other areas I need to look at?

Hi @wfadam, the report was sent! Thanks

I can assure you @wfadam that I reactivated the WF plugin with default settings a few hours ago and have not touched any settings having to do with blocking.

Just now I logged in to the site in an incognito browser. Everything seemed fine, then I logged out and in doing so got a 503 error from WordFence (“Your access to this site has been temporarily limited by the site owner”).

I went into another browser, logged back in, and checked the WF / Tools / Live Traffic as you described. The 503 error or event is not there.

• This reply was modified 3 years, 10 months ago by tark94.