cancel
Showing results for 
Search instead for 
Did you mean: 

caching gone wrong - PageNotFoundException

sam1980
Champ in-the-making
Champ in-the-making
Hi.

I'm experiencing strange behavior for page lookups in my wcmqs-based web site. The first thing I've noticed is that content may be available by multiple variations of its given id. I.E a content element  created on root with the id "test" is accessible on the website by the path /test (as expected), but can also be accessed by the url /testa, /testar, /teste and so on.

The second, and more serious issue, is that content previously available by an url all of a sudden starts to respond with 404 (as a PageNotFoundException is thrown). Trying to resolve the content item's in other parts of the site (as in related content listings) it actually resolves to the non-working url.

If I try to change the id, the content becomes accessible on the new url. But in listings it still resolved to the old url.

Is there a way to flush the cache to see if this might play a part in this behavior?

Grateful for any feedback on this matter.
3 REPLIES 3

bremmington
Champ on-the-rise
Champ on-the-rise
What version of Alfresco are you using?

sam1980
Champ in-the-making
Champ in-the-making
Sorry. It's 3.4.4 Enterprise

bremmington
Champ on-the-rise
Champ on-the-rise
Apologies for going silent on you. It suddenly became very busy in Engineering.

Unfortunately, I can't reproduce this problem. Is it still occurring? If so, are you in a position to try it on 3.4.6? There were a few changes to WQS between 3.4.4 and 3.4.6, although, to be honest, I can't see anything that might have affected the area you're reporting problems with.