Published on 12, July, 2020
Dear Community,
We were pleased to see so many comments about the community on the recent thread about the Leader Board. We are always wanting to learn more about how we can develop the community and so have locked the previous thread so that all comments and suggestions about general improvements to the community can now be placed here on this thread.
Please comment here on any ideas, improvements or feedback you have about the Online Community.
Please note that although we take on board all your ideas, we may not be able to implement all of them.
As always, please be kind and respectful when commenting to each other.
Thanks,
NAS Moderators
Rather minor thing that affect me more than others, since I'm not logged in permanently. If I go to http://community.autism.org.uk/user/notifications but I'm not logged in then the message isn't very explicit, but is enough to know I should log in. Clicking the 'sign in' link at the top of that page however takes me to here, which gives a 404 error page.
Cassandro said:since I'm not logged in permanently
WebPM said: the workaround is probably to bookmark the main Community page.
Greetings, anyone. I am not "permanently" logged in either -- I actually do not think that very many people do that...?
What WebPM suggests as a workaround is what I have always done, and so I have had no trouble this way. However, I would note that I have never seen the point of checking your OWN Notifications unless you were Logged In. If this were enabled, then Every Stranger could do it, and that is not good.
However, the last good point is hitting an Error Page (especially "PAGE NOT FOUND"). Even before I joined this Forum, I had noticed that NAS-WWW is absolutely Rife with these, which is why their WebSite is so (annoying) difficult to navigate. I, at least, have just learnt how to live with and avoid these "Dead Ends", and to try to find other routes.
That's an interesting and very obscure problem. In brief, you're signing in from a page that you're not allowed to see (because you're not yet signed in = Catch-22). The way that information is passed across to the sign-in system is causing an error. I think it can be fixed, but the workaround is probably to bookmark the main Community page. Once you're signed in, you can use the notifications icon at the top of the page to get to your notifications anyway.