Not sure if it’s just me or is the “copy quote” function broken, shows me like this when i try to quote post from another thread
I will be going though the backlog of things that need to be fixed today. for now the jump up/down buttons may be temporarily broken
5 Likes
Gallery, grid and ToC are missing entirely
1 Like
3 Likes
Oh right, QoL posting is a lot different without them 
3 Likes
Clicking links from email notifications triggers browser security warnings because the links use the unsecured HTTP protocol. (Chrome)
Example:
http://url<someNumber>.www.elitefourum.com/ls/click?upn=…
2 Likes
…shouldn’t the server auto-redirect to https, regardless of the link?
Make sure “https everywhere” is enabled, but this is an intersting behavior to me, as a cysec pro. What browser are you using, @quackcollection ?
I can replicate on:
- Chrome w/ “Always use secure connections” enabled
- Chrome Incognito (by default Incognito always warns if an initial HTTPS connection can’t be made)
E4’s main site definitely will redirect (and the email links do redirect to HTTPS), but the email subdomain doesn’t appear to support HTTPS which means under these stricter Chrome settings, Chrome will till warn because it can’t initially establish a secure connection to the email subdomain.
1 Like
There is indeed a 307 Temporary Redirect response from the server to the HTTPS URL (or well automatic https upgrade from browser), but I guess Chrome is complaining and detecting something’s wrong even before following the redirect. The reason is probably that the SSL certificate doesn’t match the domain on the HTTPS URL. For this custom subdomain, a wildcard certificate for *.sendgrid.net is being used, which is obviously not valid for this domain.
1 Like
lol. SSL certs strike again.
Trying to quote from one post to another, getting an error message that the post can’t be empty. Windows 11, Chrome browser.
I think that’s supposed to be a feature not a bug. The default setting actually have a minimum character requirement which I got rid of right away.
I think flagging a post with only a quote is appropriate though
2 Likes
I’m getting this error message when I try to edit a post on my collection thread
I’m using iOS on mobile, have also tried Windows on PC
You need to switch the editor mode for some posts that have elements not yet supported by the other editor:
4 Likes
Oh that works, thanks!
It seems like the “It’s been a while since we’ve seen [user] — their last post was {x} years ago.“ thing isn’t working 100% correctly. On this thread for example, it seems like the site is calculating x as = original hiatus + time elapsed since the post = 9 yrs. However from dyl’s screenshot we can see its supposed to be 7 yrs. Unless dyl was trolling back in march 2024 I believe this is a bug.
Also apologize if this is how the feature is supposed to be calculated and I am misunderstanding what it means
2 Likes
That is an image that I copied and pasted. It’s purple because I use dark mode. You can see your feature in white above their username.
3 Likes
Still unsure if this is a bug or I am misunderstanding the purpose of this feature. Is it supposed to highlight the length of the user’s hiatus? That’s what I originally thought so that’s why I submitted this report
he’s just using your screenclip as a set-in-stone reference for how long the hiatus was at the time of posting (7 years). it now says 9 years in his screenshot. their hiatus wasn’t 9 years, it was 7, so he’s pointing out that it saying 9 years seems to be incongruous. is that what you meant @anthony_CCG?
2 Likes
Yes! thank you for putting it in more coherent way
1 Like