Forum Notifications

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.
Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum.
This thread is closed to new posts. You must sign in to post in the forums.
2/16/2006 9:18:27 PM
Bernhard Herzog
Gravatar
Total Posts 1
View Posts

Forum Notifications

I have noticed that when changing the notifications on the forums page, the changes are not saved (I am using Firefox, MS Asp.Net and the trunk version). The CheckedChanged event is not called. I fixed this by setting EnableViewState to false in the repeater:

<asp:Repeater id="rptForums" runat="server"  EnableViewState="False">

Maybe this is of any help. PS.: I like MojoPortal, it is very clean, simple and easy to understand.
2/17/2006 1:32:14 PM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Forum Notifications

Hi Bernhard,

I would not have guessed that having viewstate enabled would cause an event not to fire. In fact in .NET 1.1 if you set enableViewState to false it will not fire the Item_Command. In any case we are not using the ItemCommand so it doesn't hurt to turn off viewstate which if anything will make the page lighter weight by sending less content so I have committed this change to svn. It may be that with viewstate enabled it was firing the ItemCommand instead of the CheckedChanged event and disabling viewstate in this case disables the itemCommand and therefore allows the CheckedChanged event to fire. Interesting.

In the 2.0 .net world things are a little cleaner because they separated controlstate from viewstate so the ItemCommand can still fire even with viewstate disabled.

In any case I have committed your change, thanks.

Thanks also for the compliment on the code, those are exactly the ideals I'm striving for.

Cheers,

Joe
You must sign in to post in the forums. This thread is closed to new posts.