How to enable HTML syntax highlighting in PHP files in JetBrains Fleet?
As far as I'm aware -- you cannot as this is not currently supported.
https://youtrack.jetbrains.com/issue/FL-12928 -- watch this ticket (star/vote/comment) to get notified with any progress.
Related
Suddenly the IntelliJ editor inspections have stopped working.
The syntax highlighting, the compiler errors and so on are not being shown.
The style highlighting works tough.
The inspections in the project navigation tree work and show compilation errors.
gradle build shows compilation errors too.
After updating to IntelliJ 2021.1, the Plugin for Swagger is not compatible anymore.
It seems to break the correct display of inspections.
Deinstalling the Plugin for Swagger helps. I was not able to find a better solution which allows me to keep using the Swagger Plugin.
GitHub issue reporting this problem: https://github.com/zalando/intellij-swagger/issues/325
Fun fact: this error popped out as I was trying to code a coding challenge for Zalando, the company which developed the Swagger Plugin :D.
Check idea.log (Help > Show Log in Explorer) for plugin exceptions and update / disable / reinstall the faulty plugin.
If by any chance, someone stumbles upon this answer and is developing with Ktor (with plugin), there's currently an issue that does the same thing as in asked question.
If your route method name and route path are the same - the IDE analyzer stops (issue link).
...
fun Route.redirect() { // <-- same word (redirect) = BAD
route("/redirect") { // <-- same word (redirect) = BAD
...
While the bug is being solved, you can just rename the route as a solution.
I've performed an update from typo3 4.7.20 to 6.2.15. The process worked fine and there were no critical errors while running the install tool.
The frontend looks fine but the backend is broken:
I've removed all uncompatible extensions before I run the update. I've also checked all settings in the installationtool und deleted the temp/cache folder first.
I've got the feeling that the error is caused by the TemplaVoila! extension, I'm using v. 1.9.8. Firebug does not shows any error.
Does anyone had a similar problem and have already solved it?
Thank you very much!
I have come across this one multiple times. More often it is because there is a broken TBE_STYLES. I suggest you look around for $TBE_STYLES in your typo3conf folder and disable it for the time being. Most likely it will be in the extTables.php or some other file which is included dynamically.
seems BE is working, but you css does not got loaded.
check your 'web inspecter' to see if you get errors on loading CSS.
clear your cache (remove everything in typo3temp) and try again
I have upgraded Prestashop from 15.6.X.X to 16.X.X.X. After the up-gradation, default-bootstrap is activated as a default theme.
When I try to active my theme, the front end page get blank page.
It showing an error, Fatal error: Uncaught exception 'SmartyException' with message 'Unable to load template file .
How can I activate the old theme in upgraded version?
Please advice.
It seems that you miss a .tpl on your theme, please try to re upload it. (Or maybe your theme isn't compatible with 1.6)
There are often problems with Prestashop upgrades.
You need to completely fix all problems before using your template.
Try to option file config/defines.inc.php and change the site to dev mode
/* Debug only */
if (!defined('_PS_MODE_DEV_'))
define('_PS_MODE_DEV_', true);
All errors will show on your frontpage, try to fix all those errors and get your website totally works. Normal you will see problems with database, some tables was not successfully added new columns, then try to add those columns manually via your phpmyadmin
Good luck!
#2plus
Prestashop 1.5+ theme will not work in 1.6 there are lots of changes need. You can enable the debut mode and then you will find the error.
in 1.6 there is new tpl implement global.tpl may be that is missing.
On my site but Securi SiteCheck is showing this:
*Anomaly behavior detected (possible malware). Details: http://sucuri.net/malware/malware-entry-mwanomalysp8
Is there anyway I can stop this malware warning for a fussy client?
Go to wp-content/themes/header.php file and open it in NOTEPAD++ and if you see any JS code below, then simply remove that code...
You have installed malware on your site (possibly your site was compromised) or your code looks like malware due to minified versions of JavaScript, which looks like obfuscated exploits.
I recently took on a project built on XUL (standalone, using xulrunner) - However I can't get it to properly run.
I'm getting this error when I attempt to start it using the command line (xulrunner.exe ../application.ini -jsconsole):
No chrome package registered for chrome://case_scenario_builder/content/case_scenario_builder.xul
The chrome.manifest file looks like this:
content case_scenario_builder file:chrome/case_scenario_builder/content/ contentaccessible=yes
content jslib jar:chrome/jslib.jar!/
skin case_scenario_builder skin file:chrome/case_scenario_builder/skin/
locale case_scenario_builder en-US chrome/case_scenario_builder/locale/en-US/
Any ideas on where I could start debugging?
I figured it out!
In case anyone else runs into this as well:
It was due to the caching system in place by default and the use of .jar containers instead of folders.
The XUL environment had cached both JS and XUL files - and even after disabling those, I had to extract everything that was in the .jar file to the content folder and update the chrome.manifest file.
Thanks for your suggestions on debugging! - they helped the process.
I guess your manifest just isn't getting loaded. To test that I'd introduce an intentional syntax error and check the error console. E.g. if you put
asdfasd
on its own line, you should get a Warning: Ignoring unrecognized chrome manifest directive 'asdfasd'. in the Error console.
(Note to other experts: initially I wanted to suggest dropping 'file:' prefix and avoiding underscores in the package name, but I tested it on a Firefox nightly, and it works fine.)
Your chrome package clearly didn't get registered. From what I can tell, the reason is the bogus file: prefix, you should drop it when specifying relative paths:
content case_scenario_builder chrome/case_scenario_builder/content/ contentaccessible=yes
Btw, I suspect that you copied contentaccessible=yes from somewhere - you should drop it as well unless you know what it does.