dlherrin
Forum Replies Created
-
Deactivating and reactivating the plugin successfully restores lost functionality. Thanks for the advice!
I understand what you would like me to do Peter, however, in order to ensure that ‘Delete Login Security tables and data on deactivation’ in Wordfence > Login Security > Settings is not selected I would have to be able to visit my Login Security Settings page. It is not on the menu and when I try to visit that page via settings I get the message “Sorry, you are not allowed to access this page.”
I see the other settings you ask for “Delete Wordfence tables and data on deactivation” in Wordfence” under the General Wordfence Options settings, and it is turned off.
This seems to be a Catch 22. I can’t ensure my Login Security settings won’t be deleted unless I can visit the page that I cannot get to…
How about if I detach this site from the template? Might that restore access to this page?
Hello Peter. Thanks for responding to my query. I have added and enabled the ‘Health Check & Troubleshooting’ plugin. Running only it and Wordfence with the default theme yields no difference at all in the availability of the Login Security page.
https://snipboard.io/W1yim8.jpg <- Shows I have disabled all plugins except WF
https://snipboard.io/jVJBxt.jpg <- Login Security does not appear in the left menu
https://snipboard.io/hCc2F4.jpg <- What happens when I press ‘Login Security Options’ button
I have sent a diagnostic report as requested.
Thanks!
DaveForum: Themes and Templates
In reply to: [Tortuga] Daily PHP error message logged in Tortuga directoryThank you. I have three WordPress websites on my hosting service that use ThemeZee themes. Two of them are protected by the Sucuri security suite, and those two have identical errors at identical times each day. The third does not. I assume that the error is generated by daily security scanning activity.
The above additon to functions.php did not work, however, the following code added to the end of wp-config.php did the trick -Dave
* * *
From: Robyn Davies <[email protected]>
Subject: Re: [#150605] Site Help Request
Date: January 28, 2020 at 9:13:27 AM EST
To: [email protected]Hi Dave,
I’ve had a look into this for you and it seems that the possible workaround that we previously suggested won’t be suitable in this instance.
Instead, I have added the following code to the end of the clone’s wp-config.php file:
global $advanced_post_cache_object;
if ( is_object($advanced_post_cache_object) ) {
$advanced_post_cache_object->flush_cache();
}This has resolved the issue there on my end, so I would recommend double checking on your end and then applying the same thing to the live site for now.
If you have any questions, just let me know 🙂
Kind Regards,
Robyn Davies
Pressable Customer Success- This reply was modified 6 years, 4 months ago by dlherrin.
FYI, Here is a possible solution offered by our web hosting provider…
From: Jess Nunez <[email protected]>
Subject: Re: [#150605] Site Help Request
Date: January 27, 2020 at 7:08:10 PM EST
To: [email protected]
Reply-To: Jess Nunez <[email protected]>Hi Dave,
I wanted to reach back out to you about this issue. It is possible to disable object caching for specific post types. As the newer version of the plugin uses the link_library_links post type, I would recommend that you try bypassing the cache for that post type by adding the following to the end of your theme’s functions.php file:
add_filter( ‘advanced_post_cache_skip_for_post_type’, ‘apc_exempted_cpts’, 10,2);
function apc_exempted_pts($return_me,$post_type) {
$exempted = array(‘link_library_links’);
if ( in_array($post_type,$exempted) ) {
return true;
}
return $return_me;
}
However I would suggest that you clone your website, and perform this update and test on the clone first 🙂 If you need assistance with that please let us know. We will be updating our public Knowledge Base with this information in the coming days!Best,
Jess Nunez
Pressable Customer SuccessHi. Thanks for writing back. Pressable has only basic controls on their back-end website. You can specify whether your site is in “production” or “development” mode — the difference being that in production mode you are using their Content Delivery Network (CDN) and server caching. Our site is in development mode using PHP 7.2. They also have two buttons for purging the CDN and Flushing the Object Cache, which is how I learned that the problem was related to the cache.
Looking at their KB they have an article about object caching at https://kb.pressable.com/article/object-caching-with-memcached-at-pressable/
Dave
