So you have an event, such as a seminar or webcast, and you need to change the date. Or you need to change the URL of a page for some other reason. But the event is already live on the site.
What do you do? The answer is amazingly simple.
Nothing (just like Seinfeld).
Just ask someone on the Web Team for help. It's great if you want to tackle it yourself, but trust us, it's much easier for everyone if you don't.
Especially if you think it will save time. It won't.
If you're satisfied with just the word "nothing," you can skip this next part.
As you may know, the JMP website operates in levels. At the top level there's the Blueprint site. Everything underneath that is a livecopy site. AEM is very finicky about keeping the blueprint and the livecopy pages in sync.
If you rename a page on the blueprint site, that puts it out of sync with the live copy. Which is why when you test registration, the confirmation page and the reply emails no longer work.
In order to fix it, we have to pop the hood and muck around in stuff we typically don't like to touch. Because then we could break something else by accident. Not good.
Any time you have something out of the ordinary (especially if the page has already been published), just ask us for help. We'll be glad to answer questions or, if need be, do it for you. We're always glad to assist!
I've posted the blueprint diagrams that are referenced above. They can be found here...
https://community.jmp.com/t5/AEM-Author-Training/AEM-Rollout-and-TMS-Structure-Diagrams/ta-p/54321
I'd also like to discuss training authors to help them better understand the pitfalls of creating events in AEM. I see three basic pain points...
- Parent pages (at the blueprint) need to be activated (or at least rolled out) before children. If children are activated before a parent (for the first time), the rollout workflow fails because the parent structure is not yet in place at the live copy. So... actiavte parent first, then children.
- Rescheduling previously activated events (changing a page name). If a page has not yet been activated, there are no worries with changing/moving file names. However, if the page HAS already been activated, changing its page name ("moving" in the edit config) and reactivating it WILL CREATE A SECOND PAGE at the live copy. Both will be connected to the same blueprint page, but each with have a different page name (and both will appear on the live site). The solution (I think) is to have authors DEACTIVATE a page before renaming previously activated events. And ALSO MAKING SURE that any children get reactivated AFTER the name change is activated. Worth further discussion...?
- Always test your events! You want to make sure the live site is working as intended AND that submissions are getting to the SF campaign.
- More pain points?
Hey Roger, nice work! I recommend including the blueprint diagram in this post, or linking to a post about it.
