Cacher allows you to move one or more pieces of content from one spot in your template to another. How is that handy? Well, have you ever had to use the same module tags twice (or more) on one page because there was no other way to place the content in all the places you wanted it?

That can be extremely wasteful, meaning your server has to work harder and your users have to wait longer to see the page. Cacher’s ability to place your content wherever you want it helps get rid of that problem.

Features:
* Move/copy chunk of content around in your template, without re-using tags.
* Move/copy them across templates.
* “Group” stuff and move/copy them around across templates or in the same template.

Download and View the documentation on my website

Hi Victor,

Looks interesting. Just wondering if you had any possible demonstrations of where this would come in handy?

As far as I know isn’t the $SESS cache just use-able for the page you are currently viewing? If so then it’s not like a true session variable is it?

Just trying to get my head around uses for this one as I like what you write!

Best wishes,

Mark

Mark Bowen - 25 July 2008 09:39 AM

Hi Victor,

Looks interesting. Just wondering if you had any possible demonstrations of where this would come in handy?

As far as I know isn’t the $SESS cache just use-able for the page you are currently viewing? If so then it’s not like a true session variable is it?

Just trying to get my head around uses for this one as I like what you write!

Best wishes,

Mark

Quick example:

Normall you will need 2 {exp:weblog:entries} call to have the entry title show up in the page title and somewhere else on the page. (or wrap your whole template with exp;weblog:entries, not possible under some situations)

What i do here is fetch the title, and make it display on 2 places with only 1 exp:weblog:entries call.

And yes $SESS->cache is only for the current pageview.

If you need some more examples.. i know a few more,
used this plugin countless time and speeds up some stuff up.

Victor very cool

Victor Gutierrez - 25 July 2008 10:28 AM

Normally you will need 2 {exp:weblog:entries} call to have the entry title show up in the page title and somewhere else on the page. (or wrap your whole template with exp;weblog:entries, not possible under some situations)

What i do here is fetch the title, and make it display on 2 places with only 1 exp:weblog:entries call.

Aha I get it now!!

Sounds pretty useful. Just wondering though does this make the system any noticeably faster than rather having the two weblog tags? Just wondering what the overall speed increase would be?

Thanks for the explanation by the way.

Best wishes,

Mark

Mark Bowen - 25 July 2008 11:03 AM

Victor Gutierrez - 25 July 2008 10:28 AM

Normally you will need 2 {exp:weblog:entries} call to have the entry title show up in the page title and somewhere else on the page. (or wrap your whole template with exp;weblog:entries, not possible under some situations)

What i do here is fetch the title, and make it display on 2 places with only 1 exp:weblog:entries call.

Aha I get it now!!

Sounds pretty useful. Just wondering though does this make the system any noticeably faster than rather having the two weblog tags? Just wondering what the overall speed increase would be?

Thanks for the explanation by the way.

Best wishes,

Mark

The {exp:weblog:entries} tag is the heaviest tag of them all.
Just calling it can produce 5 to 30 extra queries.

So on heavy pageviewed websites the {exp:weblog:entries} is a resource hog when used multiple times.
Sure that caching helps a bit…But in some situations..you cannot cache the whole page.

So limiting the use of {exp:weblog:entries} is a big winner for me

Of course this plugin works with all kind of tags.

Another example

What’s the difference between this and rEEposition?

alienne - 25 July 2008 01:53 PM

What’s the difference between this and rEEposition?

Let me try to explain:
All the stuff that reeposition does must be inside it’s tag {exp:reeposition}
So you need to wrap your content with it.

Cacher doesn’t have this limitation, it can parse stuff before it’s own tag.
And it can parse stuff in a parent template. (if the tag resides in an embedded template).

Reeposition also uses REGEX to fetch it’s data. Which is heavy.

Those are the main differences.

I can think of numerous situations Cacher is a better solution.
Of course reeposition has it own features too.

Nice one… I can see how this would be handy

Victor, does your plugin have a similar feature to rEEposition’s “group” parameter?

Released version 1.5.0

- Added “grouping” content functionality (request by smallbeer)

Download and View the documentation on my website

Hi Victor,

Is it possible to use Cacher in conjunction with EntryData?

Depending on how you want to use it.

Well, something like

I tried this already, but doesn’t seems to work.

Nico Smit - 02 October 2008 06:32 AM

Well, something like

{exp:cacher:put type="test_variable" text="{exp:entrydata:info url_title='{segment_1}' section='title' field_format='xhtml'}"}

I tried this already, but doesn’t seems to work.

The parse=“inward” parameter is needed.

Or you can always use the variable pair.

Hi Victor,

I downloaded and installed cacher And I tried to follow your example but I can’t for the life of me get this to work.

This is ny code.

any help would be great.

dchrist - 02 October 2008 11:45 AM

Hi Victor,

I downloaded and installed cacher And I tried to follow your example but I can’t for the life of me get this to work.

This is ny code.

{exp:weblog:entries weblog="{current_blog}" orderby="date" limit="1" status="draft"}

{exp:cacher:put key="my_cache" text="{title}"}

{/exp:weblog:entries}

<p>{exp:cacher:get key="my_cache" this_template="yes" here="yes"}</p>

any help would be great.

Yes this is a parsing order issue, EE loves to this kind of stuff.
Try this:

As you can see there is a hidden feature in the GET function, you can put the text while getting.

Thanks,

Worked like a charm.

Hi Victor,

It is not clear to me how content can be moved across templates. Should those templates be in parent-child relationship?

I have two templates: embedded template technical/embed and parent template technical/for_tests4. I need to move some stuff from embedded template into parent template.

I tried this code in parent template technical/for_tests4

and in embed template technical/embed this code

But this code did not output anything.