0
Hello,
Did you guys noticed that if the user presses the back button the form entries are not cleared and user can submit the entry again creating endless identical submissions? Any feedback on this?
Did you guys noticed that if the user presses the back button the form entries are not cleared and user can submit the entry again creating endless identical submissions? Any feedback on this?
Responses (12)
-
Accepted Answer
-
Accepted Answer
0Good day to you again. Well, i assure you it is NOT normal. (others may agree with that). When user fills in any form, usually the form entries are cleared after submitting the form and no matter the browser, the form returns empty. I find it normal in 2015, which it doesn't happens on any other submission form (artist, album, song). It doesn't matter the cache of the browser. Or at least to prevent submitting the same form again, that would be a solution. I use other components with forms on my site and this is not happening.
I'm afraid i cannot suggest my site visitors not to use Chrome because it may keep cached records (and i don't mean form data auto-fill) and/or can create endless duplicated records.
I kindly ask you come up with a solution/feedback, because this haven't happened with forms from other extensions i'm using. Thanks in advance for your patience and hopefully understanding. If form data (let's say) cannot be cleared on browser's back button, at least a restriction of uploading the same content should be applied.
Thank you very much. -
Accepted Answer
-
Accepted Answer
0Hi. Let's say a user submits a song in the form (own songs). Then he publishes it by pressing submit. The song is published while he can press the browser's 'Back' button, and then the same entries in the form are not cleared out. If you press submit again, it will create the same entry (because the filled data is still there), so that means he can do that endlessly, creating a mess in the listing with no condition/restriction whatsoever.
My concern is: the user can upload the same file over and over by pressing back after submission and submit again. And then is also the matter of avoiding duplicated entries like the same song title or the same file, which is not recommended. -
Accepted Answer
0hello,
PLEASE as I mentioned, make a screenshot (or even better, a video) so I can see for sure what you mean.
for what you explain, if the fields are not cleared it because the BROWSER is keeping them (not music collection in any case!). I'm sure of that. that's why I ask you to make a video, because maybe I'm understanding well what you want to say. -
Accepted Answer
-
Accepted Answer
0hello
this is the BROWSER cache taht is filling them out. I'm 99,99% sure of it.
try this: after hitting the back button and seeing the form with the fields filled out, REFRESH the page (F5, I think). do the fields are filled out now?
if they are NOT (they are blank as they should be), then it means it's the browser cache. -
Accepted Answer
-
Accepted Answer
0Nevermind, problem is solved. But only for disabling caching from browser: after
Now the function of limiting the number of submissions is still a must-have. Any ideas?-
Germinal Campsmore than a month agohello,
good work with the autocomplete=off. that will disable the browser's undesired behavior.
what you mean about limiting the number of submissions? by user?
-
-
Accepted Answer
0I mean, user should not be able to submit unlimited songs/albums. First, he can flood the server, and second, he can waste disk space by having no restriction. The possibility of having a limit per user would be more secure. Let's say the value we can set it ourselves. Like maximum 10 song/albums per user.-
Germinal Campsmore than a month agoat the moment there's no current restriction, that would require some new code. we will think about it!
-
Your Reply
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »