What would cause the text entry boxes to become unclickable (sporadically)? This occurs on a web server and also in the client's LMS, occasionally. The user is completely stuck, since we require input to move ahead. It seems to happen in FireFox and Safari, but not IE10. I think it may be related to security issues in the browsers. If I understood how the text entry functions, it might help. Any thoughts?
We are having a similar issue. In Review 360, my reviews cannot get the text entry boxes to work. However, when i view on my end everything works correctly. I have attached my .story file and the link to the Review. Could someone please take a look.
Hi there, I'm having exactly the same issues - I'm using Edge and it works perfectly for me, but my reviewers who are using review 360 cannot type text into the text entry fields. This is super urgent as my modules need to be published at the end of this week.
I'm sorry you're running into this issue as well! Can you confirm that you've reviewed the course in Review 360 using Edge as your browser?
We do have related bug reported to our team where text entries aren't focusing in Review 360 when using Internet Explorer 11.
I'm wondering if your reviewers are using IE11 and if it's possible to use a different browser in the meantime? We'll be sure to pop back in here to let you know as soon as we have an update.
For what it's worth, I've been having issues with text entries using IE11 both in Review and our LMS. A workaround is to ask the user to press the TAB key once, which seems to bring the text entry into focus, allowing them to enter text. Not ideal, but at least it's an option until the issue gets resolved.
I've just had this issue reported to me - I've sent a course via review 360, works perfectly for me on internet explorer and chrome, however an external party was unable to edit a text field.
I've asked them what browser they were using, but any thoughts persons have in the meantime would be appreciated.
I see a lot of mention about HTML and flash in this discussion - given that flash is being increasingly unsupported by browsers, could this be an issue?
I've just had this issue reported to me - I've sent a course via review 360, works perfectly for me on internet explorer and chrome, however an external party was unable to edit a text field.
I've asked them what browser they were using, but any thoughts persons have in the meantime would be appreciated.
I see a lot of mention about HTML and flash in this discussion - given that flash is being increasingly unsupported by browsers, could this be an issue?
Update - I have had this issue reported to me by a second user.
Both users were using internet explorer though I don't know what version.
Attached is screengrab of what they see - in each case the users report the scren was "frozen" and it wouldn't let them type. It probably wasn't truly frozen, but as the only thing they interact with until they enter text IS the text boxes, it would have appeared this way.
Any clues anyone? Myself and other users aren't seeing this problem when we use internet explorer so it's hard for me to problem solve....
Since you're using the Classic Player as shown in the image you shared, it could be that you're running Flash while your colleagues are not. Assuming that's the case, you might be running into this bug as well.
Is it possible for them to try a different browser?
This is a silly question, but if I open a .story file, and select "Publish", will the publish settings shown reflect what I last published it as or go back to default?
I can't recall if I published as "HTML with flash fallback" or "HTML only" - I have been publishing recent courses as HTML only but can't recall if this was one of them.....
In this case, an individual could try a different browser but in general I need this functionality to work in any browser. I am sharing covid-19 related safety information with visitors/short term contractors in advance of visiting our site (and hence who aren't on our LMS). The text entry is to they can generate a certificate of completion which they can print. I'd previously used the "Articulate tempshare" for similar purposes and never had any issues with people inputting their name. After upgrading for Articulate 360 I thought Review 360 might be a more stable, long term workaround for this purpose but maybe not...I know the best solution is to find a proper place to host in on the web, there's just a lot of bureaucracy involved in getting our IT department to do ad-hoc jobs like that so was hoping to avoid. 🤣
Thanks for the follow-up! You should be able to open up your file and select the Publish button to review the settings you last used!
While Review 360 is meant for shareholders and SMEs to provide feedback on your course, I appreciate the honesty regarding using Review 360 as a short-term method for users outside your LMS and the difficulty of hosting your files on the web.
As the bug is only being experienced in Review 360 using Internet Explorer 11, it seems making a push to your IT department is the best option, as hard as it is! It will ensure a better experience for your external users.
We'll be sure to pop back in here as soon as there's any progress to share.
36 Replies
Hello there, LaVon. We'd love to help!
I just replied to you in the discussion happening here. Let's continue our conversation over there!
Hello!
We are having a similar issue. In Review 360, my reviews cannot get the text entry boxes to work. However, when i view on my end everything works correctly. I have attached my .story file and the link to the Review. Could someone please take a look.
https://360.articulate.com/review/content/b95aff6c-0b8c-4c51-ab79-6f31317f97d8/review
Thank you!
Hi Nicole,
The boxes are working for me in your link as well.
Can you ask them what browser/environment they are using? I'd be happy to take another look.
Hi there, I'm having exactly the same issues - I'm using Edge and it works perfectly for me, but my reviewers who are using review 360 cannot type text into the text entry fields. This is super urgent as my modules need to be published at the end of this week.
Hi Cathy,
I'm sorry you're running into this issue as well! Can you confirm that you've reviewed the course in Review 360 using Edge as your browser?
We do have related bug reported to our team where text entries aren't focusing in Review 360 when using Internet Explorer 11.
I'm wondering if your reviewers are using IE11 and if it's possible to use a different browser in the meantime? We'll be sure to pop back in here to let you know as soon as we have an update.
For what it's worth, I've been having issues with text entries using IE11 both in Review and our LMS. A workaround is to ask the user to press the TAB key once, which seems to bring the text entry into focus, allowing them to enter text. Not ideal, but at least it's an option until the issue gets resolved.
I've just had this issue reported to me - I've sent a course via review 360, works perfectly for me on internet explorer and chrome, however an external party was unable to edit a text field.
I've asked them what browser they were using, but any thoughts persons have in the meantime would be appreciated.
I see a lot of mention about HTML and flash in this discussion - given that flash is being increasingly unsupported by browsers, could this be an issue?
Update - I have had this issue reported to me by a second user.
Both users were using internet explorer though I don't know what version.
Attached is screengrab of what they see - in each case the users report the scren was "frozen" and it wouldn't let them type. It probably wasn't truly frozen, but as the only thing they interact with until they enter text IS the text boxes, it would have appeared this way.
Any clues anyone? Myself and other users aren't seeing this problem when we use internet explorer so it's hard for me to problem solve....
Hi Michelle,
Can you check to see what publish settings you selected in your course?
Since you're using the Classic Player as shown in the image you shared, it could be that you're running Flash while your colleagues are not. Assuming that's the case, you might be running into this bug as well.
Is it possible for them to try a different browser?
Hmm, perhaps that's it/
This is a silly question, but if I open a .story file, and select "Publish", will the publish settings shown reflect what I last published it as or go back to default?
I can't recall if I published as "HTML with flash fallback" or "HTML only" - I have been publishing recent courses as HTML only but can't recall if this was one of them.....
In this case, an individual could try a different browser but in general I need this functionality to work in any browser. I am sharing covid-19 related safety information with visitors/short term contractors in advance of visiting our site (and hence who aren't on our LMS). The text entry is to they can generate a certificate of completion which they can print. I'd previously used the "Articulate tempshare" for similar purposes and never had any issues with people inputting their name. After upgrading for Articulate 360 I thought Review 360 might be a more stable, long term workaround for this purpose but maybe not...I know the best solution is to find a proper place to host in on the web, there's just a lot of bureaucracy involved in getting our IT department to do ad-hoc jobs like that so was hoping to avoid. 🤣
Hi Michelle,
Thanks for the follow-up! You should be able to open up your file and select the Publish button to review the settings you last used!
While Review 360 is meant for shareholders and SMEs to provide feedback on your course, I appreciate the honesty regarding using Review 360 as a short-term method for users outside your LMS and the difficulty of hosting your files on the web.
As the bug is only being experienced in Review 360 using Internet Explorer 11, it seems making a push to your IT department is the best option, as hard as it is! It will ensure a better experience for your external users.
We'll be sure to pop back in here as soon as there's any progress to share.
This discussion is closed. You can start a new discussion or contact Articulate Support.