WordPress.org

Make WordPress Core

Opened 5 years ago

Last modified 3 months ago

#14179 new defect (bug)

Theme asking to update (theme with same name on WordPress.org)

Reported by: design_dolphin Owned by:
Milestone: WordPress.org Priority: normal
Severity: normal Version:
Component: Themes Keywords:
Focuses: Cc:

Description

I have a theme with a certain name, but there is a theme with the same name in the WordPress themes directory. So now my theme keeps showing an update message.

Proposed solutions:

  1. Add unique hash to each uploaded theme in the themes directory. This way even if someone has a home-grown theme which happens to have the same name, but are not going to upload it to the themes directory, there won't be a conflict. (You could change the name of the theme, but who is to say someone won't upload a theme that also has that name.)
  1. Add more fields to the updater check such as author, and date/ time created. This could mean though that theme authors would always have to add this during theme creation, and know why they are doing this. Possibly adding a extra complicating step in WordPress theme design. Otherwise at some point they or their client could start getting a update message for their theme.

Attachments (1)

23318-upgrade-header.diff (3.4 KB) - added by meloniq 8 months ago.
Adds optional "Upgrade" header for plugins and themes. New header defaults to 'true', when "Upgrade: false" is set, it excludes plugin/theme from checking for updates in WP API.

Download all attachments as: .zip

Change History (13)

comment:1 @GautamGupta5 years ago

Same with plugins..

comment:2 @filosofo5 years ago

  • Component changed from Themes to WordPress.org

See #13928 also for a similar issue with plugins.

comment:3 @sean2125 years ago

I'd go with solution #2, because adding a hash for all already existing plugins would be quite a hassle, being that there's over 10,000. :D

comment:4 @nacin5 years ago

  • Milestone changed from Awaiting Review to Future Release

comment:5 @SergeyBiryukov2 years ago

  • Component changed from WordPress.org site to Themes
  • Milestone changed from Future Release to WordPress.org

Related: #23318

comment:6 @SergeyBiryukov19 months ago

#26645 was marked as a duplicate.

comment:7 @meloniq19 months ago

  • Cc meloniq@… added

comment:8 @dreamwhisper19 months ago

  • Cc dreamwhisper added

comment:9 @SergeyBiryukov12 months ago

#28954 was marked as a duplicate.

@meloniq8 months ago

Adds optional "Upgrade" header for plugins and themes. New header defaults to 'true', when "Upgrade: false" is set, it excludes plugin/theme from checking for updates in WP API.

comment:10 @meloniq8 months ago

Patch 23318-upgrade-header.diff adds optional "Upgrade" header for plugins and themes. New header defaults to 'true', when "Upgrade: false" is set, it excludes plugin/theme from checking for updates in WP API.

(Patch was originally submitted to #23318)

comment:11 @nhuja4 months ago

This is a major issue. Many of our clients updated to a different "free" version theme by different author with same theme name and we are at a loss. Can we not simply check for Author for this auto update? We are losing clients!!

comment:12 @dd323 months ago

#31969 was marked as a duplicate.

Note: See TracTickets for help on using tickets.