Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Parse error
#9
Now it started to happening me too. But the 2 numbers at the end were different than OP had, they were 88.
I hope Omniscient gets this fixed ASAP.

Now when i tried to post this reply it gave me unexpected $end at (path to hotwords.html) on line 96
This occured around 2 minutes before i was able to load the website even though i refreshed the page like 10 times within that 2 minutes.
[Image: siggp.png]


Messages In This Thread
Parse error - by Untouch - 01-18-2011, 05:30 PM
RE: Parse error - by Sam - 01-18-2011, 05:32 PM
RE: Parse error - by Cee Lo Green - 01-18-2011, 05:40 PM
RE: Parse error - by Untouch - 01-18-2011, 05:48 PM
RE: Parse error - by Cee Lo Green - 01-18-2011, 05:50 PM
RE: Parse error - by Omniscient - 01-18-2011, 05:50 PM
RE: Parse error - by Swat Runs Train - 01-18-2011, 05:50 PM
RE: Parse error - by Sam - 01-18-2011, 05:55 PM
RE: Parse error - by Apex - 01-18-2011, 06:05 PM
RE: Parse error - by Untouch - 01-18-2011, 06:08 PM
RE: Parse error - by Deltron - 01-18-2011, 10:00 PM
RE: Parse error - by Apex - 01-19-2011, 08:17 AM
RE: Parse error - by Cee Lo Green - 01-20-2011, 03:57 AM
RE: Parse error - by Tactic - 01-21-2011, 05:45 AM
RE: Parse error - by Untouch - 01-22-2011, 09:35 AM
RE: Parse error - by Disruption - 01-23-2011, 12:09 PM

Forum Jump:


Users browsing this thread: 8 Guest(s)