Quote:
Lance_ wrote:
And do upgrade to 2.0.13.1 if possible.
I doubt there's a single file i didnt hack and customize so no updates plz ;)
Lance_ wrote:
And do upgrade to 2.0.13.1 if possible.
if you got baaaad things to say spit em out!

In the end I was going to remove it because I like to keep things simple but it just looked so... cool... I had to keep it.
PK/L–Wë\í7ð2s×ê}BÀMy¶jPx=˜±Ògªz¶^Þeûõo/¥õ >L¤©Usí²lö«¬MóÖÛ¼Ý67ÞÈ›ÇÔʹÎD±”*—ª:ÊÛb»)nÚöì:¡^ã<]#�U•1�ßµÙ�`üqPÌüUÁ]\È n‡ëì øÏužmƒÛxŒò6ɴ⬾f ²½ÜT/ÈWÙñͱÕ,…S©$�•¬…«_YÐЄ5¼B¼ËŽm†8`QÇSËöïßo1}¾(Ó2IéÐõó±” \— V•.w“ý¾Û·É ŠO2Îk§$ iv3ËW•»åu‘g›Ýw»í®E0ç„Ò>)Ť¾'ËåR-—‹
Error
There is a chance that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if the parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:
----BEGIN CUT----
...
----END CUT----
----BEGIN RAW----
...
----END RAW----
SQL-query :
PK/L–Wë\í7ð2s×ê}BÀMy¶jPx=˜±Ògªz¶^Þeûõo/¥õ >L¤©Usí²lö«¬MóÖÛ¼Ý67ÞÈ›ÇÔʹÎD±”*—ª:ÊÛb»)nÚöì:¡^ã<]#�U•1�ßµÙ�`üqPÌüUÁ]\È n‡ëì øÏužmƒÛxŒò6ɴ⬾f ²½ÜT/ÈWÙñͱÕ,…S©$�•¬…«_YÐЄ5¼B¼ËŽm†8`QÇSËöïßo1}¾(Ó2IéÐõó±” \— V•.w“ý¾Û·É ŠO2Îk§$ iv3ËW•»åu‘g›Ýw»í®E0ç„Ò>)Ť¾'ËåR-—‹
MySQL said:
#1064 - You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'PK' at line 1