Products

Solutions

Resources

Partners

Community

About

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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogUnable to read posts after upgrading to 3.5 of the blogUnable to read posts after upgrading to 3.5 of the blog
Previous
 
Next
New Post
11/14/2008 3:37 PM
 

I am posting this as a new thread in hopes that it will get fast attention.

I just upgraded my DNN 3.7 site from blog version 03.04.00 to 03.05.00.
I am now getting the errors mentioned above.

Changing out Friendly URL's is not an option because it would break many links.
I backed up my site so I could restore it, but I would much rather solve this another way.

Is their a way I could test to see if the 03.05.01 version resolves this issue.

Even if it is considered beta, it would beat the alternative of restoring my site.

you can mail me at pspeth1 at gmail dot com

Thanks

In another post Rip Mentioned 3.5.1

Rip Rowan wrote
 

I'm not 100% sure, but the changes we've made to the 301 redirection in 03.05.01 probably fix the problem you're having.  Hopefully the update will be released soon.

 
New Post
11/17/2008 9:42 AM
 

Phil - I feel your pain.  Unfortunately, DotNetNuke forbids the prerelease of beta code, so it is not in the team's power to give you 03.05.01.

I am sorry, and hope that 03.05.01 is released publicly very soon.


 
New Post
11/17/2008 12:59 PM
 

Rip Rowan wrote

Phil - I feel your pain.  Unfortunately, DotNetNuke forbids the prerelease of beta code, so it is not in the team's power to give you 03.05.01.

I'm only sort of trolling here, but...

Who made that decision?  Is there a good reason to restrict access to the source code for an open source project or is it just paranoia?  I can understand not calling the dev branch "stable" until after testing, but keeping the source for an open source project under wraps... that's insane.

Not trolling: Do you know who needs to be showered in abuse/convinced of the error of their ways? 

Because I don't think I can recommend DNN to ANYONE until source is available between the few and far between official releases. 


Chicago Data Solutions logo
Brian Begy
Managing Partner
Chicago Data Solutions
 
New Post
11/18/2008 3:46 AM
 

Hi Brian,

I understand your concern about this. I also know that many forum posts have been written about this without leading to a constructive solution. My belief is that this behaviour of the Corp is to grant the users high quality standards, and precise security rules. Unfortunately, this results in a painful and time-consuming release process, without the availability of beta source code available for download.

If you, and other users, dream of a different future for Dotnetnuke, please promote your ideas and make your suggestions to the right places, and don't ask the team members to violate the rules that they agreed to respect. We would love to give our job to a wide audience as soon as possible, because your feedback and your help are crucial for us to develop a better product.

Best regards,
Dario Rossa

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogUnable to read posts after upgrading to 3.5 of the blogUnable to read posts after upgrading to 3.5 of the blog


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