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
There is a bit of a bug in Playa that impacts Low Variables:
exp_playa_relationships has parent_var_id field. It's supposed to be either 0 or 1. Low Variables sets it to NULL due to an oversight in our code. The solution was to set the column to 0 for rows, that were not 1.
We'll have a fix for this included in Playa in the future, but for right now, ...
4
I fixed this issue. It was/is a bug in Playa. Pixel and Tonic now knows about it and will include a fix in the next release. In the meantime, here is my solution:
Change Line 2484 of ft.playa.php to...
$data = array(
'parent_var_id' => $this->var_id,
'parent_is_draft' => 0
);
Basically added 'parent_is_draft' => 0
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 ...
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"}
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
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
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
This Stack Overflow post has an answer from Low that should work for you.
Here's how: make sure early parsing is enabled for that variable, and then use the variable syntax instead of the tag syntax:
{exp:channel:entries channel="groups" entry_id="{lv-home-groups}"}
code here
{/exp:channel:entries}
2
If you look at the Nesting quote Siebird posted, you'll also need to know what the different stages (1, 5 and 9) mean.
Stage 1 is for early parsed global variables: Low Variables with early parsing enabled and in variable syntax: {lv_my_variable}
Stage 5 is for tags: Low Variables using the tag syntax: {exp:low_variables:single var="lv_my_variable"}
Note: ...
2
I'm pretty sure this has to do with the way Low Variables parses nested variables. You may need to add both of these variables to the same group and in the right order for them to parse correctly: {lv_footer} should be above {lv_hours} in the same group
Nesting
[cue Inception music] So, there are three stages at which a Low
Variable can be parsed:
As early ...
2
try setting the is_draft column in exp_matrix_data table to NOT NULL with the default of 0. This will be fixed in the next Matrix version.
2
Is {lv_sidebar_featured_members} set to 'early parsed'? If it is, the problem could be that it contains a channel entries tag and you are nesting it inside another channel entries tag.
2
Try {exp:low_variables:parse var="lv_sidebar_featured_members"} instead of {lv_sidebar_featured_members}
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
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
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
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
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
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.
Only top voted, non community-wiki answers of a minimum length are eligible
