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 ...Skinning question DNN 4.5.3Skinning question DNN 4.5.3
Previous
 
Next
New Post
6/13/2007 11:08 AM
 

Ok, I'll investigate further later on. But still, I'm sure it does work on DNN 4. Have a look at this portal. It's using 4.3.6 along with the PORTALNAME skinobject.

P.S : you can also try contacting the developer. I remember he's a core team member.

 
New Post
6/13/2007 12:32 PM
 

Put this in your skin:

<%= PortalSettings.PortalName %>

You can find more tips like this at the following link:

Some tricks for getting more DotNetNuke variables like SkinPath in your skin


DotNetNuke Modules from Snapsis.com
 
New Post
6/13/2007 1:19 PM
 

when i installed this as a module it didn't actually install.  no errors were reported, but no files were copied and no folders created.  so i FTPd the files manually and added the statements to the skin file.  I also contacted the manufacturer...no response.

 
New Post
6/13/2007 7:17 PM
 

Thanks John, that's a handy tip.

For the skinobject problem, please be advised that it MUST be uploaded through Module Definitions. The purpose of this action is to add to the system a tag which can be translated on the client side. Just go to Module Definitions ---> [SkinObject] , you'll understand what I mean. In your case, FTP action is not enough for the server to regcognize the tag.

So here's what you should do :

1. Choose install new module ---> PortalName (make sure you use the latest version 3.0.0)

2. The installation is successful if the details about extracting files and registering controls along with the "Installation successful" message at the bottom are shown.

3. To ensure that it is installed properly, go to Module Definition --> [SkinObject] and check if the PortalName control has been added or not.

(I assume that after you installed the module, you couldn't find the folder in Desktop Modules because you tried to find a folder name "Portal Name" ; the module folder is actually "VMasanas-PortalName")

4. Register the TagName and place it in the skin like usual.

I tested the skinobject on my local computer and it worked like a charm.

Hope this helps.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Skinning question DNN 4.5.3Skinning question DNN 4.5.3


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