Problem with dotText ".Text" 0.95

Last post 08-09-2006 6:28 PM by steve harman. 1 replies.

Sort Posts:

  • Problem with dotText ".Text" 0.95

    01-25-2006, 2:10 PM
    • Member
      30 point Member
    • DaveNCheez
    • Member since 01-25-2006, 6:51 PM
    • Posts 6
    First I want to say:
    I have added a few enhancements to dottext from the original release.   I am currently using FreeTextBox 3.1.2 to allow firefox support.


    This however shouldn't cause the trouble I am experiencing.

    Basically when I make a post in dottext, everything works wonderfully as long as the post doesn't contain alot of HTML.


    If I have around 4 hyperlinks in a post, everything is golden.

    However, lets say I make a really long post, which is several paragraphs and contains 15 hyperlinks.

    In this situation when I click lkbPost to update or insert a new post, nothing happens after postback.

    In firefox, the edit post page simply turns into a blank white page.
    In IE, the edit post page gives error "You are not authorized to view this page"

    The database is never updated.

    I have tried to step through this in Visual Studio, however not code fires durring the lkbPost postback.

    It appears that something is happening on the clientside.

    If I update the text of the post manually in Query analyer, everything works wonderfully.
    so it's not on the display end, only the insert end.

    I am not sure exactly what is going on.

    Any help would be appreciated.

    I really enjoy .Text as a blong engine, Its just frustrating to have to use external apps to post.

    Thanks,
    Dave
  • Re: Problem with dotText ".Text" 0.95

    08-09-2006, 6:28 PM
    • Member
      128 point Member
    • steve harman
    • Member since 07-09-2006, 11:32 PM
    • Posts 38
    Do you happen to be using RDOS

    We use RDOS in subTEXT and noticed a similar issue that was resolved by changing the RDOS Config file. The fix we found was to set the trustedAddresses section to be a regular expression by adding the isRegex="true" attribute.  I can't recall the exact pattern that we used... but it was similar to the following:
    <trustedAddresses isRegex="true">
    <directory pattern="/admin/" isRegex="true" />
    </trustedAddresses>

    See the "Trusting Your Own Content" section here for more on that.
Page 1 of 1 (2 items)