Products

Solutions

Resources

Partners

Community

Blog

About

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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsForumForum4.3.2 comments4.3.2 comments
Previous
 
Next
New Post
3/24/2007 10:52 PM
 

Here we are in late March, and I've just encoutered this bug in the module too. Yet when I look at the entry for this in Gemini, it is listed as resolved.

Well, now, maybe it's just me, but when a module has a bug (i.e. a compatibility problem with SQL Server 2005) that causes an area on a major function of the module, it's not fixed until it's fixed in a module release. Right now, the only apparent fix is to dive into stored procedures, something that is fine for many folks but frankly, I've never done it and worry that I'm going to mess something up.

I gently suggest that the issue status be changed to pending so that it can truly be resolved.

Okay, sorry for the rant -- I just spent a bunch of time tracing obscure threads around only to arrive back where I started. Grrr.

Okay, rant over. <g>

 
New Post
3/24/2007 11:34 PM
 
I understand your rant, but Gemini is how I know what was changed and if you look everything has a date and a release which it was fixed in. I have always been fairly consistent w/ keeping up Gemini.

Chris Paterra

Get direct answers to your questions in the Community Exchange.
 
New Post
3/25/2007 12:57 PM
 
Tikkune wrote

 jliptak wrote
Order By (Alternative):
@Filter + ' GROUP BY P.ThreadID , P.CreatedDate ORDER BY P.ThreadID '

I chose the above method, and for my DotNetNuke 4.3.3 installation, it fixed the "My Posts" error.  Thank you, John.

For those like me who are new to DNN/SQL Server and such, the stored procedure that this fix has you modify resides inside the DotNetNuke Database.MDF database (assuming your database is named the typical/default: Database.mdf).  And if like me you do not know much about coding stored procedures let alone modifying them, you might use SQL Server Management Studio Express to Attach to the Database.mdf, then make your way down into Programmability > Stored Procedures > Forum_SearchGetResults - and make the change below to that stored procedure.

Before: @Filter + ' GROUP BY P.ThreadID , P.CreatedDate ORDER BY P.CreatedDate DESC '
+After: @Filter + ' GROUP BY P.ThreadID , P.CreatedDate ORDER BY P.ThreadID '

After you've modified the stored procedure, right-click and Execute to run/save the change.

This was very helpful -- I've never modified a stored procedure before and it was actually quite easy to follow your instructions. Thank you!

 
New Post
3/25/2007 12:58 PM
 

I sincerely apologize for my rant -- I was way out of line. (Having a bad day, but that was no excuse.)

Steve

 
New Post
3/25/2007 1:57 PM
 

No worries Steve, as I said I understand the frustration. I get just as frustrated when I enounter issues, fortunately I can usually fix them. Actually, my frustrations have been what has held the module up because I have been holding off release in this 2 month Beta to try, along w/ the beta team, to elminate all show stopper issues for 90% of use cases at least. We have been testing every possible scenario we can think of including:

  • Multi Portal usage
  • multi modules per portal
  • shared users across portals
  • DNN 4.4.0 -> 4.5 core bases
  • AD usage
  • single module instance on several pages
  • new installs
  • upgrades
  • dnn.com sized data
  • w/ or w/out object qualfier
  • dbo and non dbo database accounts
  • Various skins w/ new Default theme
  • Safar, IE, Firefox compatibility

While I cannot say at this point everything is pefect, we have tried really hard to make it very bug free. I see us finishing up this release for distribution either today or tomorrow. We will then have to submit to the DNN module release process, but that is the least of my concerns except it just takes time. I am trying my best to get this release packaged w/ DNN 4.5.0. You can view the latest build at www.dnnforums.com.

 


Chris Paterra

Get direct answers to your questions in the Community Exchange.
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsForumForum4.3.2 comments4.3.2 comments


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