Jan29Written by:slhilbert
1/29/2009 3:34 PM 
The Visibility Setting unique to each module and found in the Module Settings page specifys whether or not to display the +, - or nothing that allows for the module to be collapsed.
I generally don't like having this turned on and try to use the default settings to specify that it should always be set to "None". However, from time to time things get out of control and I end up with a site that has the settings sometimes set to "None" and other times set to "Maximized".
In order to get everything back in sync I have had limited success in using the "Apply to All Modules" options. It seems to work for a page, but not for the entire site.
Therefore I went looking for a solution that would be quick and easy to get all of my modules setup the way I want them.
In order to do this you must be logged in as a user account with HOST level access.
- In the menu navigate to Host and then click on the SQL page.
- In the SQL Box paste the following code
UPDATE TabModules
SET Visibility=2
WHERE Visibility <> 2
NOTE:
0 = Maximized
1 = Minimized
2 = None
You should change both numbers in order to get the update to work. - Click the Execute Button
- That's It!
2 comment(s) so far...
Re: Quickly Modify the Visibility of All Module Containers Through SQL
Thanks for the tip!
For those who try this (like me) before having their morning coffee, or are new to the SQL option in DNN, do not be fooled by the result message that shows "The query did not return any data." It did not return any data because this is not a select query. (I'm awake NOW!)
I also had to go into the host settings and restart my app for the changes to take effect. Would you expect this?
By Sam E on
1/30/2009 9:25 AM
|
Re: Quickly Modify the Visibility of All Module Containers Through SQL
Certainly you are right that you will get no results from the query as you are updating and not asking for information. You very well might have to refresh the app or the browser if the containers are being cached. I would suspect that a ctrl-F5 in your browser would be sufficent though. I wouldn't think that you would have to restart Dotnetnuke. However if you do need to restart Dotnetnuke that can be done under Host |Host Settings and then click on Restart Application.
By Stuart on
1/30/2009 9:33 AM
|