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.
...
11
Turns out my problem was the {exp:low_variables:pair} tag was nested in a {exp:channel:entries} tag. To fix this you have to use the var_prefix="" parameter.
{exp:low_variables:pair var="lv_my_image" var_prefix="assets"}
{assets:url}
{/exp:low_variables:pair}
With this syntax you can access all of the Assets' tags.
{exp:low_variables:pair var="...
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
Have you considered another of Low's add-ons? Low Yearly Archives
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
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
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
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
It's to do with the good old parse order. To get around it use the short version of the tag together with early parsing and it should work so simply {my_var} instead of e.g. {exp:low_variables:single var="my_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
The variable syntax, {lv_my_variable}, doesn't support any additions or variations like that. It's like a Snippet or Global Variable: just as is. For extra processing, you'd need to use the tag syntax: {exp:low_variables:single var="lv_my_variable"}.
However, getting to additional options like the :has_excerpt function is up to the fieldtype author to ...
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
Let me quote the docs:
Please note that only non-hidden and variables with early parsing
disabled show up in the variable list in the Publish Form.
This goes for Matrix fields as well. Make sure the variables you want to select from aren't hidden nor have early parsing enabled.
2
I have run into this problem also. The developer of Expresso has indicated that this is not supported and might never be.
While I don't have a solution, I did some tests to see if any other "wysiwyg"-style fieldtypes support this. Here's what I found:
Native RTE: No
Expresso: No
Wygwam: Yes
Wyvern: Yes
Redactee: Yes
Editor (DevDemon): Yes
2
Can't create/write to file '/tmp/#sql_a34_0.MYI' (Errcode: 28)
"Errcode: 28" means MYSQL can't write to the tmp directory because it is full. You'll need to contact the host to have them fix the issue.
2
You can do this in two ways, both require that you turn off early parsing for the form variables, and assuming you're using regular Textarea LVs. Once turned off, use the tag syntax instead of the variable syntax, thus:
{exp:low_variables:single var="form-{segment_2}"}
The variables should now turn up in the LV Fieldtype as well, so you can use the ...
2
Looks like a mod_security thing. Hard to trace and figure out exactly what triggers it. Check this thread on GetSat and ask your host to disable or add an exception.
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
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
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
I'd suggest reuploading the Matrix theme files. It's possible they were missed or corrupted if you recently upgraded.
Only top voted, non community-wiki answers of a minimum length are eligible
