Bryan Hadaway

Hense developer version on both accounts.

Unfortunately, if someone wasn’t experienced enough to NOT upload an admin folder to their root where there already is an admin folder in there it’s safe to say that they have no idea what they’re doing and are going to screw something up inevitably anyways.

Since I agree with your points ultimately, I suppose that my idea would be to one day get the developer version. Could I post that in the ideas forum without it getting deleted?

Thanks, Bryan

I’m sure there is a number of things you could do.

But, the bottom line is you can’t use Theme My Login in maintenance mode nor should you.

Like I said, in retrospect… it doesn’t make any sense and there’s an obvious conflict.

Thanks, Bryan

Okay, problem solved… we need to delete out Theme My Login manually via FTP. Reinstall at a later time when maintenance mode is not needed.

Kind of dumb and obvious in retrospect, but we are only human after all ;).

Thanks, Bryan

This just happened to me too…

Let me ask, did you install the Theme My Login plugin around the time of this error?

Thanks, Bryan

I went ahead and started from scratch again, no errors now.

Likely an encoding problem, but I have no idea and there’s really no rhyme or reason, who knows. Sometimes it’s just like that.

Thanks, Bryan

Using either simply changes the character which is throwing the error.

Whether : ; { or anything else coming off of 'comment')

Very bizarre.

Thanks, Bryan

Please see here:

https://www.bryanhadaway.com/super-simple-dynamic-canonical-link-code/

This plugin is not recommended for newer versions of WordPress, it’s primary use is for those versions of WordPress that do not have canonical support by default.

And if you were to use it with new versions of WordPress you would want to disable the default canonical function.

Please re-review the plugin with the correct understanding, also if you’d like some one on one help with your canonical link setup, feel free to post on my blog.

Thanks, Bryan

Here’s one:

“xxx.jpg” has failed to upload due to an error
Unable to create directory xxx. Is its parent directory writable by the server?“xxx.jpg” has failed to upload due to an error
Unable to create directory xxx. Is its parent directory writable by the server?

Another problem is that the cforms plugin is not working.

The first error there are dozens and dozens of threads for, but the situations and solutions don’t apply. After looking into the cforms issue it appears to be permissions related as well.

So obviously, migrating everything messed up permissions. I remember with old WordPress setups you needed to manually edit permissions, it seems with new ones it automatically sets them.

Since the folders all have the right permissions, perhaps it is a WordPress file or two that handle actions/functions that may need to have permissions corrected?

Also, I’ve migrated WordPress setups in the past without this issue, so that could point to something in WordPress 3.X.X.

Thanks, Bryan

Patience is a virtue I do not possess, it worked fine.

I just needed to hold my horses.

Another Newbie question for my first update to my first plugin.

I’ve already updated and uploaded it, changed the appropriate info, what do I want to do to notify those who are already using it of the new update?

For instance, when you see the notifications in the WordPress admin that some of your plugins have updates, how to notify that?

Perhaps it’s automatic as soon as WordPress notices the version number change, it’s been about 2 hours now and it’s updated in the directory, but I’m not getting the notice in the admin.

Thanks, Bryan

Thank you very much.