Community
Participate
Working Groups
Build Identifier: 20100917-0705 History: ---------------------- After installing the Mylyn plugin, I got this bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=323099 As suggested, I updated the pdt. and got a problem similar to https://bugs.eclipse.org/bugs/show_bug.cgi?id=282218 Actual Problem ------------------------------ A php file with html tags, too many, <?php ?> seems to have this problem Specifically, if I have <style><!-- <?php require ($styles_filename); ?> --></style> The editor crashes!! The syntax highlighting goes off and the code assist, highlighting etc and other features of the editor start going on and off without any noticable pattern. The moment I remove the <?php ?> tags from within the "style" markup, the error vanishes! and closing and reopening the file gets the editor back to normal. Reproducible: Always Steps to Reproduce: 1.update the PDT to the release as on date 2.use <?php ?> within the style markup and start coding within 3.remove the <?php ?> along with the coding within, save, close and reopen the file
Created attachment 181468 [details] the error log
Created attachment 181469 [details] eclipse configuration The Eclipse PDT Configuration, where I identified the bug
(In reply to comment #2) > Created an attachment (id=181469) [details] > eclipse configuration > > The Eclipse PDT Configuration, where I identified the bug Hi, although I tried several times to reproduce this I can't. Can you provide (structured) steps to reproduce it? I followed the steps and everything went ok so it may be fixed already...
(In reply to comment #3) > (In reply to comment #2) > > Created an attachment (id=181469) [details] [details] > > eclipse configuration > > > > The Eclipse PDT Configuration, where I identified the bug > > Hi, although I tried several times to reproduce this I can't. > Can you provide (structured) steps to reproduce it? I followed the steps and > everything went ok so it may be fixed already... Hi... I reinstalled the eclipse php and resetup my environment... And luckily (or unluckily) for the time being I am not able to reproduce the behaviour either. Will report again with details if the behaviour persists. Thanks. resolved for now. r
seems like an issue that has been already fixed in latest releases
Verified. No longer reproducible.