dnnJungle: Resources for the DotNetNuke Community

Forum Home

DotNetNuke Development

HelloWorld Tutorial

MinMax Persiste...

MinMax Persistence

shodan

2 posts

Joined
1/12/2006

MinMax Persistence
Posted: 13 Jan 06 9:28 AM

Hi all, i'm kinda new to this and i'll be grateful if someone could help me. I can't figure out where this error is coming out:

A critical error has occurred.
MinMax persistance type of cookie requires a ModuleId

i'm using vb2003/dnn3.2.2/mssql2000

have gone throught dnnjungle tutorial a couple of time starting both from zero and every time i add my custom module to a page it kicks out that damn red phrase.
The whole project compiles without any error, i red some thousands of asp.net forums posts regarding this argument but none seems to solve my problem...

i thanks everybody for the patience ^^ì and for any help you could offer,

thanks again - shodan

dnnjungle

149 posts

Joined
3/13/2005

Re: MinMax Persistence
Posted: 14 Jan 06 12:11 AM

Shodan,
I've never seen that error but seems it's related to some errors on namespaces or class names.
Take a look a this post: http://forums.asp.net/1150834/ShowPost.aspx

shodan

2 posts

Joined
1/12/2006

Re: MinMax Persistence
Posted: 16 Jan 06 1:12 AM

Finally i solved, but i don't even know how... anyway i'm grateful for ur help but i found my answer here: http://www.dotnetnuke.dk/Default.aspx?tabid=61#26

i simply added in my view[modulename].ascx.vb under InitializeComponent() this:

MyBase.Actions.Add(GetNextActionID, "Edit Page List", "", _
     Url:=EditURL(), Secure:=SecurityAccessLevel.Edit)

now everything seems fine, my custom module is working correctly now.
I hope this thread quickly solve time to other people that is struck with my same problem,

thanks everybody - Shodan (be passing by now and then ;] )

hou2you

1 posts

Joined
3/7/2006

Re: MinMax Persistence
Posted: 12 Mar 06 7:42 PM

Ive been having the same problem, but the only difference for me is that I am using C# not VB. This could be my answer as well, but I'm not sure how to transpose this from VB to C#. I originally thought it could be my NavigateUrl, but all of the dnn modules have the same exact NavigateUrl. If I take out the NavigateUrl and load it, everything works except I can't edit any of my entries.

This is my NavigateUrl : EditUrl("itemid", DataBinder.Eval(Container.DataItem,"ItemID"))

Please help!!

Nick.Bronson

1 posts

Joined
4/11/2006

Re: MinMax Persistence
Posted: 10 Apr 06 10:13 PM

2 Days i've chased this bug as well and i've finally found a solution. Please write back and let us know if it solves your particular case.

Seems that VB.Net is once again a bit lax when it comes to enforcing hard typing. It would appear that the expression EditUrl( .. ) takes, as parameters, either 2 or 3 strings (depending on which overload you use.)

However, DataBinder.Eval(Container..... .... ) is contracted only to return a type object, and seems to return in this case an int32 (Not surprisingly, the type of ItemID). VB seems to convert that to a string without asking but C# enforces strong typing and needs express permission.

The following eventually worked for me, let me know if it works for you.

NavigateUrl='<%# EditUrl("ItemID", DataBinder.Eval(Container.DataItem, "ItemID").ToString()) %>'>

Make sure that you use single quotes ' ' around the code section as well and not double quotes ( " " ). For some reason known only to language designers, that makes a difference in this particular case.

bruceutn

2 posts

Joined
4/24/2006

Re: MinMax Persistence
Posted: 01 May 06 5:23 PM

MyBase.Actions.Add(GetNextActionID, "Edit Page List", "", _
     Url:=EditURL(), Secure:=SecurityAccessLevel.Edit)

Show this error:

The name has not been declared 'SecurityAccessLevel'.

Please. Help me.

bruceutn

2 posts

Joined
4/24/2006

Re: MinMax Persistence
Posted: 01 May 06 5:26 PM

MyBase.Actions.Add(GetNextActionID, "Edit Page List", "", _
     Url:=EditURL(), Secure:=SecurityAccessLevel.Edit)

Show this error:

The name has not been declared 'SecurityAccessLevel'.

Please. Help me.

shodan wrote
Finally i solved, but i don't even know how... anyway i'm grateful for ur help but i found my answer here: http://www.dotnetnuke.dk/Default.aspx?tabid=61#26

i simply added in my view[modulename].ascx.vb under InitializeComponent() this:

MyBase.Actions.Add(GetNextActionID, "Edit Page List", "", _
     Url:=EditURL(), Secure:=SecurityAccessLevel.Edit)

dnnjungle

149 posts

Joined
3/13/2005

Re: MinMax Persistence
Posted: 03 May 06 10:07 AM

SecurityAccessLevel is an Enum defined in DotNetNuke.

I might be missing a Imports for the namespace where this is defined. I'm not sure which one it is right now, look in DotNetNuke.Security or DotNetNuke.Entitities.Modules.

lmontin

3 posts

Joined
5/9/2006

Re: MinMax Persistence
Posted: 24 May 06 6:52 AM

I found that if you are creating modules by copying other ones then modifiying them (rather than creating new modules from scratch) you need to remember to add the new module projects as references in the buildsupport project before you compile (this assumes you are using the core solution in vis studio 2003 to create your modules)

hope this saves someone the 4 hours it took me to figure it out ...

lmontin

3 posts

Joined
5/9/2006

Re: MinMax Persistence
Posted: 03 Jun 06 12:27 AM

just to elaborate on that .. buildsupport copies the dll files in its references to the bin directory .. if you are working on a new module project - you need to make sure the dll file created on compile/build gets added to the dnn\bin dir else you will the minmax error.
So you can either copy the newly created dll file to the bin dir yourself or if you have a reference to the dll file (note I mean a ref to the actuall dll not just a reference to the project) in buildsupport (and the buildsupport project is in your solution) it will copy it the bin for you.

Page 1 of 2

DotNetNuke Development

HelloWorld Tutorial

MinMax Persiste...