WordPress.org

Make WordPress Core

Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#30774 closed defect (bug) (fixed)

bug after installing 4.1

Reported by: esp2013 Owned by:
Milestone: WordPress.org Priority: normal
Severity: normal Version: 4.1
Component: Bundled Theme Keywords:
Focuses: Cc:

Description

Today I updated 4.1 and all themes. I'm running a 2014 child theme. After updating a few plugins I suddenly got a panicked call from my office that the page was just blank white. Luckily the dashboard was still working. I initially thought that it was a plugin conflict as I had just installed Open external links in a new window prior to the upgrade so I uninstalled that one and another that I had just updated. That didn't help. Next I deactivated all of my plugins - that did nothing. I then looked at the themes and found that my 2014 css was missing so tried to reinstall 2014 but the dashboard message said it was already installed. Going into the theme folder via ftp I found that it only contained one file. Somehow all the rest of the contents of the 2014 theme had been deleted. I copied the 2014 folder from another site I have running it and so installed that one. Meanwhile, when I deleted the corrupted 2014 folder Wordpress defaulted to 2015 - the site showed up, albiet not correctly because my custom 2014 child-theme css was not used, but my custom sidebar displayed properly and worked as it should. However, when I switched back to my child theme the sidebar disappeared and my Primary sidebar widget had been cleared of its contents! The inactive sidebars were all left intact but the one that mattered was empty (I use Custom Sidebars plugin to make the widgets). Luckily I had the code saved since it was just html in a text container, so I was able to re-create it.
It's back up and running but this is a heads up to others that weird stuff happens - nothing like this has happenned when I've updated before and thing kind of thing is stressful!
Word to the wise - always back up your customizations!

Change History (5)

This ticket was mentioned in Slack in #forums by kimparsell. View the logs.


6 years ago

This ticket was mentioned in Slack in #forums by kimparsell. View the logs.


6 years ago

#3 follow-up: @Otto42
6 years ago

  • Resolution set to fixed
  • Status changed from new to closed

During the release of the latest version of the 2014 theme this morning, one of the servers accidentally created a bad ZIP file. This was discovered and the bad ZIP file on that server was corrected. All the other servers were checked and validated as well, just to be sure.

The 2014 theme is currently correct on all servers, and all subsequent updates to it after that brief period this morning will have no issues.

#4 @DrewAPicture
6 years ago

  • Milestone changed from Awaiting Review to WordPress.org

#5 in reply to: ↑ 3 @esp2013
6 years ago

Replying to Otto42:

During the release of the latest version of the 2014 theme this morning, one of the servers accidentally created a bad ZIP file. This was discovered and the bad ZIP file on that server was corrected. All the other servers were checked and validated as well, just to be sure.

The 2014 theme is currently correct on all servers, and all subsequent updates to it after that brief period this morning will have no issues.

Thank you, glad to know the cause

Note: See TracTickets for help on using tickets.