search

h5p / h5p-questionnaire

3 stars 37 forks source link

Expand 255 character limit for 'success screen answer' #4

Open SteelWagstaff opened 7 years ago

SteelWagstaff commented 7 years ago

We're trying to use the questionnaire H5P type to elicit open-ended responses from learners as they work through reading activities. We'd also like to offer them some substantial post-activity feedback, and include the text of a 'model answer' in some cases. The problem we're encountering is that the 'Text to display on submit' field appears to be limited to 255 characters of input, and we'd occasionally like to include more characters in our post-response 'success screen answer'.

screen shot 2017-09-29 at 1 23 46 pm

Here's an example of what this might look like: https://wisc.pb.unizin.org/rawrtest/wp-admin/admin-ajax.php?action=h5p_embed&id=29. You can see that the response we're trying to give post-completion is truncated because of the character limit. Is this something that we can change locally, or would you be open to a pull request that would expand the size of this field?

falcon-git commented 7 years ago

Very useful feedback. The person who probably put the limit in place is on vacation. She'll get back to you on this next week.

SteelWagstaff commented 7 years ago

@falcon-git Any news on this since the developer returned from vacation?

SteelWagstaff commented 7 years ago

@falcon-git, @thomasmars, @fnoks -- any update on this? Happy to contribute if helpful, would just need to be pointed to the place where that value is set ...

falcon-git commented 6 years ago

Hi @SteelWagstaff it seems the issue was assigned to our designer the developer way. Unfortunately she is on Christmas holiday now, but I've sent it to her in the designer way and I'm sure she'll get back to you in the beginning of January :)

jelenamilinovic commented 6 years ago

Thanks for the feedback. I created an issue for removing the character length limit. You can follow the issue here: https://h5ptechnology.atlassian.net/browse/HFP-1796.

slackuj commented 2 months ago

Hello, This issue seems resolved!, isn't it?