Fred Chapman

P.S. Here’s the post with the fix:

https://www.ads-software.com/support/topic/plugin-revision-control-no-way-to-delete-revisions?replies=10

I used the PHP fix (by rayfusci and tff, near the end), and it worked fine with WordPress 3.1.

Cameron,

Thanks for your reply! I had already installed Shadowbox and enabled it in your plugin, but it didn’t solve my problem — the images were still displayed too big. I tried it again just now to be absolutely sure that Shadowbox was enabled — it was, and I’m still having problems.

What should I do?

Fred

P.S. Shadowbox JS also works fine with my images just the way they are.

P.S. I also change the Tag base in the Permalink Settings to “keyword” to provide a consistent user experience on my sites.

Matt, that’s a great question! I’d love to know the answer myself.

I don’t have a plugin for this, but I’m working on the next best thing. I’m building a WordPress solution based on premium photography themes from Graph Paper Press (GPP) and an account with Photoshelter (PS). GPP and PS have WordPress plugins which make it easy to integrate your online photo archive with your blog, and PS provides automatic print fulfillment using a variety of online photo labs.

I’d like to have an independent solution based entirely on WordPress, but that may not yet exist. I’m going to stick with PhotoShelter for now, but I may try to develop a print fulfillment plugin myself in a couple of years!

Fred
[ Signature moderated. ]

Jon,

Thanks for explaining this. I didn’t notice that I had an old version of class-ixr.php. I deleted it and reduced my severe messages by one. ??

What do you think of the idea of allowing users to define their own baseline. In other words, would it be feasible and worthwhile to let users tell the scanner to ignore a particular error in future scans? That way, if something truly malicious does occur, it won’t be buried under a pile of messages which are not cause for concern. I think a feature like that would make the scanner much more valuable.

Fred

Jon,

Thanks for your in-depth reply. Most of the severe messages are from plugins which I recently installed. Only two severe messages are from WordPress core files:

wp-includes/class-ixr.php:249
$value = base64_decode( trim( $this->_currentTagContents ) );

php.ini:982
; error_reporting(0) around the eval().

Is the first one cause for concern? The second one is just a comment, so I don’t know why it’s been flagged.

Thanks,

Fred

Thanks, Johan! I appreciate all your hard work.

Fred

P.S. The second test I mentioned has finally run to completion. It did reset the number of retries in less than the default value of 12 hours, but it took more than the 2 hour time limit I specified. I had only one failed login attempt during this entire time period. Could something else be causing the reset timer to restart?

I’m having exactly the same problem with this plugin — my blog has several categories, but the only categories this plugin lists are All or Uncategorized. I love the idea of the plugin, especially that it provides a user-friendly menu instead of requiring us to insert shortcodes into our pages, but if it doesn’t list all my categories, it’s useless to me.

Here’s a very popular plugin (100,000+ downloads) which has been updated for WordPress 3.1:

https://www.ads-software.com/extend/plugins/list-category-posts/

I’m going to give it a try.

Good luck (to both of us)!

Jon,

I tried Exploit Scanner 1.0, and the missing hashes message is gone now. Thanks for fixing that!

Instead of hundreds of messages, I now get only dozens. There are 13 severe messages, mostly eval messages, some base64_decode messages. Is this normal? I have a lot of security plugins installed and the site seems to be running normally. Should I just use this as a baseline indicator to identify possible future attacks?

Thanks again,

Fred

Jon,

Thanks for your speedy reply! I look forward to the new version of your plugin. Thanks for all your hard work!

Fred

You’re very welcome! I’ll look forward to your next update and post feedback after I try it out.

Thanks for your speedy reply, too! I always appreciate it when developers actively maintain their plugins.

Fred

Like you said, it’s too soon for WordPress to notify me of the updated plugin in my Dashboard, but I was able to delete the old plugin and install the new one with no problems.

I’m happy to report that the update works perfectly on my site! Thanks so much for fixing this so quickly. I’m also happy that I can give your plugin a five star rating.

Thanks again,

Fred

P.S. I think it’s pretty cool that PHP lets you check whether a function exists before you call it. Nice!

Thanks for the plugin! It’s a really handy feature to have, and I’m surprised it’s not already built in to WordPress.