Forum Replies Created
-
Posts
-
I was perusing posts and noticed something. The map displays depending on browser. It did not load for me in Firefox or in Chrome but worked fine in IE and Safari. <div id=”tribe-events-gmap-0″ style=”height: 350px; width: 100%;”></div> is not being populated in Chrome while in Safari it has content (the map).
New event instances work just fine.
Because pre-3.8 events were created under the bug they are not retroactively fixed with the update (to be expected, updating the plugin does not change wordpress posts).
Do note, they do not need to be recreated. Open the event in the admin panel and click update (you don’t need to change any info on the page). WordPress will churn through the recurring event instances and all the additional fields should now appear when they previously did not. This is most important for people with many recurring events, they do not need to recreate each event and reenter any info, only update each event with the problem.
I’ve been developing other things and haven’t gotten a chance to test new instances yet, but that does sound right. I am fairly certain updating to 3.8 (which I’ve done) will fix the issue for all new events, but not for events created before 3.8, which will need to be re-entered.
I will double check and post my findings.
I am fairly certain this occurs when a recurring event has already been created and then the custom fields are added later on (I had been using the Custom Fields area and then switched everything to the Additional Custom Fields in the Events Calendar area). Hope that helps.
I have been working on creating a solution to this but keep running into a problem.
Attempting to redirect a page like example.com/events/event-name/next results in auto redirecting to example.com/events/event-name/all no matter what wp_redirect() is set to. Attempting to redirect the main calendar page (example.com/events/next) results in a 404 page without redirecting the url (it stays example.com/events/next). The redirect will work on any other page or url ending in “/next”, but not “/events/event-name/” or “/events/next”.
I can’t tell if this is because the event calendar is not included in the endpoint $places (i have it set to all and all_archive) or because the calendar plugin redirects are overriding my own. Do you know what this is caused by?
I can provide my code if that would be useful, but because the redirect works on all non calendar pages I have a feeling the issue isnt within what I have written.
