Issue saving page properties | Community
Skip to main content
jkpanera
Level 4
March 13, 2020
Solved

Issue saving page properties

  • March 13, 2020
  • 2 replies
  • 3785 views

Hi guys,

I'm having an issue saving a page properties in 6.3 using touch ui. I navigated to the page using site.html and clicked properties. I changed the property and clicked Save & Close, but nothing happens. I can edit the property using crx, but touch ui does not work.

 

There are no log messages either (perhaps I need to turn up logging but which package?).

 

Any help is appreciated.

 

Thanks!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by BrianKasingli

@jkpanera,

If the page cannot save properties when the "save" button is clicked on, there is definitely some kind of error happening. Errors like what you are experiencing must exist in 2 places: browser console and error.log. 

Can you please provide a screenshot of the errors in:

  1. Browser Console
  2. ./${aemJAR}.jar/crx-quickstart/logs/error.log - for the Stack Trace.

Once you understand the errors from the logs, it should give you more information on how to fix the problem. From a quick glance, the problem can exist because of invalid the Touch UI dialogue configuration.

2 replies

BrianKasingli
Community Advisor and Adobe Champion
BrianKasingliCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
March 13, 2020

@jkpanera,

If the page cannot save properties when the "save" button is clicked on, there is definitely some kind of error happening. Errors like what you are experiencing must exist in 2 places: browser console and error.log. 

Can you please provide a screenshot of the errors in:

  1. Browser Console
  2. ./${aemJAR}.jar/crx-quickstart/logs/error.log - for the Stack Trace.

Once you understand the errors from the logs, it should give you more information on how to fix the problem. From a quick glance, the problem can exist because of invalid the Touch UI dialogue configuration.

jkpanera
jkpaneraAuthor
Level 4
March 26, 2020

Okay so what was going on is that a required page property was not filled out. The thing that was confusing is that the required field was on another tab, so I couldn't actually see it. There should be a banner/snackbar/something so that it is easier to see even when on other tabs.

BrianKasingli
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
March 27, 2020
Yup, typically when you include the property of "required=true", then the Touch UI dialogue will highlight the field in read, along with it's parent tab (if any).