5

I recommend using SEO Lite. It will save you from having to open up a channel:entries tag just to grab the title. Plus it can be used for a meta description tag (which is also useful for og:description and social share text). And it has a variety of useful parameters to help you pull the right title and to add prefixes or suffixes to your title. Just ...


4

You'd be better off just 'stashing' the image urls and using the CE Image tag from within the layout. Article {f-archive-images} {exp:stash:set_list name="images"} {stash:url}{f-archive-images-image}{/stash:url} {/exp:stash:set_list} {/f-archive-images} Layout First image: {exp:stash:get_list name="images" limit="1"} {exp:ce_img:single src="{...


3

@Jae - You can use rules in the same way with CE Cache. The parameter tag= allows to you add tags and then in the cp, control when they are refreshed - hope that helps. In terms caching and partials, I use CE to cache the wrapper with the parameter global="yes" and then escape the stash:get. Then within the stash:set cache the page. I also set the caching ...


3

I'm really confused by your question, but I'm going to make an attempt at clarifying some base concepts that I think you are wrongly assuming about a commercial grade CMS (content management system) like ExpressionEngine, and CMS's in general (possibly, not trying to say you don't know what you are doing). First of all, this is a content management system. ...


3

The easier and faster way to do this is using Preload Text Replacements and snippets. Snippets are parsed before Preload Text Replacements. So you can put them inside snippets. Let me show you an example. This is part of a snippet called doctype-and-styles-snip: {preload_replace:pre-rootclass=""}<!doctype html> <html class="no-js no-jquery {if ...


2

Depth isn't an issue with embeds and neither is URLs, so if the embed works from template A, it will work from Template B. So it isn't any parameter issue (unless you use embed variables in the parameters - see 2 below). Three factors that are most likely: The embed in Template B is within a conditional which is not being met. You're passing embed ...


2

This is a common question and there is a technique you can use with the add-on "Stash." It's already been described and documented multiple times. Check out the selected answer for this other, similar question: How to use a common template for all pages?


2

You should try separating the data-fetching from the markup-assembly - this way you'll be able to cleanly fetch all your member variables and store them into Stash vars for use later (either in the same template or an embedded one). Here's a tutorial I wrote describing how to do this: http://www.jamessmith.co.uk/articles/expressionengine-stash-tutorial-level-...


2

The Variables plugin is a good option for passing data to the header embed. The variables plugin gives the possibility to create variables (either static or dynamic) and use them later on. This means that for example you can set certain data and use it in the head (if it's embedded) without having to re-create a tag pair for the specific channel. ...


2

Tags inside parameters aren't parsed at all unless you use parse="inward". That's because once parsed a tags' parameters are removed from the template (replaced with the output of the tag). Thus tags in parameters are never parsed. The parse="inward" parameter tells EE to parse the other parameters passed to the parent tag before they are received by the ...


2

There's no need for conditionals as the fields are mutually exclusive. With Stash on the inside of channel:entries tags there's also no need for parse_tags or parse_depth since the enclosed content contains no tags. (The custom fields are variables, not tags). Otherwise it should still be fine the way you have it. Personally I prefer putting Stash on the ...


2

So if you only want a snippet to display on certain entries, you can apply that via a field and small code addition to your template(s). I understand you have a lot of templates and don't want to add more; there is no reason to add more. You can just edit the templates you currently use for these entries, and they'll work either way. In this example, just ...


1

It is possible with a bit of messing around you could achieve what you are trying to do by installing the Allow EE Code add-on. This add-on makes it possible to evalute EE template code placed within entries in EE channels - to use you simply bracket the template output you want to have evaluated between an {exp:allow_eecode} tag pair. So it might be that ...


1

If you are in a model (Any backend PHP file). You can do something like, $data = ee('Model')->get('ChannelEntry', "82")->fields('title', 'field_id_118')->first(); $product_minimum_order_value = ""; if($data) { $product_minimum_order_value = $data->field_id_118; unset($data); }


1

Here's another example that I hope will help others with similar confusion (as I was until about 15 minutes ago). I was recently trying to get the following template to work: {exp:app:voucher hash="{segment_3}"} {exp:pdf_press:parse_pdf filename="{product_url_title}-voucher.pdf"} <html> <body> ... </body> </...


1

In stash builds, I would use stash embeds for things like sidebars, etc. so maybe not as granular as CTA buttons. In those cases, I use them with the process=start parameter, which makes them act pretty much like EE snippets and include them in the other template before any other EE tags are parsed. Using that, I often don't need to pass variables around. ...


1

Very late response here, and not quite an answer. In your case you want to cache all these things, in mine I want them to behave as functions, basically. However it's in the same area so I thought might be useful for the discussion. I use stash in a functional way all through he site I am developing. I guess coming from a programming background I just ...


1

A simple solution for this would be to simply add a select dropdown to the publish page with each of your wrapper templates listed. So for example, if your select dropdown field is called {wrapper_template}, your template code would look like this: {exp:channel:entries channel="ch-archive" limit="1"} {embed="{wrapper_template}"} {exp:stash:set name="...


1

One possible option might be to add a variable on the wrapper embed, which passes a value for the template being accessed. Within your wrapper, switchee could be used to adjust markup. Using your sample above: {embed="_wrappers/homepage" template="templateA"} Within your wrapper, it could then be utilized such as this: {exp:switchee variable="{embed:...


Only top voted, non community-wiki answers of a minimum length are eligible