Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Successfully upgraded 600 to 610 but unable to browse itSuccessfully upgraded 600 to 610 but unable to browse it
Previous
 
Next
New Post
12/4/2011 5:42 AM
 
Saeed Ali hosseini


www.saeedalhs.net
Joined: 6/10/2007
Posts: 31
Costas Zividis wrote:
Apparently this is a hosting setup, after i opened a ticket with my hosting company ... they fixed it.

 Hi Costas Zividis,

Could you please ask your hostting company how did they fixed it? I'm facing this trouble yet. Thanks.

سعید علی حسینی

w w w . a l i h o s s e i n i . n e t

 
New Post
2/21/2012 5:13 AM
 
Olivier Chicaud

Joined: 6/19/2008
Posts: 5

I migrated to windows 2008 R2 and DDN 06.01.03 and I still had the problem
but ... only in production with fixed IP, and not when the server was connected in dev, with dynamic address

 In my netwrok config, I only hav e1 prefered DNS server. I filled the second one (but it's a fake. I even don't know where it points) and now it works.

 I also deactivated IP V7, but I don't know if it has an inpact.

However, not having the possibility to have only one DNS server could  it be considered as a bug ?

caresses,
 
New Post
4/10/2012 3:03 AM
 
Saeed Ali hosseini


www.saeedalhs.net
Joined: 6/10/2007
Posts: 31
  • I disabled the clientDependency part in web.config, voila the site successfully loades and the dashboard shows that it was upgraded, but it is displayed now in a messy and garbled format, nothing is in order and all the menu items are displayed.
  • The second time I completely replaced the clientDependency part with its equivalent part in the Standard Configuration described here: Client Resource Management Web.config The site successfully loads but again in a messy and disordered format.

Note:

  1. Here's the old part that I removed from the web.config:
    <clientDependency version="0" fileDependencyExtensions=".js,.css">
        <fileRegistration defaultProvider="LoaderControlProvider">
          <providers>
            <add name="DnnBodyProvider" type="DotNetNuke.Web.Client.Providers.DnnBodyProvider, DotNetNuke.Web.Client" enableCompositeFiles="false" />
            <add name="DnnFormBottomProvider" type="DotNetNuke.Web.Client.Providers.DnnFormBottomProvider, DotNetNuke.Web.Client" enableCompositeFiles="false" />
            <add name="PageHeaderProvider" type="ClientDependency.Core.FileRegistration.Providers.PageHeaderProvider, ClientDependency.Core" enableCompositeFiles="false" />
            <add name="LazyLoadProvider" type="ClientDependency.Core.FileRegistration.Providers.LazyLoadProvider, ClientDependency.Core" enableCompositeFiles="false" />
            <add name="LoaderControlProvider" type="ClientDependency.Core.FileRegistration.Providers.LoaderControlProvider, ClientDependency.Core" enableCompositeFiles="false" />
            <add name="DnnPageHeaderProvider" type="DotNetNuke.Web.Client.Providers.DnnPageHeaderProvider, DotNetNuke.Web.Client" enableCompositeFiles="false" />
          </providers>
        </fileRegistration>
        <compositeFiles defaultFileProcessingProvider="DnnCompositeFileProcessor" compositeFileHandlerPath="~/DependencyHandler.axd">
          <fileProcessingProviders>
            <add name="CompositeFileProcessor" type="ClientDependency.Core.CompositeFiles.Providers.CompositeFileProcessingProvider, ClientDependency.Core" enableCssMinify="false" enableJsMinify="true" persistFiles="true" compositeFilePath="~/App_Data/ClientDependency" bundleDomains="" urlType="MappedId" />
            <!-- For webfarms remove the above CompositeFileProcessor and uncomment this section
                <add name="CompositeFileProcessor" type="ClientDependency.Core.CompositeFiles.Providers.CompositeFileProcessingProvider, ClientDependency.Core" enableCssMinify="false" enableJsMinify="true" persistFiles="true" compositeFilePath="~/App_Data/ClientDependency" bundleDomains="" urlType="Base64QueryStrings" />
                -->
            <add name="DnnCompositeFileProcessor" type="DotNetNuke.Web.Client.Providers.DnnCompositeFileProcessingProvider, DotNetNuke.Web.Client" enableCssMinify="false" enableJsMinify="true" persistFiles="true" compositeFilePath="~/App_Data/ClientDependency" bundleDomains="" urlType="MappedId" />
          </fileProcessingProviders>
        </compositeFiles>
      </clientDependency>
  2. and the new part which I copied is as:
    <clientDependency version="0" fileDependencyExtensions=".js,.css">
                    <fileRegistration defaultProvider="LoaderControlProvider">
                        <providers>
                            <add name="DnnBodyProvider" type="DotNetNuke.Web.Client.Providers.DnnBodyProvider, DotNetNuke.Web.Client" enableCompositeFiles="true" />
                            <add name="DnnFormBottomProvider" type="DotNetNuke.Web.Client.Providers.DnnFormBottomProvider, DotNetNuke.Web.Client" enableCompositeFiles="true" />
                            <add name="PageHeaderProvider" type="ClientDependency.Core.FileRegistration.Providers.PageHeaderProvider, ClientDependency.Core" enableCompositeFiles="true"/>
                            <add name="LazyLoadProvider" type="ClientDependency.Core.FileRegistration.Providers.LazyLoadProvider, ClientDependency.Core" enableCompositeFiles="true"/>
                            <add name="LoaderControlProvider" type="ClientDependency.Core.FileRegistration.Providers.LoaderControlProvider, ClientDependency.Core" enableCompositeFiles="true"/>
                        </providers>
                    </fileRegistration>
                    <compositeFiles defaultFileProcessingProvider="CompositeFileProcessor" compositeFileHandlerPath="~/DependencyHandler.axd">
                        <fileProcessingProviders>
                            <add name="CompositeFileProcessor" type="ClientDependency.Core.CompositeFiles.Providers.CompositeFileProcessingProvider, ClientDependency.Core" enableCssMinify="false" enableJsMinify="true" persistFiles="true" compositeFilePath="~/App_Data/ClientDependency" bundleDomains="" urlType="MappedId" />                
                        </fileProcessingProviders>
                    </compositeFiles>
                </clientDependency>

سعید علی حسینی

w w w . a l i h o s s e i n i . n e t

 
New Post
5/30/2012 7:23 AM
 
Olivier Chicaud

Joined: 6/19/2008
Posts: 5

The problème came back again while nobody changed anything on the site for weeks. Maybe the network config changed, but I have no way to know.

Then I changed the jquery settings in the host config and I disabled "use hosted version" .
mayby using "http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js" as an hosted source was not a good idea.

Now it works.

ps : I just upgraded to 6.2, and it still works

 
New Post
6/9/2012 1:57 AM
 
Saeed Ali hosseini


www.saeedalhs.net
Joined: 6/10/2007
Posts: 31
A new issue related to this error is registered in DotNetNuke Issue Tracker at:
http://support.dotnetnuke.com/issue/V...

Please write any useful hint/info in resolving the problem there, too.

سعید علی حسینی

w w w . a l i h o s s e i n i . n e t

 
 Page 3 of 4
Previous1234Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Successfully upgraded 600 to 610 but unable to browse itSuccessfully upgraded 600 to 610 but unable to browse it


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