#1554 - Manually deleting a member row may stop new zones working

Identifier #1554
Issue type Minor issue (breaks specific functionality)
Title Manually deleting a member row may stop new zones working
Status Completed
Handling member Chris Graham
Version 9.0.11
Addon General / Uncategorised
Description If a new zone is added, new pages are put in place. The first time it loads, it finds the first admin, and assigns ownership to that member.

If an admin was manually deleted from the f_members table, but still has a secondary membership row defined in the f_group_members table, Composr will pick up the orphan reference, associate it with a zombie user, and then crash when setting the page ownership (if you're unlucky and the first admin row to come out of the database happens to be the zombie row).

There is a feature to delete a member that does full cleanup. However, we do want to allow webmasters to manually edit the database even if it does lead to occasional accidental broken references - therefore this can be considered a bug.

The hotfix directly prevents the zombie row coming up. However, Composr 10 will also make it so new zones are automatically assigned to the submitter of that zone, which makes more sense anyway.
Steps to reproduce

Funded? No
Hotfixes

hotfix-1554, 2014-01-30 3pm.tar

Only apply these hotfixes if you absolutely need them and cannot wait until the next release of Composr (releases are more reliable and strictly tested). We provide no guarantee that hotfixes will work; they may even break your site especially if a hotfix depends on another hotfix. Always make a site backup if you attempt to apply a hotfix.

As of Composr version 11, the recommended way to apply a hotfix is by following the same steps as an upgrade:

  1. Download the hotfix into the data_custom folder of your Composr installation directory
  2. Back up your site
  3. Go to yourbaseurl/upgrader.php
  4. When you get to the 'Transfer across new/updated files' step, use the hotfix that you downloaded.
  5. The upgrader will automatically apply hotfix files, skipping any files belonging to addons that you do not have installed, and also skipping hotfix files that are older than the files on disk
  6. Run a database upgrade if prompted
  7. You may wish to run a file integrity scan and resolve issues.

For Composr version 10, manually extract the files (e.g., using 7-Zip) and overwrite files in your Composr installation that are older than the ones in the hotfix (check the file modification date/time). Skip hotfix files that do not exist in your installation.
Commits

c06f868
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".

Rating

Unrated