Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

AEM 6.0 SP2 / Components & Refresh Problem

Avatar

Level 2

We do have AEM 6.0 SP2 in test and authors are going crazy. Whenever they work on a component or copy a component hit the back button and go back to the site the content change seems to be lost but as soon as they hit F5 everything what they changed appears. This leads to a lot of frustration, has anybody similiar experiences or even a clue what the problem might be related to?

I see the following erros in the log :

com.day.cq.wcm.core.impl.PermissionsInfoProvider Unable to retrieve allowed user actions
javax.jcr.AccessDeniedException: Access denied at /xyz

They do have the same rights as with 5.5 and as soon as they hit refresh the page is changed and it's also possible to activate the page. Someone a clue what this could be?

1 Accepted Solution

Avatar

Correct answer by
Level 10

pbriner wrote...

We do have AEM 6.0 SP2 in test and authors are going crazy. Whenever they work on a component or copy a component hit the back button and go back to the site the content change seems to be lost but as soon as they hit F5 everything what they changed appears. This leads to a lot of frustration, has anybody similiar experiences or even a clue what the problem might be related to?

I see the following erros in the log :

com.day.cq.wcm.core.impl.PermissionsInfoProvider Unable to retrieve allowed user actions
javax.jcr.AccessDeniedException: Access denied at /xyz

They do have the same rights as with 5.5 and as soon as they hit refresh the page is changed and it's also possible to activate the page. Someone a clue what this could be?

 

 

When working in AEM - its not best practice clicking the back button. Instead - make the change that you want to to make in author with the page opened in a browser. Then move to the next page by opening a new page using the website console view (as shown here in classic view):

[img]components2.png[/img]

As a matter of fact - i never even see the back button enabled in a page opened in author -- as shown here:

[img]Website2.png[/img]

So please avoid using the back button in a browser. Instead navigate by opening new pages as shown here. This way - you will never have a component refresh issue.

  •  

View solution in original post

0 Replies

Avatar

Correct answer by
Level 10

pbriner wrote...

We do have AEM 6.0 SP2 in test and authors are going crazy. Whenever they work on a component or copy a component hit the back button and go back to the site the content change seems to be lost but as soon as they hit F5 everything what they changed appears. This leads to a lot of frustration, has anybody similiar experiences or even a clue what the problem might be related to?

I see the following erros in the log :

com.day.cq.wcm.core.impl.PermissionsInfoProvider Unable to retrieve allowed user actions
javax.jcr.AccessDeniedException: Access denied at /xyz

They do have the same rights as with 5.5 and as soon as they hit refresh the page is changed and it's also possible to activate the page. Someone a clue what this could be?

 

 

When working in AEM - its not best practice clicking the back button. Instead - make the change that you want to to make in author with the page opened in a browser. Then move to the next page by opening a new page using the website console view (as shown here in classic view):

[img]components2.png[/img]

As a matter of fact - i never even see the back button enabled in a page opened in author -- as shown here:

[img]Website2.png[/img]

So please avoid using the back button in a browser. Instead navigate by opening new pages as shown here. This way - you will never have a component refresh issue.

  •  

Avatar

Level 2

You are working with the multi window view which none of our over 300 authors uses because it's useless from their point of view and  I totally agree.

I guess it's quite a different behaviour whether you have to manipulate 5 pages a day or like some of our authors 300, not using the back button (or backspace how they do it) this simply saves you 300 x 1 Second per Day or half an hour per week. And as a matter of fact it works perfect in 5.5