Hi all,
Thanks very much for re-reporting the login timeout issue. I've re-raised the same ticket with our developers so they can track down the problem.
We haven't been able to reproduce the 'missing posts' problem in any browser and think it may be down to the design of the page – the POST and CANCEL buttons are right next to each other, the same colour, and CANCEL is actually bigger than POST yet asks for no confirmation or gives any feedback telling you it's cancelling -- it just goes back to the conversation just like if you'd clicked POST. You'd think you'd posted until you were unable to find your new message. If you're clicking quickly or tapping [tab][tab][tab][tab][enter] to post, it's way too easy to activate the wrong button. We're going to fix that first as the most likely cause of this issue.
Originally Posted by: Online Community Memberyou said that at some point achieved material would be locked and be available as “read only.” I assume this means that even the person who set up the thread is subject to the read only arrangement. If so, then the option at that time, or before, will be for the person who set up the thread to decide whether or not a thread which was based on current clinical opinion at that time needs to be noted to show the posting is valid up to the at the time when the archives went “read only” – alternatively the posting could be deleted.
That's right, and we're happy to update those old threads with such notices by request, even after the archives are made read-only.
We'll fix that after the more urgent fixes are done. I've put in a request to add a link at the bottom to switch to the search page to find more results.
We have a request in to make this work better.
Done: http://prostatecanceruk.org/we-can-help/online-community/continuing-an-archived-conversation
We haven't had any further complaints or any emails asking for help registering.
We already have a ticket in with the developers on the issue of WYSIWYG editor display not matching the posted output in terms of the way linebreaks are displayed. This will hopefully solve the need for preview.
We've not had any more complaints about users not being able to cut and paste - developers tell us it's a browser issue as it's a user's local browser and operating system that handles cut and paste, not the online community software. The online community software doesn't have any cut-and-paste functionality to be fixed.
Originally Posted by: Online Community Member
Comment 12 Recent Conversation: My “Since .........“ box is set to “Since Last visit on xx xx xxy” and this has shown the wrong time, and even the wrong date, when I last logged in.
Developers are working on a better definition for what 'last login' means -- ie, last time you signed on vs last day you visited vs last page you loaded.
Are there particular parts that were puzzling besides those logged in this thread? Please let us know.
Originally Posted by: Online Community MemberI think it would be good if you could say which fixes are under consideration and give an expected date when the fixes will go live. Also, can you say which problems or issues will not be fixed so they will continue as they are. If you can say why they will not be fixed that would be good.
We're prioritising bugs vs feature requests. Bug fixes are free, since something's not working right. New features needed that weren't caught in testing or other steps of the process, we have to pay for and balance against the other services we provide to men and their families. So, we do have to look at whether a change someone's requested (like a button to switch signatures on and off per post) is as urgent as a bug that's stopping someone from finding the information they're looking for, or a change to the community homepage that would mean everyone finds it easier to find the topics they want.
We've put all of these useful requests in to the developers, but some we've prioritised and some we're hanging onto for a slow time when we have developer time to spare. I've tried to say that when responding to a feature request if it couldn't be prioritised.
We have developer time booked in this week to get through more bug fixes. Some of the problems people have reported are very hard to reproduce and diagnose, and we may think we have a fix but then it turns out it hasn't fixed it for all users. So I can't promise a particular day for a particular issue. I can say that I will keep updating you as the changes go live and keep asking for your very helpful feedback so we can continue to improve the service.
I really hope this is helpful and will update soon with more improvements made.