3.3.1 problematic on a multisite

Hey svinqvmraka! Thanks for the note here, and for taking the time to write this review. While we’re bummed to see a 1-star review for something that sounds more specific to your install than the overall codebase, it’s understandable that you’re disappointed here.

A few points I’d like to touch on here, regarding some of the notes you brought up:

* You make an excellent point on the 404 issue, though I’m a bit confused because – as I noted above – this isn’t a core behavior of the plugin. I just checked with Barry, who runs the forum here on dot-org, and he verified that this has yet to be confirmed as a bug within the plugin. It sounds like, if this isn’t a conflict with another plugin or your theme, something that can be addressed via flushing permalinks (though I’d love to hear whether either of those solves your issue).
* Regarding the forum response time: if you’re talking about a thread here on www.ads-software.com, there are indeed limitations to how much support we provide. We cannot help everyone here on the free forum and indeed are only really concerned with actual bug tickets impacting the plugin. While we make an effort to hit everything on the forum during our weekly pass, ultimately we have a fixed number of hours we can budget for dot-org per week. Whatever doesn’t get hit during that will unfortunately have to wait until the following week. While we’d love to be able to help everyone out with every situation, the reality is that as a small team with limited resources, we cannot. We ask users who are seeking a greater level of support to purchase a PRO license, which entitles them to quicker/more detailed support.

Anyway, all that to say: I’m sorry to hear we let you down. I sincerely hope that as the plugin continues to evolve, you find it useful to add back to your stable of plugins and feel empowered to update your review accordingly. But if not, we wish you the best of luck finding a solution that better meets your needs.

Hey and thanks for the reply,
First of all, I’ve edited my impulsive one-star review with some actual information on the issue instead of just ranting. Sorry for that, it was unnecessarily harsh.

The site I have the issue on is a multisite install with a kind of basic theme(whispy if that matters) with not too many plugins. Changing the theme to twenty twelve and deactivating all plugins doesn’t affect the behaviour of the events calendar which is 404 errors when clicking on a link for a single event.
Urls for the plugin are the default ones(event/events), the problem persists when changing them to something else.
I’ve tried flushing the permalinks already and what happens is kind of weird:
I flush the permalinks and the event pages all work great(from a logged in admin account in wp). Then I open a new incognito window in chrome and try to open an event – this results in a 404 again. When I go back to the normal chrome window(logged in as admin) and refresh the single event page(or for that matter try opening another one), it breaks and I get 404s until I flush the permalinks again and everything repeats.
On The Events calendar 3.2, there was not such issue(I updated directly from 3.2 to 3.3.1, skipped the 3.3 release)

Again – I’m not usually that a-hole that randomly writes 1-star reviews for every problem they encounter, but to me this seems as a serious issue with the plugin that people should be aware of before installing. I can assure you I will change the rating and review if the issue is resolved or I find out it’s not the plugin’s fault.
Cheers

update: I gave up and rolled back version 3.2 of the plugin from my backup and it’s working fine. So, yeah.

Thanks again for the follow-up here, svinqvmraka — this is really helpful and gives us a good glimpse into how we could better serve other users in your position down the road.

It does look like this may be something introduced in 3.3.1; yours is the first report we’ve seen of it and we’re still unable to recreate locally, but based on your troubleshooting steps it does seem like you’ve clearly identified an issue in the codebase. We’ll continue looking into this and will try to patch in a subsequent build if we can get to the bottom of it.

In the interim, sounds like you’re in a good spot with 3.2 for now. If you find a subsequent build does better address this for you and would feel open to sharing your experiences here/possibly updating your review to reflect that, we’d really appreciate it. Otherwise thanks for the feedback.