13
Stash and Low Variables are complementary.
Low Variables
Essentially a replacement for native snippets and global variables. Provides a control panel interface for managing variables. Variables may be considered content - text values, matrix data, default images - or code, such as a tag that outputs your primary navigation or contains your footer markup.
...
7
For any variable that needs extra processing, like the Wygwam variable type, use the tag syntax rather than the variable syntax:
{exp:low_variables:single var="my_wygwam_var"}
Note that having early parsing on or off is irrelevant for the tag syntax, so you can leave it off.
6
The variables inside the field need to be prefixed with the Grid variable name, like this:
{lv-home-slider:slide}
{lv-home-slider:caption}
5
Okay, this definitely is an Assets issue, but here's a temporary fix.
Open up ft.assets.php and look up the grid_replace_tag method, around line 1771. In there, you can see this line of code:
$field_name = ee()->db->select('field_name')->from('channel_fields')->where(array('field_id' => $this->field_id))->get()->row('field_name');
...
4
To make sure extra processing is done before the var is put in the template, use the tag syntax rather than the variable syntax:
{exp:low_variables:single var="my_wygwam_var"}
4
Adding a custom CP navigation tab is the best way to do it. But as you said it is tedious to log in as each individual user and manually create the link. There are two add-ons that will enable you to do it on a per-member-group basis.
1) Member Group Tabs
This extension allows you to create navigation tabs for entire member
groups in the ...
3
OK - got it working by using :parse in a tag pair around the channel:entries tag:
{exp:low_variables:parse var='default_site:gv_ft-featured-stories'}
{exp:channel:entries site="default_site" channel="project_news|projects" limit="1" entry_id="{gv_ft-featured-stories:data}" orderby="date" sort="desc" dynamic="no" disable="category_fields|member_data|...
3
Okay, first, turn off early parsing for the myassetsimage variable. Then try and use Asset's {url} variable (see docs) in CI Img's src-parameter instead of the Low Variables name. That means that your code would look like this:
{exp:low_variables:pair var="myassetsimage"}
{exp:ce_img:pair src="{url}" width="640" height="400" class="img-polaroid" alt=""}
...
3
I hear what you're saying about automating but in reality just how many holidays do you honour? It's not going to take too long to do it manually.
I would create a channel for holidays and create an entry for each holiday with the entry and expiration dates set.
Then on your template use a channel entries tag pair with show_future_entries="no"
In theory ...
3
You can use the Search parameter to return only rows that have the checkbox cell checked.
{exp:low_variables:parse var="lv_homeslider" search:name_of_checkbox_cell="true"}
{total_rows}
{/exp:low_variables:parse}
"true" should be the actual value that you entered under "Multi-Select Options" in the checkbox field/cell settings.
3
Enabling Save As Files in Low Variables does have a slight performance impact. In order to tie in to native EE functionalities, LV needs to update the native exp_global_variables table with the data gathered from the files. This means, in contrast to what jchrono-battle is saying, EE does not load from the DB or filesystem, as far as LV is concerned. Rather ...
2
If you are manually editing the options of the custom field, why not replace <p>Description One.</p> etc with low variables? (Separate text fields, not a matrix field)
{if custom_field =="Option One"}{lv_description_one}{/if}
2
I would check to see if you have mod_security installed on your server. That seeing the http:// in your form post (saving LV) may be triggering the save to be blocked.
2
Low Variables are stored in the exp_low_variables , exp_low_variable_groups and exp_global_variables tables.
You can dump these tables from your previous build into your new project.
Note that it won't work for complex Low Variable types that store their data in their own database tables, like Matrix/Grid.
2
I'd suggest reuploading the Matrix theme files. It's possible they were missed or corrupted if you recently upgraded.
2
Try making this a global variable in your config file, then you can do all the date checking in PHP. Go to http://www.epochconverter.com/ and get the start and end date of when you're closed, then add this to your config.php file.
if (time() > 1387497600 && time() < 1388016000) {
// Use this in your template {hours_open} and it'll show if ...
2
You can't. Global variables (which LV are, essentially) aren't searchable by the native Search module, nor by any 3rd party search add-on that I know of.
2
Andris was close to the solution:
Add the following code right above the switch statement.
`if (($context == 'grid' || $context == 'matrix') && !empty($this->var_id))
{
$context = 'low';
}`
Then in the 'low' case (around like 163) change the query to:
`$sql .= " ae.var_id = {$this->var_id} AND ae.row_id = '{$this->row_id}'";`
Now ...
2
You could try two things:
One is to set this particular Low Variable as Early Parsed (in the variable settings). Then you can call it like this:
{exp:cartthrob:arithmetic expression="{option_price_numeric} -({option_price_numeric} * {early_bird_discount} / 100)"}
Or you could try adding parse="inward" to the arithmetic tag:
{exp:cartthrob:arithmetic ...
2
I'll quote the docs here:
Please note that only non-hidden and variables with early parsing disabled show up in the variable list in the Publish Form.
So, make sure the vars you want to select are not hidden and have early parsing disabled.
2
Looking at the content of your lv_article variable, you could just use the variable syntax instead of the tag syntax:
{lv_article}
Having early parsing enabled has no effect when using the tag syntax, only when using the above variable syntax.
2
This is what the assign_to_config array in your main index.php file is for (assuming you're not using something like FocusLab Master Config, which makes multi-environment really easy). If you don't want to use that approach, the quick way is to just crack open your index.php file, scroll down to the bit where assign_to_config gets set, and create some global ...
2
This will be fixed in the next version. In the meantime, if you make sure all columns are not required, you can avoid the issue, too.
2
I just ran into this. All my grid fields were set as required, so leaving any field empty when saving removed the images. Adding data to all fields (including images) and it saved ok.
2
You might be able to do this with the help of Math:
{exp:low_variables:parse
var="banner_ads"
offset="{exp:math formula='{count}-1'}"
limit="1"
parse="inward"
}
2
Using an early parsed var (or a Snippet for that matter) like that doesn't work. To illustrate, using the var you geva as an example, and using it like this:
{exp:low_events:entries entry_id="not {lv_exclude_id}"}
...
{/exp:low_events:entries}
...will result in this code when we come to the stage where tags are parsed:
{exp:low_events:entries entry_id=...
2
You could try and use the playa:children tag instead of the Parse tag:
{exp:playa:children var="lv_book_slider_en"}
{title}
{/exp:playa:children}
2
Adding to this, I had to put transcribe=“disable” inside of the Playa tag (not the ece loop) to get it to output. Credit goes to EE Harbor.
2
You can, but you will have to use the Parse tag or one of its aliases:
{exp:low_variables:single var="my_site:my_var"}
2
Check out the Variable creation options bit. Batch creation of multiple identical vars happens when using multiple suffixes when creating a variable.
Only top voted, non community-wiki answers of a minimum length are eligible