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 ForumsRepositoryRepositoryPermalink pointing to the wrong contentPermalink pointing to the wrong content
Previous
 
Next
New Post
11/2/2008 5:10 PM
 

3.01.13 is the version that I was using, so "quite a while ago" seems like bit of an overstatement in respect of revisions.  If this kind of feature breaking error can be introduced in one revision then i'd rather not upgrade every time a new version comes out to be totally honest, no disrespect meant.
 

Steve Fabian wrote
 

I'm not sure what version of the Repository module you are using, but that particular issue was fixed quite a while ago. If you would use the latest version you would not have that issue.  The current version is 3.01.15

from the release notes of 3.01.14
=======================================================================
03.01.14 Build 35870
Released 08.01.2007
=======================================================================

-- Fixed an issue where the wrong item would be downloaded or opened if
   you clicked on a file link in a Dashboard on a different page then
   the Repository Module. The issue was a mispelled v13wstat3 variable
   that kept track of the item's ID. The code would check for mItemID
   but the code that set the variable was setting mitemID (lower case i)
   Since mItemID was always blank, it would default to the first item
   in the Repository instead of the item being displayed.
 

 
New Post
11/2/2008 5:14 PM
 

Regardless of that, just out of curiosity, I thought these modules went through "rigorous" testing?  I guess that test doesn’t involve any kind of regression testing?

 
New Post
11/2/2008 7:24 PM
 

it was fixed in Aug of 2007 and has remained fixed. In terms of software development .. that IS quite a while ago.

I'm really not sure what your point is. There was a bug over a year ago, I fixed it, it was tested and released as an update, since then a new update was released and regression tests were performed and the bug remained fixed.

If there is a bug in the version that you are using and it is an important issue for you .. and there is a newer version of the software that fixes the problem, I don't know what else I can suggest other than upgrading to the latest version.  No one is forcing you to upgrade. look at the release notes for each release, if it doesn't make sense for you to upgrade then by all means, don't upgrade.  If an upgrade will solve important issues, then I would suggest you upgrade .... seems pretty simple.  ..   no disrespect intended :)

 
New Post
11/3/2008 5:38 AM
 

Steve Fabian wrote
 

it was fixed in Aug of 2007 and has remained fixed. In terms of software development .. that IS quite a while ago.

I'm really not sure what your point is. There was a bug over a year ago, I fixed it, it was tested and released as an update, since then a new update was released and regression tests were performed and the bug remained fixed.

If there is a bug in the version that you are using and it is an important issue for you .. and there is a newer version of the software that fixes the problem, I don't know what else I can suggest other than upgrading to the latest version.  No one is forcing you to upgrade. look at the release notes for each release, if it doesn't make sense for you to upgrade then by all means, don't upgrade.  If an upgrade will solve important issues, then I would suggest you upgrade .... seems pretty simple.  ..   no disrespect intended :)

My point is that recently I was flamed for suggesting that there was a security flaw with one of the modules I'm using which caused my website to be hacked, I was informed that these modules went through rigorous testing.  Rigorous testing that would easily have picked up this permalink issue so then it wouldn't even have got into a release, unless I ended up with a beta release somehow?  As far as I know that was the build that came with the DNN that I installed.

 

 
New Post
11/3/2008 5:45 AM
 

Steve Fabian wrote
 

it was fixed in Aug of 2007 and has remained fixed. In terms of software development .. that IS quite a while ago.

BTW, in terms of software development, 2 revisions is not long ago, regardless of time frame.  The code doesn't change all the time you're not working on it.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsRepositoryRepositoryPermalink pointing to the wrong contentPermalink pointing to the wrong content


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