WordPress.org

Make WordPress Core

Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#6893 closed defect (bug) (duplicate)

Wordpress Database Upgrade Fails Improperly when tables can't be created

Reported by: elharo Owned by:
Milestone: Priority: high
Severity: critical Version:
Component: General Keywords:
Focuses: Cc:

Description

When upgrading from 2.2 to 2.5 (probably 2.3 or later) the upgrade will fail if the user does not have database permissions to create and drop tables. However:

  1. Wordpress does not notice this problem, and attempts to upgrade anyway; thus breaking the blog. It should realize it doesn't have permissions and not attempt the upgrade, while giving the end user an appropriate error message.
  1. WordPress reports success with the upgrade, despite its obvious failure.
  1. The upgrade seems to be ignoring SQL errors generated during the process. If any SQL errors occur, WordPress should roll back the database to its original state.

This has been discussed on the mailing list and verified as a real problem that does occur in practice, despite many devs beliefs that it is impossible for this to occur.

I am not suggesting that Wordpress should be able to upgrade when tables cannot be created or dropped. However its error behavior in these and similar circumstances needs to be cleaned up.

Change History (4)

comment:1 @Scott H7 years ago

See also #4027

comment:2 @ryan7 years ago

  • Milestone changed from 2.5.2 to 2.9

Milestone 2.5.2 deleted

comment:3 @mrmist7 years ago

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

Much more discussion in #4027 than here.

comment:4 @thee177 years ago

  • Milestone 2.9 deleted
Note: See TracTickets for help on using tickets.