Robert --- Thanks for this.
All over every module I've ever written, I've done the
NavigateURL(TabId, "", "name",value,"name",value); bit and now with 5.5.x, my inbox is blowing up with things like this. You're a gentleman and a scholar.
So, not aimed at you but just aimed at the cloud of DNN Team onlookers:
So, I don't mean to start something here and I know this isn't exactly the right location for this... but WHY? Why do we make the decision that in a x.5 release -- we (by we, I mean You -- DNN Team geniuses) are going to completely break backward compatibility for module developers in things like this. Really frustrating.
I mean, I understand, the need (or is it.. desire? yes. desire) -- to some degree - to mark a method as deprecated and eventually nuke it in the release schedule.
I wouldn't. Not when my app is used by 10's of thousands of module developers to house their apps. You're torturing module developers trying to keep with compatibility over multiple versions to make your code pretty. But whatever, we'll agree to disagree.
I just really don't understand how these releases can cause me and my developers so much work that add null value to my customers, just in trying to keep up with needless architecture changes.
As happy and thrilled as DNN once made me and as giddy as I once pitched it as a solution to my clients, I'm becoming really exhausted of where we're headed here, guys.
I'd really like to spend my time coding value-adds for my customers and not chasing my tail for completely changed or -- in this case -- broken method overloads.
Best,
Bill Dodd
DNN Frustrated Chief Developer, Gulf Technology
www.gulf-technology.com
bill.dodd[at]gulf-technology.com
Robert Collins wrote:
Thought I would share some thoughts.
I used to do URLs as follows:
NavigateURL(TabId, "", "name",value,"name",value); //(CSV)
This works fine until DNN 5.5.x and then it breaks.
I changed the calls to be like yours:
NavigateURL(TabId, "", "name="+value,"name="+value);
And it appears to work in all versions of DNN.
I thought I would share in case anyone else runs into this issue like I did.