Known issues with version 2.1.6 and above and possible solutions

Thx.

As I mentioned after a lot of meddling around I could solve my problem.

So to be clear: I do not need support on this subject anymore. I want to criticize the quality of your software in a forum friendly way.

Mentioning that your software as good and beautiful as it is in many aspects in terms of stability it is not tested as well as it should in my opinion and wastes time and, as someone else mentioned, money of users in various occasions.

I know that the paid version is the same code base. That is the reason why I haven’t bought your pro version yet though I am generally paying for most plugins my customers use.

BTW: I think your support is great, to be honest, your’s is one of the best support teams out there in providing quick and individual solutions.

My point is that incidents of breaking complete sites should and can be avoided. Showstoppers due to lack of nonpublic testing annoy users and harm your reputation.

thx for reading,
piedro

@piedro, thanks for your feedback.
We actually do have non public testing as we have beta tester and so we try to test before release to avoid breaking sites.
2.1.6 was an error we did, we had a meeting and we had decided to ship it with compatibility mode ON and when we shipped, we shipped it with compatibility mode OFF.
Anyway we obviously have to improve.
Right now the whole team is doing support while developing new features, i think this will make for better releases as it brings us developer closer to what users really want/need, like stability when upgrading.

Thank you very much for your honest response.

I am very glad your team takes these issues seriously and it is possible to have an open disussion about it.

Sincerely I believe your plugin offers the best calendar features out there. And yes, as you mentioned, I also think users value stability way higher than new feautures. When installing a plugin most people look at the feature list at that point in time. Speaking for me, after installing I rarely feel the need for new features as I’ve already sold the site with a fixed set of features. If it works most customers do not ask me for new features. Though those are nice to have, stability while upgrading is an absolute necessity: – there never is a budget for fixing routine upgrade issues.

Having said that I perfectly understand that features are the most interesting and rewarding part of working as a developer.

I guess these two perspectives are not exclusive but they demand a decision on which one to focus on.

Thx for your work and keep it up!

piedro

I totally agree with you that when you look for a plugin you look for features and afterwards you just look for stability. I’ve been thinking like that for a long time.
Fact is, if you the team doesn’t do support and just focus on development, it loses “touch” with stability and just think “the support team will handle that”.
That’s why i think it’s much better than now we have the whole team, me included, on support, i was the first one to think what i wrote above ??
From a business perspective, we have some clients asking for new features, and lots just asking for stability.
The goal is to find a way to achieve both, probably the only way it’s just adding more and more add ons trying to touch core as little as possible. Each new feature is a new add on, so that we break as few things as possible.

None of the above has helped me guys! Stop patting or smacking each other on the back.
The reality is, this plugin is now no longer working for us and even going back versions has corrupted the database or something that we cannot use ai1 at all!

My situation – Upgraded WP to 4.1, and upgraded every plugin we have in one hit. Only ai1 is causing issues. All other plugins work perfectly!

And yes I am referring to HTTP Error 500 and the white screen of death!

Have you tried 2.2 beta?