Re: DotNetNuke (DNN) Upgrade to version 5 = NOT YET!!!!!!!!!!!!!!!!!!! (5.2.2)

Thanks for the nice blog :)

Re: DotNetNuke (DNN) Upgrade to version 5 = NOT YET!!!!!!!!!!!!!!!!!!! (5.2.2)

Hi Rashid, thank you for the comment. Are you the same Rishi who was trying to help me out? If you are, thank you very much for that!

I'm VERY surprised nobody else jumped in, like the guy who creates the module? He usually gets in there. I don't always like what he says, BUT I have a conclusion at least.If you are not, then that's cool too, sorry for the mistake, and thank you for leaving a comment!

I know I was a bit harsh but I get "invested" when doing an upgrade like this that's supposed to just work and I get something supposedly so simple as "An Error Occurred" and I can't figure it out! I played with languages, skins, and a few other shots in the dark. In the end, the only thing that worked, unfortunately, was backing everything out and return back to the ver 4 stream. Nasty solution IMHO.

PS I just left a message on your blog posting as well.
http://bestvisualization.blogspot.com/2010/01/blog-gives-error-after-updating-dnn-4x.html

Re: DotNetNuke (DNN) Upgrade to version 5 = NOT YET!!!!!!!!!!!!!!!!!!! (5.2.2)

Hi,
I just checked the below error and it looks like references to solpart. I may have a suggestion as i know solpart was retired in dnn 5 for dnnmenu (Solpart2) As i found out they not entirely compatable. Try as a possibiliy as i noticed you have custom containers switching to defauilt containers on the new http://www.pchenry.com/resources/blogs/2010/0126/AnErrorOccurredAsHost.png

Checkout http://dnngallery.net/Blog/articleType/ArticleView/articleId/139/DNNMenu-Improved-in-DotNetNuke-Version-514.aspx may help or as a test change ya default container to the new MinimalExtropy container and see if you still get the error. If not then update the current container to reflect changes.

Hope Helps
MK

Re: DotNetNuke (DNN) Upgrade to version 5 = NOT YET!!!!!!!!!!!!!!!!!!! (5.2.2)

Thank you Craig for your comment. Ya, I am using a custom skin/container (still learning about their interactions). I did try to change the skin to the default one and I even did try the minimum extropy one (thinking the minimum would help) but to no avail. I am going to check out the dnnGallery Blog you mentioned! I'm reading it now (need a fresh coffee first LOL). Thank you very much for the help, I value your input and attempt at trying to help me out.

Re: DotNetNuke (DNN) Upgrade to version 5 = NOT YET!!!!!!!!!!!!!!!!!!! (5.2.2)

Hi phenry,
I would try not to much the skin but the container you are using. As the container has the problem rather than the skin.

Regards
MK

Re: DotNetNuke (DNN) Upgrade to version 5 = NOT YET!!!!!!!!!!!!!!!!!!! (5.2.2)

Thanks for the heads up Craig! Much appreciated! I might give'er another go tonight and get back to you.

Re: DotNetNuke (DNN) Upgrade to version 5 = NOT YET!!!!!!!!!!!!!!!!!!! (5.2.2)

Hi phenry,
I would try not to much the skin but the container you are using. As the container has the problem rather than the skin.

Regards
MK

Re: DotNetNuke (DNN) Upgrade to version 5 = NOT YET!!!!!!!!!!!!!!!!!!! (5.2.2)

No Probs.... Hope it helps.

MK

Re: DotNetNuke (DNN) Upgrade to version 5 = NOT YET!!!!!!!!!!!!!!!!!!! (5.2.2)

Ran into your blog by accident right while I was ready to start using DNN Blog 3.5.1. Although this post made be think twice ;-) Anyway, the Codeplex site has new 4.0.0 Beta 3 available for download. You can see the Issue Tracker - and possibly post in there if you still have same problem with the 4.0. http://dnnblog.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=21003

Since you're a programmer (me too) - then that means you must live (or die) by the programmer motto: "Never give up", damn it, until you get the sucker working!

Re: DotNetNuke (DNN) Upgrade to version 5 = NOT YET!!!!!!!!!!!!!!!!!!! (5.2.2)

Hi Sheila, thank you for the comment! How did you do with your upgrade? Did you in fact, go ahead with it? How did it turn out? Is it a publically accessible site or private (if public, can I try the URL?)?

re developer motto
HAHA Very cool, I haven't heard that one before, BUT, have lived it for many years! HAHA Been there with linux (one night I had to last at home without going to Home Depot until 10:00PM, cause that's when it closed and I couldn't go buy a sledge hammer to go "Office Space" on the server box!).

re get the sucker working
HAHA! :> Have a good weekend.

Re: DotNetNuke (DNN) Upgrade to version 5 = NOT YET!!!!!!!!!!!!!!!!!!! (5.2.2)

Hi Phenry, great read. I have successfully donw an upgrade and all my exiting users that already had blogs worked fine. There was a need today for me tocreate a new user to use the blogs and encountered a similar issue to your self. I found in the bug tracker a reference when creating the blog, the language dropdown box was empty. this was due to a language not being installed on the system but this did not fix my issue as I had already had one installed.
What I ended up doing was copying the records of one of my existing users to a new row of the dnn_blog_blogs table and just changed the UserID field to the ID of the user I wanted to create a blog for.
Then when the new user logged in, the blog was already created and could then add new blog entries with no errors. let me know if you would like to see what the values of the fields look like if you have a blank table.

Re: DotNetNuke (DNN) Upgrade to version 5 = NOT YET!!!!!!!!!!!!!!!!!!! (5.2.2)

sorry the bug track blog link is
http://dnnblog.codeplex.com/WorkItem/View.aspx?WorkItemId=14072

Re: DotNetNuke (DNN) Upgrade to version 5 = NOT YET!!!!!!!!!!!!!!!!!!! (5.2.2)

Thank you Charlie for your comments, I'm looking at the link right now.

Interesting. I tried the "Language" thing, and like you, unfortunately it didn't work. My major hiccup with trying this again is when I did this the last time, the entire blog list was reproduced on all the blog readers looking to get updates. DOH! Going back in time is one thing, but only faking it isn't what I had in mind. :>

Thanks again for the comments, I'll post a reply here when I try this upgrade again.

Re: DotNetNuke (DNN) Upgrade to version 5 = NOT YET!!!!!!!!!!!!!!!!!!! (5.2.2)

Just read your blog and the original support forum postings on DNN Blog version 3.5.1 not working with DNN versions 5.0 and above. I wish I had read these BEFORE I upgraded my site! It's now more than A YEAR since the original errors were reported and the problem has NOT been fixed! To make matters far worse and, as you so eloquently pointed out, there is complete silence from the DNN Blog Module development community. I've been using DNN for several years now (since version 1.4) and am sorry to say I have noticed the quality of documentation and open source community support go down significantly over the past year or more. The change seems to have coincided with the decision to provide the "Professional" version as a pay for product. This is a real shame as I believe the energy and creative force that was driving DNN to continue to improve was the efforts and energies of the open source community and that model of doing business (which is very similar to the driving force behind Linux). I understand that obtaining capital can be a real help and even sometimes required to continue such projects and have no problem with offering "for fee" versions of the product to mainline customers such as corporations and large entities. RedHat has shown that this can be a successful venture while still maintaining the open source creative drive that fueled Linux development in the first place. Sadly, DNN seems to be following a different path one where only the paying customers get support and even then I don't know that the aid for product isn't as buggy as the "community" version. It may only mean that paying customers get "point" solutions to solve critical issues. I hate to say it, but it may be time to check out the PHP CMS and web application offerings. I see that even Microsoft is now pursing the PHP community and is actively building alliances with them.

Re: DotNetNuke (DNN) Upgrade to version 5 = NOT YET!!!!!!!!!!!!!!!!!!! (5.2.2)

Thank you very much American Wolf for your comments!

You've been working with DNN for a loooooong time then? WOW! I've only been doing it for a year and a bit. I can certainly see how disappointing it can be to go from lots of support/help/encouragement to almost null. That bites!

And you're saying the specific problem I'm seeing has been around for more than a year? DOH! Man, that's terrible on two fronts, one to not communicate fixes/work around, and two, to have that bug AROUND that long!

Ya, ya, for you DNN module person(s) reading this, you read that correctly, we got it right! Maybe from YOUR perspective there are many, many, many different reasons for it, but from our perspectives, the users (and some like American Wolf) who've been supporting you for a long time only see one BIG FAT ERROR! And it's growing in frustrations! You know, if I have to install something NEW (like a new DNN install and reconfigured it all over again..........) hhhhmmmm SharePoint ain't looking like a bad option????

re following a different path
Very true, and if you're right (and unfortuantely, all indications are pointing in that direction) it seems like DNN is going to SHOVE people over to SharePoint.

Thanks again for your comments and I hope we can resolve these issues soon. If not......onwards and upwards to bigger and better things! Have a good week!

Re: DotNetNuke (DNN) Upgrade to version 5 = NOT YET!!!!!!!!!!!!!!!!!!! (5.2.2)

guys i am another victim of this problem.

So changing container to minimal entropy would fix the problem?

Re: DotNetNuke (DNN) Upgrade to version 5 = NOT YET!!!!!!!!!!!!!!!!!!! (5.2.2)

Hi Id, thank you for the posting/comment. Unfortunately for me, the ONLY solution is to revert back to the 4.x stream. GGGRRRRR Not very acceptable, especially since I KNOW there's an updated version out there. The MOST frustrating thing of all though is the lack of support/feeback/help from ANYONE at DNN!!!!!!!!!

If you find a solution, please post a comment! The next time I try this will either by when someone posts a concrete "I did THIS and it worked!!!! YAHOO!" or a significantly updated/different/changed upgrade is released. Otherwise, I have better things to do with my time.

Thanks for your comment and good luck!

Re: DotNetNuke (DNN) Upgrade to version 5 = NOT YET!!!!!!!!!!!!!!!!!!! (5.2.2)

Henry, i would fix it if i would have been a developer (a skilled one), but i am not at good at these, i can only troubleshoot issues and tell the developers about problems.

However, if this something won't prevent me from posting new posts to blog module with dnn 5.2.3 i can live with it.

Re: DotNetNuke (DNN) Upgrade to version 5 = NOT YET!!!!!!!!!!!!!!!!!!! (5.2.2)

re not a good dev but can tell devs about probs
OH! Your a manager? DOH! Just kidding! It's Friday, just trying to be comical. :>

re can live with it
Unfortunately I'm not able to as the whole crux if this site, is to be able to blog about stuff. :> So I kind of need that functionality. I'll revisit this again in six or so months when I come up for air again. Starting to get into mobile dev now (maybe?) and I might be doing down deep there. We'll see...

Have a good weekend.