Christophe Posted Tuesday at 06:13 PM Share Posted Tuesday at 06:13 PM Hello @bernhard, Any updates on the date/time picker issue that you could also reproduce? Thanks in advance! Link to comment Share on other sites More sharing options...
bernhard Posted Tuesday at 06:24 PM Author Share Posted Tuesday at 06:24 PM @Christophe I don't have any open issues on my list. If you have one, please open a separate thread, so it's easier to keep track. Please describe everything as good as possible and please check if you have the latest versions of all modules. Link to comment Share on other sites More sharing options...
Christophe Posted Tuesday at 11:05 PM Share Posted Tuesday at 11:05 PM (edited) @bernhard It's the issue that I had on a website that we had talked about via PM around the 5/6 January where I had explained everything, and with more/complementary details the 9th (PHP 8.2, utfmb4, InnoDB, MariaDB..., the steps I took, etc.) and for which I had sent you via your cloud a copy of the fresh new installation I had done, as you asked me to, where the issue was reproducible a second time. You told me that you could reproduce my issue and that you were working on it. It was apparently the day the version 1.5 was released, the 11th. Compared to the installation copy I had sent you (where the modules were all the latest at that moment), I've just upgraded now the modules listed below (all the others were already up to date): *** By the way, RockCalendar, be it with 1.4.3 or 1.5.0 installed, still shows as 1.0.1 for "Latest"/ 1.0.1 (older than the one you already have installed!), in the Upgrades module page or in Admin -> Modules -> RockCalendar -> Download and Update *** RockCalendar RockCalendar 1.4.3->1.5.0 1.0.1 RockFrontend 4.0.0->4.1.0 RockMigrations 6.5.0->6.7.0 TracyDebugger 4.26.47->4.26.57 The issue is still present. With new events created (past, present and future) and with several times of the day/night. The time is saved correctly in the calendar as before but the time still goes back to 00:00 in the date/time picker field after saving the page, as before. Do you want that I summarize/condense/merge/compile everything discussed concerning this specific time issue on a separate thread under Modules/Plugins (or another sub-forum)? Added: Do you want me to create a thread specific to the date/time picker fieldtype and/or inputfield? Added 2: if you want me to create a specific thread I'll remove everything in this post and just link to the thread with the details (I'll probably remove all the content of this post anyway as I don't like when my posts are messy). Added 3: I tested after only upgrading RockCalendar to 1.5.0, and then also after upgrading the other modules, trashing the old events and creating new ones. And even logging out/in of ProcessWire, etc. Edited Tuesday at 11:23 PM by Christophe Link to comment Share on other sites More sharing options...
bernhard Posted Wednesday at 10:25 AM Author Share Posted Wednesday at 10:25 AM Hey @Christophe sorry for that. I totally missed that and after your last message talking about RockCommerce and some other projects on your side my brain dumped everything we talked before. It was quite an easy fix though, so it might have been good to start over with a fresh head, because I can remember I was on another track with solving that issue 2 weeks ago. Please grab v1.5.1 and let me know if it works now! https://www.baumrock.com/en/releases/rockcalendar/ Also @Stefanowitsch could you also please upgrade and see if it breaks anything on your project? 1 Link to comment Share on other sites More sharing options...
Christophe Posted Thursday at 06:09 PM Share Posted Thursday at 06:09 PM (edited) Hi @bernhard, And thank you! I've just updated the module on the website that I had copied. I've done several tests, also with the date range option on the same day and on several days, from the calendar or creating directly children. It seems to be working. In the calendar (in the admin) I see the starting time but not the ending time (the same day or another day) but I'm sure it's normal by default. I've not yet installed RockGrid and tested repetitive events like for example on several days (consecutive days or not) starting at the same time. But I've noticed something: if I have a range like 31/01/2025 12:00 - 04/02/2025 13:05 that is on 2 different weeks on the calendar, the starting hour of the first day is also displayed on the first day of the new week, making it seem as if it only starts at 12 pm on the 3rd February. Is it the default "behaviour" of FullCalendar? Is this only happening in the admin or will it also happen on the frontend if someone uses FullCalendar? I'm thinking/I guess that repetitive events (at the same time range or not the same time range each of these days - I haven't tested yet) (can) resolve this case. I'll have to test. Edited Thursday at 06:12 PM by Christophe Link to comment Share on other sites More sharing options...
Stefanowitsch Posted Thursday at 06:11 PM Share Posted Thursday at 06:11 PM On 1/22/2025 at 12:05 AM, Christophe said: The issue is still present. With new events created (past, present and future) and with several times of the day/night. The time is saved correctly in the calendar as before but the time still goes back to 00:00 in the date/time picker field after saving the page, as before. I am using the RockCalendar too and I tried to reproduce this error but everything looks normal to me. Can you explain how to reproduce this step by step? One thing that I did notice: If you edit an event that has a time assigned to i, then uncheck the "set time" checkbox and then re-check it, the time will default back to "00:00". I don't know if this is the problem you are experiencing but it seems as the default behaviour for me. Link to comment Share on other sites More sharing options...
Christophe Posted Thursday at 06:18 PM Share Posted Thursday at 06:18 PM Hello, It was an issue where if you put 31/01/2025 18:30 for example and saved the page, the time was displayed in the calendar/parent page, but in the child page the time was back to 00:00. Link to comment Share on other sites More sharing options...
bernhard Posted Thursday at 06:20 PM Author Share Posted Thursday at 06:20 PM 10 minutes ago, Christophe said: But I've noticed something: if I have a range like 31/01/2025 12:00 - 04/02/2025 13:05 that is on 2 different weeks on the calendar, the starting hour of the first day is also displayed on the first day of the new week, making it seem as if it only starts at 12 pm on the 3rd February. Sorry, I don't understand your example. Please show screenshots and explain what you'd expect and what you actually see. Link to comment Share on other sites More sharing options...
Christophe Posted 19 hours ago Share Posted 19 hours ago (edited) Hi @bernhard, The screenshot was the one at the end of the post. But I thought I had replaced it with the version where the 04/02 was added to show that only the first day (03/02 ) of the 6th/new week displayed again the start time (12:00/12 h) of the first day of the event. With "31/01/2025 12:00 - 04/02/2025 13:05" I wouldn't expect to see "12 h Event range on 2 weeks" on the 03/02. It could be to show some time info if a weekly calendar view is chosen but the (test) event doesn't start at 12pm on the 03/02 (or any other day other than the 31/01). It is supposed to be a continuous event, so I suppose only "Event range on 2 weeks" would be expected to the displayed on the 03/02. Edit: or the start date of the event should be displayed too on the first day of the new week (perhaps it would be easier to do, but it would probably also make no sense...) Edited 19 hours ago by Christophe Link to comment Share on other sites More sharing options...
bernhard Posted 19 hours ago Author Share Posted 19 hours ago That's how FullCalendar renders Events and shows their info. It should be configurable though: https://fullcalendar.io/docs/displayEventTime which should be easy to hook: https://www.baumrock.com/en/processwire/modules/rockcalendar/docs/hooks/#getitemarray 1 Link to comment Share on other sites More sharing options...
Christophe Posted 19 hours ago Share Posted 19 hours ago Ok, thanks. I normally won't have that "problem" appear on the 2 websites where I want to try to implement it but I just wanted to let you know about this specific "behavior" I had encountered. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now