Plugin doesn’t do anything

  • Resolved Nate

    (@goseongguy)


    3 years, 11 months ago

    Hello,

    I thought I’d give this plugin a try, but upon checking my resulting source code, I don’t think the plugin is working. When I make a CSS file async, should I see something different in the HTML source to verify it’s working?

    Could you advise as to the syntax for keywords? For example, do you need users to enter comma separated values, or a new line, or ???
    I guess it would be helpful to show users of this plugin which format you expect them to give the keywords.

    Cheers,
    Nate

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Arya Dhiratara

    (@aryadhiratara)

    3 years, 11 months ago

    Hi Nate,

    Yes you should check the difference in the html source.

    Can you share the url so I can see if it’s working or not?

    About the keywords, it’s 1 keyword per line. Really sorry, I will add more explanation in the next update.

    Give it a try. The delay css on user interaction will be really helpfull if you have a lot of css that is ony requeired in below the fold area.

    Thread Starter Nate

    (@goseongguy)

    3 years, 11 months ago

    Hello Arya,
    Thanks for the prompt response. No big deal, it’s just helpful.

    Aha, I think I see now that this is only activated when logged out. I was looking for a change while logged in to wp-admin.

    However I do see a console error:
    Uncaught SyntaxError: Identifier 'userInteractionEvents' has already been declared (at (index):99:578)

    Could the error be related to a conflict with another plugin I’m using Flying Scripts which delays JS?

    Here is a URL: https://goseongguy.com/the-hideout-bakery-cafe/

    This is with the following IDs async, entering keywords as below:

    trp-floater-language-switcher-style-css
trp-language-switcher-style-css

    I also tried to make a CSS file delayed (which doesn’t work due to the console error I believe) using the keyword:

    non-critical-css

    Thanks,
    Nate

    • This reply was modified 3 years, 11 months ago by Nate.
    • This reply was modified 3 years, 11 months ago by Nate.
    Thread Starter Nate

    (@goseongguy)

    3 years, 11 months ago

    Hi Arya,

    For the Delay CSS feature: Any chance you might be able to rename the userInteractionEvents variable (or some other tweak) to avoid conflicts with the Flying Scripts plugin?

    I edited $print_delay_css_interaction_inline_script in optimize-more-css/includes/functions/delay-css-on-interaction.php by renaming userInteractionEvents to userInteractionEvents2, and now the delay CSS feature works!

    It would be ideal though to not have to manually edit the plugin on each update, and in case any of the other 20,000+ Flying Scripts users try your plugin, they would encounter the same.

    Plugin working great now.

    Cheers,
    Nate

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

The topic ‘Plugin doesn’t do anything’ is closed to new replies.