• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.

In general TWiki is good about preserving form field entry in the event of the user backing up.

BlogPlugin (at least in my install) lost the submission.

Does this do this elsewhere?

Thanks, Martin.


Wbniv reported the same thing and I made the same painful experience just recently after typing for nearly an hour frown .

This is not related to the BlogPlugin. The only thing that I can do is to remove as many of the mandatory flags as possible.

So which are the circumstances that come together in the BlogPlugin when creating a new posting? Here is the form to create a new posting:

<form action="%SCRIPTURL{"edit"}%/%WEB%/BlogEntryXXXXXXXXXX" method="post">
<input type="hidden" name="onlywikiname" value="on" />
<input type="hidden" name="templatetopic" value="BlogEntryTemplate" />
<input type="hidden" name="formtemplate" value="BlogEntryForm" />
<input type="hidden" name="topicparent" value="WebHome" />
<input type="hidden" name="topic" value="BlogEntryXXXXXXXXXX" />
<input type="hidden" name="BlogAuthor" value="%WIKINAME%" />
<input type="hidden" name="TopicType" value="%TOPIC%" />
<input type="hidden" name="TopicDescription" value="" />
<input type="hidden" name="action" value="form" />
<input type="hidden" name="Date" value="%SERVERTIME%" />
<input type="submit" class="blogSubmitButton" value="New Posting" />
</form>

Both, templatetopic and formtemplate settings, get lost clicking on back.

This needs further investigation to check the issue on a simpler setup.

Besides this error I would suggest to improve the workflow in the case a mandatory field is empty: redirect to edit right away and highlight the missing bit with an appropriate message instead to insist that the user should go back in his browser. That's what other webapps do.

Recasting it to "Engine" and "Urgent".

-- MD.

Here's what I tried:

| *Name:*| *Type:* | *Size:* | *Values:* | *Tooltip message:* | *Attributes* |
| Text | text | 50 |  a,b,c,d | Arfle | |
| MText | text | 50 |  a,b,c,d | Barfle | M |
In a topic, created this form:
<form action="%SCRIPTURL{"edit"}%/%WEB%/TestThreeXXXXXXXXXX" method="post">
Text: <input type="text" name="Text" />%BR%
MText: <input type="text" name="MText" />%BR%
formtemplate <input type="text" name="formtemplate" value="TestForm" />%BR%
<input type="submit" />
</form>
Typed in something to the Text field, left MText blank, hit submit. Got a mandatory field exception, so I hit back; and the correct value of Text was still there. Also tried with save instead of edit. This works as expected, so I'm bouncing this back to the BlogPlugin until it can be demonstrated on the engine with a testcase. See MandatoryTestTopic

CC

I think I saw this/similar behaviour only once or twice with Firefox. In both cases some time passed (30 mins+) from the loading of the page till the submit, and other tabs were used to browse the site in between.

I think there is nothing in the headers suggesting any timeconstraints, so I know this observation is not that helpful; just wanted to note it anyway.

Crasy idea: Perhaps this could be related to the internal cache mechanism in browser (submit page gets "swapped out" after some period)?

-- SP

I think SP is right. The page just displayed has been displaced from cache and is not added back again when visiting another... a thing that can't be fixed from within the BlogPlugin extension. The recent BlogPlugin releases removed the "mandatory" field almost all formfields despite those that can be set automatically.

Ponging this item back to "engine".

MD

Shame we don't have a "not our fault" status. I'm pretty much convinced wthis is a browser problem, and there's nothing TWiki can do about it. If someone can produce a testcase that proves otherwise, please go ahead and re-open it.

Discarded.

CC

ItemTemplate
Summary Mandatory field exception can result in lost URL parameters
ReportedBy TWiki:Main.MartinCleaver
Codebase ~twiki4
SVN Range Sat, 06 May 2006 build 10108
AppliesTo Engine
Component

Priority Normal
CurrentState No Action Required
WaitingFor

Checkins

TargetRelease n/a
Edit | Attach | Watch | Print version | History: r10 < r9 < r8 < r7 < r6 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r10 - 2006-09-19 - CrawfordCurrie
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback