Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter sakowporg

    (@sakowporg)

    Thanks again! I will also take a closer look into this plugin:

    https://de.wordpress.org/plugins/wp-webhooks/

    Thread Starter sakowporg

    (@sakowporg)

    Hi! Thanks for your answer. And you are right, I need to find a way to setup NodeJS, Selenium WebDriver, the ChromeDriver and the GeckoDriver for Firefox on my Server as a first step and then try to find a way to run those “flows” by using a “trigger URL”… so that the script excecution and the wordpress environment are completly separated. The only “connection” is the Trigger URL send from a wordpress admin page.

    Thread Starter sakowporg

    (@sakowporg)

    Hi Joy!

    That a VERY interesting article. Will probably find it´s way into my future productions. Thanks a lot!

    Thread Starter sakowporg

    (@sakowporg)

    After some research: When you use the PRO version of Loftloader and activate the page transition function, then the preloader actually works as expected: Appears directly after the click on the link for the new page and goes away as soon as the new page is rendered.

    NO OTHER PRELOADER PLUGIN DOES THAT AT THE MOMENT (02/2021)

    Thread Starter sakowporg

    (@sakowporg)

    Hi!

    If anybody is interested in some newbee background: After doing some research I figured that the whole page transition process is spreaded as follows:

    – Click to open new page
    – While server recieves all requests the new page requires to be organised and gathers all assets for your new page that will need to be transfered to your browser, you still see the old page.
    – Then the Server starts to send all data to your browser (You still see your old page)
    – In the moment all HTML, CSS and JS has reached your browser starts to build the DOM of your new page. (You still see your old page)
    – If your page uses JSON files, they are loaded now. And delay all site buildup. (You still see your old page)
    – Somewhere inbetween loading JSON Files the old page vanishes and the new page starts to render. Mostly starting off with a white page with no content and then quickly compsoing your layout together with a few cranky jumps as the components fill their space.

    This procedure does change in it´s timely proportions depending on how you use your caching tools or how many times you have visited the page allready, but the overall described order of excecution stay the same. Specially in terms of when the old page actually switches to show the new page.

    So without an ajax or css page transitions the internet still looks like it´s still 1995 😉 Preloaders make no sense as they only show up after 75% of the process is done, no matter how you tweak them and they do not “transition” from the old page, but only show up after the old page vanished from one millisecond to the other.

    Thread Starter sakowporg

    (@sakowporg)

    Solution:

    When using the Plugin: “AnalogWP Style Kits” the first thing you have to do after installing the plugin is to go to Style Kits -> Settings -> General Tab. There you find the setting “Global Style Kit”. Although this setting is by default set to “Default Kit” you have to press “Save Changes” once, otherwise any changes to the Style Themes will not affect the page anymore.

    The guys from analogWP should definitly look into this…

Viewing 6 replies - 1 through 6 (of 6 total)