When creating a New Event from an Event Template, and entering custom data for the event, hitting "Continue" doesn't save the custom data. This happens for me on 5.10.4, on the CiviHosting demo which is running 5.10.0, and the CiviCRM Sandbox running 5.12.alpha1.
How to reproduce
Add a custom field to Event entities
Click Events > New event
Choose an Event Template
Enter the mandatory fields and the custom data
Click Continue
Reload the page to force CiviCRM to fetch the event from the database
Visit the Info and Settings tab
The custom data is unset
Hint
In my debugger I had a breakpoint in my implementation of hook_civicrm_pre() and this didn't trigger when Continue was pressed, but did when Save or Save and Done were pressed. If Continue bypasses pre() then perhaps it skips the Custom Data too?
Edited
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items 0
Link issues together to show that they're related.
Learn more.
I just tried & failed to replicate this (on master but I don't think it has changed) - there must be some other factor involved - can you replicate on http://dmaster.demo.civicrm.org ?
Hmm - I see some changes that are in the 5.11 rc (due for release on Wed) that might relate - I retested against 5.11 & couldn't replicate it there either so I think we already merged a fix
@eileen thanks for sharing your screen grab. I think the issue has to do with Event Templates. On the sandbox, when I followed the same steps as you I didn't have the problem, but when I use the Event Template, I do.
I'll clarify the issue. Sorry for missing that detail - I just use templates automatically!
kenchanged title from New Event - clicking "Continue" doesn't save custom data to New Event using a template - clicking "Continue" doesn't save custom data
changed title from New Event - clicking "Continue" doesn't save custom data to New Event using a template - clicking "Continue" doesn't save custom data
I'm re-opening this bug report as the problem is again reproducible on CiviCRM 5.39.alpha1 and CiviCRM 5.37.2 - https://dmaster.demo.civicrm.org/
Custom values are not being saved on the Event, instead being saved on the Event Template, event#58 (moved)
And for this issue, Event custom values are not being saved when the Event is populated from a Template and the custom values are changed prior to saving.
Honestly, I feel that the whole idea of "Event Templates" duplicates the "Copy Event" functionality. I would be supportive of removing "Event Templates" altogether as a feature. Is there anythiing that Event Templates provides that Copy Event does not?
Hmm - I guess it would have potentially less data - ie a very long time ago I used them because I wanted to repeat events which were about 50-50 specific & non- specific data
For me it's the same reason we have Message Templates rather than just Reusing mailings.
If we copy an event we not only copy the "pattern" but also the "specific" elements for that event. And the template can include instructions for tailoring the event template, which would be lost in the copied event.
@ken I like the idea of including "instructions", but where do you put these instructions currently? In the actual event fields? As there's no capacity to provide instructions on any of the event tabs and I agree that this would be useful. Similar to the idea of CiviTutorial.
@mattwire thanks for the pointer to your awesome extension, CiviCRM Advanced Events. Lots of great ideas bundled in there, well done
However, as you probably know the problem still exists: custom field values are not saved for an Event. I'll try and get funding to have this bug fixed.
Just replying to myself here. Our client has refused to fund fixing this bug.
So at this stage, Event Templates can be used. But if the Event Template has custom fields, then the custom field values are not saved. This is fairly easy to miss too, since the user is redirected to the 2nd tab, away from where the custom fields would be displayed. So they have to click back to the 1st tab, scroll down and possibly expand a section to be see the problem. Given the steps required, there's a fairly high chance that this will go unnoticed.