Hey Jeff,

I just upgraded cal to 1.0.0 and one of our staff emailed me saying that she couldn't add events. I tried myself (using the frontend) and confirmed that the added event wasn't showing up. I looked in the backend and all of our attempts did show the records in the backend (June 1, 200 as they were created in the frontend.

I also noticed that the Where: dropdown list for predefined locations wasn't being populated with anything. However, if you go to a record in the backend, the Where: dropdown list works.

Thanks for your help Jeff and have a great day!

Hey Chris,

Are the events being saved on the same page as where your backend-created events live? Is there anything you can do from the backend to make these frontend-created events show up, such as clearing the cache or saving the record?


Which location model are you guys using (it's a setting with the Extension Configuration options)?

Do you remember offhand what version you upgraded from? That may give a clue as to any critical settings that changed along the way.

Thanks,
Jeff

The records for both frontend and backend created events are stored in the same sysfolder. Neither saving the record in the backend or clearing cache seems to have had an effect. I even upgraded from 4.1.6 to 4.2 in the off-chance that it might correct things (It didn't.)


I'm not sure what this is you're referring to. Do I look for this in the constants editor, the flexform, the extension template or somewhere else?


I do not, sorry.

Hmm, I guess the next logical step in debugging is to figure out what is visibly different between the record that works and the one that doesn't. it seems like the selected calendars and categories would be the most likely culprit. What if you manually create a new event that is identical to the frontend-created event in each field.


I'm referring to the options when you click on Calendar Base in the Extension Manager (the stuff that shows up when you first install the extension). Calendar Base supports loading its locations and organizers from tt_address, frontend users, as well as its own internal tables.

Thanks,
Jeff

I see the problem now, categories selected in the frontend aren't being set when you look at the event in the backend record. The calendar is configured to display calendar events of a certain category so they aren't showing up because no category has been set in the record.


Okay, Dave informed me that the extension title area of the extension manager is actually a clickable link. I had no idea since it doesn't look any different than the other red-colored text parts that aren't links. Anyway, we are using the built in location manager and organizer data model.

Chris,
Sorry for the delay in getting back to you here. Been tied up with development and lots of other questions around here, but I've finally made my way back around I just got done testing this with the default Typposcript configuration as an admin user in frontend editing and the categories are saved correctly for me. Of course, this doesn't mean there's not a bug, but its probably not one in the most basic setup that would affect all users.

Do you have any custom Typoscript that's related to setting the categories? It might be worth temporarily commenting out all your frontend-editing related Typoscript to see what happens when only the defaults are in place.

If you're not an admin user for frontend editing, it might be worthwhile to change that temporarily to see if that causes things to work also.

Thanks,
Jeff

I know very little about Typoscript so I avoid it like the plague. That being said, perhaps some custom Typoscript was put in place when you and Mark pulled an all-nighter putting up the Bowie prayer schedule? Maybe, maybe not. Anyway, I think we installed some non-public betas early on so maybe there is some sort of non-standard setup resulting from that. Who knows. Anyway, I haven't tried to do anything with cal that wasn't "out of the box."


FWIW, Michele is a non-admin user and I am an admin user and the results are identical between our posts.

Chris,
Thanks for the info. After a quick round of testing on the Ginghamsburg site, I'd agree with your initial assessment that the category issue is a bug. It seem to occur when there's only one category available on the page, so that would explain why we haven't seen it reported from others.

We were already planning on a bugfix release in the next week or so and I'll add this to the roadmap for the release. As a short term fix, you could add a new dummy category that appears before the real category.

One the location issue, the problem is that there are no location records on the page that is set for the pidList (in Typoscript) or Starting Point (in the Flexform). You'll probably want to expand this to include the page where you store all your location records. You can still filter the calendar plugin to only show the calendars and categories that you want, even if its pulling data from several locations.

Thanks for the bug report!
Jeff

Thanks for taking a look Jeff. You guys are the best!