Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Configuration of Host tab skins is a bit of a problemConfiguration of Host tab skins is a bit of a problem
Previous
 
Next
New Post
5/23/2011 12:43 AM
 
I have a problem with the configuration of the Host tabs, I think someone should rethink the solution.



Host and Admin tabs used to come in admin skins and with admin containers. Since the difference between admin tabs and normal tabs has become reduntant, Host and Admin tabs come in the default portal skin.The argument is that you can manually modify the skin of each page.



With Admin Tabs, this is true, but Host tabs cause a problem. I have tried to change the skin of the Host tab, an had to manually correct tab settings in the database. Tabs were saved with a reference to the portal that saved the tab settings (instead of null) and the host settings became unavailable in any portal.



I can change the skin in the portal settings to a host skin which will be the same for every portal. But I have no way to select the "default Admin skin" and ditto container for Host tabs, which would give different skins in different portals. This seems like a step back to me.



DNN still has different logic for hosting tabs. When I copied a module to all tabs, the module indeed appeared on all tabs (even the admin tabs where I had to go and delete them) except for the host tabs. Which is of course what one would expect. So why not implement the admin skin on the Host tabs? Or at least leave the option.


____________________________________
The one-eyed in the land of the blind.
 
New Post
5/30/2011 12:02 AM
 
Actually, the process of copying a module to all pages may also be subjected to some critical thinking.

When I copy a module to all pages, it is usually a module that goes to a side panel. After I copied the module to all pages, I find myself deleting the module from those pages that have no side panel, mainly the Admin pages, but also for instance from pages with the Silverlight Photo Gallery coz the width thereof also forced me to eliminate the side panel.

Just a suggestion: maybe allowing to copy a module to all pages with one or more selected skins?


____________________________________
The one-eyed in the land of the blind.
 
New Post
6/10/2011 8:10 AM
 
Another inconsistency:

When I make a skin, I can name all the panes in the native language, except for the ContentPane. The problem is that in the control panel and the control pages, this pane will also appear untranslated and untranslatable.

Somehow, an alias in the foreign language or any way to make the contentpanel appear under a translated name, should exist.

Update:

The problem of the Host tabs' skin, I solved through DSLocalizator: I added a feature to the localized tab settings: the tab skin source control and the tab default container will have in the new release the option "Use Admin Skin" and "Use Admin Container". For the Host tabs, that means that in every portal, the host tabs will appear in the portal's admin skin.

I now use this feature also for my Admin tabs, as that makes them inherit from the default admin skin and I can change all admin tabs by changing default Admin skin.

Maybe consider including that solution in DNN?


____________________________________
The one-eyed in the land of the blind.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Configuration of Host tab skins is a bit of a problemConfiguration of Host tab skins is a bit of a problem


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out