devot:eeDevoted to ExpressionEngine

Hi!

I’ve been trying to get CE Cache to work for a while now. I’ve re-done the installation guide a couple of times, but to no avail. I’m at this point:

The static driver is showing up in the CE Cache Home. It is also writing files to the cache. However, when I’m browsing the website, it is still slow, and no debug information is being shown at the bottom. It seems like the driver is not being loaded?

I’ve tried replacing the %DOCUMENT_ROOT with my server path. Didn’t help.

My .htaccess containing the driver part looks (quite straightforward) like this:

I am using Transcribe for multi-lingual. Is that interfering maybe?

Cheers,
Rutger

I was correct in assuming that Transcribe was getting in the way. I had to adapt the ce cache tag to:

After this fixed my caching issue. I noticed that the cached entries broke my CSS link of the form:
http://www.domain.com/en?stylesheet - Since this served up the cached en/index.html file. I had to change:

<link rel=“stylesheet” href=”{stylesheet=embeds/stylesheet}”>

into

<link rel=“stylesheet” href=”{path=embeds/stylesheet}”>

Hi eboost!

I’m happy to see that you found the url_override solution and got everything sorted out.

I would highly recommend moving the style sheets from EE to flat files. EE literally loads dozens and dozens of files, and runs several database queries every time it runs. It’s a lot of overhead for simply serving up a style sheet.

Does that make sense?

Our static driver works fine on the homepage w/ Transcribe but on interior pages/templates this static tag:

{exp:channel:entries limit=“1” disable=“categories|custom_fields|member_data|pagination”}
{exp:ce_cache:stat:ic tags=“basic-content-{transcribe:language_abbreviation}|{entry_id}” url_override=”{transcribe:language_abbreviation}/{current_path}”}
{/exp:channel:entries}

Writes to the static folder but the URL does not read from it, thus taking the full load time when the URL is visited. When I take out the url_override parameter, the URL reads from the cache but the correct language does not pull up.

What can be the issue on the url_override parameter?

Also, can I use the {entry_id} as a cache breaking tag without wrapping the {exp:ce_cache:stat:ic} in an {exp:channel:entries} tag?

Thanks!

Hi ejaeDesign!

What can be the issue on the url_override parameter?

That static driver reads requests based on the Apache (or nginx) rewrite rules. If the URL matches up with the file path, it should work.

For example, if I cache an item using the static driver to “/test/ce_cache_static”, then Apache would look for “%{DOCUMENT_ROOT}/static/xxxxx/static/test/ce_cache_static/index.html”. If it finds that file, then it sends it to the _static_cache_handler.php file and displays the page.

Can you troubleshoot and see if your static item’s cache path and page URL match up?

Also, can I use the {entry_id} as a cache breaking tag without wrapping the {exp:ce_cache:stat:ic} in an {exp:channel:entries} tag?

I think you should be able to use the Add Tags tag anywhere in the page if using the static tag. Theoretically, this should work:

Hi Aaron,

Thanks for the quick reply! So this is what’s happening:

I double-checked the path to the static folder and that’s correct. I can confirm it by removing the url_override tag, which makes the page read from the cached file w/o a problem.

By adding the url_parameter tag, CE Cache creates an additional segment that corresponds to the hidden language variable used in Transcribe, as shown the screenshot.

So, Apache/htaccess/CEC cannot match the URL (/about) to the cached path (/en/about or /ko/about, etc.)

Is there a way to account for this extra language segment (“en”, “ko”, etc.)?

Thanks!

Also, thanks for the tip on the {add_tag} tag.

Can that {exp:channel:entries} be below the {exp:ce_cache:static} tag? If so, I can run it elsewhere in the template that already runs a {exp:channel:entries} loop.

Is there a way to account for this extra language segment (“en”, “ko”, etc.)?

If the URLs match the cache structure, it technically should work.

If you were to create a link to a transcribe page, what does the actual URL in the href look like?

Does it look like this?

Or does it have query strings, like this?

If the request to the server is “/en/about” then the corresponding cache item should be found if the URL matches it. If the URL is different, then I would need to know what it looks like to try to determine an .htaccess rewrite to match.

Can that {exp:channel:entries} be below the {exp:ce_cache:static} tag?

I believe the static tag can be added anywhere on the page and the tags should work.

Hi Aaron,

The URL looks like /about and not /en/about nor /ko/about on the front-end. For example, the following segment works for both EN and KO languages:

In other words, Transcribe does not show the first language segment (I believe it is ignored, like the Freebie segments).

So for the static cache, the front-end URL must match the cached directory like:

or

Thanks!

if you are using a separate index.php file for each language(a physical directory for each lang) then you’ll have be better off separating things using something like {exp:ce_cache:it id=“pagename__lang:{country_code}”}

Yeah, I agree that fragment caching is probably the way to go on this. Since some of the URLs don’t have any indication of which language they are for, there is no way for the .htaccess redirect to determine whether or not they have a cache file. The Transcribe docs say that the following works well:

I suppose you could specify an .htaccess rewrite rule for each language, and then the default. This is probably kind of okay for a language or two, but in general, I would advise against this:

The reason that is not a great idea, is that .htaccess could potentially check the server for 3 files every time a page is requested.

Note: You would replace the xxxxx text snippets in the code above with the actual hash from your static driver installation page.

Thank you very much for the guidance, both of you.

So, I went ahead and made sure Transcribe is saving the static content on /en and /ko directories and added the following to the htaccess file:

The page is still not reading the cache however:

https://new.theologyofwork.org/about

What could I be missing?

Hi Aaron,
We’re planning to go live early next week—would you mind taking a look at the htaccess I posted above?
Thanks!

For the record, I really don’t recommend this approach. But, since you asked, your .htaccess should look like this:

You’ll need to ensure that the ‘xxxxxx’ matches the correct hash for your site. You can figure out what that should be by looking in your Static Driver Installation Instructions page in the CE Cache module, or by looking at the folder path on your filesystem (it would something like “/static/ce_cache/xxxxxx/static/”, where the xxxxxx is the hash you should be using).

The above .htaccess assumes that you are caching your pages using the static tag like you had previously posted:

Also, be sure the update the hash in the _static_cache_handler.php file.

There are also setup and debugging instructions in the Static Driver Installation Instructions page in the CE Cache module page. Please check those too to see if any of those steps were missed or help to debug and correct a potential issue.

Hi Aaron,

Thanks for the detailed answer, once again. We still had issued with the methods posted above, so we simply made all KO entries have a unique URL.

However, now we have a different issue. We need the old URLs to redirect/rewrite to the new ones. For example, this URL:

https://new.theologyofwork.org/ko/old-testament/psalms-and-work/book-4-psalms-90106/human-creativity-with-god-psalm-104

Should go to:

https://new.theologyofwork.org/ko-old-testament/ko-psalms-and-work/ko-book-4-psalms-90106/ko-human-creativity-with-god-psalm-104

I was able to do this by adding the rewrites:

Above the default CE Cache rewrites (screenshot):

Now the redirect works but caching no longer does. How can I resolve this?

Thanks again!