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, ...Wanted: Skin Object or procedure to pull in centralized editable content blockWanted: Skin Object or procedure to pull in centralized editable content block
Previous
 
Next
New Post
11/16/2015 4:20 PM
 

I'm working on a skin with a set of 4 footer panels with a responsive design. I'd like for the content in those panels to be editable in a central location, from which a skin object could pull that content and place it on every page where that skin file is chosen.

We are already doing something similar on this set of sites for simpler applications using MyTokens; however, I'd like the "footer editor page" to use a friendly HTML editor where the site's content editor can go to one admin page of the site, and edit the content or menu links for each of the 4 footer panels in that one place. I then envision using a skin object that will pull that content out of the database by PortalID and place that on the page in the layout pane of each page as defined in the skin template.

A few ideas that I've ruled out for various reasons:

  • Using DNNSharp MyTokens - while this does work great even with complex HTML code snippets, there's not an easy-to-use editor for the tokens, especially as we are using database-based tokens to support a large number of portals under one install.
  • Using DNNSharp NavXP - this is what we used in another skin for the footer, and can be embedded as a skin object; however, it is too involved and configurable on the one hand, and not free-form enough for non-menu related content options on the other.
  • Xmod - this could be a solution for the "Footer Editor Page", but I haven't discovered an HTML editor based "field" to edit HTML code in a friendly non-programmer interface. Also, no ability to embed Xmod Query results directly into a skin object that I've found.
  • Just edit one page, add HTML modules to standard skin content panes and "Add to All Pages" - Not all pages will be using the same skin file with the same layout panes. "Add to all pages" always seems to create problems, too.

Does anyone have any ideas or suggestions to pursue? Thanks! David

 
New Post
11/17/2015 8:48 AM
 

Hi,

1) The OpenBlock module archive your needs.

- It contain a simple block module for managing simple text or html from the site admin menu.

- The content of the block module items can be injected by tokens by using the TEXT skinobject.

More info : https://openblocks.codeplex.com/wikip...

2) An other alternative which need a little development.

- Add a OpenContent module on a admin page with structured edit form that feed your needs.

- Create a skinObject that retrieve the content of the OpenContent module and inject it in your skin (i can help with that)

More info : https://opencontent.codeplex.com/

 

 
New Post
11/17/2015 9:19 AM
 
FBS Clarity wrote:

I'm working on a skin with a set of 4 footer panels with a responsive design. I'd like for the content in those panels to be editable in a central location, from which a skin object could pull that content and place it on every page where that skin file is chosen.

We are already doing something similar on this set of sites for simpler applications using MyTokens; however, I'd like the "footer editor page" to use a friendly HTML editor where the site's content editor can go to one admin page of the site, and edit the content or menu links for each of the 4 footer panels in that one place. I then envision using a skin object that will pull that content out of the database by PortalID and place that on the page in the layout pane of each page as defined in the skin template.

A few ideas that I've ruled out for various reasons:

  • Using DNNSharp MyTokens - while this does work great even with complex HTML code snippets, there's not an easy-to-use editor for the tokens, especially as we are using database-based tokens to support a large number of portals under one install.
  • Using DNNSharp NavXP - this is what we used in another skin for the footer, and can be embedded as a skin object; however, it is too involved and configurable on the one hand, and not free-form enough for non-menu related content options on the other.
  • Xmod - this could be a solution for the "Footer Editor Page", but I haven't discovered an HTML editor based "field" to edit HTML code in a friendly non-programmer interface. Also, no ability to embed Xmod Query results directly into a skin object that I've found.
  • Just edit one page, add HTML modules to standard skin content panes and "Add to All Pages" - Not all pages will be using the same skin file with the same layout panes. "Add to all pages" always seems to create problems, too.

Does anyone have any ideas or suggestions to pursue? Thanks! David

You could use open content, but why don't you use a reference of a module (display module on all pages)? That's how I solve this. You can in that case edit the content on any page and it will change on all pages.
 
New Post
11/17/2015 1:42 PM
 

Thanks for the suggestions, Sacha and Timo. I'll consider them carefully.

A couple more details - we already use MyTokens extensively through this set of sites - it appears that would be very similar to the OpenBlocks suggestion, as MyTokens does allow a skin object to inject the token value.  I like the availability of the Rich Text editor in the Open Content interface, and see that it could be customized to utilize whatever template I needed - however, would have to work on making it into a skin object, etc.

Timo, just using a reference of a module would be the most straightforward option - how "Display on all pages" would place the footer content on all the Admin pages, special use pages, PDF-generation source pages, etc. and have to be cleaned up for every site (and I'm looking at 150+ sites).  If only there were a way to reference/inject a particular existing module's content  through a skin object, I could just create a standard DNN page with the 4 footer modules as a central place for editing, and I'd be done.

 

 

 
New Post
11/17/2015 2:51 PM
 
FBS Clarity wrote:

Timo, just using a reference of a module would be the most straightforward option - how "Display on all pages" would place the footer content on all the Admin pages, special use pages, PDF-generation source pages, etc. and have to be cleaned up for every site (and I'm looking at 150+ sites).  If only there were a way to reference/inject a particular existing module's content  through a skin object, I could just create a standard DNN page with the 4 footer modules as a central place for editing, and I'd be done.

 

 

 Hmm, interesting. Only problem would be how to connect it to the right "Edit page"..

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Wanted: Skin Object or procedure to pull in centralized editable content blockWanted: Skin Object or procedure to pull in centralized editable content block


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.

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  

What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out