Support Forum

Problem with appsotrophe in plugin name for activation

UN
Unknown
Member
Feb 12, 2012 · 3:22 pm · Edited

I tried earlier to day to activate the Who’s Online plugin. But, when I clicked activate I got a “page not found” error from WordPress (ver 3.3.1) I’m running the pre-release ver of simple-press and the plugin from the pre-release page.

I found that if I edited the url in the “page not found” location bar, to take out the apostrophe, and hit reload, then the plugin was properly activated.

The only reason I went back to try this again is because I just tried to activate a plugin from the WordPress repository called: Peter’s Login Redirect. Had the same problem with trying to activate that plugin. Noticed the apostrophe and put 2 and 2 together.

So, I don’t know if this is WP 3.3.1 issue, or just a plugin issue, or just bad practice to have an apostrophe in the plugin name…

Make what you will of it, but I would avoid using apostrophes 🙂

5 Answers

New Answer
MP Mr Papa
Mr Papa
Member
Member since Dec 2006
19,448 posts
Feb 12, 2012 · 4:15 pm

hmmm… cannot duplicate that… you did the activation from within the sp plugins panel and not wp, right?

and no other reports with many, many downloads of that particular sp plugin…

UN
Unknown
Member
Feb 14, 2012 · 12:44 pm

I activated the plugin through the SP plugin admin panel.

Glad to hear you were not able to repeat the problem. Maybe there was just something wacky with my browser during those activations.

YS Yellow Swordfish
Yellow Swordfish
Member
Member since Nov 2008
16,437 posts
Feb 14, 2012 · 2:29 pm

This has been a totally unique report actually. So far I don’t think we have any ideas why it happened to you either.
Anyone?

WA Waynem
Waynem
Member
Member since Feb 2012
4 posts
Mar 7, 2012 · 9:35 am

Update:

I think I figured out what the problem was.

On all of my WordPress installations I use the Bulletproof Security plugin – which I highly recommend to anyone who is serious about WP site security. It’s fairly easy to setup and works great.

Anyhow… this plugin makes some pretty extensive changes to your WP root .htaccess file. After setting up the BPS plugin it is recommended that you lock down the .htaccess file permissions to 404. This is a good idea. However, it will create a problem whenever you do things that require edits to your .htaccess file. For instance, when you might want to update (or force update) your permalink structure. Fortunately, The BPS plugin has a feature to lock/unlock your .htaccess file for just this kind of circumstance.

To make a long story short: My permalinks needed to be force updated (that means to choose a different permalink structure, save that choice, and then switch back to the original structure, and save that). Doing that without unlocking the .htaccess file is pointless – as nothing gets updated. So, once I figured out that I need to unlock it, make my changes, and lock it back up, all is well.

Since updating my permalink structure all updates, and fresh installs of SP and WP plugins have gone off without a hitch.

I hope that this post might help others who may have had an issue like this.

And again – I highly recommend the BPS plugin:
http://wordpress.org/extend/plugins/bulletproof-security/

YS Yellow Swordfish
Yellow Swordfish
Member
Member since Nov 2008
16,437 posts
Mar 7, 2012 · 9:59 am

Wow! Useful information,. Thanks for sharing it and updating the thread. We are grateful for that. And glad the issue is resolved nicely and the puzzle solved.