There is a current install of DNN on one of my local webservers - this was installed before I took over this position. I am trying to add a second site, but the instructions I am following appear to be for attaching an existing site. Do I simply run the installer to create a new site in addition to the current? I've never used DNN before, so I am going at this blind.
All information I am finding is referencing the same as the instructions link I provided. Any assistance is greatly appreciated.
To add a little bit more information, here is another area where I am confused. Referencing the link, it states #2 to add a binding to my site, then #3 is to add the new portal. What I am trying to do is create a new DNN site - one does not yet exist, so I cannot do step 2 until a new portal is created. As said, I've never used DNN. I was tasked today to have this done by July 4th (nice, huh) so today is the first I am looking at DNN ever.
What I have done is added a new portal and I assumed it would create a new bare-bones site for me, but that is not what happened (obviously). So, instead of just adding an existing site for DNN, how do I add a new one (that is why I asked if I needed to reinstall)? From what I understand, there was an initial website setup with the installation of DNN. That basic site served what they needed - I need to do the same thing again, but, as can be seen, I've no clue how to do so.
No, you don't run the installer again. Remember DotNetNuke is PORTAL Hosting software, meaning with just 1 install you can run ~unlimited websites (of course there's always limits, depending on the hardware you're running on).
For instance if you're DNN install is running on www.myweb.com, and you want to add a site for www.yourweb.com, you simply point your DNS entry for www.yourweb.com to the IP of your DNN install, should be the same IP as www.myweb.com.
You then log into your DNN install as a HOST (superuser) user. You can't do this from using the Admin Login for www.myweb.com, that admin won't have the permissions to add a portal. When you do login as Host, you'll see two more menu items appear, 'Admin' and 'Host'. Admin pertains to functions you want to accomplish ONLY on www.myweb.com, the Host menu applies to the ENTIRE DNN install, including ALL portals you've setup.
Depending on your version number, you probably will see either 'Portals' or 'Site Management' (if it's a newer install, like 6.0+), once you click on or drop the HOST menu.
From there you fill out the specifics regarding your new www.youweb.com website, including the url and any aliases you want. Once you do that and the DNS propegates, you'll then be able to go to www.youweb.com and login and set that site up.
Step #2 is talking about adding a binding in IIS, not doing anything in DNN. You need to tell IIS about strategicplanning.mysite.com, so that it will send requests for that URL to your DNN site.
So, the process looks like this:
Make sure that the DNS record for strategicplanning.mysite.com points to your web server's IP address.
In IIS, update the host header bindings for the current application to include strategicplanning.mysite.com.
a. If you only have one portal in your DNN installation, at this point, trying to navigate to strategicplanning.mysite.com will automatically add it as a portal alias for that one portal.
b. If you have multiple portals in your DNN installation, at this point, trying to navigate to strategicplanning.mysite.com will show an error message about that URL not corresponding to an existing site.
In DotNetNuke, you need to go to the Site Management page in the Host menu (previously called Portals), and use the Manage/Action menu to add a new site. In the form that comes up, use strategicplanning.mysite.com as the alias (keep it marked as a parent portal), and fill in the rest of the details. If you want a blank site, make sure that you pick the Blank Website template (otherwise you'll need to delete a bunch of pages and modules you don't need).
This should be all that you need to do. If you navigate to strategicplanning.mysite.com and you see the original site, then strategicplanning.mysite.com has been added as a portal alias for that site, and you'll need to remove it (in Site Settings under the Admin menu).
Related
I'm doing a tutorial on communities, and after setting pages and themes, i wanted to add users. The access is made from the contact object.
I setup the community, but think i should have a link here
i setup the user of a contact like this:
User License = Customer Community
Profile = Customer Community User
Active = true
but when i try to log him in, i get: "Looks like this portal user is not a member"
I tried the same with another profile, a clone of the native Administrator profile, to which i added, in Profile Overview > App Permissions
Manage External Users = true
then, one by one, i activated all permissions, and still had that warning.
edit:
i'm using Classic
This is a developer licence
What am i missing?
The links disappeared because you killed off your own access to community (on Sysadmin, cloned profile etc). Do you remember editing this page? (sorry I had to censor some bits). If you removed System Administrator from the list of profiles - #fail.
If you can work with the new community and it's OK to have old one lying around - cool. If not - You might be able to resurrect it by exporting the community definition file, tweaking it and deploying back. I'm assuming you have some dev experience.
Prepare package.xml that contains
<types>
<members>*</members>
<name>Network</name>
</types>
Export the zip file (you don't neccessarily need developer tools, http://workbench.developerforce.com/ might be enough). Inspect the networks/YourCommunityName.network file. There should be a section similar to this
<networkMemberGroups>
<permissionSet>Censored1Access</permissionSet>
<permissionSet>Censored2Access</permissionSet>
<profile>Censored User</profile>
<profile>Admin</profile>
</networkMemberGroups>
Make sure "Admin" is on the list and deploy it back to org. It should give you access back and then you can add your customer community user's profile, permission set or whatever you plan to give them.
I run a DNN site where we have used a 3rd party module for several years to let our client administer their own users. Now that we are upgrading to DNN 9.2, that module no longer works, probably because of all the deprecated code.
I created a blank page, and added module "Users and Roles" to it.
Problem 1: It is not visible on the page, probably because it behaves more as a popup in the "admin" menu.
Problem 2: When I attempt to change that modules setting, I get an Exception:
ModuleLoadException: The file '/DesktopModules/Admin/Security/UserSettings.ascx' does not exist' Indeed, when I look for the file UserSettings.ascx it is nowhere to be found.
I need to give our client a way to edit their own users, without giving them Administrators privilege. How can I fix these problems?
Picked up an existing project built on Composite C1 version 4.3, and I'm trying to install a package. All the information online says to go to System -> Packages -> Install Local Package, but I don't even see a Packages option on the System page at all.
I've tried to see if this option was disabled or not available in this version, but nothing definitive so far.
EDIT:
I do have direct access to code, so if there's a config file I could edit it directly, but haven't found anything that indicates where this might be.
It looks like the account that you are logging in with isn't the main admin account. It's probably a developer account to which the admin has added the ability to make backups and tweak Google Analytics settings. You'll need to contact the admin and ask them to give you full privileges, in order to install packages yourself.
If you have FTP access to the website, there is a way to move an account from one group to another:
Open: ~/App_Data/Composite/DataStores/Composite.Data.Types.IUser.xml
Find the user account for the user you want to change group membership for, and make a note of the Id GUID value.
Open: ~/App_Data/Composite/DataStores/Composite.Data.Types.IUserGroup.xml
Find the group you want that account to have membership of (ie: Administrator or Admin), and make a note of the Id GUID value.
Open: ~/App_Data/Composite/DataStores/Composite.Data.Types.IUserUserGroupRelation.xml
Make a backup copy of this file, just in case it doesn't work!
In the origional, find UserId GUID matching your account Id, then ammend the UserGroupId to the group Id. Save the file.
I've tried this out on my local copy of C1 and it appears to work. You should now have access to everything the admin has access to.
i downloaded the old version of C1 4.3 from github and started a new site, and looks like something is wrong with your site, because this version have package manager.
Something error on Log's Folder? (no Console Log item found in your capture)
I tested on this version (see the image uploaded), so, wich especific version have you?
The two files I needed to change were IUserActivePerspective, and IUserGroupActivePerspective. The perspectives for what I was missing were removed from the admin account, so I just needed to add them back there.
We have three projects in Google App Engine, each of them have a custom sub-domain name mapped to it like this:
Project A: projecta.domain.com
Project B: projectb.domain.com
Project C: projectc.domain.com
That worked very well until we added a wildcard ssl-certificate to Project A. Suddenly all three subdomains are mapped to Project A.
They appeared under Project A, custom domains (Project A->App Engine->Settings->Custom Domains) and not one under each Project B and Project C, and when browsing to projectb.domain.com and projectc.domain.com, we get content from projecta.domain.com and not from b and c.
We have tried this but none of it fixes the problem:
Removed the SSL-certificate
Removed all custom domains and added them again
Disabled all projects, removed all domains, added them again
and enabled the projects
Logged in as different users, verify the domain again, add/remove etc
Two more notes:
We also have a fourth project, Project D (projectd.domain.com), which strange enough has not been affected and still works.
When trying to add a custom domain under project B or C (Project [B/C]->App Engine->Settings->Custom Domains), clicking on Add button does not give any response at all. Checking network, the click performs a call to Console servers, and when checking Project A (App Engine->Settings->Custom Domains), the custom domain name has appeared there instead.
Edit 1:
After deleting all custom domains in every project, when trying to add custom domain projectb.domain.com to Project B, we get this error message "This domain points to another app. If you point it to this app, the other app will stop working." But it does not appear in any another app. After confirming domain is not added.
Edit 2:
After deleting all custom domains in every project, when adding projectb.domain.com to Project B first, nothing appears. But when adding projecta.domain.com to Project A afterwards, both projectb and projecta appears under Project B. And when trying to delete projecta from projectb, we get the error message "Error. Failed to delete mapping.". Something is really wrong here.
Does anyone know how to access the domain mappings settings in any other way? It seams like the domain mapping data has been corrupted and we are stucked.
Edit 3:
For some unknown reason everything worked again after 8 hours of trying and failing, and I have no idea why. Suddenly I could delete all custom domains and when I added them they appear under the correct project. I've tried the exact same thing several times before. However, when I now add the SSL-certificate again every custom domain mapping moved by itself from their own project to the very project I added the SSL certificate to. Can somehow the SSL-certificate change the domain mappings?
I found a solution! There is a bug in Google App Engine Console when adding custom domains and connect to a ssl-certificate in different project right after each other.
ADDING CUSTOM DOMAINS
Steps to reproduce the bug:
Select a project in the toolbar
Goto App Engine->Settings->Custom Domains and after pressing "Add Custom Domain", add a sub-domain and press "Add"
Nothing happens, but when going back to "Custom Domains" the new subdomain appears there
Change project in the toolbar
Click on "Custom Domains", press "Add Custom Domain"
Add a sub-domain and press "Add"
The domain added in step 6 is now in fact mapped to the project selected in step 1.
Workaround
Make a page refresh in the browser between step 5 and 6.
CONNECT SEVERAL PROJECT TO WILDCARD SSL-CERTIFICATE
Steps to reproduce the bug
After uploading a Wildcard SSL-certificate
Select a project in the toolbar
Goto App Engine->Settings->SSL Certificate
Click on your SSL-certificate, then check the domain and press "Save"
Change project in the toolbar
Click on "SSL Certificate",
Click on your SSL-certificate, then check the domain and press "Save"
The custom domain previously connected to the project selected in step 5 is now added to the project selected in step 2.
Workaround
Make a page refresh in the browser between step 6 and 7.
I've been tasked with maintaining a DNN site that has been running for a while, so I copied it to my local development environment to get up to speed on the setup. I have the site up and running locally, and I can browse all (I think) of the pages. It seems to display correctly and yesterday, the DNN login worked correctly. However, today, when I try to login to manage changes, I enter my username and password on the login page, but it does not actually log in. On screen, all that seems to happen is that the password field clears. No error message displays. In my Firebug console, the only error message that appears is "Password fields present in a form with an insecure (http://) form action. This is a security risk that allows user login credentials to be stolen." Again, yesterday, I was able to log in and get to all of the DNN management features -- I changed skins, modified CSS, changed code, etc. I've tried multiple logins (host, superuser, and regular user) -- all have the same result.
I don't see anything in the database EventLog, except for a startup record.
I saw a couple of other SO posts tangentially related to failed DNN logins on development environment, and checked that Form Authentication is Enabled in IIS and the security for the site folders are set correctly and the folder is not read-only.
I generally use Firefox for development, but I also tried IE. I'm certain I'm missing sometime obvious, but it has me stumped. Ideas? I'm new to DNN, so I'm not up to speed yet on the best practices for debugging. Any other suggestions would be welcome.
Some details: Live site is SQL Server 2008; Dev is SQL Server 2012. Both sites use IIS 7. Dev is DNN 7.2.2. Locally, I'm using VS 2010 for development.
Couple of things to check.
1) Check to make sure your database connection strings (2 of them) in the web.config are both pointing to your local database.
2) Check to make sure the MachineKey values in the web.config still match the values in the production web.config
3) You might turn off SSL on the site, though you'll have to do that in the database as you can't get logged in. I believe you can likely just set Secure to 0 on all of the Tabs table records, but you might need to track down a HOST setting as well to make this work (hostsettings table)
An update. I was able to get this to work by using a different user account. I'm still not sure what the root of the problem was, but I believe it was related to specific settings on my particular user account. I used a generic 'admin' account, and was able to make it work.
Im experiencing the same issue, I think its something to do with the the .dotnetnuke cookie