keltic Posted July 1, 2005 Posted July 1, 2005 Any idea how I find a parse error on line 255, when there are only 253 lines of code ? Regards keltic
♥bruyndoncx Posted July 1, 2005 Posted July 1, 2005 empty spaces at the end ? KEEP CALM AND CARRY ON I do not use the responsive bootstrap version since i coded my responsive version earlier, but i have bought every 28d of code package to support burts effort and keep this forum alive (albeit more like on life support). So if you are still here ? What are you waiting for ?! Find the most frequent unique errors to fix: grep "PHP" php_error_log.txt | sed "s/^.* PHP/PHP/g" |grep "line" |sort | uniq -c | sort -r > counterrors.txt
boxtel Posted July 1, 2005 Posted July 1, 2005 Any idea how I find a parse error on line 255, when there are only 253 lines of code ? Regards keltic <{POST_SNAPBACK}> the parse error line number is the line where php does not understand your instructions anymore. That is usually caused by an error some lines back. Treasurer MFC
keltic Posted July 1, 2005 Author Posted July 1, 2005 I have deleted yet another whitespace in the file and the error now moves to line 254. I assumed that the error was caused by lines further back, but is there an easy way to find it ? Is there a logical way to find it ? Do I now have to trawl through 253 lines of code ? :'( :'( :'( Has anyone written a debug tool ?
♥bruyndoncx Posted July 1, 2005 Posted July 1, 2005 may be you missed a closing } bracket somewhere in the middle and thus you are missing a matching end bracked for the first bracket used, that would explain it bumming out at the end. I used UltraEdit and this indicates the matching brackets (highlighting) when you select either begin or end bracket, makes it easier to see where you missed one. KEEP CALM AND CARRY ON I do not use the responsive bootstrap version since i coded my responsive version earlier, but i have bought every 28d of code package to support burts effort and keep this forum alive (albeit more like on life support). So if you are still here ? What are you waiting for ?! Find the most frequent unique errors to fix: grep "PHP" php_error_log.txt | sed "s/^.* PHP/PHP/g" |grep "line" |sort | uniq -c | sort -r > counterrors.txt
keltic Posted July 1, 2005 Author Posted July 1, 2005 Thanks. I have just been on their website. Looks like a must have tool together with ultracompare. I will give it a go. Regards keltic
keltic Posted July 1, 2005 Author Posted July 1, 2005 You were right. I have just done a search on opening and closing brackets. 21 opening, 20 closing. :-" :-" Now where did I put that spare one ? :rolleyes: Thanks again. Regards keltic
New 
Recommended Posts
Archived
This topic is now archived and is closed to further replies.