Cachelite with one page about cachelite HOT 20 CLOSED

I would question the whole architecture design you have. Why not create actuall pages for your urls ?

Please remember that this extension works on a per url basis. It means that there is only one cache entry (one html result) per actual url and Conditionalizer breaks that rule.

I would consider splitting your DS across multiple pages and fetch the data via ajax (?) or use Cacheable Datasource, but I do not know how well it plays with Conditionalizer.

I am closing the issue since it's not a bug and there are no way to get what you are hoping for with it.

from cachelite.

That's fine I just didn't know where to pose the question. Building the site under one Symphony page allows my client to easily create one-off pages via a Section without having to do any Symphony XSLT work. That being said there are multiple URLs but everything is essentially coming from one single page. It sounds like (and my testing has confirmed this) that Cachelite will not work well in this scenario.

from cachelite.

@nitriques, if different URLs are in use, shouldn't this extension be suitable, even if only one actual Symphony page is in use?

from cachelite.

That being said there are multiple URLs but everything is essentially coming from one single page.

Sorry I miss that. The problem is, every time a single entry is created or updated, the cache needs to be flushed. I thjnk that Conditionalizer breaks that since what cachelite does is looking at which entries all datasources (that executed) returned in order to build the cache map (url -> entries relationship and url->section relationship). See

if different URLs are in use, shouldn't this extension be suitable, even if only one actual Symphony page is in use?

Yes and not. If the same url always returns the same entries from the same sections (with the same DB state) than yes it should. (but would still feel hacky to me),

Also, it might be a good thing to point out that the actual cache key is a hash of the $_GET array, sorted by keys, (see

from cachelite.

Just remebered that #19 as never been pulled.

I am reopening, since this may be why @jdsimcoe setup does not works.

from cachelite.

Still doesn't work 👎

from cachelite.

:( leave the issue open than!!

from cachelite.

Did you tried the latest integration branch https://github.com/symphonists/cachelite/tree/integration ?

from cachelite.

Yes I did. ?debug was also broken in that branch.

from cachelite.

Yes I know about that. This sucks... Which version of Symphony are you using ?

from cachelite.

2.5.2-rc1

from cachelite.

Can you update to 2.5.2 official (released 2 days ago) ?

from cachelite.

Why is debug broken? What happens?
On 7 Nov 2014 08:08, "Nicolas Brassard" [email protected] wrote:

Can you update to 2.5.2 official (released 2 days ago) ?

—
Reply to this email directly or view it on GitHub
#21 (comment)
.

from cachelite.

@brendo See #22. I've meant to fix this a long time ago... Will do it tomorrow...

from cachelite.

@nitriques Tested on 2.5.2 release and still doesn't work on my single-page site.

from cachelite.

Ok Thanks @jdsimcoe

from cachelite.

Can you post two cachelite files + there corresponding url and hash please ?

from cachelite.

@nitriques What cachelite files do you want me to post?

from cachelite.

Those in manifest/cache/ (the filename starts with cache_) Please give at least two with corresponding urls...

from cachelite.

All values from the $_GET superglobal are used to create the cache key. Maybe that's the problem. Closing for now.

from cachelite.