[xwiki-users] Attachments on new pages that contain 'Objects' of 'Class'.
XWiki has the nice feature of Class and Class related sheets and templates. I feel there is a annoying bug with regard to uploading attachments, although XWiki experts explain why it's happening. (they do not confirm it's a BUG!!) When you create a Class, Sheet and Template there is a moment to add a new-object on a page. In XWiki you could, like app-within-minutes, create a button: Create new "record of something" The user will then see a new-page in inline edit mode (a html form) and usually a few buttons: Save and View, Save and Continue and Cancel. I think the last one: 'Cancel' is why the 'In my opinion BUG' is happening. The new document and object are not yet saved... You are first considered to fill in the form and when you reconsider or not able to fill in all the required fields there is 'Cancel'; nothing saved and gentle exit (although sometimes you get: XWiki document does not exist, a smarter CANCEL that would redirect you to the page with the creation option...) But now about my BUG; If the form contains a option to upload a attachment (like the avatar image on XWikiUsers) we get very user unfriendly things. The explanation of the error is; you can not attach anything to a page not yet saved! But the results are quite dramatic; a page, sometimes two are created, but not containing any object (so all the data in the form is lost). The user is not informed about what happened... What coding can be done to prevent the above.. Why I consider it a BUG? The same problem occurs when you have a Large Text field with the wysywig editor. This editor has a button 'Image' or 'Attachment'. How can we then prevent the problem occurring? Gerritjan
I would... ...let the users fill in the form ...let the users browse for attachments and store these "vars" Only when the user hits "Apply" (or "Save and View"), then... ...create the page (with the contents from the form) ...attach all the attachments from the stored "vars" If the user hits "Cancel", then no page will be created and no attachments will be uploaded. -- View this message in context: http://xwiki.475771.n2.nabble.com/Attachments-on-new-pages-that-contain-Obje... Sent from the XWiki- Users mailing list archive at Nabble.com.
Hello, Personnally I would merely add some hints on concerned fields (wysiwyg, attachment chooser, ...) to warn users that they must first save the page one time THEN re-edit it to add this information, or you could update your Sheet in edit mode to not display those fields if object does not yet exist. That's what is done on xwiki org when you contribute an extension. BR, Jeremie 2014-03-27 10:16 GMT+01:00 Gerritjan Koekkoek <[email protected]>:
XWiki has the nice feature of Class and Class related sheets and templates. I feel there is a annoying bug with regard to uploading attachments, although XWiki experts explain why it's happening. (they do not confirm it's a BUG!!)
When you create a Class, Sheet and Template there is a moment to add a new-object on a page. In XWiki you could, like app-within-minutes, create a button: Create new "record of something"
The user will then see a new-page in inline edit mode (a html form) and usually a few buttons: Save and View, Save and Continue and Cancel.
I think the last one: 'Cancel' is why the 'In my opinion BUG' is happening. The new document and object are not yet saved... You are first considered to fill in the form and when you reconsider or not able to fill in all the required fields there is 'Cancel'; nothing saved and gentle exit (although sometimes you get: XWiki document does not exist, a smarter CANCEL that would redirect you to the page with the creation option...)
But now about my BUG; If the form contains a option to upload a attachment (like the avatar image on XWikiUsers) we get very user unfriendly things. The explanation of the error is; you can not attach anything to a page not yet saved! But the results are quite dramatic; a page, sometimes two are created, but not containing any object (so all the data in the form is lost). The user is not informed about what happened...
What coding can be done to prevent the above..
Why I consider it a BUG? The same problem occurs when you have a Large Text field with the wysywig editor. This editor has a button 'Image' or 'Attachment'. How can we then prevent the problem occurring?
Gerritjan _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
participants (3)
-
Gerritjan Koekkoek -
Hamster -
Jeremie BOUSQUET