Privacy page always points to site 1 page, even with several sites added

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.
Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum.
This thread is closed to new posts. You must sign in to post in the forums.
5/27/2013 4:52:31 PM
Gravatar
Total Posts 5

Privacy page always points to site 1 page, even with several sites added

Not a great big deal, and I thought it might be fixed in latest download so i upgraded to 2.3.9.7, however, it is not.

Windows server 2003, Microsoft sql server 2008 running mojoportal 2.3.9.7

But when you create a new site, the privacy page points to main/first site, and only the file name can be change but not the site.

Example, site1 is thissite.com, site 2 is thatsite.com

The privacy page on site one says www.thissite.com [/privacy.aspx]

The privacy page on site two say www.thissite.com[/privacy.aspx] where it should point to www.thatsite.com/whatever.aspx

The actual page name; /privacy.aspx can be changed and appears in a text box, but the site designation is not in a text box, and therefore can NOT be changed.

My site has two additional site running, so this doesn't happen to the first added site. It happened to two sites.

Guess  I can scour through the database and see if it can be changed there, and in the meanwhile I don't require a privacy page yet.

But it is something that appears to be a minor bug.

David

 

5/28/2013 10:32:40 AM
Gravatar
Total Posts 18439

Re: Privacy page always points to site 1 page, even with several sites added

Sorry but I cannot reproduce this problem and looking at the code for PrivacyPageLink.cs I do not see how it is possible for it to use a different host name than the one used by the containing page.

I just added it to our demo site in the art41-bookheader skin and it correctly points to demo.mojoportal.com/privacy.aspx even though the demo site is not the root level master site, it is a child site in a multi site installation. (though the actual page does not currently exist in the demo site the link is correct, all I would need to do is actually create the page). For the base part of the url it uses SiteRoot property of mojoBasePage which is used alsoi by all kinds of other links so if it were not working correctly there would be lots of incorrect links not just the privacy link, but it is working correctly as far as I can see.

5/28/2013 6:55:21 PM
Gravatar
Total Posts 5

Re: Privacy page always points to site 1 page, even with several sites added

Sorry for taking you away from useful work.

This "appears" to happen when you are on the main site and create child sites. The site as created and the site settings viewed through the main site admin, the privacy page shows the mainsite privacy page.

This happens any time you look at the child site through the main site admin interface.

However, when logged into the child site admin, the privacy page points to the correct child site privacy page.

Maybe a small doc note would avoid confusion, in case anyone else sees it from the main site admin.

But I am no longer confused, and appreciate the good work. When DotNet Nuke was new and developing, I all over it, and had a number of sites running it. The need for those sites went away.

Now I needed a couple more and converting some of my old sites (not dotnetnuke sites as they were for an old client) to Mojoportal.

It feels very much easier than I remember DotNetNuke.

Once again, thanks for your efforts and quick response.

David

You must sign in to post in the forums. This thread is closed to new posts.