1-888-365-2779
+1-888-365-2779
Try Now
More in this section

Forums / Developing with Sitefinity / Why Can't The New Thread Page Use View State???????????!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Why Can't The New Thread Page Use View State???????????!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

3 posts, 0 answered
  1. Joe
    Joe avatar
    40 posts
    Registered:
    11 Sep 2007
    01 Apr 2008
    Link to this post
    I understand that this isn't directly Sitefinity related (although I may learn more about the answer myself when I dive into the Forum Module) but why can't the data entered in this rad editor be saved in view state?

    I just completed a decent sized post, then when I went to submit it was re-directed to the login page to re-authenticate, and bam 10 minutes worth of writing waisted because this forum doesn't use view state, and that isn't the first time this has happened to me here.

    Sorry, just had to vent.
  2. Gabe Sumner
    Gabe Sumner avatar
    440 posts
    Registered:
    09 Sep 2007
    01 Apr 2008
    Link to this post
    Yeah, that sucks.

    This is a problem not only here, but on many other web sites.  I'm so paranoid about this that I now copy all my stuff into Notepad before ever hitting submit.

    The way ASP.NET handles authentication it will do a redirect back to where you were before hitting submit.  However, "post" information gets lost in the midst of this redirect.  Which means you end up with a blank editor.   :(

    Gabe Sumner
    http://www.goondocks.com/

    Select All, Copy, paste into Notepad and now I click
  3. Georgi
    Georgi avatar
    3583 posts
    Registered:
    28 Oct 2016
    04 Apr 2008
    Link to this post

    Thank you Gabe, for taking a part into this discussion. You are right that "The way ASP.NET handles authentication it will do a redirect back to where you were before hitting submit".
    The viewstate for the editor is enabled but when your session timeouts, the viewstate information is destroyed. The only possible solution is this information to be saved somehow when the session timeouts and restored on logon.

    We will consider such feature in some of our next releases.

    What you can do to avoid this is increase the time of inactivity after which Sitefinity will force you to log in. This can be tuned in the web.config file:

    <authentication mode="Forms"
        <forms name=".ASPNET"  
          loginUrl="~/sitefinity/login.aspx"  
          protection="All"  
          timeout="1440"  
          path="/" /> 
    </authentication> 

    The value is in seconds.

    Regards,
    Georgi
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
Register for webinar
3 posts, 0 answered