I just upgraded to your newest version 1.6 but no Meta Descriptions autogenerated (!!)
I just upgraded to your newest version 1.6 but 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.
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 http://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.
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.
http://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 http://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 ...
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 wordpress.org 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.
All my meta data seems to be gone...
My "All SEO Pack" Title, Description, and Keywords are all still there... but they are not showing up in Custom Fields anymore.
On Facebook when I linked to articles on my site it used to include the description I put in as well as the picture... now it doesn't even show up...
Please help :(
@halls: Thanks for your feedback and taking time to explain things. Seems much less scary now. (Me: Quite experienced, no expert)
- There is no better way to warn people than using your red text. But picking your words more carefully would be fine. It sent me away.
- (De)active buttons are present with some plugins (like in Maintenance mode) but you might leave it checked by default. Having it off by default put up an extra warning sign to me.
- Updating the database is rare but (as I understand) sometimes necessary with complex plugins (like with major upgrades for Simple:Press forum - a great forum plugin, by the way)
- Lots of downloads and missing feedback from users don't reflect the eventual problems out there. My impression is that people rarely give feedback (donations might be the on action even less common...)
I still wonder
if it really is required to backup the database before upgrading your plugin. I understand that the database is altered, but is there any risk involved? If so, you might add a link to superb plugins like DB Manager or DB Backup. Just a thought.
By the way, it is fully possible to guard oneselves from rewriting all the inputs in this plugin. Open the settings panel in a new browser window before deactivating the plugin. With the new version activated, you have all the settings there for copy - paste (IF the settings in the new version are erased). Second best, but should work(?)
Keep up your good work - and don't be offended by Mr Diesel and others. After all we (the lot) depend on the work work from you and other good guys.
Kjetil
kjetilgf,
Thank you for your reply.
But picking your words more carefully would be fine
I've said several times that if someone recommends better wording, that I will release an update with that wording.
De)active buttons are present with some plugins (like in Maintenance mode) but you might leave it checked by default.
I know it's annoying, but there are several reasons why it's best that way. I gave a lot of thought to it before making the decision. Maintenance mode, WP Super Cache, etc do it as well.
Updating the database is rare but (as I understand) sometimes necessary with complex plugins (like with major upgrades for Simple:Press forum - a great forum plugin, by the way)
SimplePress (great forum plugin), CForms, WordPress, various other WordPress plugins and also many other applications (SugarCRM, Drupal, etc) will require changes to the database structure from time to time on an upgrade. It was necessary. I could have just had the script run automatically, but just like when you upgrade WordPress, I gave users a button (or two) to click.
Lots of downloads and missing feedback from users don't reflect the eventual problems out there. My impression is that people rarely give feedback (donations might be the on action even less common...)
I don't understand what you're saying here.
I still wonder if it really is required to backup the database before upgrading your plugin.
Personally, I back up my databases before any major change, and before any upgrade of a plugin. Production sites *should* always have a development environment where new plugin upgrades, WordPress upgrades, theme modifications, etc are tested before being pushed to the live site.
I understand that the database is altered, but is there any risk involved?
There is always some risk with upgrading any plugin, or making any change to your site, however I spent many many hours working on this upgrade, and had several dozen beta testers.
By the way, it is fully possible to guard oneselves from rewriting
This was an issue that affected a minority of users, and has already been corrected in an updated version. However, if you're like me, you're very paranoid about these things. I am absolutely adamant about data retention, so backups, etc are always recommended. Again, I backup my database before doing anything. It only takes a few seconds to do a database dump, and can save you a tremendous amount of time and headaches.
Thank you for your sentiments Kjetil. Of the 10s of thousands of users of All in One SEO Pack, there will always be a few complaining. These are just a vocal minority. Just look at all the threads in these forums of people bashing WordPress itself.
Just so you know, I've started All in One SEO Pack support forums at http://semperfiwebdesign.com/forum/ and won't be visiting these forums often, so if you have any more comments, suggestions, etc, I'd recommend posting there where I'll see it and be able to reply quickly.
@halls
It was an unusual (if not scary) upgrade routine with the advent of version 1.6. But as you said, upgrades like these are necessary from time to time so that the script can evolve. I'm ok with that and got past those buttons without a problem. I needed an upgrade from WordPress 2.5 to 2.8 and chose to go through the whole process locally (on my machine). So when I saw the warning and all, it didn't feel so terrifying.
But I guess a few people updating their production site with the "upgrade automatically" button got surprised. Anyway, it's not your fault that they chose to do that without backing up their database.
I got a problem on the 1.6.4 upgrade, a problem I didn't have with any of the previous versions. All the fields in AioSEO's admin page were gone and reset to default after the upgrade. Lucky me I keep a development version of the site so it was just a matter of copying and pasting them back into the fields. All back to normal here, but maybe something to be controlled... :P
Cheers, it is the greatest plugin in my opinion!
Thanks for clearing things up.
About my remark some days ago:
Lots of downloads and missing feedback from users don't reflect the eventual problems out there.
What I tried to say was that there might be many people having problems without shouting it out loud. The number of people giving feedback doesn't necessarily reflect how many who are using your plugin, how many who are satisfied or have problems.
No big deal :o)
I cannot restore the pervious setting. may i know what is the setting for Home Title, Home Description, Home Keywords (comma separated), Additional Post Headers, Additional Page Headers, Additional Home Headers.
I have just realized that my meta description is now missing as well. I have downgraded and upgraded and upgraded and downgraded several times. I cannot get this tag to come back into place. I just now downloaded the newest version 1.6.4 and installed that, still not appearing. This is absolutely crucial to have working right. I will continue to look for a fix, but it would sure be appreciated if you'd update the plugin asap, I also just upgraded to the newest WP as of today's date prior to this happening. (2.8.4)
I just fixed mine ... :) yayyyyy!
Any of you that are experiencing this problem, make SURE you have:
<?php wp_head(); ?>
in the proper place in your header. I just found that this was missing in mine and once I added it, my meta description tags are BACK!
I just did an update on another blog and had no real issues.
After I clicked the first button it did its thing but no page loaded - I hit back and was back at the ainseo page. I then clicked the next button and the same thing happened. I hit back on the browser and the titles were in again.
I clicked activate and saved and all is working well.
I really do not want to upgrade but DO want to get rid of the annoying red message at the top of all the pages. Is there a way to do it?
This topic has been closed to new replies.