-
Notifications
You must be signed in to change notification settings - Fork 15
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
defaultWeekStartDay Support #11
Comments
That config setting, and users’ Week Start Day settings, are currently only used when displaying the calendar popups on date inputs. But we could update Store Hours to respect it as well, yes. |
@brandonkelly that would be awesome :-) I tried to work out how to do it for a PR but failed miserably |
Haha that’s ok, we’ll get to it. |
Thanks for making this update! But it seems the release hasn't been made so the 1.2 update shown in the CP doesn't link to anywhere. (https://codeload.github.com/pixelandtonic/StoreHours/zip/1.2) |
Should be resolved now! |
Doesn't this break the output though? If you use the recommended output method of creating a days array, the accuracy of the information being outputted changes depending on who the last person to update the entry was. If USER A has their week starting on Monday and saves the entry it breaks the output, if you change your array to reflect that and USER B (whose week starts on Sunday) updates the entry, it is broken again. Do I need to check the defaultWeekStartDay of the last user to update the page and create my array from there? I think the name of the day of the week should be built into the data coming from the field. |
@gregorydavidjenkins That change shouldn't have affected the way the data is stored, with the first day being Sunday. Are you just speculating or have you actually found the data to be ordered differently? |
(and if the latter, please open a new issue so we can track it separately from the original feature request.) |
I have my defaultWeekStartDay set to Monday, but the plugin starts on Sunday - shouldn't it honour whatever the default is set to?
The text was updated successfully, but these errors were encountered: