Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to set allday event #143

Open
Showa opened this issue Jan 22, 2014 · 5 comments
Open

Unable to set allday event #143

Showa opened this issue Jan 22, 2014 · 5 comments

Comments

@Showa
Copy link

Showa commented Jan 22, 2014

Trying to set an allday event the start and endtime box disappaer. After that it is impossible to save the event. You get an error that start and end times are neccessary.

@CharlesMx
Copy link
Owner

try to clear your browser cache, that was a JS script update which should now automatically update the fields even though they are no longer visible.

@Showa
Copy link
Author

Showa commented Jan 23, 2014

Hi Charles, thank you for your quick reply.
I cleaned the browser cache removed the modx-cache manually, used other browsers, but no succes. Also in the front-end times are still visible in an allday event.

Updating 1.1.9 to 1.1.10 also gave a strange problem. At first I downloaded 1.1.10 and it installed without a problem. Because I had Some problems with googlemaps see issue #139 I deinstalled 1.1.10. After I solved the googlemaps/setlocale issue I downloaded 1.1.10 again, but it wouldn't install again. In core/packages there was mxcalendar2-1.1.10-pl..transport.zip and mxcalendars-1.1.10-pl after changing the last file to mxcalendar2-1.1.10-pl it installed. Now all three files are in core/packages. In modx manager packagemanagement there is mxCalendar 1.1.10 pl and I still got mxcalendars 1.1.8 pl. The snippet also still got version 1.1.8. Could this be the cause of the problem?

@Showa
Copy link
Author

Showa commented Jan 24, 2014

I deinstalled 1.1.10, removed all 1.1.10 files in core/packages was able to update 1.1.9 in a normal way, but issue still exist.

@Showa
Copy link
Author

Showa commented Feb 9, 2014

I now uninstalled and removed 1.1.10, removed all older versions except 1.1.9 updated with 1.1.10 and now I can set an all-day event without the error.

In the frontend there is still a time 8:00 and also in detail there is a duration from 8:00 until 17:00 is this normal? I would prefer to see no time indication at all for an all-day or if necessary automatically from 0:00 until 24:00.

@Showa
Copy link
Author

Showa commented Feb 9, 2014

Cheered to soon. Problem occurs again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants