| |
|
|
|
|
|
|
|
|
|
 |  | |
| | |
| | |
| | |
 | | |
|
|
|
| Re: Module Settings Different for different portals |
|
|
Carlos,
I agree with the statement that you will be hitting the same portal regardless of which URL you enter in this case. I didn't meant to imply that you could customize settings based on the alias being used, but rather that the browser itself would think of the two sites as being completely different, and may have cached the pages temporarily for one of the URLs. In that scenario, one would potentially see two of the same pages configured differently , even though its the same portal (as the browser has the page cached for a particular URL).
However, I don't think setting the modules cachetime would make any difference in this scenario (as I thought it would earlier) -- as that is completely different from the browser keeping a cached version of a page or site.
Take care,
Ian
The leading provider of DotNetNuke support, training and custom development. |
|
|
|
| |
|
|
| Re: Module Settings Different for different portals |
|
|
Ruchir,
I feel I should also mention that you should probably have one of those two URLs redirect to the other (which is pretty easy to do in IIS) -- instead of having two URLs that reach the same content. Search engines really frown on duplicated content, which is the way they would interpret your site.
Take care,
Ian
The leading provider of DotNetNuke support, training and custom development. |
|
|
|
| |
|
|
| Re: Module Settings Different for different portals |
|
|
Hi Ian and Carlos,
I was busy in site completion and also I didn't get the notification of your replies so did not update this.
I have checked the code and knew that module settings are stored in cache using HttpRunTime.Cache and HttpRunTime.cache uses Temporary ASP.NET files for this.
The issue was that as my portal has to aliases www.domainname.com and www.domainname.co.nz and for IIS it’s two different web sites and because of this “Temporary ASP.NET files” folder contains two separate folders for each site. So when user request site www.domainname.com, module settings would be cached in folder of domainname.com and when user request site www.domainname.co.nz, module settings is stored in domainname.co.nz folder.
So when I change the module settings value from domaniname.com, cache of domainname.com is updated so it works fine but who will update the cache stored in domainname.co.nz folder.
I think there is only one way to resolve this is call Config.touch() method as it clears the cache of both folder.
Thanks,
Ruchir
|
|
|
|
| |
|
|
| Re: Module Settings Different for different portals |
|
|
Rachir,
You are most likely correct about the method that is needed to fix this, but it presents a few items that to me would be major warning signs of bad things to come.
1.) Calling config.touch() will restart the application, causing a delay in loading for anyone working in the site
2.) Serving the exact same content via 2 urls will put you very likely for penalty from Google and other search engines for duplicate content.
I would STRONGLY recommend doing as mentioned above and redirecting to a single URL!
-Mitchel Sellers
MCITP, MCPD, MCTS
CEO/Director of Development - IowaComputerGurus Inc.
Visit mitchelsellers.com for my mostly DNN Blog and support forum.
Visit IowaComputerGurus.com for free DNN Modules, DNN Consulting Quotes, and DNN Technical Support Services
I reccomend 3Essentials for shared hosting and BaseCamp for project management |
|
|
|
| |
|
|
| Re: Module Settings Different for different portals |
|
|
Hi,
Thanks for pointing out this two points. Now we both are on the same page.
1) Yes, Config.touch() method updates web.config file and it restarts my application. But I had tried to find out the other way to resolve this issue but didn’t succeed. Do you know other way to resolve this issue?
2) In my application I have one portal with two aliases. 50% modules of site are alias specific i.e if you visit www.domain.co.nz site then contact us module will display the contacts of New Zealand and if you visit www.domain.com site then the same contact us module will display company’s main office address. However there are some other modules which are general like announcements, terms &conditions, etc. So I cannot make two different portals. To resolve the Google search issue what I added “rel=nofollow” attribute for almost all links which redirects user to NZ portal.
Thanks,
Ruchir |
|
|
|
| |
| | |
| | |
| | |
|  |
| |
|
|
|
These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.
For the benefit of the community and to protect the integrity of the project, 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 DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.
|
| |
|
|
|
|
|
|
|
|