Re-Enable Landing page in DotNetNuke - dotnetnuke

I am new to DotNetNuke and Mistakenly have disabled the landing page of the my site built in DotNetNuke and now i am neither allowed to access my site nor am i able to login to my site.
How can i re-enable the disabled landing page.
Any suggestion will be highly appreciated.
Thanking you in advance

http://www.yoursite.com?ctl=login
This will allow you to login aa then you can update the settings.

You will likely need to get into the database and edit the PortalSettings table's content.
What setting did you actually change on your website? One of the "pages" drop downs from the Admin/Site Settings?
Look in the portalsettings table and find the columns for Login Home Splash page, etc, and set those to Null.
Though if you didn't change that, perhaps you mean you changed the "default" page in IIS? IF that is the case try going to www.yourwebsite.com/default.aspx?ctl=login to login

Related

DNN custom skin made login page disappear

I am new to DNN and I'm trying to make a site with custom skin.
Skinning is all ok but once the superuser is time out, I couldn't login again.
The login page has disappeared and was being redirected to an empty custom skin page which only shows the header and the footer.
I have tried
localhost:1234/login
localhost:1234/admin
localhost:1234/?ctl=
but neither of them are working.
I tried to search for solutions but none of them seems to work and not relating.
Please show me a way, if I am missing somethings.
You might look at the Admin/Event Viewer page if you happen to still be logged in somehow (or eventlog table in the database) to see if there is an error being thrown, that isn't being displayed (because you aren't logged in).
That may point to the problem.
You might have a problem with a "container" that is missing thus the module isn't being loaded.
A few other things to try, try
localhost:1234/?ctl=login
localhost:1234/?ctl=register
See if anything loads for those.
Last resort, go into the database and NULL out the SKinSRC columns on the TABS table and see if you can find the default site Skin setting in the PortalSettings and make that null or something other than your custom skin.

Remove or Customize the default popup skin in DNN 7.3

I am trying to customize the Gravity skin in DNN 7.3. Specifically, i would like to either remove the popup page that appears to users after they login ("welcome to your website"). However I couldn't find how to. Any ideas?
It used to be a Getting Started page found on the admin/page management page, but it appears that it is now loaded straight from DNNsoftware.com when you login for the first time.
I found a hostsetting that you can change in the DB to turn it off
UPDATE dbo.HostSettings SET settingvalue = 'false' WHERE settingname = 'EnableGettingStartedPage'
Once you run that you should clear the cache/restart the APP from the TOOLS menu in DNN in order to ensure the setting is updated for any future SuperUser accounts that login.

Dot Net Nuke issue with new page visible to Admin Only in Nav

I have an issue with DotNetNuke where only the admin can see a new page I've added in the main navigation (the page appears in sidebar for all users)
After creating a new page with DotNetNuke, I can manually browse to the page, and all links to it work however it is only visible in the navigation menu when I'm logged in as administrator.
Manually going to the page works fine when not logged in. Include in Menu? is checked (and been toggled) and I've tried all variations of permissions I can think of (which apart from the navigation issue work exactly as I would expect).
I hope this is the correct format I'm still relatively new!
Sounds like you have the page settings set to admin only for view... navigate to the page click on pages>page settings. click on the permissions tab and make sure inherit page settings from parent page is unchecked. Then next to All Users, Registered Users, Subscriber,
Translator (en-US), Unauthenticated Users and Unverified Users make sure there is a green check mark in the view section. Then make sure that page is disabled in advanced settings is unchecked and include in menu in page settings is checked.... Hope this helps... If not try making a new page and copy all the modules from the old one and see if that works

how to set visual force page as default in salesforce

I have a requirement that there is a user with particular profile and if he logs into the salesforce account, I want that he should be directly shifted to a visual force page. I tried to replace home tab with visual force page. But in profile this option is not editable. What I can do to accomplish this.
You could create a new "app". Apps are pretty much just sets of tabs (with exception of special stuff such as Service Cloud Console). In app you can define that there should be no home page, instead your visualforce (as a tab) would be added and marked as default landing page. Then you'd share this app with his profile and revoke access to other apps?
People can still add/remove tabs they wish to see in each app though so somebody might override your configuration.

Dotnetnuke 6 Ribbonbar Admin and dropdown gone

Above is the ribbonbar after I have logged in as a super user. The Admin option next to Host is completely gone
The site is running DNN6, the skin is only in the site portal folder, and it seems that all admin modules and options have gone away. Even the header, which I set in Site Settings (under Admin), went away!
Has anyone else had their admin options completely disappear on them? Is it possible that the skin is messing it up (all other sites use the same _default menu files and they work fine)?
Thanks for any replies.
We've recently had this exact situation occur in one of our DNN sites. It turn out that one of the site's administrators had accidentally renamed the Admin page from within the "Page Management" section (it's easy to see how that could happen). The fix was to go directly to /Admin/Pages.aspx and change the "Page Name" back to "Admin" ... and it will show up in the ribbon bar again.
As a suggestion to DNN developers, I would recommend making the Admin page and its subpages impossible to rename....
Can you check the database to see if those pages exist? What if you try to navigate to http://website/admin.aspx do you see the admin page and all the child pages there?

Resources