david

My apologies. I didn’t notice that. Thanks for all your effort the past few days to update the plugin. It’s really super, as well as your support.
Thanks.

It WORKS!!!!! I updated my two sites and all is well. Thank you, thank you, thank you. Just terrific support. Regards,
david

I appreciate what you’re doing. This plugin is the only one that gives real login security and I admire that you respond so promptly to support questions. Thank you.
david

KEWL! Awesome. Thanks so much. I rely on this plugin. Really appreciate your devotion to it.

Mark,
Please see my post as of Jan 26, titled “EASY Bypass”. If you see a 67.249… URL in your logs, I was just testing my bug report to see if your fix addressed it. It does not. I was not attempting to hack; once I saw the login screen I stopped and then posted the bug.

The limit is 128. However, I’m not server-literate. I have two duplicate sites on same server: one is production and one is to test new plugins. The test version works fine, but the production version produces the message
Allowed memory size of 268435456 bytes exhausted (tried to allocate 31457280 bytes)
When I click the Clear image cache button. The gallery has only 150 photos, so it’s a puzzle for me. However, I’m having no problems; clearing the cache was primarily just some housekeeping for me.
I do have a question: Do I ever need to clear the cache if I’m not having problems? And what would be symptoms of a Nextgen problem? I’ve been using Nextgen for two years with flawless performance. Thanks for any suggestions.
david

This might just be a timing issue. One one site, after installing the update it seemed that my backups weren’t there, but after doing a backup they all appeared. For my purposes, the issue isn’t serious, but people installing the plugin should check their backups.

Thank you for clarifying. I was hoping that it would delete just the page or post being updated. Now I understand it. Thanks for your help.

WOW! That’s just perfect. Let me play it back to be sure I understand it. I can set the Timeout to anything (e.g., one hour, one day) and uncheck that other box and the cache won’t be deleted ever. That seems (to me) to be an outstanding, but undocumented feature. However, I assume that the cache will be cleared for any updated page or post. Please confirm. Thanks for being so prompt. Please also confirm the proper setting for ‘Timeout’. I’m wondering if it’s best to leave at the ‘Choose one’ setting.
david

Okay, Thanks for your thoughts. I’ll advise if I uncover anything.
david

Yes, it’s the latest: 2.1.1. And the login URL is 15+characters, almost impossible to guess. I’m also using the Wordfence plugin and the Bulletproof Security plugin and I’m very pleased with those two, plus your rename plugin. I was just wondering if there might be some back door technique that might be exposed that I need to lock up. Any suggestions are welcome. Thanks. I’m not reporting a “problem” with the plugin; just looking for ideas. And I’ll close the topic after your response. Thanks, much.

Thank you!. Your code worked perfectly on all browser platforms.
regards,
david

Never mind. I found a workable solution. Not perfect, but it works. There remains an issue on the width of the content field, but I’m content with the changes made.

I found the answer. Just did a search on Wordfence forum. I should have posted there.

There is an option in WordPress to do that. My guess is the hacker is then changing IP addresses. My solution to the problem was to create a list of blocked ID addressses in the .htaccess file.