Thinking Anglicans has now moved to its new home.
We hope that you’ll find all functionality and content here. If there are any transitional glitches, we’ll try and sort them out as quickly as we can. Issues can be reported by adding a comment to this article. If commenting itself is the problem then you can email editors@thinkinganglicans.org.uk.
You can take advantage of one immediate improvement, and we encourage you to do so. The site is now available over secure, encrypted, https, as well as over the old unencrypted http. Just access the site at https://thinkinganglicans.org.uk and update your bookmarks. Note the ‘s’ after ‘http’; and you should see the https padlock appear in the URL bar.
We hope to introduce other improvements in the coming weeks and months.
We continue to be hosted by our friends and colleagues at Justus.
Well done. Works well for me and thanks for everything you do to keep us well informed.
The previous site had a “recent comments” link in which one could look at the last 25 comments or so, regardless of what post they related to. I found this to be very helpful in keeping up with various conversations on various topics without having to click on each post to see what whether or not there were new comments on each and every post. I can’t find that kind of link on the new site. (I can find a series of links to individual comments but that’s not the same thing.) Am I missing something? Also, I just noted… Read more »
Thanks for the feedback. I assume you were using the Comments RSS feed.
If so, then there is a similar feed for the new blog at https://thinkinganglicans.org.uk/comments/feed/
I’ll add a link to the sidebar. And I’ll investigate previewing comments.
The feed in the link is really not very good. The previous feed was not perfect — it had a few coding symbols thrown in and put everything into one paragraph. The feed in this link includes all coding symbols (and there’s a huge amount of it) and it is very, very difficult to find the actual text of the comment in the midst of all the coding symbols. Can this be improved? Thanks.
What are you using to read the feed? This is a picture of what I see if I click on the link in Firefox:
https://www.thinkinganglicans.org.uk/comment-feed/
which looks just fine to me.
I use Google Chrome. I’m not adept enough to figure out how to add the screen-shot of what the comments look like using Google Chrome. I will send it to you by email if I can figure that out. Suffice it to say, it’s a mess.
Thanks — with the hint that you’re using Chrome I can (and have) looked at it myself. You’re right, it’s a mess. Firefox does a very nice job of displaying the feeds, but Chrome just shows the source 🙁
As with other glitches, I’ll investigate and see what can be done.
The comments feed also looks fine in Internet Explorer. So this may be just a Chrome issue. Thanks for looking at this issue
Yes, there is a big need to be able to view comments before posting.
No problems here, and I like the fact readers can now make replies directly to other readers.
BTW, I echo Kate’s remark. Many times I found the review process extremely useful to correct mistakes or make a comment more clear.
I use an ipod touch most of the time to access TA. (Archaic, I know…) Everything displays properly on landscape view. I like the larger font size than previously on portrait view but the main banner heading of Thinking Anglicans doesn’t wrap to the narrower width. The title of the post does wrap. It’s possible this is an older OS version problem as I am stuck on 9.3.5 but if it also happens with other devices any chance of fixing it please. Thanks.
Thanks Mary.
I get similar behaviour on my iPhone, and judged that it was liveable with. I do have a solution for it but it will probably take a day or two for it to get to the top of the list.
The title doesn’t wrap on Android but that is ideal because it is off screen and out of the way
Welcome to your new home. This new arrangement is so much clearer and far easier to read – a great improvement. Keep up the good work.
Looking good. Now I’m trying to get my picture to turn up, like Father Ron’s!
Have you considered adding HSTS (HTTP Strict Transport Security)? It’s one single header (“Strict-Transport-Security: max-age=31536000”) and means that once anyone has loaded TA over https, they will continue to get it over https.
Yes. I’ve chosen not to implement it yet as it caused some problems with another site I manage — if your page references, say, an external graphic, that is served as http not https then browsers count the page as not being fully https. And then if you have HSTS enabled you can’t see the page at all. And you can’t back out of it until your HSTS timeout has expired, which might be six months. So I’m a bit wary of imposing it. But I do encourage everyone to use the https version if they are able.
They’ll get “mixed https and http” warnings from the https version irrespective of HSTS, depending on the browser, so you’ll need to be careful about that anyway. But yes, it is a rather committing move…
What’s happened to the [MAIN] page link on the old site. Now if I go to an article and read comments, i have to use the back arrow key to return to the top page.
Just click on the “Thinking Anglicans” logo text at the top of the page. That will always bring you back to the main page. (As indeed it always did.)
The old triple of text links {previous article, Main, next article} has been removed as it’s probably pretty rare for people to browse through articles that way and the “Main” link on its own is redundant because you can click on the logo just above.
That was the reasoning, anyway.
Thank you. I never knew you could simply click on the logo.
This looks very clean. Thank you to all who worked on it!
Now that we have had the first really long thread under the new site (on Steven Croft’s statement about George Carey, 128 posts when I just looked) it shows that the new structure of sub-threads within the main thread, whilst logical and helpful in some ways, makes it extremely difficult to keep track of new postings, which can appear at any point in the very long thread. Am I missing a trick somewhere?