wpsecuritylock

Same here, eventually the site times out after spinning for awhile trying to load.

Is this plugin compatible with WP 5.6?

• This reply was modified 4 years, 1 month ago by wpsecuritylock. Reason: forgot to check notify me

Will there be an update on this plugin to work on PHP 7.2+?

Details say tested up to WordPress 4.4.9 and has been over a 1 year since an update.

We have upgraded to WP 4.7.4 and PHP 7. Can you tell me when you are going to push out an update to work with WordPress 4.7.x and PHP 7?

I have the same issue after converting my site from http to https. Would really like to hear a solution.

I have the same issue on a site. It has been two months since nickterry posted above.

Any resolution to this? We are using WordPress 4.0.

Here is the error code:

Strict Standards: Declaration of EPS_Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output, $object, $depth = 0, $args = Array, $current_object_id = 0) in /home/mydomain.com/public_html/wp-content/plugins/eps-301-redirects/class.drop-down-pages.php on line 66

FYI: I just clicked the update button on the Ultimate Category Excluder settings page and the warning goes away, but must be clicked first.

I have the same issue on my site.

My pretty links are set to nofollow and 301 redirects. Even if the pretty links are not linked directly on any content (page/post) they are still being indexed on Google.

Blair any idea why this is happening and what can be done about it?

Same here. I just upgraded from 1.4.10 to 1.4.11 and the “Save Settings” button is gone on Yoast WordPress SEO: Titles & Metas.

I only have admin.

HostGator dedicated, error_logs via cPanel > File Manager, located inside public_html directory.

Anyone know how to fix the cron in WordPress 3.5? Scheduled posts are still getting missed.

Another scheduled post failed to publish today. I have checked the error_logs and cannot find the culprit.

Any ideas how to get cron’s working in WordPress 3.5?

It was working fine in version 3.4.2 so calling my host probably would not help since it stopped working after upgrading to 3.5.

Crons are not running for scheduled posts in WordPress 3.5 either. Tried it on two updated sites with no luck.

Found this error so far:

WordPress database error MySQL server has gone away for query SELECT option_value FROM wp_options WHERE option_name = ‘_transient_doing_cron’ LIMIT 1 made by _get_cron_lock

Any ideas?