Calendar [Paid] 2.4.5
- Thread starter Naz
- Start date
Mouth
Well-known member
Bug on recurring events, possibly related to 2024 being a leap year?
When adding/editing a recurring event, after save the event is for the day after date picker.
For example, here we see an add/edit with Mon 22 Jan (today) within the date picker.
When saved and displayed, the event is now for the following day, Tue 23 Jan (tomorrow).
If you re-edit the event and untick the recurring option, the event is then showed correctly for 22 Jan (today). Edit once more, and only (re)tick occurring, without changing the date, and event again jumps to 23 Jan (tomorrow).
When adding/editing a recurring event, after save the event is for the day after date picker.
For example, here we see an add/edit with Mon 22 Jan (today) within the date picker.
When saved and displayed, the event is now for the following day, Tue 23 Jan (tomorrow).
If you re-edit the event and untick the recurring option, the event is then showed correctly for 22 Jan (today). Edit once more, and only (re)tick occurring, without changing the date, and event again jumps to 23 Jan (tomorrow).
Mouth
Well-known member
You must have a different expectation to me on what is considered engagement and abandonment on paid resources.
It's why XF has a resources housekeeping policy.
btmgreg
Well-known member
I personally don't think a developer/product owner should offer things for sale (be it any price, but especially a premium price for an addon in terms of other addons of a similar price bracket) if they cannot actively support and engage with their customers on at least a semi-regular basis. 4+ months is not 'semi-regular' and the support forum itself has many unanswered posts and threads.
My personal thoughts are sales and support should officially be paused until the developer actually has a window of time on a continual basis to support his products. If this product can't be supported, then change the status. It gives false hope and poor value to customers who rightly expect more.
I also think this personally reflects badly on XF. It's not a good image. I'm happy that we have more developers on board for XF- it's a great thing, but putting too many eggs in one basket isn't. Do one or the other - both don't seem to be working, at least for this addon.
No offence intended.
My personal thoughts are sales and support should officially be paused until the developer actually has a window of time on a continual basis to support his products. If this product can't be supported, then change the status. It gives false hope and poor value to customers who rightly expect more.
I also think this personally reflects badly on XF. It's not a good image. I'm happy that we have more developers on board for XF- it's a great thing, but putting too many eggs in one basket isn't. Do one or the other - both don't seem to be working, at least for this addon.
No offence intended.
Mouth
Well-known member
This is why the housekeeping policy exists, and should be actioned. Otherwise, XF is saying that this sort of behaviour is acceptable for their product and brand. Even more so when it's a staff developer.
Ozzy47
Well-known member
This will typically only apply to resources where the author is no longer licensed, has had their forum account deleted, has been permanently banned, or has not visited the site for a period of time.
I want to apologise for not updating this (and some of my other products) for the past two years. Being busy isn't an excuse, and I realise I have a higher standard to uphold that I've often fallen short of. With 2.3 development winding down, I'll be updating this and my other products more frequently. As a gesture of goodwill, I have also extended licenses.
FWIW, I can't reproduce this but recurring dates are kind of wonky. I have a version where the implementation of them has been entirely rewritten but it needs more testing. I'll send it over to you directly with some caveats later.
ichpen
Well-known member
Ditto here.
I’ll check your licenses tomorrow and get back to you. It should apply to all customers.
These should be sorted now. Feel free to reach out to me directly if there's still issues.
Mouth
Well-known member
This update has failed for me, has anyone else been able to successfully update?
Extracted/copied all files into appropriate dir structure, but neither ACP nor cmd.php show an upgrade as being available/possible.
And with the 2.4.4 files within the XF dir structure and unable to trigger the upgrade, now getting ongoing errors in ACP ..
Code:
ErrorException: Template error: [E_USER_WARNING] Method canAlertRespondents is not callable on the given object (NF\Calendar\Entity\Event) src/XF/Template/Templater.php:1190
Last edited:
Does it work if you upload the archive and use the add-on installer to update? I just tried and it worked fine.
Similar threads
