bad programming practice? –> code injection on every page?

  • Resolved jochenthomas

    (@jochenthomas)


    4 years, 8 months ago

    Hi,
    on every single page, a bunch of code is injected into the header.
    6 to 10 single HTTP requests are existing. This is slowing down the site and a plugin provider should know this.

    If bookly is ONLY integrated/used on a single page, how it is possible to avoid code injection on 99% of the rest of the page?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Bookly

    (@ladela)

    4 years, 8 months ago

    Hello,

    Can you try changing the “Method to include Bookly JavaScript and CSS files on the page” setting from “Enqueue” to “Print”?

    Thread Starter jochenthomas

    (@jochenthomas)

    4 years, 8 months ago

    Sorry for the late reply…
    NO, not possible. Only the Spinner is visible.
    How I am going to resolve this?
    How I can dequeue to manage the deployment on certain pages?

    • This reply was modified 4 years, 8 months ago by jochenthomas.
    Plugin Author Bookly

    (@ladela)

    4 years, 8 months ago

    Can you check if you don’t use caching(plugins or on the server side)? The plugin is not compatible with caching. If that’s not the case and the mentioned setting didn’t help, then you need to investigate – which plugin or theme is causing this problem and look for an alternative.

    Thread Starter jochenthomas

    (@jochenthomas)

    4 years, 8 months ago

    Thanks for your answer, but I do not understand…

    In the source-code of ALL pages I see -as already stated- dozens of CSS and js-scripts included in the header only for a single plugin (= bookly). Each of them creates unwanted HTTP calls, which slows down the pages or will affect the page scores – even on pages not necessary.
    As you are the plugin programmer only you can take care of such performance-critical topics…

    I want to see such a high number of scripts/CSS-calls only on a single page (where bookly is used).

    How is this related to a caching tool?
    That your plugin is not compatible with caching is understood.
    But how a caching plugin minimizes the vast amount of HTTP-calls?

    How -again the question- I can dequeue all existing bookly scripts in functions.php on certain pages if your print method has no effect?

    What is the idea behind the print-method.
    How is it working?
    Why other plugins can prevent this method from working?
    What could be a possible reason?
    Without background information, I cannot investigate…

    Plugin Author Bookly

    (@ladela)

    4 years, 8 months ago

    Hello. The issue you’ve raised requires personalized support, therefore, please contact us directly on our site for further actions and details.

    Many thanks!

    Plugin Author Bookly

    (@ladela)

    4 years, 6 months ago

    Hello,

    As we haven’t received any support request from you via our website, we will go ahead and mark this thread as resolved.

    You can always reach out to us in the future via our website if you have any issues, and we’ll be happy to help.

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

The topic ‘bad programming practice? –> code injection on every page?’ is closed to new replies.