Avoid

  • Turned from good, simple and solid plugin into a mess when it was acquired. Focus of the plugin is now to upsell you paid version.

    Instead of using simple fields for UI, it uses their own fancy Javascript thingy. Which often doesn’t load. If (and when) you don’t notice it’s not loaded, as is often the case when updating a page or post, it destroys title and description.

    Again: your data is lost when UI doesn’t work. And it happens often.

    Looks like it also uses two separate custom fields for saving data. _aioseo and _aioseop. This makes it impossible to automatically switch to another plugin. Manually it’s possible, but extremely difficult. Takes hours to migrate data to any other plugin.

    So if you get fed up about loosing data, like I did, it takes hours to switch to another plugin. And pretty strong understanding of WordPress, and also WP All Import plugin, costing 169 USD.

    Strong avoid.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Steve M

    (@wpsmort)

    Hi @veikkaajat,

    Thank you for your review.

    Our focus is, and always will be, making the best SEO toolkit for WordPress. Our team works hard every day to develop a feature rich plugin for everyone to use.

    With regards to loading issues with the UI, if you’re having problems then we’ll be happy to troubleshoot this for you. Please reach out to me using our Basic Question form here.

    Data is only stored in two different places to enable backward compatibility. All settings for versions of the plugin prior to 4.x are stored in the aioseop_ options and all settings for version 4.0 and later are stored in the aioseo_ options. This means you can switch between version 3.x and version 4.x without any problems because the old data is preserved and not touched by v4.x.

    Again, if you’re having problems with the plugin then we’re here to help you and would be happy to troubleshoot any issues with you if you reach out to us.

    Thread Starter Veikkaajat.com

    (@veikkaajat)

    With regards to loading issues with the UI, if you’re having problems then we’ll be happy to troubleshoot this for you.

    By the time I noticed the issue, I had already lost data, randomly, for who knows for long, on several sites. After going through hundereds of pages on 5 different sites, in 5 different languages, to see what is lost, I wasn’t particularly in mood for “troubleshooting” with you.

    There could be dozens of reasons why your JS-based form doesn’t load on certain environment. It looses data every time that happens, and it’s very hard to notice. Keep in mind not all of us maintain sites in languages we can understand, and sometimes a lot of thought has been put into those titles. It’s not like you can always just write a replacement off the top of your head.

    I can’t think of any advantage that the new UI gives that is worth users loosing data randomly (and in a way that is very difficult to notice). Why not just use forms like literally everyone else? New one looks cooler but IT LOOSES DATA. Who thought this is a good trade-off?

    This means you can switch between version 3.x and version 4.x without any problems because the old data is preserved and not touched by v4.x.

    This also means it’s hours of work to get rid of your plugin that just lost my data. Very convenient “side-effect”, no?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Avoid’ is closed to new replies.