Exclusive plugin calls ONLY to relevant pages

  1. houseofstrauss


    It's the most obvious problem, but wordpress, like many other cms/blogs seems to integrate code for plugins globally on the site. So, example; I install a contact plugin and suddenly its javascript, css and other supporting code is available on EVERY page of my site, even though I only want it on one page. Contact.

    We do this for 15 plugins or more on a site and the net result is that the site becomes burdened with code and processing most of which is totally superfluous to most pages. Additionally, some plugins simply conflict because another's JS code is permanatly stuck in the header unnecssarily.

    Some plugins (cForms) seems to have grasped this issue and made exclusive calls just for the page IDs, so this is clearly possible.

    Implementing this idea would speed wordpress up by a huge amount, plus clean the page code and database processing

    We need a clear mechanism for this, so that as an option supporting code is ONLY called for pages/posts that need it, or added globally.

    What if every plugin automatically created a default PAGE/POST TEMPLATE and we could select this to make it active or not?

    Any ideas or development in this area?

    Posted: 9 years ago #
  2. Feathers


    i agree wholeheartedly. have posted a similar idea here yesterday:

    Posted: 9 years ago #
  3. nickohrn

    This is already possible, it's just the plugin author's perogative to test it. They can use various conditionals instead of just throwing things into wp_head or admin_head. This isn't something the WordPress core needs to worry about, in my opinion.

    Posted: 9 years ago #
  4. houseofstrauss


    I know it is the developers choice to do this as we have seen in some plugins. But how many bother to do it? Very few. So there is a need for incentive/persuasion to make this available and this is where changes to the core might make things easier, or more entising for the developer.

    I might add that a proper deactivation and optional database cleanup routine is also needed to stop the remains of old plugins needlessly clogging the database.

    On the face of it wordpress is a very good system for the beginner and regular user, but to keep it running lean and efficient requires a major step into understanding php and Mysql. It does not need to be like this, if concepts like this were implemented.

    Posted: 9 years ago #
  5. Robbi


    This would be amazing. I have an e-Commerce plugin and a Gallery plugin that are interfering all the time and it's so irritating. This actually is a problem for lots of people. I know the volunteers and everyone here at WordPress are busy with lots of things, but would anyone know of a plugin or something to sort this out?

    Posted: 8 years ago #

RSS feed for this topic

Topic Closed

This topic has been closed to new replies.

  • Rating

    5 Votes
  • Status

    This is plugin territory