Keith P. Graham

I have not tested it with a cache.

The plugin only works when it detects a 404 page not found error. If you can type in a url that does not exist and you get a standard 404 page then the plugin will probably work on your site.

thanks,
Keith

Hey, it was already fixed.
There used to be a method called mysql_escape. I wrote my own version when I converted over to mysqli and named it mysql_escape_mimic. Your compatibility tester was lazy and just looked for the mysql_ string in the code.
I renamed the function so that the tester will ignore it.
You can install the old version safely. I am updating the WordPress version to have the renamed function so it should show up in your updates as soon as I test it.

Keith

It’s time. I will get to it right away.

Keith

It appears that some of images are “background” images and the plugin does not block background images. When you right click, the javascript checks what is happening and sees that you clicked on a DIV so it gives up.

It also may be that you have another plugin running that is hiding images on “mouseover” events. I know that my plugin will check to see if there is already an onclick or or other event defined and then it will ignore the image.

My plugin will only work on images that have no events defined. and assumes that if you define an onclick or onmouseover event for an image that you know what you are doing.

My plugin doesn’t show anything. All it does is disable the context menu on images.
If you are seeing this message then it must be coming from another plugin.

Keith P. Graham

The plugin only works on HTML img tags. It won’t work on css style background images. I have not been able to find a way to stop the clicks, mainly because it would stop all clicks, including links. Right lick is useful and and I can’t ban it entirely.

So be careful what you use as a background image. Put all the images that you want to protect in an img tag and, if you can, put them behind a clear div tag so that the div gets the clicks and not the image.

When an image gets to the browser and displays it is always available to steal. It is just a matter of how much work someone wants to put in. The plugin will stop the casual user, but a determined thief will be able to get around it.

Thanks,

Keith

Jetpack is the source of the problem. Jetpack uses a huge amount or memory. I checked and the Permalink Finder only loads when there is a 404. I doubt if it has anything to do with this.

Keith

I tried to use your site to see if permalink finder is working, but it looks like it is not active so I could not check it in action.
Permalink finder does not use very much memory, so I am guessing that you may have a bunch of memory hog programs and permalink finder is just large enough to push things over the edge.
Please try to uninstall the plugin and then reinstall. Sometimes the plugins break while being installed. This is a frequent problem that I have with the WordPress plugin repository.
My other advice is probably not very good. Try getting rid of all the plugins that maybe aren’t doing too much. You only need one anti-spam program so use a good one like the “Astounding Spam” plugin that uses very little memory. In my experience most of JetPack is not very useful so if you want to keep it, disable all the stuff in it that you don’t use.
Permalink finder is an ancient plugin that changes slowly. When I next update it I will see if there is something I can do to delay loading of modules until they are needed to put less of a strain on system memory.
Keith

Please give me the URL of your blog so that I might look at the links to see what is different about them.

Keith

• This reply was modified 5 years, 10 months ago by Keith P. Graham.

I will look into making a .po file.

thanks,

Keith

Hi,

The program makes very little money. I do not speak French, and I cannot afford to pay someone to translate it to French.

I am sorry.

Keith

I was searching PHP.net for the workaround, and forgot about the esc_sql function even though I have used it in other plugins.

I really need to rewrite the code to use prepared statements. That would make the code more secure and easier to read. I may need to get to it someday.

It is hard to justify spending the time on this plugin since it mostly works and does not generate income. There is also a clone of my code in the repository by another author that does the same thing.

Keith

I uploaded a fix this morning. It is not pretty. I test for the existence of the functions before executing them. PHP version and configuration makes a difference in how the plugin works, I need a good way to account for all of these including future changes. I need to support PHP 4 and some ancient versions of WP as well as the latest greatest.
I have 5 or 6 plugins that I haven’t updated in many years that use the old sql cleaning techniques. Luckily, everyone using them must be living back in 2008.
Optimistically I am marking this as resolved.

OK, I found it. I will fix it and upload a new version as soon as I can.

Keith

It had already been changed in a previous version.

I will keep looking. I am going to release a new version, just to make sure that everyone gets the code, since the plugin, in your case, did not update.

Keith