|
|
|
[
Permlink
| « Hide
]
Glen Ainscow - 28/Jan/08 01:49 PM
See: http://forums.aptana.com/viewtopic.php?t=4546
 This is not only an php issue, same things go for HTML, JavaScript and CSS as well.
In what ways does this impact HTML, JavaScript, and CSS?
This should be fixed by setting our content type priority to low since content type doesn't directly affect our editors opening.
"In what ways does this impact HTML, JavaScript, and CSS?"
Apart from PHP, Aptana also install content types for HTML, JavaScript, and CSS, although these already exists in Eclipse. I am not sure but assume they belong to/come with PDT. I started out with installing the "All-in-one" PDT version of Eclipse 3.3 and have only added Aptana after so I guess they must have been there. The problem is that neighter the Aptana nor PDT content types can be changed as all items are (locked). The only thing that can be done/changed,afai can see, is to set the default editor for a File association, but for these duplicated types the result seem to be the will be the only available editor. I installed version 0.2.11 today and this issue happened to me. I can use the Aptana PHP plugin just fine but trying to change the association to PDT break the content type for php files.
I don't know if this will help but only the locked content types are afected because I can change between editors just fine when the file extension is *.thtml (CakePHP extension for view files). Hello, thanks for your reply.
I'm using the patch version for the 1.1.1 release. My PHP plugin version is 0.2.11.00706 So you are seeing errors when you open the PDT editor?
Yes, I get the message "unsupported content type" from Eclipse but going trough the supported PHP content types all my supported file extensions are there. When I change the default editor for php files to be Aptana then everything works as expected.
Not fixed atm - my PHP plugin version: 0.2.11.006706_200801112034
When installed, "PHP Editor" and "PHP/HTML WYSIWYG Editor" are not working any longer. It's the same for me: I'm using PDT editor by default. When Aptana PHP plugin is enabled, the PDT editor signals "unsupported content type in editor". So I must disable Aptana PHP plugin.
My plugin version is 0.2.11.006706_200801112034 This still happens, so I reopen this bug.
I have Aptana plugin for Eclipse version: 1.11.1.00004 PHP plugin version: 0.2.11.006706_200801112034 This is an annoying bug and should have high priority. I am forced to make a clean eclipse install as the redundant content-types provided by Aptana are locked up. I've removed the aptana php plugin, but the php content type is still regisered with aptana, so pdt can't open php files anymore. I think that the eclipse integration needs to be more smooth, and it is therefore better to use the file-association system from eclipse itself, rather than introducing a new and conflicting system.
Hope the team will comment/fix on this issue soon! Somehow I fixed this a while back. I've had to re-install, and now it's back. Duplicate content types for HTM, JS and CSS. This makes it impossible to associate these files types with Aptana.
Interferencing of launch configuration delegates is fixed. PHP editors are binded to different content types. So it seems that issue is fixed. According to other content types(HTML,CSS,...) issue #STU-1898 is created.
If this problem occurrs again please reopen this issue.
Verified. This appears to be the same issue as http://support.aptana.com/asap/browse/STU-1898
. |
|||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Closed
Unprioritized
Aptana PHP content type interferes with PDT PHP content type