Quarterbore
02-24-2006, 12:41 PM
I am running vBa 2.0.0 with vB 3.5.2. with vbLinks and the addlink.php file being included insite the CMPS system using the Integrating Other vB Pages & Hacks (http://www.vbadvanced.com/membersarea.php?do=viewusermanual&productid=4&pageid=6)
I don't get this error all the time but it seems to happen on a somewhat regular basis as detected in my error logs.... Following is an exaple of the error I am seeing....
Fri Feb 24 07:33:24 2006] [error] PHP Parse error: parse error, unexpected T_STRING in /home/MYSERVER/public_html/links/addlink.php(108) : eval()'d code on line 1
I am curious if somone might be able to suggest what this error may mean for me and how I might correct the problem? Like I said, it works fine most of the time and I have a tough time reproducing it but I do get this error every now and then...
It is possible that the page I am including is busy at the moment that the addlink.php file is being called? Should I make another cmps page that the addlink.php file would live in?
If I should have posted this over at vBulletin.org just let me know and I will post it over there instead... I figure this is more of a vBa concern then vB.
Thanks!
I don't get this error all the time but it seems to happen on a somewhat regular basis as detected in my error logs.... Following is an exaple of the error I am seeing....
Fri Feb 24 07:33:24 2006] [error] PHP Parse error: parse error, unexpected T_STRING in /home/MYSERVER/public_html/links/addlink.php(108) : eval()'d code on line 1
I am curious if somone might be able to suggest what this error may mean for me and how I might correct the problem? Like I said, it works fine most of the time and I have a tough time reproducing it but I do get this error every now and then...
It is possible that the page I am including is busy at the moment that the addlink.php file is being called? Should I make another cmps page that the addlink.php file would live in?
If I should have posted this over at vBulletin.org just let me know and I will post it over there instead... I figure this is more of a vBa concern then vB.
Thanks!