-
Notifications
You must be signed in to change notification settings - Fork 0
Big Official 2.x to 3.x Upgrade List of Issues #33
Comments
|
This is how it is in the 2.x version now too. Should I change the both of them? |
It wouldn't match the 2.x version if I did that, though. The current pagination element I've got uses Bootstrap pagination elements and is similar in design to the one I made for the 2.x version. |
Do you have an example of the error? Because there's no error like this on my end, nothing in the console etc. So I'm lost. |
This, I did on purpose to sort of downsize the form, so if someone wants an email every day then they can check every checkbox, or just the ones they'd like depending on the day, or if they'd like it weekly they can do that too. |
A quick way to fix the problem would be in
to
But the better solution is probably to change this line in
to
|
^Done. I wonder why I never got the error message. |
The month method URL reads /month/MM/YYYY. However, due to weird counting or whatever is happening there, advancing past December into January reads not as /01/YYYY, but rather /13/YYYY of the previous year. e.g. if you want to check out January 1992, you can put /01/1992 into the URL, but you can also put /25/1990 into the URL.
Month widgets only show the current month; using the prev & next buttons take you to month pages. Clicking prev & next buttons does not open the in-widget month.
Feed widgets show all the events at once, rather than a couple weeks at a time with a "More Events" button.
Clicking events in the feed widgets opens the event page, rather than the in-widget event.
Locations & custom tags don't autocomplete in the event form.
The mailing list might work? I don't know if it does and I don't know how to test it.
"More Events" button appears 100% of the time in indexes, even if there are literally no events to index.
The paginator buttons are ugly & awkward.
The index breaks if the events are more than two weeks apart.
BOLD INDICATES HIGH PRIORITY
The text was updated successfully, but these errors were encountered: