Plugin repository management for addons

  1. samjco


    It would be nice to have addon plugins (plugins made as extension to an existing plug) to appear in the same folder as the parent plugin.

    They should have the subtitle Addon to: (e.g: Addon to: Gravity forms) This makes it easier to search for the difference between the two.

    The parent Plugin owner should also be able to approve addons to appear in his/her folder.

    Within the dashboard of WordPress under plugins, there should be the Parent plugin and a dropdown arrow revealing the Addons.

    Posted: 4 years ago #
  2. Ipstenu (Mika Epstein)

    The actual FOLDER wouldn't work, since the code deletes the plugin folder and reuploads on upgrade.

    Now organizing visually might be an idea.

    Posted: 4 years ago #
  3. samjco


    Sorry let me clarify.
    When I say FOLDER, I meant the area of where (or how) WordPress stores the Plugin data on the repository site.

    Posted: 4 years ago #
  4. Ipstenu (Mika Epstein)

    No, not possible at this time. The way WPORG stores the repository is via SVN. While Git would have the ability to pull in sub-modules like that, SVN does not, so we can't pull in children plugins and themes like that.

    And anyway, you don't want to, since the SVN repo is pretty much a mirror of what you get on your own install, so the plugins would always have to remain separate folders for technical sanity.

    Posted: 4 years ago #
  5. samjco


    Well i not saying the change the WPORG, just a better way users can know the difference between the actual plugin and the Plugin's add-on.

    For example:
    If you log into your WordPress dashboard and do a search for the plugin: Gravity forms... A whole bunch of other add-ons to gravity forms show up on the first page. But no Gravity Forms (actual plugin).

    For a new user, this is confusing. I am saying that can we rethink the way this works. Perhaps add a tag that says "Add-on for Gravity Forms" for all add-ons. And a tag that says "Plugin" for the actual plugin. Having these tags will allow, when searching for the plugins, that the actual plugin shows up first.

    in addition if I add a bunch of add-ons to my WordPress and open up my install plugins section, I will see a whole bunch of add-on sorted by name so they would be everywhere... Perhaps by having the add-on tag, this will sort them as children to the actual plugin.

    Posted: 4 years ago #
  6. Ipstenu (Mika Epstein)

    Well. That's a case of people not naming the plugin as well as they could. "Gravity Forms - Captcha Add-On" would be better than "Gravity Forms Captcha" but that's outside the scope of what we want to enforce in the repo at this time.

    People SHOULD use the tag 'gravity forms' in their readme, and that would sort, and then you read each plugin to see what it does, but ... it's not really fasiable to go back and fix everything. Maybe if we re-do the whole repo.

    Posted: 4 years ago #
  7. samjco


    Well Mika,

    You seem to know everything.
    Thanks for listening to my ideas.

    Keep in mind, that half of my day goes to testing out plugins constantly.

    Posted: 4 years ago #
  8. Ipstenu (Mika Epstein)

    So does mine :) I'm on the plugin review team ;)

    Posted: 4 years ago #
  9. julianprice

    I agree with @samjco. @isptenu it does not make it right -- the plugin repository is mess . It's need to be categorized on function/tools it's adds to your site:
    Admin/Develop tools

    You by far know best how to think of organizing various components. Limiting to only 3 cats and at least require 1,

    Additionally tags, same thing up to 5 no more than 10 with the exception to meta tag compability with other plugins/ext/addons

    Some tag some don't . Some submit with great detail with screenshots others don't. Some submit plugins that worthless with nothing to see.

    There needs to be clean house & protocol on future submitters guidelines. Additional rolling out announcing a time limit for others to update to like 6 months otherwise they will be archived seperately.

    I made a very similar suggestion some time ago but seems the whole make wordpress better speech only applies to those that are developers --not the everyday user that's trying to contribute to the community.

    Yes --I am on rampage and appreciate all you do for the community but merely unwilling to be receptive of others ideas represent narrow mindness on how it's always have been done.

    How it's always been done or has been done doesn't make it right.

    Instead you should have thanked @samjco for contribution with encouragement: "that's a great suggestion here's the make.wordpress.org plugin committee and possible creating an ad hoc group that interested.

    Let's embrace everyone's insuring inclusion in making WordPress better.

    Posted: 4 years ago #

RSS feed for this topic


You must log in to post.

  • Rating

    1 Vote
  • Status

    This is not a core suggestion