How to get the month, week and year selection back to the bottom as it was on the other versions

[deangky]

If I don't allow top menu, then I don't get the options at all. I prefer to have the entire menu at the bottom as I always have, but if I deselect top menu, then the option for month, week and year disappear. Is there a setting I am missing? Is this no longer an option?

[craigk5n]

You weren't missing a setting — this was a bug, and thank you for the side-by-side screenshot. It made the cause obvious straight away.

What happened

In v1.3.0, the Month/Week/Year pulldowns were drawn by a function that print_trailer() could place at the bottom of the page. WebCalendar v1.9.0 replaced the old menu with the Bootstrap navigation bar, and the selectors were rebuilt as dropdowns inside that navbar — and nowhere else. Because the navbar is only loaded when "Allow top menu" is on, switching it off took the selectors with it, with nothing left at the bottom.

That also quietly broke Admin → Appearance → "Date Selectors position: Top / Bottom". The setting was still shown and still saved, but nothing ever read the value, so choosing "Bottom" did nothing. That's the setting you went looking for.

Fixed

Tracked in #695, fixed by #696, now merged. The selectors are no longer tied to the top menu, and "Date Selectors position" works again:

Allow top menu	Date Selectors position	Where the selectors appear
Yes	Top	In the top navigation bar (unchanged)
Yes	Bottom	Below the calendar
No	either	Below the calendar

So the layout you want — the whole menu at the bottom, month/week/year included — is just "Allow top menu: No". They render above the "Go to: My Calendar | Today | Admin …" line, the same place they sat in 1.3.0.

One difference from 1.3.0 worth flagging: these are Bootstrap dropdown menus rather than the old <select> + Go buttons, so they'll look like the ones in the top bar of your right-hand screenshot — just relocated. You click the dropdown and pick a month/week/year directly; there's no separate Go button to press.

The fix is on master now and will be in the next release after v1.9.22. If you'd rather not wait, you can pull master — or let me know and I can point you at the specific files if you'd prefer to patch your 1.9.22 install by hand.

[deangky]

Very welcome! I'll wait until the update comes out, I'd rather not try and mess with the files one by one