Forum functionality issues

[kphoger]

I've got to say, it does make this post of mine look a lot less meaningful:

Am I the only who memorizes the alt codes?

ñ is alt+164
Ã' is alt+165
á is alt+160
Á is alt+0193
é is alt+130
É is alt+144
í is alt+161
Í is alt+0205
ó is alt+162
Ã" is alt+0211
ú is alt+163
Ú is alt+0218
ü is alt+129
Ü is alt+0220

ß is alt+225
Þ is alt+0222 / makes a good emoticon hat (o:Þ or tongue :-Þ
Ø is alt+0216 / makes a good null symbol
... is alt+0133
– is alt+0151
— is alt+0150
½ is alt+0189
¼ is alt+0188
¾ is alt+0190
° is alt+248
§ is alt+987654321123456789 / I'm sure there's a shorter one but I can never remember it

And the list goes on!

[freebrickproductions]

I've got to say, it does make this post of mine look a lot less meaningful:

Am I the only who memorizes the alt codes?

ñ is alt+164
Ã' is alt+165
á is alt+160
Á is alt+0193
é is alt+130
É is alt+144
í is alt+161
Í is alt+0205
ó is alt+162
Ã" is alt+0211
ú is alt+163
Ú is alt+0218
ü is alt+129
Ü is alt+0220

ß is alt+225
Þ is alt+0222 / makes a good emoticon hat (o:Þ or tongue :-Þ
Ø is alt+0216 / makes a good null symbol
... is alt+0133
– is alt+0151
— is alt+0150
½ is alt+0189
¼ is alt+0188
¾ is alt+0190
° is alt+248
§ is alt+987654321123456789 / I'm sure there's a shorter one but I can never remember it

And the list goes on!

Now I want to know what the last one was, lol.

Also, is it just something on my end, or is the "total users who logged in today" box at the bottom of the main page duplicated?

[kphoger]

§ is alt+987654321123456789 / I'm sure there's a shorter one but I can never remember it

Now I want to know what the last one was, lol.

§

[1995hoo]

That list above appears to have the en dash (which is Alt-0150 and looks like this – ) reversed with the em dash (Alt-0151, — ), which suggests perhaps a programming error as to the two.

[Alex]

It is a frustrating endeavor, so not worth pursuing anymore.

At the very least, you should edit the Forum Guidelines.

Photos and images posted in forum threads should not exceed 800 pixels in width or 600 pixels in height. Everyone is not using the same monitor. To reference larger images, just add a link from the 800×600 sized image to the larger file in question.

Good call, thanks

I had to look up what × was, and its "×"

[bugo]

I'm *terrified* to ask. I don't frequent rhe non-state/region sections... For good reason I guess??

He spent a lot of his time in the Central States forum. Mostly spreading falsehoods and saying outlandish things to get attention.

[bugo]

An enthusiast of little green shrubs? 

We usually call them "trees".

[index]

Lately the forum has been barking at me saying posts are coming from my IP too fast. Not sure why.

[hotdogPi]

Lately the forum has been barking at me saying posts are coming from my IP too fast. Not sure why.

It's been happening to everyone in the last 2 months or so and predates the forum downtime.

[index]

Lately the forum has been barking at me saying posts are coming from my IP too fast. Not sure why.

It's been happening to everyone in the last 2 months or so and predates the forum downtime.

This would be the first time it's happening to me. Not saying you're wrong, just pointing that out. I didn't see anyone talking about it in this thread or mentioned anywhere else so I didn't know.

[vdeane]

Lately the forum has been barking at me saying posts are coming from my IP too fast. Not sure why.

It's been happening to everyone in the last 2 months or so and predates the forum downtime.

This would be the first time it's happening to me. Not saying you're wrong, just pointing that out. I didn't see anyone talking about it in this thread or mentioned anywhere else so I didn't know.

https://www.aaroads.com/forum/index.php?topic=33650.0

[US 89]

If we're still fixing these, ™ has become ™

[Rothman]

I'm still a big fan of Fatbol.

[US 89]

If we're still fixing these, ™ has become ™

ä has become ä as well

[Alex]

If we're still fixing these, ™ has become ™

ä has become ä as well

I got rid of a couple thousand of these in the post subjects via database queries yesterday. Will add the two cases you mentioned on my to-do list. Thanks.

[JMoses24]

I had a bit of an issue when I logged in.

When I would click on any internal link (for want of a better term) to access anything else in the forum, it would open in a new tab. Also, an attempt to type in a search box would just lead to something opening in windows explorer. This seems to be fixed after a reboot.

[US 89]

é has become é

[formulanone]

ç (as seen in Curaçao) has turned into ç

[kphoger]

Thus far I have dealt with all of the ones mentioned upthread ...

é has become é

ç (as seen in Curaçao) has turned into ç

Were these last two not already corrected?

[rickmastfan67]

I had a bit of an issue when I logged in.

When I would click on any internal link (for want of a better term) to access anything else in the forum, it would open in a new tab. Also, an attempt to type in a search box would just lead to something opening in windows explorer. This seems to be fixed after a reboot.

Sounds like you somehow had a stuck key on your keyboard.  Having the 'CTRL' button somehow stuck and clicking on a link will make your browser open in a new window.

[US 89]

Were these last two not already corrected?

They might have been corrected in post titles, but they still show up in the text of actual posts.

[wriddle082]

I have been using Duck Duck Go browser on iOS on an iPhone 14 (no, I will NOT use Tapatalk!).  I tried visiting the site on Safari the other day and it was still giving me issues.

There's your answer then.

This theme wasn't built with 'mobile' in mind sadly.  Nothing we can really do about that till we consider upgrading the forums to the 2.1 branch.

Well the font sizes were fine before the forum was taken down, regardless of browser, so that's why I brought it up.

Did you patch the browsers at any point on your phone?  That's what possibly triggered it.  That's all I can think of, since I don't roll iOS (android here for my phone).

I did this morning hoping it would fix the issue, and it did not.

But now that I think about it more, I did upgrade the iOS to 17.0.2 from 16.x.x during the down time.  It didn't affect any other sites, but considering the other oddities I'm now starting to catch, I can see this as the possible culprit.

It was definitely the iOS that was causing the issue.  Last night I installed iOS 17.1 and now everything is back to normal with regard to line spacing.  And I also had other issues with not hearing some alerts, and now those issues are resolved as well.

[Alex]

All quoted posts above were fixed because of the queries I just made, so here is what I addressed:

If we're still fixing these, ™ has become â,,¢

Fixed

ä has become ä as well

Fixed

é has become é

Fixed, if any instances that should be © instead became é, that is because © = © and of course SQL cannot parse the difference of the caret and tilda's above the A.

ç (as seen in Curaçao) has turned into ç

Fixed. The queries may have gotten this right, as 150 or so rows with ç were converted to ç and the remaining 293 rows of § were converted to §.

Were these last two not already corrected?

They might have been corrected in post titles, but they still show up in the text of actual posts.

This is accurate, as my previous database queries were focused on subject fields.

[Rothman]

Have to say that the forum has been running pretty slick for me recently, minor special character annoyances aside.

[rickmastfan67]

I have been using Duck Duck Go browser on iOS on an iPhone 14 (no, I will NOT use Tapatalk!).  I tried visiting the site on Safari the other day and it was still giving me issues.

There's your answer then.

This theme wasn't built with 'mobile' in mind sadly.  Nothing we can really do about that till we consider upgrading the forums to the 2.1 branch.

Well the font sizes were fine before the forum was taken down, regardless of browser, so that's why I brought it up.

Did you patch the browsers at any point on your phone?  That's what possibly triggered it.  That's all I can think of, since I don't roll iOS (android here for my phone).

I did this morning hoping it would fix the issue, and it did not.

But now that I think about it more, I did upgrade the iOS to 17.0.2 from 16.x.x during the down time.  It didn't affect any other sites, but considering the other oddities I'm now starting to catch, I can see this as the possible culprit.

It was definitely the iOS that was causing the issue.  Last night I installed iOS 17.1 and now everything is back to normal with regard to line spacing.  And I also had other issues with not hearing some alerts, and now those issues are resolved as well.

Good to hear.