[Plugin: All in One SEO Pack] After Upgrade, No Meta Descriptions autogenerated

i also get the problem after i upgrade to the newest version i miss all the setting in the admin setting. how to slove this problem.

now my website didn’t autogenerated anything like meta, title.

https://freakfinder.net

Same here, meta-description appears on the startpage, but not in the articles or pages.

Thank you everyone for reporting the bug. The description auto generator issue should be fixed in version 1.6.1 which has now been released.

I’m a little upset. Not because of the Amazon Wishlist or the big donation button that’s new and on pole position in your plugin (we all need to make money somehow) but because of upgrade issues just like these. Also, some settings change when upgrading, like the “exclude tag from index”, and the database fix does not bring all old settings back.

If one runs a big blog with your plugin, such “upgrades” may severely damage ones site performance and earnings: If title tag and description change from one second to the other in your whole blog, you will loose reputation in SERPS – the engines are very sensitive to such changes.

All in all I’d like to ask you to develop this good plugin and release upgrades with more caution – thanks!

thebuckmaker,
If you’d like to report a bug, feel free to post at https://semperfiwebdesign.com/forum/ and provide more information about exactly what settings you think changed during the upgrade.

Still not showing Description for Japanese characters posts

I agree with thebuckmaker, extremely dangerous to have your aioseo settings get erased when you upgrade. Many folks will not notice these changes as they are unprecedented and there is no warning. Also unprecedented to have the “plugin status: abled / enabled” setting….again, with no warning. Not sure how this is useful to the end user as the WP norm is to simply enable or disable plugins as a whole. These changes are going to get a lot of folks upset and with good reason. Also odd with this upgrade are the ominous upgrade database warnings … kind of scary.

Both the empty fields and the last mentioned warning made me downgrade again. Might try again some other day when I have time to study it more carefully.
Dear hallsofmontezuma, you have developed a very nice plugin. I hope these special steps won’t scare people away – maybe to other SEO plugins.
Keep up your good work – and please try to avoid scary database changes if possible.
Kjetil

@diesel12
No settings have been erased. You click 1/2 buttons, and your settings are migrated to the new format. If you don’t click the button(s), they stay in the old format, which an older version (pre 1.6) will read.
If the “warnings” are ominous, it’s because I didn’t word them well enough. Pretend I worded it as “migrate data,” “import SEO settings,” or whatever would make you feel better than “update database”.
@kjetilgf
Approximately 55,000 people have downloaded this version of the plugin in the past 2.5 days, almost all of which don’t share your view, and had no problems. Requiring you to enable a plugin on the settings page isn’t unheard of, try WP Super Cache, one of the other most popular plugins.
My intention was to give the user the control, and also to give them one last opportunity to back up their database (just in case), by providing buttons. I could of course just had the data migration script run without asking the user to click a button or two, but people would have complained about that. So I guess I just can’t win.

@halls: little thicker skin please, we’re just trying to give you friendly user feedback. ??

I personally found the upgrade confusing, I can confirm that in fact my user settings were reset when I upgraded and the plugin turned itself off even after upgrading db as advised by the plugin. Generally speaking, I think that turning off the plugin on upgrade would generally be considered bad practice, especially without a warning that it is doing so. Maybe there is a reason for doing so that I’m not getting.

I have never had a plugin ask to upgrade the db, so it is, from my experience, out of the ordinary…..

I personally found the upgrade confusing

I’m sorry you found one or two buttons to be clicked, with a line above to click it confusing. A few dozen beta testers over the past month had no problems. I specifically asked them if it was obvious what to do. They all felt it was, along with most of the other 55k or so people who’ve upgraded so far the past couple days. If you think that there is a less confusing way that it could be worded in the plugin, let me know and I will release 1.8.2 with that change immediately.

especially without a warning that it is doing so

You get one. It’s in red at the top of every page in wp-admin.

I have never had a plugin ask to upgrade the db

Now you have. There are plenty of others as well that change the structure of the data that they store.

Again, just trying to provide user feedback that might help in some way. Instead of being patronizing, just tell us if you would prefer us to not give such feedback. ??

This is what I see when I upgrade, this is specifically from one our MU installs, so maybe there is a MU conflict… also please note that this is prior to DB component of the upgrade and all settings have been completely erased.

https://i8.photobucket.com/albums/a22/tracedef/aio.png

Again, just trying to provide user feedback that might help in some way. Instead of being patronizing, just tell us if you would prefer us to not give such feedback. ??

I’m not patronizing. I am very serious. I specifically asked my beta testers if they felt it was obvious what to do for this upgrade, and they all felt that the button(s) with the sentence above was sufficient. The beta testers ranged from very technical to not technical at all. If you feel that there is a better way it could be worded in the plugin, let me know and I really will release 1.8.2 with that change immediately.

This is what I see when I upgrade, this is specifically from one our MU installs, so maybe there is a MU conflict… also please note that this is prior to DB component of the upgrade and all settings have been completely erased.
https://i8.photobucket.com/albums/a22/tracedef/aio.png

Your data hasn’t been erased. It’s just in the pre-1.8.x format, only readable by pre-1.8.x versions. Once you click the button, it will be in the 1.8.x+ format, only readable by 1.8.x versions. Take a look at https://semperfiwebdesign.com/blog/all-in-one-seo-pack-must-be-configured/ for more explanation if this is still unclear.

As for whether the migration script will work on WPMU, I don’t know. At least two of my beta testers that I know of tested the beta version of the plugin on WPMU with no problems, but I personally haven’t tested that aspect on WPMU. In theory, if each site admin clicks the button(s) on their own AIOSEOP options page, it should work for each of them.

@hallsofmontezuma: A unexperienced user might …

• not notice the new activated/deactivated button thats deactivated by default
• not notice that the check/uncheck settings aren’t back to the user settings even after the manual database upgrade

It is very, very likely that many users of your plugin now have changed or default WP site titles and / or descriptions and don’t even realize that. This WILL hurt their SE rankings.

BTW Be sure that I will post issues like these here at www.remarpro.com as what you did is really dangerous to those who already have some SE traffic and rely on your plugin.

I wanted to do other things today than looking for another SEO plugin, but regarding this discussion and the style of your posts & feedback (+ all the new donation stuff and checks), it might be a good idea for the future.

not notice the new activated/deactivated button thats deactivated by default
not notice that the check/uncheck settings aren’t back to the user settings even after the manual database upgrade

What would you recommend as a better method of notifying the user other than a big red notice at the top of every wp-admin page to enable the plugin, and two notice(s) on the options page (that they obviously must go to) to update their database? Most people don’t seem to have a problem with it.

I’m not sure what you mean by my “style of posts & feedback”. For the very few people having issues, I’ve tried to explain here in detail what happens, asked for specifics of perceived bugs, and have even said that if you suggest a better way of informing the user of the required data migration, I’ll release an immediate update with the change. At this point, thebuckmaker, I’m really not sure what you want from me.

I’m sorry you don’t like the donation links. I really don’t know how to respond to that.