Tom_Fought
Tom_Fought
06-03-2019
Looking for some direction here.
I have created a Touch UI component that works normally for editing the component properties, but:
What am I missing here?
Thanks for your assistance.
smacdonald2008
smacdonald2008
06-03-2019
Is this behavior observed in only this component or in all custom TOUCH UI components.
Are you seeing any browser errors?
This should not be occurring.
Tom_Fought
Tom_Fought
06-03-2019
Quick check with the OOTB text component and text/image component. Seeing same behavior.
smacdonald2008
smacdonald2008
06-03-2019
This certainly should not be happening. As you know - as soon as you a component onto a page - the component should be visible immediately. Are you seeing any log errors or browser errors.
smacdonald2008
smacdonald2008
06-03-2019
I am checking too if this is a known issue.
Prince_Shivhare
Prince_Shivhare
06-03-2019
If it is for specific one or two component, please use listeners.
How to refresh a page when a component is modified
few things:
1. Please check error log or console once component is drag n drop to a page. It can be a problem with page.
2. Restart AEM and check if issue still exists.
~ Prince
Tom_Fought
Tom_Fought
07-03-2019
Thanks for further ideas on this.
I created a clean 6.2 and 6.4 authoring environment. Loaded the touch ui component into the environments and proved the refresh works properly for add, delete, and modify.
Guessing it must have something to do with our templates and possible jquery/javascript conflicts.
Tom_Fought
Tom_Fought
07-03-2019
This has been marked "Assumed Answered" yet I still have the problem.
Even though the OOTB AEM works as specified, my instance is not working and I am looking for leads to resolve the issue.
When I discover the solution I will post it here.
smacdonald2008
smacdonald2008
07-03-2019
AS you specified - this looks like a lib conflict on this specific instance. A fresh instance - as you said - you are not seeing this behavior.
To get more background - did this start happening all of a sudden or after a new package was installed.
Tom_Fought
Tom_Fought
08-03-2019
We are just starting to work with Touch UI and found this issue occurring. So no idea when it started in relation to any change.