Discussion:
Unique Theme/Plugin identifier
Alexander Höreth
2013-06-05 19:45:37 UTC
Permalink
Hey everyone,
some time back there was a post on the list which gave a rough idea on how
themes and plugins are uniquely identified on WordPress.org to located the
right update packages etc.
Can anyone here give me some more insights?

Obviously, plugin names are not unique. Author+plugin name won't do the
trick either I guess. The author can change. How is .org doing it?

Regards,
Alex
Mika A Epstein
2013-06-05 19:47:00 UTC
Permalink
Plugin Slugs are unique, however :) That's how we do it.
Post by Alexander Höreth
Hey everyone,
some time back there was a post on the list which gave a rough idea on how
themes and plugins are uniquely identified on WordPress.org to located the
right update packages etc.
Can anyone here give me some more insights?
Obviously, plugin names are not unique. Author+plugin name won't do the
trick either I guess. The author can change. How is .org doing it?
Regards,
Alex
_______________________________________________
wp-hackers mailing list
http://lists.automattic.com/mailman/listinfo/wp-hackers
John Blackbourn
2013-06-05 19:56:14 UTC
Permalink
Post by Mika A Epstein
Plugin Slugs are unique, however :) That's how we do it.
I don't believe that is how it works actually. A plugin can live in a
directory with a different name locally and updates to it will still
be found.

IIRC from past threads, the API makes an informed decision based on
the plugin name, author, URI, and filename. Maybe other fields too.

John
Andrew Nacin
2013-06-05 19:57:27 UTC
Permalink
Post by John Blackbourn
Post by Mika A Epstein
Plugin Slugs are unique, however :) That's how we do it.
I don't believe that is how it works actually. A plugin can live in a
directory with a different name locally and updates to it will still
be found.
IIRC from past threads, the API makes an informed decision based on
the plugin name, author, URI, and filename. Maybe other fields too.
Correct, John.

WP.org uses a combination of the plugin slug, plugin name, plugin URL,
etc., to identify a plugin. Assume that we use any header sent back, we use.

Alex, for your GSoC project, use the plugin's slug + filename, as returned
by plugin_basename(), and as used for activate_plugins().
Alexander Höreth
2013-06-05 20:00:53 UTC
Permalink
Thanks Andrew. Atm I wanted to use author, plugin name, file name.
Idea of asking here was to do it the same way as .org because others maybe
already spent more thoughts on it.
Post by Andrew Nacin
Post by John Blackbourn
Post by Mika A Epstein
Plugin Slugs are unique, however :) That's how we do it.
I don't believe that is how it works actually. A plugin can live in a
directory with a different name locally and updates to it will still
be found.
IIRC from past threads, the API makes an informed decision based on
the plugin name, author, URI, and filename. Maybe other fields too.
Correct, John.
WP.org uses a combination of the plugin slug, plugin name, plugin URL,
etc., to identify a plugin. Assume that we use any header sent back, we use.
Alex, for your GSoC project, use the plugin's slug + filename, as returned
by plugin_basename(), and as used for activate_plugins().
_______________________________________________
wp-hackers mailing list
http://lists.automattic.com/mailman/listinfo/wp-hackers
Continue reading on narkive:
Loading...