Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » PHP Development Tools (PDT) » Cannot open PHP files after updating - Editor could not be initialized(With PDT 2.2.0.v200911190058 Eclipse gives me an "Unable to create editor ID org.eclipse.php.editor: Editor could not be initialized." error when I try to open any PHP file)
Cannot open PHP files after updating - Editor could not be initialized [message #500210] Wed, 25 November 2009 12:01 Go to next message
Tomas Zilvar is currently offline Tomas ZilvarFriend
Messages: 7
Registered: November 2009
Junior Member
Hi,

I cannot open PHP files any more after the latest update of PDT. When I attempt to open any PHP file, it says that it is "Unable to create editor ID org.eclipse.php.editor: Editor could not be initialized." and gives me this stack trace:

Eclipse: Version: 3.5.1 Build id: M20090917-0800
PHP Development Tools (PDT) Runtime Feature 2.2.0.v200911190058-7L7JF8NcJKhTTUhJK5Y
Dynamic Languages Toolkit - Core Frameworks 2.0.0.v20090917-1518-7L--EAAoOQBUSjFBcvjL

java.lang.NoSuchMethodError: org.eclipse.dltk.compiler.IElementRequestor.acceptMethodRefe rence([CIII)V
at org.eclipse.php.internal.core.compiler.PHPSourceElementReque stor.visit(PHPSourceElementRequestor.java:455)
at org.eclipse.php.internal.core.compiler.PHPSourceElementReque stor.visit(PHPSourceElementRequestor.java:652)
at org.eclipse.php.internal.core.compiler.ast.nodes.PHPCallExpr ession.traverse(PHPCallExpression.java:37)
at org.eclipse.php.internal.core.compiler.ast.nodes.UnaryOperat ion.traverse(UnaryOperation.java:51)
at org.eclipse.php.internal.core.compiler.ast.nodes.IfStatement .traverse(IfStatement.java:54)
at org.eclipse.dltk.ast.statements.Block.traverse(Block.java:43 )
at org.eclipse.dltk.ast.declarations.ModuleDeclaration.traverse (ModuleDeclaration.java:70)
at org.eclipse.dltk.core.AbstractSourceElementParser.parseSourc eModule(AbstractSourceElementParser.java:35)
at org.eclipse.php.internal.core.compiler.ast.parser.PHPSourceE lementParser.parseSourceModule(PHPSourceElementParser.java:2 8)
at org.eclipse.dltk.core.SourceParserUtil.parseSourceModule(Sou rceParserUtil.java:237)
at org.eclipse.dltk.internal.core.AbstractSourceModule.buildStr ucture(AbstractSourceModule.java:530)
at org.eclipse.dltk.internal.core.Openable.generateInfos(Openab le.java:185)
at org.eclipse.dltk.internal.core.ModelElement.openWhenClosed(M odelElement.java:182)
at org.eclipse.dltk.internal.core.BecomeWorkingCopyOperation.ex ecuteOperation(BecomeWorkingCopyOperation.java:45)
at org.eclipse.dltk.internal.core.ModelOperation.run(ModelOpera tion.java:698)
at org.eclipse.dltk.internal.core.ModelOperation.runOperation(M odelOperation.java:764)
at org.eclipse.dltk.internal.core.SourceModule.becomeWorkingCop y(SourceModule.java:68)
at org.eclipse.dltk.internal.ui.editor.SourceModuleDocumentProv ider.createFileInfo(SourceModuleDocumentProvider.java:1271)
at org.eclipse.ui.editors.text.TextFileDocumentProvider.connect (TextFileDocumentProvider.java:478)
at org.eclipse.dltk.internal.ui.editor.SourceModuleDocumentProv ider.connect(SourceModuleDocumentProvider.java:1517)
at org.eclipse.ui.texteditor.AbstractTextEditor.doSetInput(Abst ractTextEditor.java:4134)
at org.eclipse.ui.texteditor.StatusTextEditor.doSetInput(Status TextEditor.java:203)
at org.eclipse.ui.texteditor.AbstractDecoratedTextEditor.doSetI nput(AbstractDecoratedTextEditor.java:1413)
at org.eclipse.ui.editors.text.TextEditor.doSetInput(TextEditor .java:166)
at org.eclipse.wst.sse.ui.StructuredTextEditor.doSetInput(Struc turedTextEditor.java:1712)
at org.eclipse.php.internal.ui.editor.PHPStructuredEditor.doSet Input(PHPStructuredEditor.java:2208)
at org.eclipse.ui.texteditor.AbstractTextEditor$19.run(Abstract TextEditor.java:3115)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread( ModalContext.java:464)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.ja va:372)
at org.eclipse.jface.window.ApplicationWindow$1.run(Application Window.java:759)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:70)
at org.eclipse.jface.window.ApplicationWindow.run(ApplicationWi ndow.java:756)
at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow. java:2579)
at org.eclipse.ui.texteditor.AbstractTextEditor.internalInit(Ab stractTextEditor.java:3133)
at org.eclipse.ui.texteditor.AbstractTextEditor.init(AbstractTe xtEditor.java:3160)
at org.eclipse.wst.sse.ui.StructuredTextEditor.init(StructuredT extEditor.java:2321)
at org.eclipse.php.internal.ui.editor.PHPStructuredEditor.init( PHPStructuredEditor.java:1151)
at org.eclipse.ui.internal.EditorManager.createSite(EditorManag er.java:798)
at org.eclipse.ui.internal.EditorReference.createPartHelper(Edi torReference.java:644)
at org.eclipse.ui.internal.EditorReference.createPart(EditorRef erence.java:462)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(Workb enchPartReference.java:595)
at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:31 3)
at org.eclipse.ui.internal.presentations.PresentablePart.setVis ible(PresentablePart.java:180)
at org.eclipse.ui.internal.presentations.util.PresentablePartFo lder.select(PresentablePartFolder.java:270)
at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrd er.select(LeftToRightTabOrder.java:65)
at org.eclipse.ui.internal.presentations.util.TabbedStackPresen tation.selectPart(TabbedStackPresentation.java:473)
at org.eclipse.ui.internal.PartStack.refreshPresentationSelecti on(PartStack.java:1256)
at org.eclipse.ui.internal.PartStack.handleDeferredEvents(PartS tack.java:1224)
at org.eclipse.ui.internal.LayoutPart.deferUpdates(LayoutPart.j ava:400)
at org.eclipse.ui.internal.PartSashContainer.handleDeferredEven ts(PartSashContainer.java:1409)
at org.eclipse.ui.internal.LayoutPart.deferUpdates(LayoutPart.j ava:400)
at org.eclipse.ui.internal.WorkbenchPage.handleDeferredEvents(W orkbenchPage.java:1416)
at org.eclipse.ui.internal.WorkbenchPage.deferUpdates(Workbench Page.java:1406)
at org.eclipse.ui.internal.WorkbenchPage.closeEditors(Workbench Page.java:1380)
at org.eclipse.ui.internal.WorkbenchPage.closeEditor(WorkbenchP age.java:1435)
at org.eclipse.ui.internal.EditorPane.doHide(EditorPane.java:61 )
at org.eclipse.ui.internal.PartStack.close(PartStack.java:543)
at org.eclipse.ui.internal.EditorStack.close(EditorStack.java:2 06)
at org.eclipse.ui.internal.PartStack$1.close(PartStack.java:122 )
at org.eclipse.ui.internal.presentations.util.TabbedStackPresen tation$1.handleEvent(TabbedStackPresentation.java:83)
at org.eclipse.ui.internal.presentations.util.AbstractTabFolder .fireEvent(AbstractTabFolder.java:270)
at org.eclipse.ui.internal.presentations.util.AbstractTabFolder .fireEvent(AbstractTabFolder.java:279)
at org.eclipse.ui.internal.presentations.defaultpresentation.De faultTabFolder.access$1(DefaultTabFolder.java:1)
at org.eclipse.ui.internal.presentations.defaultpresentation.De faultTabFolder$1.closeButtonPressed(DefaultTabFolder.java:70 )
at org.eclipse.ui.internal.presentations.PaneFolder.notifyClose Listeners(PaneFolder.java:626)
at org.eclipse.ui.internal.presentations.PaneFolder$3.close(Pan eFolder.java:206)
at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:21 99)
at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.j ava:327)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3493)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3112)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 21)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)

I have no idea how to fix this, any help is appreciated.
Re: Cannot open PHP files after updating - Editor could not be initialized [message #500317 is a reply to message #500210] Wed, 25 November 2009 16:10 Go to previous messageGo to next message
zetxx is currently offline zetxxFriend
Messages: 1
Registered: July 2009
Junior Member
can anyone help, we are stuck here?
10xs
icon13.gif  Re: Cannot open PHP files after updating - Editor could not be initialized [message #500758 is a reply to message #500210] Sat, 28 November 2009 09:32 Go to previous messageGo to next message
Tomas Zilvar is currently offline Tomas ZilvarFriend
Messages: 7
Registered: November 2009
Junior Member
Can I provide some more info? Am I the only one stuck with this issue? Is it a bug in Eclipse/PDT or is it something I screwed up? It pretty much renders my Eclipse unusable... I guess I'll have to try NetBeans Confused , then a paid solution like MyEclipse, Zend Studio or something like that Sad
Re: Cannot open PHP files after updating - Editor could not be initialized [message #500776 is a reply to message #500317] Sat, 28 November 2009 15:54 Go to previous messageGo to next message
Sorin  is currently offline Sorin Friend
Messages: 6
Registered: November 2009
Junior Member
I have exactly the same problem, and i don't know how to solve it.. I uninstalled the PDT 2.2, but i still have the PHP perspective, and when i'm trying to open a .php file in editor, i got that error..

What we can do? Sad

Regards
Re: Cannot open PHP files after updating - Editor could not be initialized [message #500803 is a reply to message #500210] Sat, 28 November 2009 22:13 Go to previous messageGo to next message
No real name is currently offline No real nameFriend
Messages: 1
Registered: November 2009
Junior Member
Hey, same Problem here.

Try to install Eclipse + PDT today and get the same error, when I try to open a php file.
Last week at work everything works fine. Sad
Re: Cannot open PHP files after updating - Editor could not be initialized [message #500819 is a reply to message #500210] Sun, 29 November 2009 10:12 Go to previous messageGo to next message
Sorin  is currently offline Sorin Friend
Messages: 6
Registered: November 2009
Junior Member
probably it's a bug.. can anyone confirm this? So many errors with this Eclipse and it's plugins..
icon4.gif  Re: Cannot open PHP files after updating - Editor could not be initialized [message #500820 is a reply to message #500210] Sun, 29 November 2009 10:32 Go to previous messageGo to next message
Tomas Zilvar is currently offline Tomas ZilvarFriend
Messages: 7
Registered: November 2009
Junior Member
I think it is already filed as a critical bug under

https://bugs.eclipse.org/bugs/show_bug.cgi?id=295865

which may be a duplicate of

https://bugs.eclipse.org/bugs/show_bug.cgi?id=295871


I guess we just have to wait an hope it will be resolved soon. I'm just surprised and bewildered by the fact that they can release such a broken update, which pretty much makes an up-to-date Eclipse unusable for PHP developers Sad I would understand if it were some other type of file, but *.php? Come on, has any testing been done at all?

It casts a bad light on open source projects in general. Imagine a company which uses it as a primary development tool, they can close the business and go on vacation in the most critical time of the year :-/
Re: Cannot open PHP files after updating - Editor could not be initialized [message #500822 is a reply to message #500210] Sun, 29 November 2009 10:55 Go to previous messageGo to next message
Tomas Zilvar is currently offline Tomas ZilvarFriend
Messages: 7
Registered: November 2009
Junior Member
Now it's our job to vote for the bug so that it could be fixed soon Wink It only has 2 votes so far, so don't be shy and vote like you've never voted before! Very Happy
Re: Cannot open PHP files after updating - Editor could not be initialized [message #500887 is a reply to message #500210] Mon, 30 November 2009 06:07 Go to previous messageGo to next message
sherlock  is currently offline sherlock Friend
Messages: 1
Registered: November 2009
Junior Member
I have the same problem, it seems I have to wait...
Re: Cannot open PHP files after updating - Editor could not be initialized [message #500906 is a reply to message #500210] Mon, 30 November 2009 09:20 Go to previous messageGo to next message
Christian Rosenau is currently offline Christian RosenauFriend
Messages: 1
Registered: November 2009
Junior Member
After manually installing the lates nightly build (for me it was 200911230913) everything worked fine again. (Could not downgrade, so I decided to take the risk)

greatest improvement for me was, that autocompletion now inserts argument variables automatically (like java does)
Re: Cannot open PHP files after updating - Editor could not be initialized [message #500912 is a reply to message #500906] Mon, 30 November 2009 09:40 Go to previous messageGo to next message
Tomas Zilvar is currently offline Tomas ZilvarFriend
Messages: 7
Registered: November 2009
Junior Member
That's great news, Christian, hope the fix will be released into the updates soon Cool Installing the nightly build just doesn't seem the right way to go, since I'm not the proper "risk taker" Wink I could not downgrade either, that was another strange thing about this bug... Forward, comrades, not a step back! Very Happy
Re: Cannot open PHP files after updating - Editor could not be initialized [message #500916 is a reply to message #500210] Mon, 30 November 2009 10:11 Go to previous messageGo to next message
Tomas Zilvar is currently offline Tomas ZilvarFriend
Messages: 7
Registered: November 2009
Junior Member
Another solution is to uninstall PDT 2.2 and install the 2.1 version, which is included in Galileo update site. (http://download.eclipse.org/releases/galileo). After that, everything worked fine. This may be the proper way if you want a stable environment and it renders my previous complaints useless and out of the picture. However, there was no notice that the 2.2 was an experimental development branch...
Re: Cannot open PHP files after updating - Editor could not be initialized [message #500938 is a reply to message #500916] Mon, 30 November 2009 11:42 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: dkel50.hotremovemail.com

If you look at the main PDT page, you should see that PDT 2.2 is
scheduled for final release in June 2010, so all 2.2 builds at this
point are test builds for people who want to try the latest development
version and to provide valuable feedback on the progress of the release,
but be aware that things may get broken during this period so they
aren't recommended as your main development environment.

Dave Kelsey

On 30/11/09 10:11, Tomas Zilvar wrote:
> Another solution is to uninstall PDT 2.2 and install the 2.1 version,
> which is included in Galileo update site.
> (http://download.eclipse.org/releases/galileo). After that, everything
> worked fine. This may be the proper way if you want a stable environment
> and it renders my previous complaints useless and out of the picture.
> However, there was no notice that the 2.2 was an experimental
> development branch...
Re: Cannot open PHP files after updating - Editor could not be initialized [message #500955 is a reply to message #500938] Mon, 30 November 2009 13:17 Go to previous message
Tomas Zilvar is currently offline Tomas ZilvarFriend
Messages: 7
Registered: November 2009
Junior Member
Dave, you're right, sorry for the complaints and remarks. I have already installed the stable version, which works with no problems. My bad, I should have seen it coming, at least the "-dev" suffix should have warned me.

However, it might be a good idea to add a notice to the installation page, or at least show the 2.1 version at the top of the page. I came to the page via search engine results and hadn't therefore studied the main page properly. To be honest, I wouldn't pay attention even if I had, because it is too low and nothing labels the branches as "experimental" or "stable" apart from the release date.
Previous Topic:PHPTaskValidator does not work for folders
Next Topic:Is there a feature or plug-in for PDT to send files via FTP to a remote server?
Goto Forum:
  


Current Time: Sun Sep 23 18:21:02 GMT 2018

Powered by FUDForum. Page generated in 0.01857 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top