WordPress.org

Make WordPress Core

Opened 9 years ago

Closed 8 years ago

#3543 closed defect (bug) (wontfix)

Plugins fail if default theme does not exist

Reported by: drewrockshard Owned by:
Milestone: Priority: lowest
Severity: minor Version: 2.0.6
Component: Template Keywords: needs-patch
Focuses: Cc:

Description

Upon restoring a site, I delete everything from wp-content/themes directory. This includes "default" and "classic" themes. Then I upload my design. Well, I did this today with the 2.0.6 release and it failed. It uploaded fine. When I went to the "Presentation" tab to view the currently installed theme, it just say "By" ... nothing else. Also, if I try clicking on "Theme Editor", it says something like "Theme does not exist in this directory"...

So, I thought it could have been a bad xfer (FTP), so I reverted to my backups. Those didn't work either. So I reverted to other backups, didn't work. Tried a few install of wordpress on a separate directory, still got the "By" issue.

So, what I did this time was I uploaded my theme (still getting the "by" prob) ... and then uploaded the "default" theme. It them worked, showed my screenshot of my theme and everything. Then I removed the "default" theme from the server (via FTP) ... and it was fine. So it seems this only happens when you initialling install wordpress without the "default" theme, but you can delete the "default" theme once it registers with wordpress and sees that the default theme "was" there.

I don't quite know how the core code works, as I'm my own developer and haven't actually really dug through the code, myself.

Maybe its just me, maybe not.

Change History (4)

comment:1 @Viper007Bond9 years ago

  • Keywords needs-patch added; templates removed
  • Priority changed from normal to lowest
  • Severity changed from major to minor

Sounds like you deleted the active theme. Not usually a good idea. ;)

We should probably code into the presentation tab a checker like the plugins page has (if the activated theme doesn't exist, pick a different one).

comment:2 @drewrockshard9 years ago

That does sound like a good idea. As stated above, I have not really looked at the core code, so I probably won't be doing this :D. But yea, if you could put it on the list a "fixes" ... that would be good.

Thanks for having a look.

comment:3 @Otto429 years ago

There are several hard references to the default theme when the active theme is determined to have been missing some file or other.

Because of this, it's possible that a (n00b) theme designer could design their theme in such a way that it inadvertently uses bits of the default theme, without realizing it.

Thus, I would always suggest leaving the default theme in place even though you're putting in other themes. It's hard referenced, so it's expected to be there.

comment:4 @foolswisdom8 years ago

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

Closing WONTFIX, based on Otto42's comment. drewrockshard if still concerned with the current trunk behavior please consider opening a new bug after isolating the problem.

Note: See TracTickets for help on using tickets.