chancery wrote: ↑Sun Jun 02, 2024 2:58 pm
I thought that I'd experienced problems even when I didn't use the link code wrapper, but I guess that's unlikely.
OK, I'm not completely delusional.
Here's an example of a post with a twitter link for which x.com has been replaced by Twitter.com, with no link wrapper code around the twitter link, and the Fogbow post does not display the twitter post unless you click on it:
The code that looks for embedded twitter links is case sensitive. It is looking for "twitter", not "Twitter". So that is part of the problem. Domains in URLs are not case sensitive, but the code that locates twitter links in posts is.
chancery wrote: ↑Sun Jun 02, 2024 2:58 pm
I thought that I'd experienced problems even when I didn't use the link code wrapper, but I guess that's unlikely.
OK, I'm not completely delusional.
Here's an example of a post with a twitter link for which x.com has been replaced by Twitter.com, with no link wrapper code around the twitter link, and the Fogbow post does not display the twitter post unless you click on it:
That is a very strange one you have stumbled across chancery. I took the above link directly from the post on Twitter. Bizarre.
“Remember, democracy never lasts long. It soon wastes, exhausts, and murders itself. There never was a democracy yet that did not commit suicide.” —John Adams
Well, also, too, I do not have an X/twitter account so I might be underage and not allow to see the content, so for me the content is "not found". Do the users who see the content have X/twitter accounts?
much ado wrote: ↑Mon Jun 03, 2024 11:41 am
Well, also, too, I do not have an X/twitter account so I might be underage and not allow to see the content, so for me the content is "not found". Do the users who see the content have X/twitter accounts?
To answer my question, I set up an X account and now I can see the sensitive content. You probably have to be over 18 years old to view the content. If you don't have an account, you can't see it.
Just FYI the board picks up x.com now, you don't have to change it to twitter.com anymore to embed the tweet.
But you do have to surround it with url tags if you don't want it to embed.
“Remember, democracy never lasts long. It soon wastes, exhausts, and murders itself. There never was a democracy yet that did not commit suicide.” —John Adams
neonzx wrote: ↑Tue Jul 30, 2024 6:30 am
The log out problem is becoming more serious.
Could explain the declining post/replies #s (yes I think some people are giving up when it goes haywire)
It's on the sever side, not the end user.
But I am no expert, apparently, as I've been scolded by dick tator previously.
I can't speak for anyone else, but I've found for me that checking the "remember me" box under the login information fields prevents the constant logoff/login issues.
neonzx wrote: ↑Tue Jul 30, 2024 9:21 am
I can be just typing a reply and hit Submit. *bam* "you must be logged in to post a reply"
This is not just me and not a new issue. Just browsing around and *bam* no longer logged in.
This can be particularly annoying when you are on your phone and tediously composing and revising a lengthy reply, because the text is not saved to "drafts" after the sudden log out.