Having an issue with the Event Calendar module – Reccurring date – URGENT

[Khaled]

Hi Barry,

I would appreciate if you can give me an estimated timeline for the same to communicate it to our client as it’s an urgent matter.

Regards,

[Barry]

Hi Khaled, I’d hope to get back to you no later than tomorrow with a more definitive answer. One of the dev team are currently looking at this to see if we can get a fix in place.

What I can tell you is that it is not a problem in our 3.0 code (3.0 is the next major release and should be available soon). If you like, we could certainly send you a copy of our 3.0 beta code and – though it is not officially production ready – you could assess it and even use it on your client site if you felt it was stable enough.

Note also that we don’t support beta code on the forums as it has yet to be released officially, but it might provide you with an alternative path in case we can’t solve this with 2.0.11. If you are interested in this, please email us ([email protected]) and include a link to this thread and we’ll be happy to help you out.

I will in any case update you tomorrow and let you know what progress we have made.

Thanks for your patience!

[Barry]

Hi again Khaled.

So on this occasion we aren’t going to be able to provide a fix (for 2.0.11) as it is anyway fixed in 3.0 – which will be available shortly.

Once again if you want to evaluate 3.0 (bearing in mind it is still beta code and so not completely real-world tested) you are welcome to do so – please just email us as directed in my last post … and thank you for your patience while we looked into this 🙂

[Khaled]

Hi Barry,
Appreciate your time and efforts in getting back to me, but to be frank with you, this will not help in our case with the client. We need to rectify this issue on our client website’s website at the earliest by tomorrow (EOD). If you guys think it’s not possible to give a public fix by releasing a new update for V2, fair enough, but you need at least to lead us on how to fix it for our client. I will ask our dev team to look into it, but let us know where this issue is appearing in the code and how to get it resolved, any help from your help at this stage will be highly appreciated.

[Khaled]

** Any help from your team at this stage will be highly appreciated.

[Barry]

Hi Khaled,

I’m really sorry to hear that you’re in a difficult position here, realistically though we just can’t offer up spot fixes for every bug that is reported – though we do of course strive to do so if it’s possible and if it is a good use of resources.

I can’t actually bring to mind any other reports of this and so suspect for most of our users this either isn’t a problem that they notice or it just doesn’t affect them greatly. So, although we definitely appreciate that this issue might have more significant dimensions for you and your client, I’m sure you’ll appreciate that we have to allocate our development resources wisely in order to achieve the best results for all of our users. On this occasion we feel the cost of investigating and fixing the 2.0.11 code outweighs the benefits of keeping our team focused on 3.0 development – which will ultimately benefit all of our users.

Once again we do sympathize but we feel this is the best course of action here. Our offer of sending you the 3.0 beta code still stands – so if you have second thoughts and want to take a peek at that before the official release then please do feel free to let us know.

[Barry]

Hi Khaled, I’m just checking in to see if you had any other thoughts/concerns on this one? If not, or if you and you’re client are through the woods here, then I’ll close this ticket in a few days time.

Thanks!

[Barry]

We’ll close this off now. If there’s anything else please just create a new thread.

[Author]

Posts