Hi,

I have a very complex website with hundreds of block. I thought I'd "try out this module", thinking it would provide a block visibility overview page in the admin. But after trying out, of course I figures it was not what I imagined.

So I uninstalled the module.

BUT IT WIPED ALL MY VISIBILITY SETTINGS PERMANENTLY.

There needs to be a bold red uppercase warning on this project's homepage. Please. Warn people. Warn the hell out of them.

Comments

pelicani’s picture

pelicani commented
Version: 6.x-1.x-dev » 6.x-1.0

agreed.
y'all should also post that it only works on the default theme. (I may have missed this in your notes)
Perhaps this module should not have an official release for dv6 with these major issues.

I've not had this happen with any other module, so I feel it warranted to place this comment here.
Your idea is nice, but it can cause damage by altering info you would not expect.
Just giving some advice for making a happy open source community.
I totally appreciate everyones efforts towards making Drupal rock!!!

of course, backing up data and reviewing all notes is important when launching new modules.

ddimalen’s picture

ddimalen commented

I am currently using this module and I haven't found any problems except for some suggestions which will help "baby drupalers" like me a lot. My only complaint is the documentation was not user friendly, it took me 2 days to finally implement it successfully on our stagging server. I also experienced the same problem when I dissabled the module, it wiped out all the visibility settings of my blocks. Fortunately, I always backup tables which I thought would be affected by modules I am about to install. So when my settings were wiped out, I just fired up my sql file for my blocks table using phpmyadmin and "voila!" all settings were restored.

My suggestion to drupalers: Don't be lazy, backup tables that might get affected by the modules you are about to install. You need to open the module source code to identify these tables (they are enclosed with {} so it should be easy to pin point it).