Year: 2019

August 2019

February 2020

Leo Love and Sex

Leo’s, being of a Fire sign, are heartfelt and passionate, being capable of expressing their feelings effortlessly and with transparency. Toward their beloved they […CLICK TO EXPAND] are giving, respectful, devoted and fun. They are strongly independent and driven, and so will try to be the dominate party of the relationship. The partner of a Leo may grow tired of being domineered, in particular if the Leo imposes their will upon matters that are not of their concern. In order to tolerate the Leo’s strong imposing will, the partner of a Leo needs to be learned and at an equivalent intellect. They also need to be willing to speak up for themselves and to defend their ground, else the blazing Sun of the Leo will scorch their personality. The Leo’s sex life is dynamic, fun and adventurous. They are very aware of the fine line separating love and sex, which can cause them trouble within an established relationship if they too often neglect to show intimacy or connect emotionally with their partner during love making. Ultimately, Leo’s want that their partners peer past their self-centered shell and look deep into their subconscious sensitive core, so as to search out their want of satisfaction resulting from a purposeful relationship. Leo Love Compatibility: Aries, Gemini, Libra, Sagittarius! [CLICK TO HIDE]

This is a test for integrating T(-) Countdown with Gutenberg Blocks.
First, we need to tidy up how the Javascript is being used. Here is a basic countdown that uses a gutenberg block set to 2 minutes.

Now let’s try a shortcode with a launch target of an external element.

[tminus t="+10 secs" launchtarget="#monkeymonk"]monkey is in space… space monkey![/tminus]

Of course, we can still use the old countdown (default), above and below targets:

[tminus t="+10 secs" launchtarget="tophtml"]this is the tophtml target area[/tminus]

[tminus t="+10 secs" launchtarget="bothtml"]this is the bothtml target area[/tminus]

Test 1: [expand tag="span" title="this is a span: hey dude"]…did you like that[/expand]

This is a quick test to try out the new years and month options added in version 2.3.20… this looks like it might end up being version 2.4.0 at this rate. Yup, it will be a major release.

Test 1 – Show it All

This test should show everything: Years, Months, Weeks, Days… and the rest.
[tminus t="+410 days +10 sec" style="c-3po"/]

Test 2 – Omit Years

This test will omit the years, resulting in expanded months.
[|tminus t="+410 days" omityears="true" style="c-3po"/]]

Test 3 – Omit Months – Keep Years

This test will display the years, but convert months to weeks.
[tminus t="+410 days" omitmonths="true" style="c-3po"/]

Test 4 – Omit Years and Months

The title, pretty much says it all. No years, no Months… just a whole lott’a weeks:
[tminus t="+410 days" omityears="true" omitmonths="true" style="c-3po"/]

Test 5 – Omit Years, Months and Weeks

Days for days…
[tminus t="+410 days" omityears="true" omitmonths="true" omitweeks="true" style="c-3po"/]

Test 6 – Omit Weeks Only

No weeks, but the rest.
[tminus t="+410 days" omitweeks="true" style="c-3po"/]

Test 7 – Omit Months and Weeks

No months, no weeks.
[tminus t="+410 days +10 secs" omitmonths="true" omitweeks="true" style="c-3po"/]

Test 8 – Omit Years and Weeks

No years, no weeks.
[tminus t="+410 days" omityears="true" omitweeks="true" style="c-3po"/]

This is a test of print-pro-matic using wp_localize to pass js vars to the js file. it also passes print-only elements.

Like this one with the .printonly class listed in the shortcode

And here is the shortcode:
[print-me print_only=".printonly"/]

Actually, this should not be passed via shortcode, but rather only defined in the option page.
[print-me /]

This is just a simple test where we pass some pause_time and a special target

[print-me target=".print_this" do_not_print=".printomat" pause_before_print="4000"/]

This is a test where a scroll-to target will open an expand, however will then scroll back to the top of the page–or actually an element at the top of the page defined as:
<h2='top'>Scroll Target at Top<H2>

Scroll Target at Top

This is just some filler text to move the expand item a bit further down the screen. In fact, why not just throw in an image and save us all a heap of blibber blabber text. Here is a photo of a donkey stuck in a manhole cover. Silly donkey, you are not a man… you’re a donkey.

Now we place an expand element with a defined ID and scrolltarget value:
[expand title="trigger text" id="monkey" scrolltarget="#top"/]

So navigating directly to
https://spacedonkey.de/3439/scroll-targets-and-url-hash/#monkey

will scroll down to the monkey element, open it, then scroll back up to the top element. This bouncing around is quite annoying.

Introducing: hash-trigger

This is a test where we introduce a new attribute called hash_trigger. This is an secondary id that will be use to expand but not scroll to a collapse element based on the url anchor hash. For example. We create an expand element like so:
[expand title="trigger text" id="smashing" hash_trigger="pumpkins"/]

Now when we link directly to the page with the url anchor hash of #smashing it will scroll to and expand the element above as normal. However, if we use the url anchor hash of #pumpkins it will only expand the element and NOT scroll anywhere , providing:
1. there is no other element with an ID of pumpkins
2. there is no scroll-to attribute defined on this expand element.

Note: to assign the hash_trigger using the roll-your-own method, simply assign a data-hash-trigger attribute to the trigger element:

<div class="collapseomatic" id="smashing" title="trigger text" data-hash-trigger="pumpkins">trigger text</div>