EVO 3.1.7 page caching issues

[fourroses666]

I have updated a website with YAMS from 2.0.4 to 3.1.7 and all looked to be working.
But it seems there is weird behaviour on the site.

When i browse the site the alias is okay but on some pages I keep seeing a different page.
Only when I save a random page in the manager and refresh the page/alias on the front of the website the correct page is being previewed.

I really have no idea what's going on. Tried allot to fix it like disabling caching etc. but it still keeps having the weird behaviour of showing the wrong content!

Need to revert the site now and will try again but I think there is something not working well..

[Deesen]

I also have no idea or overview of changes on EVO3 that could be the reason for such an issue. Maybe YAMS-plugin in wrong order or some other plugin interfering with it?

[fourroses666]

That's something I didn't check yet. (order). YAMS plug-in as first or last? If I remember correct it has to be first.
Doubt other plug-ins interfer but its worth a try too! Thanks.

I do suspect some settings which EVO 3 uses different. Many Configuration settings stopped working.

So you have no EVO 3 and YAMS sites?

[Deesen]

Here from the README.md :

5. Make sure that your YAMS plugin is set-up to be active on all the events described in the installation instructions below.
6. Check that YAMS always appears first in your plugin execution order for each event that it is active.

And no, I have none. Maybe you can send temporary FTP- and Manager-Login so I can "have a check" myself.

[fourroses666]

Hmm. Seem to have the same issues on an other test site which has the latest version.
So YAMS is not correctly working with EVO 3 or at least not with the installed plugins.
I will mail you a login and you can freely test that site, its going to be deleted anyway.

[Bahbv]

Hi @fourroses666 since YAMS is deprecated im searching for other posibillities. But the problem you described is something I've encountered myself on 2.0.4 as well. What worked for me is switching to the [(cache_type)] setting to "Based on doc id (standard)" found in the configuration.

[fourroses666]

I don't have the issue on a 2.0.4 site.
Also the [(cache_type)] doesn't help for me. It is already set on "docid standaard"

[Deesen]

But maybe this is the required hint for me to find out what exactly is going on. I cannot refactor whole YAMS but maybe just some small tweaks/fixes are needed. I hope I find some time soon to check this issue.

[fourroses666]

If there are any updates let us know :)