Closed (fixed)
Project:
MySite
Version:
5.x-2.19
Component:
Code
Priority:
Minor
Category:
Bug report
Assigned:
Reporter:
Created:
16 Feb 2008 at 19:41 UTC
Updated:
15 Apr 2008 at 01:04 UTC
Jump to comment: Most recent file
When blocks are loaded as droplets but the blocks themselves are later deleted, the entries in the database table mysite_content are not deleted. This results in the Droplet page at admin/settings/mysite/type/droplet refusing to load (it gives an error about how something is missing in droplet.inc on line 243--the line where blocks are loaded). This wouldn't normally be a problem, but blocks are sometimes deleted when modules are turned off, uninstalled, or deleted. Specifically, I experienced this problem after turning off Activity and Simple Karma.
The deleted blocks also still show up for users to choose on the Droplet selection page.
I apologize, but I won't be able to do any more testing on this. I'm very tight on time right now and I got everything working by manually deleting the offending database entries.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | droplet.patch | 5.32 KB | agentrickard |
| #2 | droplet.patch | 3.97 KB | agentrickard |
Comments
Comment #1
agentrickardI understand. Thanks for the report. I suspect something similar may happen with Views.
Comment #2
agentrickardPlease test the following patch against 5.x.2.19. To apply, put the patch in your mysite > plugins > types folder.
This will prevent the errors and delete Droplets when you go to the Droplets administration page. Then, those items will be deleted from user pages on the next MySite cron run -- which is scheduled for once per day.
If we need a more robust fix, I'll consider it, but it is hard to react to module deactivation.
Comment #3
agentrickardAnd a patch against 5.x.3.
Comment #4
agentrickardComment #5
agentrickardCommitted to HEAD.
Comment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.