Posted by StryKaizer on May 2, 2011 at 8:38am
7 followers
| Project: | Mongodb |
| Version: | 7.x-1.x-dev |
| Component: | Field storage |
| Category: | bug report |
| Priority: | normal |
| Assigned: | StryKaizer |
| Status: | closed (fixed) |
Issue Summary
After uninstalling mongodb module, the field_storage_default variable isnt set back to the default field_sql_storage value.
Manually executing variable_set('field_storage_default', 'field_sql_storage'); seems to fix the issue
Comments
#1
Will submit a patch
#2
This patch will remove the field_storage_default variable again after disabling the module
This will make the default storage type active again.
#3
+1 for porting this to the module.
Thanks StryKaizer!
#4
#5
The last submitted patch, mongodb.fieldstoragedefault.patch, failed testing.
#6
A problem with formatting of the patch, corrected it, and applied it.
#7
Patch was applied to 7.x-1.x
#8
#9
Automatically closed -- issue fixed for 2 weeks with no activity.
#10
This problem still persists.
Apply the patch above but still did not work. :-(
I disabled and uninstalled the module after the patch and still the error persisted.
Tried to find in another place but I could not =/
Can Anyone to help me ?
#11
That patch doesn't resolve anything, because that variable is being set in every boot of the Drupal.
So now i cant create new fields when i disable+uninstall the mongodb_field_storage module, because the default field_storage is still mongodb.
The question is, how the mongodb_field_storage did to persist always even if i disable+uninstall the module?
This is some core bug? or the field_storage_default is being set in the wrong way.
Please some help! this really ruined my project.
Cheers,
Sebas.
#12
I resolved the problem.
When you install the mongodb_field_storage, must remove this line from the settings.php:
$conf['field_storage_default'] = 'mongodb_field_storage';
Doing that resolve all my problems :)
I think this must be a warning in some place in the README file or some warning message, i don't know which is the better approach.
Cheers,
Sebas.
#13
Thanks Sebas.
Resolved my problem :-)