Copying and pasting timestamp notes from newly installed CLG FS
7 thoughts on “Session: Oct. 4 2020, Sunday”
Module: Topics
Long Topic And a Ridiculously Long Name that is more than 84 characters long and counting times 2 – Long Topic And a Ridiculously Long Name that is more than 84 characters long and counting times 2 –
The testing of what works and not work. The additional function did not work. Best to keep Signatures out.
Best solution I see now is to just not make available what has the propensity to get abused by spammers and hackers.
The tweaks I did yesterday, was good for the Display Name field, which also is connected to the “Likes” under each post.
The Long topic titles does not break the forum design or the widget area.
It’s the Display Name and Nickname fields that pose as a risk area that affects the layout.
Okay. Here’s what I did. I just deactivated the “Display Name” since that seem to NOT have any character limit that I can find easily on the codes.
I experimented on Lines 1336-7 and the code I added didn’t work. So reverted back.
Users can change their nicknames on their Profiles, currently, as tested, it could accommodate up to 50 characters, more than that errors out.
Test67890gggggggg20gggggggg30gggggggg40gggggggg50
It’s the “Display Name” that would have an effect on another area of the forum, so that’s why I disabled it for now.
Brute also tested on the Main and at SH, it’s a WP Core issue. Not the versioning.
Will add another article on the Session for the new code snippet I added.
Also, this is from Sofy & it’s good to know:
Each web project that uses the SQL DB that are vBulletin, phpBB, XenForo, and other giant forums and shops uses INT(11) unsigned field type (Maximum Unsigned Value for INT(11) is 4294967295) for autoincrement of post ID. Forum developers decided to use the biggest SQL numeric type i.e BIGINT(20) unsigned max value (Maximum Unsigned Value for BIGINT(20) is 18446744073709551615).
Module: Topics
Long Topic And a Ridiculously Long Name that is more than 84 characters long and counting times 2 – Long Topic And a Ridiculously Long Name that is more than 84 characters long and counting times 2 –
The testing of what works and not work. The additional function did not work. Best to keep Signatures out.
Best solution I see now is to just not make available what has the propensity to get abused by spammers and hackers.
The tweaks I did yesterday, was good for the Display Name field, which also is connected to the “Likes” under each post.
The Long topic titles does not break the forum design or the widget area.
It’s the Display Name and Nickname fields that pose as a risk area that affects the layout.
Okay. Here’s what I did. I just deactivated the “Display Name” since that seem to NOT have any character limit that I can find easily on the codes.
I experimented on Lines 1336-7 and the code I added didn’t work. So reverted back.
Users can change their nicknames on their Profiles, currently, as tested, it could accommodate up to 50 characters, more than that errors out.
Test67890gggggggg20gggggggg30gggggggg40gggggggg50
It’s the “Display Name” that would have an effect on another area of the forum, so that’s why I disabled it for now.
Brute also tested on the Main and at SH, it’s a WP Core issue. Not the versioning.
Will add another article on the Session for the new code snippet I added.
Also, this is from Sofy & it’s good to know:
Each web project that uses the SQL DB that are vBulletin, phpBB, XenForo, and other giant forums and shops uses INT(11) unsigned field type (Maximum Unsigned Value for INT(11) is 4294967295) for autoincrement of post ID. Forum developers decided to use the biggest SQL numeric type i.e BIGINT(20) unsigned max value (Maximum Unsigned Value for BIGINT(20) is 18446744073709551615).
ON CLG Share Forum:
Test Private Topic – TEST if admins can see this.
Yes. Only visible to specific Member who set the topic to private and the Admin.