With the newest update, we've fixed a problem with events in which setting the category did not save once it was set to None. However, there is a display issue of which we are aware in that though the category setting does save, the backend still displays None. The database IS updating with the appropriate category despite the display in the backend.
We are working on this fix today and hope to roll it out shortly.
If you are having issues with frontend display of events within category, make sure your Root is published and assigned an access level.
Thanks for the news Jen.... Much appreciated to have you comment here. Keep on the good work... I'm looking forward to coming back to DT Reg when things stabilize a bit further!
If you are having issues with frontend display of events within category, make sure your Root is published and assigned an access level.
What do you mean with that ? I can't understand it.
New events are not showing in under their assigned categories in the front-end.
When do you think you will come with the solution to this bug ?
I am waiting for a solution for about 20 days ...
Thanks
I'm unable to make to make that work.
Also, after publishing root, the categories now show as:
Root>>Category
This looks a bit ...poor.
Although he event with "No" category, does seem to have the right category selected which shows correctly in the event_category table in the database, it doesn't sit with the rest of the events in that category and if I change the menu item to list all events, it still sits outside of the events in that category.
All this functionality works on the J30 version...