SyntaxBomb - Indie Coders

google chrome and edge explorers.

Was already mentioned - but never fixed.


Meanwhile insert "www." before syntaxbomb.com and it will show up properly.




@ Qube
Just use "//" instead of hardliine http://www.syntaxbomb.com or https://www.syntaxbomb.com




bye
Ron

QuoteWas already mentioned - but never fixed.

Tis fixed now

Since we are talking about errors, the search function fails! 

Quote from: therevills on January 02, 2018, 01:08:40
Since we are talking about errors, the search function fails! 

Holy crap balls! - How do I recreate that error?

Check apache error logs - and/or check the access.log for the given time to see what therevills did search at that time.

If you are not excited to do that, simply ask him what he searched to maybe be able to replicate that.


bye
Ron

Quote from: Qube on January 02, 2018, 04:26:04
Holy crap balls! - How do I recreate that error?

Sorry should have put the steps:

Click the Search hyperlink:

https://www.syntaxbomb.com/index.php?action=search

and search for "logo" without quotes.

As it does not happen on other SMF 2.0.14 boards I assume it is either something in the search results (Qube should run the query in a DB-Browser or via cmd line) or in the rendering process (html output and a cache system or so).


bye
Ron

I think this is something to do with the returned posts in the code archives ( some are huge posts ). It also does the same on my local copy of the forums. It doesn't happen on a MYSQL search.

In the meantime if you get this error, tick "Show results as messages" and it'll work fine. I'll find out what's causing it.

Ok so then it has to do with processing the mysql data in the php backend - maybe some sanitizing-try VS big chunk of posting-content-data. Dunno if they have some "while" or some recursive "until" stuff.


If you need help, drop a line.


bye
Ron

@Derron - I plan to look at the code that the SMF forum uses for searching and then simulate the same in a more debug environment. I'm sure it's just something silly like a single post that has an odd character that has not been escaped properly when I imported all the BB code archives. I probably won't get a chance to look at it until the weekend though.