Products

Solutions

Resources

Partners

Community

About

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...Skins, Themes, ...Skins, Themes, ...Solutions for Container errors in DNN 8Solutions for Container errors in DNN 8
Previous
 
Next
New Post
2/24/2016 2:43 PM
 
Can't wait for the day containers are no longer necessary.
 
New Post
2/24/2016 5:56 PM
 
Erik,
Containers are just a segment of skins, preventing you to provide a bunch of containers for every skin.
It could be replaced by a tabmodule CSS file and toggle button settings, but I doubt, that would be much easier to handle.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/25/2016 3:23 AM
 
Sebastian Leupold wrote:
Erik,
Containers are just a segment of skins, preventing you to provide a bunch of containers for every skin.
It could be replaced by a tabmodule CSS file and toggle button settings, but I doubt, that would be much easier to handle.

 But in that case you could not have HTML variations of a container, which is really handy sometimes.
I actually like that we have containers, I just don't like the fact that it's so "difficult" to select one (should be directly accessible from the module drop-down IMO)

 
New Post
2/25/2016 10:23 AM
 
Timo Breumelhof wrote:
I actually like that we have containers, I just don't like the fact that it's so "difficult" to select one (should be directly accessible from the module drop-down IMO)

+1


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
4/26/2016 1:59 PM
 
I know this is an old thread, but I just came across this problem.

How is this considered a "solution"? Doing this means you lose the MENU on each module that uses these containers. Many modules add their own links to the MENU, this would basically break almost any module from being able to access their administrative features.

Is there a "real" fix yet?

-Ben

Ben Santiago, MCP Certified & A+ Certified
Programmer Analyst
(SQL, FoxPro, VB, VB.Net, Java, HTML, ASP, JSP, VBS, Cognos ReportNet)
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Solutions for Container errors in DNN 8Solutions for Container errors in DNN 8


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