This is a test to use a accessible button as the print trigger.
[print-me printicon="false" tag="button" title="print-me" /]
A Pluginoven Test Site
This is a test to use a accessible button as the print trigger.
[print-me printicon="false" tag="button" title="print-me" /]
As of version 1.1.2, multiple categories can be selected using the cat_id attribute. Simply provide a comma separated string of the category ID’s to include. Use a negative ID to omit multiple categories.
For example to include a yearly archive of posts with both the categories of ‘Archive-Pro-Matic’ (ID 55) and ‘collapse-pro-matic’ (ID 43) the shortcode would be:
[archives type="yearly" cat_id="55,43"/]
[archives type="monthly" cat_id="55,43" limit="10" /]
Shortcode using AFC’s get_field:
Age: [whats_my_age_again]
Shortcode function:
add_shortcode('whats_my_age_again', 'my_age');
function my_age($atts, $content = null){
if(function_exists('get_field')) {
$age = get_field('age');
return $age;
}
}
Testing a potential conflict with the get_field function from AFC and Annual Archive
Introducing a new attribute for Archive-Pro-Matic: highlight
Highlight accepts the following values:
Assigning ‘current-year’ as the value of the highlight attribute will add a current-year
class to the current year in the archive list. Assigning ‘active-year’ would only be assigned to the archive list when placed on an archive page.
We have added a bit of css to highlight each of the classes:
.current-year {
border-left: 2px solid red;
}
.active-year {
border-left: 2px solid blue;
}
Assigning ‘current-year’ as the value of the highlight attribute will add a current-year
class to the current year in the list:
[archives type="yearly" cat_id="4" limit="5" highlight="current-year"/]
Assigning ‘active-year’ would only be used on the archive page itself. To see this in action, first visit the an archive page, say 2014 and on that page place an archive list using the sidebar widget or following shortcode.
[archives type="yearly" cat_id="4" limit="5" highlight="active-year"/]
Of course this also needs to work with drop downs.
[archives type="yearly" format="option" highlight="active-year"/]
Here is a typical nested collapse group with highlander grouping
[expand title="state1" id="state1" togglegroup="state-highlander"]
[expandsub1 title="city1" id="city1" togglegroup="city-highlander"]bar1 bar2[/expandsub1]
[expandsub1 title="city2" id="city2" togglegroup="city-highlander"]bar3 bar4[/expandsub1]
[/expand]
[expand title="state2" id="state2" togglegroup="state-highlander"]
[expandsub1 title="city3" id="city3" togglegroup="city-highlander"]bar5 bar6[/expandsub1]
[expandsub1 title="city4" id="city4" togglegroup="city-highlander"]bar7 bar8[/expandsub1]
[/expand]
Notice how the main level and nested sub-elements have their own highlander grouping defined. This makes it so the main level items do not affect the nested children expand/collapse states.
This is how it works:
Now to do the exact same thing using the roll-your-own method:
<div class="collapseomatic" id="state1" title="state1" data-togglegroup="state-highlander">state1</div>
<div id="target-state1" class="collapseomatic_content">
<div class="collapseomatic" id="city1" title="city1" data-togglegroup="city-highlander">city1</div>
<div id="target-city1" class="collapseomatic_content">bar1 bar2</div>
<div class="collapseomatic" id="city2" title="city2" data-togglegroup="city-highlander">city2</div>
<div id="target-city2" class="collapseomatic_content ">bar3 bar4</div>
</div>
<div class="collapseomatic" id="state2" title="state2" data-togglegroup="state-highlander">state2</div>
<div id="target-state2" class="collapseomatic_content">
<div class="collapseomatic" id="city3" title="city3" data-togglegroup="city-highlander">city3</div>
<div id="target-city3" class="collapseomatic_content">bar5 bar6</div>
<div class="collapseomatic " id="city4" title="city4" data-togglegroup="city-highlander">city4</div>
<div id="target-city4" class="collapseomatic_content">bar7 bar8</div>
</div>
The roll-your-own method has already been documented, however, what if you wanted to create your own sroll-to targets for each element? How can we do this with roll-your-own?
First we create an example using the shortcode:
[expand title="trigger text" findme="auto"]hidden content[/expand]
<div class="collapseomatic find-me" id="my_example" title="trigger text" data-offset="-60" data-findme="auto">trigger text</div>
The Target
<div id="target-my_example" class="collapseomatic_content ">Target Content</div>
As of version 1.6.7c we introduced a new printstyle value ‘external’ for Print-O-Matic. Now it is possible to create an external button to trigger a print in a less-hacky way. Here is an example of this works: To print the following div with an id of ‘print_me_please’:
<div id="print_me_please">This is our target print element</div>
First we create a kind of roll-your-own print trigger. The details that must be included are:
printomatic
or printomatictext
data-print_target
attributeFor example:
<button id="my_print_button" class="printomatic" data-print_target="#print_me_please">Print Trigger</button>
Which will output:
The final thing we need to do is include a hidden print trigger using a print-me shortcode with the same id as our external trigger and the new external printstyle attribute. This shortcode must be placed someplace on the same page, and will load in all the required scripts and settings to make the print trigger work correctly.
[print-me id="my_print_button" printstyle="external"/]
Here it is:
[tminus cid="1031"]
Test of the new Template feature in Collapse Commander. Template 1885 should expand the target above the trigger.
[expand title="Trigger Text" template_id="1885"]This is a test using template number 1885[/expand]
Example using cid:
[expand cid="2039"/]
Alt Test
Expand Trig:
Expand Targ: