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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Portal disappeared after changing skinPortal disappeared after changing skin
Previous
 
Next
New Post
9/7/2008 3:20 AM
 

I have recently setup dnn on my own development server and have been playing with several modules and skins since last couple of months. I have downloaded a bunch of free dnn skins. Portal has been working well ever since I installed it but today when I switched between skins the site has become virtually inaccessible. I suspect its a faulty skin which has made all the pages invisible now and I have now no way to revert back. When I access the main url I am presented with empty page with two rectangles at the top (probably from the faulty skin which I tried switching to).

Is it possible now to get back my site. Thought of creating a brand new instance and then installing all those modules (I did buy one actually as well) and contents is giving me shudders.

thanks,

Hassan

 
New Post
9/7/2008 4:55 AM
 

Could it be that I applied a container / skin in a wrong way so as to lock myself out and that skin is not at fault ?

Here is what the source of the first page of my dnn site looks like now. Pasting here to see if it can provide any clue ...I don't know much about dnn from code perspective.

 

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html  lang="en-US">
<head id="Head">
<!--**********************************************************************************-->
<!-- DotNetNuke� - http://www.dotnetnuke.com                                          -->
<!-- Copyright (c) 2002-2008                                                          -->
<!-- by DotNetNuke Corporation                                                        -->
<!--**********************************************************************************-->
<meta id="MetaDescription" name="DESCRIPTION" content="My Website" /><meta id="MetaKeywords" name="KEYWORDS" content="DotNetNuke, DNN, Content, Management, CMS,DotNetNuke,DNN" /><meta id="MetaCopyright" name="COPYRIGHT" content="Copyright 2007 by My Website" /><meta id="MetaGenerator" name="GENERATOR" content="DotNetNuke " /><meta id="MetaAuthor" name="AUTHOR" content="My Website" /><meta name="RESOURCE-TYPE" content="DOCUMENT" /><meta name="DISTRIBUTION" content="GLOBAL" /><meta name="ROBOTS" content="INDEX, FOLLOW" /><meta name="REVISIT-AFTER" content="1 DAYS" /><meta name="RATING" content="GENERAL" /><meta http-equiv="PAGE-ENTER" content="RevealTrans(Duration=0,Transition=1)" /><style id="StylePlaceholder" type="text/css"></style><link id="_dnn484_Portals__default_" rel="stylesheet" type="text/css" href="/dnn484/Portals/_default/default.css" /><link id="_dnn484_Portals_0_" rel="stylesheet" type="text/css" href="/dnn484/Portals/0/portal.css" /><title>
    My Website > Home
</title></head>
<body id="Body">
    <noscript></noscript>
    <form name="form" method="post" action="/dnn484/Default.aspx" id="form" enctype="multipart/form-data" style="height: 100%;" autocomplete="off">
<div>
<input type="hidden" name="__EVENTTARGET" id="__EVENTTARGET" value="" />
<input type="hidden" name="__EVENTARGUMENT" id="__EVENTARGUMENT" value="" />
<input type="hidden" name="__v13wstat3" id="__v13wstat3" value="/wEPDwUJMjgzMDU3ODk3D2QWBmYPFgIeBFRleHQFPjwhRE9DVFlQRSBIVE1MIFBVQkxJQyAiLS8vVzNDLy9EVEQgSFRNTCA0LjAgVHJhbnNpdGlvbmFsLy9FTiI+ZAIBD2QWDAIBDxYCHgdWaXNpYmxlaGQCAg8WAh4HY29udGVudAUKTXkgV2Vic2l0ZWQCAw8WAh8CBThEb3ROZXROdWtlLCBETk4sIENvbnRlbnQsIE1hbmFnZW1lbnQsIENNUyxEb3ROZXROdWtlLEROTmQCBA8WAh8CBRxDb3B5cmlnaHQgMjAwNyBieSBNeSBXZWJzaXRlZAIFDxYCHwIFC0RvdE5ldE51a2UgZAIGDxYCHwIFCk15IFdlYnNpdGVkAgIPZBYCAgEPZBYCAgQPZBYCZg9kFhJmDw8WAh8BaGRkAgEPDxYCHwFoZGQCAg9kFgICAg8WAh8BaGQCAw8PFgIfAWhkZAIEDw8WAh8BaGRkAgYPDxYCHwFoZGQCBw8PFgIfAWhkZAIIDw8WAh8BaGRkAgkPDxYCHwFoZGRkJQM+AJfSp6o/hmKhyj7jtB4tBGU=" />
</div>

<script type="text/javascript">
//<![CDATA[
var theform = document.forms['form'];
if (!theform) {
    theform = document.form;
}
function __doPostBack(eventTarget, eventArgument) {
    if (!theform.onsubmit || (theform.onsubmit() != false)) {
        theform.__EVENTTARGET.value = eventTarget;
        theform.__EVENTARGUMENT.value = eventArgument;
        theform.submit();
    }
}
//]]>
</script>

 
New Post
9/7/2008 5:41 AM
 

please do not apply new skins for the complete portal or installation (in host settings) when testing, it is usually easier, if you apply it to single pages only. To re-access your site, you need to modify database directly, open Tables portals and host settings to remove the offending skin setting.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
9/7/2008 7:34 AM
 

In addition to Sebastian's advice, always test both skins and containers on a test page which you do not mind having to delete. Since the container is what provides the menu for accessing "Settings" and "Delete" - if there is a problem with the container, it may affect your access to that menu. Unless you are comfortable mucking around and directly updating the database to overcome such issues (and even if you are), the simplest and safest way to test containers and skins is on a page that you can delete without regret.


pmgerholdt
 
New Post
9/7/2008 12:14 PM
 

Thanks for the advice and pointers. Last night before going to sleep I tried something that worked for me. I opened the Skins and table and found which skin exactly I was trying (since I was merely clicking through skins) and then proceeded to rename the skin folder so that it becomes inaccessible. Portal appeared back again and I proceeded to switch to a known working skin.

Now i am not sure if that alone provided a fix since I had earlier copied all the files of a working skin under \Portals\_default\Skins\_default folder and had hide (by renaming) the file 'No Skin.acsx'. Had done the same thing with \Portals\_default\Containers\_default and 'No Container.acsx' file.

DNN did complain about these files being missing at that point I restored them.

Testing a skin on a single page is a good idea.

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Portal disappeared after changing skinPortal disappeared after changing skin


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