WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 4 years ago

Last modified 3 years ago

#13067 closed feature request (wontfix)

Configuration of Plugin and Theme Repository/ies

Reported by: hakre Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.9.2
Component: Administration Keywords: needs-patch
Focuses: Cc:

Description

Currently the plugin and theme repositories are hardcoded into core code. The only way to intercept here is to write a plugin which needs to be installed therefore - which is a downside since the repositories are about plugins: you need to install a plugin to add a repository to install a plugin to ... (an endless self-reference with getting nothing done).

It would be very useful that an Administrator can configure / change the default repository and even add other repositories. This would be the same as with package managers in the linux world where you can add multiple repostories.

Plugin and Theme developers can then offer remote access to their repositories for example.

Or admistrators can offer access to their checked and verfified repositories, which can be a local one as well.

Can be as simple as a textbox with one repository per line.

Change History (17)

comment:1 @hakre5 years ago

Additionally those reportitories should provide a name (either via API or via configuration [or both]) so that on the plugin / themes screen the content can be filtered by repository.

comment:3 @hakre5 years ago

Related: Ryan Boren; 4:54 pm on May 28, 2010 in "Some pre-release to do items":

  • Setup MU -> 3.0 upgrade handling for api.wordpress.org ( we need to make a 3.0 package with a wordpress-mu root to satisfy MU’s update-core.php)

comment:4 follow-up: @westi5 years ago

  • Milestone changed from 3.1 to Future Release

I'm not sure this is somewhere we want to go at the moment.

The idea behind have a centralised repository is that people can trust the content and security of it.

I would much rather people have the current hurdle of having to install a plugin in order to support upgrade/install from another location.

It is very unlikely that we would ever add a UI visible option for this.

Removing from the 3.1 milestone as this is not a committed feature and would need discussion during the 3.1 roadmap setting dev-chats which will happen post 3.0 release.

comment:5 @dnautre5 years ago

  • Cc dnautre added

I think it's a good idea.

How about not having an UI but simply a text file where you can add 1 line per repository ?

It's not like people couldn't install every plugin they want already, so having the default repository set to the official WP one seems enough security.

comment:6 @hakre5 years ago

It's always good to not hardencode stuff. I do not see any need to that hardly argument against that out of nothing. It will obviously make things more open, transparent and user-specified.

I do not want a central repos as the only option. I want to see more here. That's what this is about as well. Like with any Linux Distribution where you can add more package repositories.

comment:7 in reply to: ↑ 4 @hakre5 years ago

Replying to westi:

I'm not sure this is somewhere we want to go at the moment.

Then why do you change the milestone then?

The idea behind have a centralised repository is that people can trust the content and security of it.

Well, this won't remove the centralised repository (wordpress.org can run it as long as they want to), it will only add the options to add more and/or change to other repositories.

I would much rather people have the current hurdle of having to install a plugin in order to support upgrade/install from another location.

Well, that's unrelated to this tickets topic. With or w/o multiple repositories you can do that with a plugin as well. But this ticket is specifically about the point to not do it via a plugin but in core.

Next to that, the plugin idea is slightly misleading for the point that the current hardcoded repository imlementation offers no API for that.

It is very unlikely that we would ever add a UI visible option for this.

Well, a simple multi-line-text-box is enough for that. I do not see any problems to easily integrate that. If that's too much for the overall UI, please honot that there have not been made any concrete suggestions on how to implement that. A file and configuration directives can be usefull as well. There is no need to convert this ticket into a "should or shouldn't we add another option box for that"-discussion. I would rather love to see this tickets discussion is focussing more on how that new feature can be easily implemented.

comment:8 @hakre4 years ago

Tag: WPFP

comment:12 @mikeschinkel4 years ago

  • Cc mikeschinkel@… added

+1

comment:13 @dd324 years ago

  • Milestone Future Release deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Cleaning out the old tickets which we do not have any plans on supporting.

comment:14 @hakre4 years ago

  • Resolution wontfix deleted
  • Status changed from closed to reopened

Is this confirmed by Jane Wells? I could read on the worpdress foundation homepage that it want's to foster the open character of the application. So a stronger confirmation that this is not wanted, would be great. Re-Opening therefore.

comment:15 @nacin4 years ago

  • Resolution set to wontfix
  • Status changed from reopened to closed

comment:16 @mikeschinkel4 years ago

  • Cc mikeschinkel@… removed

comment:17 @hakre3 years ago

Related: #16898

Note: See TracTickets for help on using tickets.