Menu | JAQForum Ver 19.10.27 |
Forum Index : Site News : Forum upgrade
![]() ![]() ![]() ![]() |
||||||
This is the post I had problems quoting https://www.thebackshed.com/forum/ViewTopic.php?TID=13305&P=2#162046 Others mention problems here https://www.thebackshed.com/forum/ViewTopic.php?FID=16&TID=13312#162043 I use HxD for viewing hex data. I have copied a few times but have been unable to find any suspect characters. Jim |
||||||
Thanks Looking at mclout999 posts, I see its full of those double spaces at the end of every sentence. I might try replace a few pest >127 characters before I test for other >127 characters. Going over the java forums I see its a common thread, other developers trying to block stuff over 127. Apparently 160 is a major pest. Updated the code, see how that goes. Glenn |
||||||
test OK, I think this is working for non-32 space character. Edited 2021-01-04 11:16 by Gizmo |
||||||
Are you aware that code now has to be in capitals only and won't work if lower case is used? ie [code] [quote] etc won't work but in capitals it will? This breaks older posts formatting properly |
||||||
I've not made any change to the forums tags. Its always been uppercase as far as I can remember. Can you give me a link to a old post that no longer works? Glenn |
||||||
https://www.thebackshed.com/forum/ViewTopic.php?TID=11088&PID=130357#130357 That used to work because anytime I saw it not working I correct it and I definitely would have corrected that Maybe I only notice because I do the tags manually instead of using the buttons This is the same https://www.thebackshed.com/forum/ViewTopic.php?TID=10302&PID=116575#116575 Edited 2021-01-09 21:00 by lew247 |
||||||
Looks like those posts were made on the old forum code, and that old code may have accepted the tags in lower case. The new forum code only accepts upper case, as this was the format used in the old code when a user clicked the button to add a quote, code, etc I guess this is a bit like the unicode emoji problem, it only causes problems when users dont stick with the forums standard set of tags and emojis. Glenn |
||||||
Also having great difficulty posting - behavior is consistent in both Chrome and Safari on my iPad, and Chrome on Windows 10. The dialog that displays is as follows: ![]() As far as I can tell, there are no special characters in my text, and I have copied it into a few online "rogue character detectors" and it came back clean. FYI, this post went up clean - 99% of my activity on the TBS is in the "Microcontroller" forum Edited 2021-01-21 06:46 by RetroJoe |
||||||
A similar problem for me was caused by 'curly quotes'. Bill |
||||||
The code looks for any character over 127 ascii. Finding a balance between a forum where users can post code, and a forum that wont let someone post code that breaks the forum, isn't easy. Glenn |
||||||
"This is test" Curly quotes does indeed seem to be the culprit - thanks very much, Bill ! Edited 2021-01-21 17:32 by RetroJoe |
||||||
What's the ascii or keyboard combination for curly quotes? I can tell the code to replace some characters before checking for >127 characters. I did this with the non breaking space, they are replaced with a normal space, so they no longer trigger the warning message. Glenn |
||||||
This, copied from a pdf file (CMM2 Manual): ![]() Gives this in a Hex editor: ![]() I don't know if that's of any help? To borrow someone else's signature: 'It's all too hard'. Bill |
||||||
if ch$=chr$(145) or ch$=chr$(146) then ch$=chr$(39) ' single quote if ch$=chr$(147) or ch$=chr$(148) then ch$=chr$(34) ' double quote if ch$=chr$(150) or ch$=chr$(151) then ch$=chr$(45) ' EN dash to hyphen You may also need: if ch$=chr$(152) or ch$=chr$(153) then ch$=chr$(39)' single quote if ch$=chr$(157) or ch$=chr$(156) then ch$=chr$(34)' double quote Jim |
||||||
Made some changes. Could someone please test if those curly quotes are replace with normal quotes and the page no longer complains about them please? Glenn |
||||||
This is from the CMM2 manual again ![]() The image is of the original. Bill Edited 2021-01-23 14:44 by Turbo46 |
||||||
Thanks |
||||||
Glenn--I've been getting this message fairly often lately--would it be possible to extend the time to, say, 45 seconds? "Fatal error: Maximum execution time of 30 seconds exceeded in C:\inetpub\wwwroot2\TheBackShed\forum\SearchForum.php on line 35" |
||||||
Hi Lizby If the code is that busy that it times out for you, it means anyone else visiting the site is also experiencing a delay, something I try to avoid. So I need to look at how I've written the search code and fix it. Could you give me an example of a search that causes this bog down? Glenn |
||||||
Hmmm . . . Right now late at night in eastern North America activity seems to be low enough that I can't reproduce the timeout. I think one of the ones today was "any" occurrence of "ili9341" in a post by "Geoffg"--probably around noon Atlantic time. I'll try to keep track of what and when so I can post. It's probably happened to me 4-5 times in the past week. |
||||||
![]() ![]() ![]() ![]() |
![]() |
The Back Shed's forum code is written, and hosted, in Australia. |