- This topic has 16 replies, 4 voices, and was last updated 11 years, 2 months ago by
.
-
Posts
-
Hello,
I have been looking through the doco and the forum for help with getting
the next month link to show up, the previous month always show up. I have tried everything suggested in the 20 or 30 threads I found related to this and none of it made any difference.So I set up a blank default wordpress site and installed Event Calendar Pro. This has made no difference at all. I tested this in IE 7, 8, 9, 10, 11, Opera, Firefox and Chrome and it simply does not work.
I look forward to hearing your succinct no flowers answer ASAP please.
The test site is here;
http://pcsolutions.net.au/natest/?post_type=tribe_events&eventDisplay=monthKevin
Howdy Kevin,
The Next and Previous links only show up when there are events in the future (next) or past (previous). If there are no future events, that link will not show up. This prevents wild goose chases. To get said link to appear, just add an event in the future for it to point to! Does that make sense?
If you wish to modify this behavior, I believe I colleague of mine has a snippet that will force those links to always show regardless of past or future events. I will gladly dig that up for you. Cheers!
– Brook
Hi Brook,
Of course I tried that and if you put in an event for a couple of days ahead it works sometimes, the previous always seems to be there even when there are no previous events. The behaviour is totally inconsistent. I put one event in for a year ahead and no link.Yes I would like the code that makes the links always visible and I suggest that you test this properly or remove it from sale.
Hello Again,
That is phenomenally strange. We do test this very thoroughly. Each release there are seven of us that put this through at least three rounds of QA, in addition to the QA the devs do and the QA that happens throughout the life of each release. Problems like this that neither us QA folks or 99.9% of our users experience usually result from a plugin or theme conflict. If you want the default behavior to work properly it is worth testing for those.
I have seen one other person with a sort of similar issue. For them the link did not appear even though they had one future event. I believe they deleted said event, then added a new one in the future, and suddenly it worked properly. I am still not sure why that is. I have been unable to reproduce that problem in my tests. If we could nail down some specifics though, and found that it was a bug and not the result of another plugin gumming up the works, then we would certainly patch it.
Here is the snippet which forces those links to always show. It sounds like this is your preferred solution. If however you do want to dive into a Conflict test, let me know the result and we can try to identify why this is happening.
Cheers!
– Brook
Quick followup, I should note that when you said “blank WordPress site” you might have already tried a conflict test. But, I have seen too many definition of blank WordPress site to be sure.
Are you running a caching plugin, or is your host perhaps? It occurred to me that a caching system could easily result in this happening. Does clearing it help?
– Brook
Hi Brook, You can be sure I thought of all of those things. I am a developer with over 30 years experience. I stand by my comments that your plugin is poorly tested and very buggy.
Could you also provide the code you promised to allow the Next and Previous links to always be there.
Frustratedely yours
Kevin BerginI am really sorry to hear you think that. While it is by no means expected that our users help us improve our QA process, if you do have some constructive feedback for us on what more we can do we would be gladly take it under advisement.
Ooops. I linked to that snippet in my above response, but perhaps you didn’t see it. Here is is again: https://gist.github.com/elimn/67679b0b9b74793a53f0
– Brook
Hi Kevin! Rob from Modern Tribe reaching out – I head up the support team here and after Brook brought this thread to my attention earlier today, I wanted to chime in. It’s clear you’re frustrated based on your experience with the plugin so far. First and foremost I should apologize on behalf of the whole team for the experience. I know how it feels to pay for a plugin and find yourself struggling with getting basic functionality to work, and it’s never a good feeling. We really appreciate your patience in explaining the scope of the problem and helping Brook understand the scope of what’s going wrong so far.
That said, I think it’s worth clarifying that the problem reported here isn’t something we can conclusively call a bug in the code – it’s something that we aren’t seeing a lot of reports on nor is it something we’re able to recreate locally, which suggests there’s a conflict of some kind at play. It’d be awesome if you could provide us specific steps recreate – what type of events are you configuring? Do you have caching in place with your hosting provider? etc – so we can definitely continue to hunt that down and try to identify if it is a bug in the codebase. (Until it’s something we’re able to recreate locally, though, I’m hesitant to call it as much – our tests so far have yielded only the intended results).
Either way, hopefully the snippet Brook provided to force the links to show (even when no events are present) will serve as a workaround. But it’s a bit disappointing to see comments suggesting the plugin is “poorly tested and very buggy.” I can assure you that we spend between dozens and hundreds of QA hours per release cycle testing this plugin before we ship it to the public. While no level of QA is going to ever render any plugin 100% bug free – there will always be use cases that are untested, simply based on the fact that tons of people use this plugin in many different ways – we catch a lot in our pre-launch testing; and when we critical bugs do slip through, you’ll almost always see a follow-up maintenance release shipped in short order to address that so users don’t have to wait until the following month’s release to see their issue fixed. If you have ideas on how this QA process could be improved – or have worked with another plugin shop in the past who you think does a particularly graceful job at it – I’d love to hear your thoughts there. We’re always looking to deliver better service and a higher quality product, and it’s the feedback from our harshest critics who help us improve the most 🙂
All that to say: sorry we let you down here. Know that if at any point you’d like a refund, which would allow you to take your $ to a product with a codebase you find more stable, that offer is on the table. While it’d suck to lose you as a customer – I want to do right by you. If that means sending you into the arms of a competitor, so be it. And if you’ve got further feedback that you’d like to pass along privately, I can always be reached directly at rob (@) this domain.
Hi Rob,
Thanks for ‘chiming in’ just want to challenge some of your remarks.
‘it’s something that we aren’t seeing a lot of reports on nor is it something we’re able to recreate locally’
That’s not true Rob, there are so many posts from people struggling with this and replies saying what you have said here!!
I have already discussed with Brook my setup and the fact that I have done everything you listed. Clearly your ‘chiming in’ didn’t include reading the posts!
If I decide to not use your product because as I said it is clearly not tested well at all it will be for more than a refund and thanks for the offer of a private chat but lets keep it very public.
Yes the fix Brook gave me worked and again that was in our posts that are clearly feeling neglected by you.
Kevin BerginHi Kevin. Thanks for the follow-up! I can assure you that I did read the thread, and beyond that actually spoke with Brook about the situation. I chimed in because it looked like the tone was getting increasingly hostile. While I welcome your constructive criticism, let’s just try to keep it civil on the forums here…at the end of the day we’re just a group of folks who love working with WordPress and aren’t trying to cause anyone problems 🙂
As soon as we’re able to identify this as a legitimate bug rather than a conflict of some kind – as I noted, we’ve thus far been unable to recreate it – we’ll definitely do what we can to get it patched. Until then, we appreciate your support. Do let us know if you have any other concerns as you continue to use the plugin.
I have some great news here, Kevin. I asked each of the support reps if they had seen a similar problem. We did end up finding a third person experiencing this problem, including yourself and my other similar thread that found an alternate solution. Rob asked if there was anything more we could do to try and reproduce the issue if we took even more time to do so. Long story short, I was eventually able to reproduce the problem and isolate it. Then my colleague Barry wrote a snippet that will fix the issue outright. If you prefer the original functionality which hides those links at times then give this snippet a whirl instead of the one you are already running.
The bug details: The original date for an event, the one that you selected before first clicking “Publish”, will update the “date range” that you can page through in Month view. So if you have an empty calendar and save an event for next month, a link to next month will appear. However, if you were to instead save an event for today. Then come back and edit it so that the event appears next month instead. No link will appear in this case, because unfortunately edited dates did not update the date range. That snippet causes edits to events to update the date range as well as saves. This explains why the bug is relatively rare. The event you are saving not only has to be the furthest one out, but you have to have initially saved it with an incorrect date, then come back and modified.
Thank you very much for helping us spot this Kevin. If the new snippet or the other one is providing you the functionality you wanted when opened this topic, would you mind letting us know or marking this resolved? If you have any other questions let me know. Cheers!
– Brook
Hi there,
Thanks for your patience while we looked into this problem. We are working on a secondary maintenance release that addresses this issue. Keep an eye on your site for a new update to version 3.9.1. We’ve tested this release thoroughly and it should resolve the reported issue. However, if you are still running into trouble please start a new thread and we will respond as soon as possible. Thanks again for your patience and support!
Best,
Leah
and the team at Modern Tribe
- The topic ‘Next Month Link’ is closed to new replies.