Re: PHP parse erreor in error_log

Marc-Etienne Vargenau wrote:
>Sabri LABBENE a écrit :
>> Marc-Etienne Vargenau wrote:
>>> Hello again Reini,
>> 
>> Hello Marc-Etienne,
>> 
>>> In the Apache error_log, I have the following:
>>>
>>> [client 139.54.31.221] PHP Parse error:  parse error, unexpected 
>>> T_CONSTANT_ENCAPSED_STRING in 
>>> /opt/gforge-1.2/www/wiki/themes/default/Wikiwyg/Wikiwyg/Phpwiki
>>> .js on line 184,
>>> referer: http://acmev/wiki/g/cssforge/acos1.2-VTS?action=edit
>>>
>>> I did not activate the Wysiwyg mode.
>>>
>>> Do you have an idea where I should look to correct this bug?
>>>
>>> Code is latest from CVS.
>> 
>> Wysiwyg is my contribution. I'm the maintainer of wysiwyg.
>> Wysiwyg latest cvs sources are, unfortunately, not stable. I didn't 
>> have time those last days to fix what is wrong. Sorry for 
>this inconvenience.
>> I'll have a look on that soon (may be this night) and keep 
>you informed.
>> 
>> Thanks for the report,
>> -- Sabri LABBENE.
>
>Hello,
>
>Thank you for the answer.
>
>Next question :-)
>
>In file lib/WysiwygEdit/Wikiwyg.php
>I would like to replace
>src="/blank.htm" with src="blank.htm"
>
>This is necessary for us, because we are integrating Phpwiki 
>with Gforge and in that case the "blank.htm" file is not at top-level.
>
>Would this modification have bad side-effects? It seems to work for me.

Yes you can replace it. 
I have a blank.htm at top level cause it used by other stuff of CodeX :)
I'll add some comments to the code.

Thanks,
-- Sabri.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/