Hey, I'm no pro and learned things by studying them in production environment where each mistake meant loss.

But i think i have that test and trial bug, and a drive towards all this that helps.

Anyway, the problem is easy to replicate.

1. Go to sh404sef page under components in administrator panel.
2. search for "Click here to switch to extended display (with all available parameters)" and click the link. This will display the advanced options in sh404SEF Configuration.
3. Go to "sh404SEF Configuration".
4. There will be a tab that says "Advanced". Click it.
5. Activate the very first option under "Cache management" to activate cache.

Sidenote: I have SH404SEF extended mode enabled in master and slaves. This problem has a temporary fix i.e. don't use cache. But it puts drain on system resources.

I hope now you can get things going... While i don't use all the features of SH404sef, others might and you can test things in extended mode to see what all sh404sef does or you can wait for someone to report issues and then correct it.

But i would really appreciate if you can give a quick fix for the current issue before next release.

One more thing... when you test things always enable advanced modes to understand all the features.

Thanks

I have saw that sh404 version 1.5.5.388 also moved some peace of code into new files.
I will try reproducing this behavior in this sh404 version and will provide new patch for it.

Can you tell me which version of sh404 you are using.

I have SH404SEF 1.5.4.302

Thanks

Any update?

And again... Any update? (I have the same problem)

Would you please describe the problem.
Normally all the patches were released.
Which version of JMS and which patches definition do you have ?
Which version os SH404SEF are you using ?

Latest tested is sh404sef 1.5.5.388