[serendipity_event_entryproperties] still cached output?

[bernd_d]

I have used serendipity_event_entryproperties a while ago to cache entries...but after a few problems with caching i removed the plugin completely.

But now i mentioned, if i modify an old entry, it isn't changed in frontend even if i clean up templates_c and browser-cache.

Could it be, that field ep_cache_body from database is still used, even if the plugin is removed or disabled? Would be an ugly bug.

How can i fix this problem for the moment? Simply delete every ep_cache_* from database?

[yellowled]

if i modify an old entry, it isn't changed in frontend even if i clean up templates_c and browser-cache.

Are you 100% sure you're not behind some kind of (caching) proxy or something? I seem to recall similar issues with your blog in the past on your end which I could never reproduce, which could indicate some kind of caching mechanism in your network …

YL

[garvinhicking]

Hi!

Did you completely remove the entryproperties plugin, or simply disabled the cache option? Since caching is somewhat coded into the core itself, when the plugin is removed, it coulud be that the cache is somehow still used; but if the plugin is active and caching disabled, I think this shouldn't happen.

I'm sure we can get to fix this somehow

Regards,
Garvin

[bernd_d]

Are you 100% sure you're not behind some kind of (caching) proxy or something?

No proxys (as far as i know), different browsers, different networks (home, work). Don't know what else i could do. The current problems with modfied entries always has gone after i deleted ep_cache_* for the modified entry. Until now i didn't delete the complete database so it could be posible to reproduce it.

Did you completely remove the entryproperties plugin, or simply disabled the cache option? Since caching is somewhat coded into the core itself, when the plugin is removed, it coulud be that the cache is somehow still used; but if the plugin is active and caching disabled, I think this shouldn't happen.

I've removed it completely. Before this, i only disabled caching for a few days/weeks because of some strange issues i never could reproduce finaly.



...and for booth of you, i have made some screenshots from backend and frontend for this entry: http://bernd.distler.ws/archives/1273-F ... chten.html

backend

2012-12-28 12 28 15.png (44.03 KiB) Viewed 7591 times

frontend

2012-12-28 12 30 47.png (81.86 KiB) Viewed 7591 times

[kleinerChemiker]

I think, this is a very old problem, had it about 2.5 years ago (http://board.s9y.org/viewtopic.php?f=10&t=16564) No real solution, only to remove the cached results.

[garvinhicking]

Hi!

the short fix would be a SQL query:

Code: Select all

DELETE FROM serendipity_entryproperties WHERE property LIKE 'ep_cache_%'

That would delete the cache completely (it could be regenerated, you don't lose anything really).

I'll try to set this up to reproduce the issue on my server; but now I'm away for the next few days, so that might take some time

[bernd_d]

Thanks in advance

[Timbalu]

the short fix would be a SQL query:

Code: Select all

DELETE FROM serendipity_entryproperties WHERE property LIKE 'ep_cache_%'

That would delete the cache completely (it could be regenerated, you don't lose anything really).

I'll try to set this up to reproduce the issue on my server; but now I'm away for the next few days, so that might take some time

Garvin, did you find time to already investigate this issue and isn't this something we should fix in core and also maybe for 1.7?

[Timbalu]

Bernd, the uninstall cache purge is simple and should go through, if you have cache = true = enabled in your entryproperty plugin options. If not, the purge will not take effect.

[bernd_d]

So, it seems to be a bug. Cache should always be cleaned, even if Caching has been disabled before.

[Timbalu]

No. It's a feature, ... whyever... entryproperties - like Garvin said - is somehow "...coded into the core itself, ..." and still used when the plugin is removed ... until you know what you are doing...

[onli]

- is somehow "...coded into the core itself, ..." and still used when the plugin is removed ...

Sounds like a bug to me ;)

Besides, if the plugin really only cleans the cache iff the cache is enabled in the plugin, this is a bug on its own and probably easy to fix (just remove the if checking $cache).

[garvinhicking]

Hi!

Yeah, this can definitely be regarded as a bug. I only wanted to say it's more complex, because it's inside the core where entyrproperties are fetched, and that would need to be removed somehow. So it's just a bit complex and only affects a very small scenario. If someone would like to dig into it, of course I'd love a fix for this

Regards,
Garvin