Support branch 3

@yarr2 I’m afraid that we no longer support the 3.x version of the plugin and have no plans to do so in the future.

What exactly troubles you with the current version of the plugin? If you’re running into any issues, we’re more than happy to help you troubleshoot them. If you have any other feedback, please let me know since we’ll definitely take it into account.

The current version just sux.
It broke descriptions from the previous version, it makes the site working slower, its interface is an example of how it should be never made.
I switched twice to using 4.x and both times switched back to 3.7.1 wasting a lot of time on this.
So for now I’m not going to try 4.x anymore and looking for an alternative solution instead.

• This reply was modified 3 years, 10 months ago by yarr2.

Hi @yarr2, I’m sorry to hear you’re still having problems with our latest version of All in One SEO. As @arnaudbroes said, we’re happy to work with you to troubleshoot any problems so please let us know how we can help. Please provide as much details as possible so we can troubleshoot the issue with you.

Hi,
Actually I do not want to spend time on troubleshooting or solving something.
I just want to continue using plugin, which works fine on the site as long as possible. Then I’ll switch to another plugin, which require as less efforts as possible to move, or will just move manually necessary functionality to the site’s theme.
I’ll never try 4.x for the third time. In addition to already noted problems I remember there was an issue with setting data for social networks. Also unclear why plugin created additional 4 tables in the database, increased amount of queries should affect site’s performance negatively.

I’m not sure what the social networks issue is that you mentioned, but with regard to the additional tables and queries, these actually positively affect the site’s performance.

Typically WordPress plugins use the post/term meta tables to store data. The issue with these tables is that everyone uses them and they get incredibly large, which means lookups take a lot of time. By switching to our own custom tables, we’re able to perform lookups much faster. We run more queries than we used, but if you’d look at the execution time of those, you’ll see they are incredibly lean and optimized. On average they add 5 milliseconds to the load time, which is negligible.

Hi @yarr2,

We haven’t heard back from you in a couple of weeks, so I’m going to go ahead and close this thread for now. But if you’d like us to assist, please feel welcome to continue the conversation.

Thanks! ??