Just today, I can't post with Safari on a Mac--I get what should be a post editing page, but no space to edit in. Firefox on a Mac works just fine. Are others with Safari on a Mac working just fine, so that this is probably me?
@ChickenFreak I was able to post with Safari, but this must be related to the SSL update. I will look into it. I may need you to help me with testing and identifying the issue.
Thanks! (I say from Firefox. ) Happy to test. I did try typing in the front-door URL with https (https://www.writingforums.org) rather than going to a bookmark, in case it's a redirect issue, but, nope, same problem.
Good thinking. You don't use an external account to log in here do you? (Facebook, Twitter, Google) Edit: @ChickenFreak Xenforo support says it's likely a browser caching issue (unless others are reporting it). Can you try clearing your cache and cookies? Second Edit: Safari on Mobile isn't display the post field, just the Post Reply button. Not an isolated incident.
I'm no longer experiencing the problem on mobile after clearing my history and making a few backend changes.
I had a problem posting a couple of days ago as well. The site demanded that I log in (normally I don't need to) and then wouldn't acknowledge my log-in or password. It didn't indicate an error, it just refused to leave the log-in page. I contacted Wreybies on Facebook ...in a panic ...but meantime kept trying. I closed down my browser. (Firefox.) I closed down my computer. I came back on. Still no joy. However, I kept trying again every 5 minutes or so, until, after about 10 tries, I got back in. Bizarre. Not a clue. I cleared the cookies from my cache (which I do regularly) but not till AFTER I'd got back in. So that wasn't a factor for me.
You're right ...ish. I posted my Halp message to Wreybies on Facebook on Monday at 6.55am, our time here in the UK. That's when I was having the problem. Just checked back to make sure.
That would be 12:55 a.m. Monday morning (late Sunday night) if I'm not mistaken, which is the night I was up all night making the https conversion. It's almost certainly related and I think it's safe to assume it's resolved now that I've made all the major adjustments. If it does reoccur please let me know. @ChickenFreak are you still experiencing the original issue in Safari? I'm pretty confident your browser cache is referencing some elements from the old http:// version. When you get the chance try reclearing you cache and cookies. I think it should resolve the issue.
I am, and that theory makes sense. I'm making sure I have all my passwords before I trash my cookies, so it may be a while before I report results.
I had the same problem with not being able to reply via Chrome last night. Clearing cookies and cache has fixed it for me.
