1) Ensure that you have all plugins updated to their latest version -- I've seen few kind of similar reports (not the same, but still) that were caused by incompatible plugins.
2) Please run "File | Invalidate Caches..." and restart IDE
Any better? If not -- anything interesting in idea.log (Help | Show Log in XX)
That's only a part of the log -- it even does not show what plugins you have got there. It shows no useful info that may help here -- no exceptions or anything.
If anything -- you should always post full log (as downloadable link, e.g. Google Drive or alike).
BTW -- what error IDE reports. Mover over the error (e.g. the very first red marker on 1st line) and show more detailed message.
You can also run "Code | Inspect Code" to see all issues IDE finds for this file.
If anything #2: disable all custom plugins (not bundled by default) and see how it will behave now.
1) What was the previous version you have upgraded from: was it 2017.2.x or older .. or was it 2017.3 EAP builds.
2) Were all plugins updated straight away (before even project was loaded) or only after that.
In first case (2017.2 and straight plugin update) it should not affect at all .. as caches/indexes are stored in separate folders for each major version. In send case (EAP builds) it's not the case as it's already 2017.3. .. or older plugin did provide some incorrect data etc.
I always use full installer and invalidating caches when removing older/installing new build +plugin update on first launch -- never have such issues. Yes -- more traffic (as full installation package is much larger than a patch) + time waster for re-indexing / loosing Local History (as its linked to indexes sub-system) but it pays off just fine in my case -- no big inconveniences at all.
@Andriy I had 2017.2. I did the update thru the toolbox. As my project loaded and I saw re-indexing, I clicked on the "Update Plugin" buton from the pop-up.
So the plugin update has happened after that (even though new plugin version is downloaded, the actual load happens on IDE launch) .. so it was not technically updated till next launch... so initial indexing was done with old plugin.
So far it could be that you have another language injected for the whole file instead of default HTML and it did not worked properly for some reason. Without knowing the details I cannot say if it's a bug or what. if you are sure that you have not used it and after deleting that file it now works .. then I guess it's resolved for now.
In general (if it still does not work in this project) : just backup and delete whole .idea subfolder (while project is closed in IDE, of course) and then use "Open" or "Open Directory" and point to the that project root folder -- IDE will create brand new project with default settings from those files. You can then re-configure the project as needed.
Hi there,
Looks odd.
1) Ensure that you have all plugins updated to their latest version -- I've seen few kind of similar reports (not the same, but still) that were caused by incompatible plugins.
2) Please run "File | Invalidate Caches..." and restart IDE
Any better? If not -- anything interesting in idea.log (Help | Show Log in XX)
Invalidate cashes does not work for my phpStorm,
my update was from tool box, i've checked plugins , not sure which one is incompatible.
down below is the recent log, hope it helps
thanks, anyway
That's only a part of the log -- it even does not show what plugins you have got there. It shows no useful info that may help here -- no exceptions or anything.
If anything -- you should always post full log (as downloadable link, e.g. Google Drive or alike).
BTW -- what error IDE reports. Mover over the error (e.g. the very first red marker on 1st line) and show more detailed message.
You can also run "Code | Inspect Code" to see all issues IDE finds for this file.
If anything #2: disable all custom plugins (not bundled by default) and see how it will behave now.
I had many errors after updating to 2017.3
Anytime I clicked ALT+F7 on a method, I would always says that it found not match.
Doing the Invalidate Cache & restart fixed my issue
@Christiand
That may depends on:
1) What was the previous version you have upgraded from: was it 2017.2.x or older .. or was it 2017.3 EAP builds.
2) Were all plugins updated straight away (before even project was loaded) or only after that.
In first case (2017.2 and straight plugin update) it should not affect at all .. as caches/indexes are stored in separate folders for each major version. In send case (EAP builds) it's not the case as it's already 2017.3. .. or older plugin did provide some incorrect data etc.
I always use full installer and invalidating caches when removing older/installing new build +plugin update on first launch -- never have such issues. Yes -- more traffic (as full installation package is much larger than a patch) + time waster for re-indexing / loosing Local History (as its linked to indexes sub-system) but it pays off just fine in my case -- no big inconveniences at all.
somehow, i have finally decided to compare the ./idea folder to other "working normally project"
then i have found an additional templatlanguages.xml, after delete this xml file , restart project , re-indexing
this project works correctly
any idea why this file exists?
@Andriy I had 2017.2. I did the update thru the toolbox. As my project loaded and I saw re-indexing, I clicked on the "Update Plugin" buton from the pop-up.
@Christiand
So the plugin update has happened after that (even though new plugin version is downloaded, the actual load happens on IDE launch) .. so it was not technically updated till next launch... so initial indexing was done with old plugin.
@Alessi0413
>any idea why this file exists?
Such file should hold settings for https://www.jetbrains.com/help/phpstorm/template-data-languages.html . If you are sure that you do not use that ... then deleting such file is fine.
So far it could be that you have another language injected for the whole file instead of default HTML and it did not worked properly for some reason. Without knowing the details I cannot say if it's a bug or what. if you are sure that you have not used it and after deleting that file it now works .. then I guess it's resolved for now.
In general (if it still does not work in this project) : just backup and delete whole .idea subfolder (while project is closed in IDE, of course) and then use "Open" or "Open Directory" and point to the that project root folder -- IDE will create brand new project with default settings from those files. You can then re-configure the project as needed.