Forum Replies Created
-
Posts
-
That was it! Between the second instance of jQuery loading and needing Day view to be active, everything seems fixed now!
It sure would be nice if there is some warning on the Admin Settings screen about the importance of Day View for both Find Events and the month view “View All Events”.Hi Brian,
I am talking about the “View All Events” link for days with more than 3 events. The majority of the days on my calendar that are at 3 events actually have closer to around 8. http://arts.stanford.edu/events/
I fixed the “NetworkError: 404 Not Found – http://arts.stanford.edu/events/js/bootstrap.min.js” error. In the theme template there was a second load of bootstrap.min.js that was unneeded.
Thank you for your assistance!
RobertI was actually able to get the “Find Events” button working (there were two instances of jquery loading).
The “Show More” link is still not working, however.
Glad you’re able to reproduce, Brook. Thanks for passing the issue along to development. I look forward to a fix in an upcoming release.
Sorry about the weird formatting in the SQL above. Apparently the backticks that SQL uses to contain table and column names are interpreted as code markers in text posted here. The backticks aren’t really necessary in this case. The correct SQL is:
SELECT * FROM wp_terms WHERE term_id = 1;Hi, Brook. Sorry I wasn’t clearer in my description. I don’t have any custom code. I’m reporting a bug in your Events Pro code.
To reproduce the problem:
- Figure out what term in any of your taxonomies has term_id = 1. You can search the database for this if you want: `SELECT * FROM wp_terms WHERE term_id = 1;`
- Add that term to your Event categories.
- Visit your main Events page.
- Select either the Week view or the Photo view. Notice that the page you land on is limited to the category with term_id = 1.
The initial report describes where in your code this bug is triggered. I realize now I should’ve provided some context for my report, i.e. what the symptoms are on the front end. Hopefully the steps to reproduce above will help. I’m hoping since I’ve pointed you straight to the code that causes the bug it should be quick and easy enough to fix that it might make it into your next release. But I understand if no one else has reported it, it might be a lower priority for you.
Thanks for your swift reply! Let me know if you need further info.
