#51890 closed defect (bug) (invalid)
WordPress Theme Update Bug
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | 5.5.3 |
| Component: | General | Keywords: | |
| Focuses: | Cc: |
Description
Hello WordPress Volunteers!
I'm Enes Cantürk. I own the wpdoz.com.
I was developing a theme with a friend of mine recently. We named the theme 'Flare'.
I saw the text 'Flare update avaliable' from the update panel. I did the update because my friend might have sent it. Was updated. And there was a new theme in front of me :)
That was the new theme => https://salientthemes.com/product/flare/
new theme screenshot => https://prnt.sc/vrpxcl
Fortunately, I saved our theme from backup.
older theme from backup => https://prnt.sc/vrpy8d
Best regards!
Change History (2)
Note: See
TracTickets for help on using
tickets.
Hi and welcome to WordPress Trac,
This ticket is not directly related to WordPress Core, so I'm closing it as
invalid. It's more something for Support forums :)https://wordpress.org/support/forum/wp-advanced/
Your issue is that you're using a theme slug already existing in the WordPress.org repository: https://wordpress.org/themes/flare/
You just have to change your slug to avoid this issue.
Regards,
Jb