Each time I restart a Run/Debug Configuration, WebStorm opens a new Tab in Chrome, which is extremely annoying. Instead it should rerun the same configuration and use the same tab.
The WebStorm-debug-config documentation says, that you need to explicitly allow such behavior by setting the Allow running in parallel checkbox, which is off in my configuration.
Is there something else I am missing to prevent WebStorm from opening new tabs?
I am using the latest Chrome and Webstorm version on Windows
I had the same problem and could not find the right settings in Webstorm,
but if this is an option you could install, for example, chrome extension: "Clutter Free - Prevent duplicate tabs". It will prevent Webstorm from opening a new tab with the same URL.
In the Clutter Free settings also check the "Refresh existing tab" this way when you rerun your app, the changes in the code will be shown, but extra tabs will not open.
The solution is far from ideal, but it is better than the annoyance.
Related
I have decided to use WebStorm it seems good however most of the time if I go to Tools - Deployment the upper menu options are greyed out? I can configure and I can go to Options but I cannot download from the server? I can open the remote host just fine and scroll through documents that way but from what I understand WebStorm loses a lot of functionality if you develop this way.
I have no Git and am just working by myself so this workflow is fine for me right now.....if I can download from the server!
In my Deployment Menu from Tools all of the tests work and I can autofind my folder and all that. Whats going on?
Here is the Mappings section:
Your Local path has to be part of your current project (root or a subfolder).
The deployment path a folder of your server where it should be stored - if it should be stored on the root it is just a slash: '/'.
If your connection is successful you should be able to select a folder with the dialog (on the right).
Make also sure your server is marked as 'default' which is your default connection for this project - based on that link.
The projects has been indexed by WebStorm so you can easily refactor and other fancy stuff.
Every project has a root folder with a config folder .idea.
For those that are convinced their mappings are set up the right way, here's one key thing to check. It seems like their SFTP usage does not follow symbolic links (on the remote) correctly. And you can see that if you go to the Mappings tab and click on the "..." for the Deployment path - when it shows the list, symlinked dirs do not show up. By avoiding symlinks in the path, I was able to get the upper part of the Tools/Deployment menu to be active again (non-grey)
I was using PyCharm Pro 2017.3
I'm trying to add the cumulative hotfix to ColdFusion 9.0.1. The instructions say to click on the 'i' in CFAdministrator and In the "Update File" text box, browse and select chf9010004.jar located under CF901/lib/updates.
The issue seems to be that whatever browser plugin that is being used is no longer supported by the current JRE version. Is there a way to manually add the hotfix without this step requiring to use the Java file browser?
In Safari the Java file uploader plugin says java out-of-date even though I'm running the latest version.
In Chrome a message comes up that says This site uses a plugin JAVA (TM) that will soon be unsupported. The plugin seems to load, but never goes past saying retreiving initial directories
Do not use the Browse Server button, just type the full path to the extracted chf9010004.jar file into the Update File text box then click the Submit Changes button.
The path should be something like:
C:\directory_where_you_extracted_the_zip\CF901\lib\updates\chf9010004.jar
So I'm just starting to work in sitecore and for some reason none of menu options are working in Page Editor mode for the site that I'm working on. We pretty much have the sitecore website and add some extra page content (MVC app files) to it. I'm getting a variety of javascript errors.
In content Editor, if I click the Sitecore logo and click on Properties I get
TypeError: contentIframe.dialog is not a function
In page editor if I click on the blue components button I get:
TypeError: i.widget is not a function
I'm guessing maybe it's a conflict between jquery that we're using for this website and whatever Sitecore is using. I think it's 7 - but I can't see it via the menu option :)
That guess could be wrong - it could in fact be a browser issue, but I've ensured Firefox is not blocking popups. It doesn't work in Firefox, IE or Chrome though.
The weird thing is that no one else on the project is having this issue it's only on my computer.
Edit - I've also just tried re-installing (7.2) without any local code changes I still can't click on a page and go to Presentation, Details (Layout) - I get a TypeError: contentIframe.dialog is not a function
Edit 2 - I've noticed that I can use sitecore in the QA environment and the dialogs work fine there. So it's something specific to my local build of the site we have (sitting on top of sitecore). But the dialogs just throw jquery errors when I do stuff locally. I was hoping it would be a browser setting but doesn't look like it.
Edit 3 - What I've tried this morning.
Same thing happens in all browsers (FF, IE, Chrome) and I’ve cleared
my browser cache I can access the QA site and the dialog appears as
expected
Copied across the QA site files, pointed my local Digital
site in IIS to the new folder – dialogs don’t work
Team member tried accessing the site from his machine (pointing to my IP address) and
dialogs work for him
I tried seeing if another local sitecore site dialogs were working – but the menu items for that are opening as new windows (so I’m guessing it’s a sitecore 7.2 feature that they appear as jquery dialogs??)
So after googling for rejected-by-urlscan it turns out there's a program called UrlScan from microsoft that was blocking my dialogs. Uninstalled that and I now have dialogs appearing for sitecore. Very exciting :)
I guess it is a problem with some browsers plugin. Sitecore is sensitive to scripts that are used(different versions of jquery or prototype.js). Plugins can inject scripts to HTML source of pages and it can cause errors.
Try to switch off all plugins at least at one browser and check the results.
I recently downloaded the Aptana Studio 3 and installed it on my computer..I also configure the webserver in aptana by navigating in window > preferences > webservers, and then i click new button i choose "external web server". then filled all fields ,
Name:WampSerever
Base URL://localhost
C:\wamp\www
Start Command: NET START wampapache
stop Command: NET STOP wampapache
After that, when i am going to test my php by clicking the green button above in the Aptana Studio select "Run firefox-Internal Server"...the firefox open but it displays blank page...
This is what is displayed in the URL
http://127.0.0.1:8020/TestAptana/Hello.php
If your code is correct then try this. I use XAMMP as my server so I'm not sure if this will work with WAMMP.
Go to run configurations select Web Browser then choose which browser you want to use. Then in the main tab under Server find "Use base URL" and click on it. Enter http://localhost/ and make sure that you check the "Append project name".
Make sure that your index page's name is index.html or index.php if you are using php and try running it.
I have this problem too, but one additional thing you need to is to set the path for PHP.exe.
Do this by going to Preferences/Aptana Studio/Editors/PHP/PHP Interpreter. Add and fill in blanks (browse) to php.exe.
When we set the addAspxExtension web.config setting to true for our website, debug mode stops working for all pages of our site except for the homepage. When I say that it stops working I mean that it displays the actual page but without the Sitecore ribbon and profiling information.
I guess we could apply this setting only in our content delivery environments and leave it on (addAspxExtension="true") for our content entry environment but I was wondering if anyone has managed to get around this issue?
Update
Until Sitecore resolves this issue I have decided to only set the addAspxExtension setting to "true" in our Preview and Production environments. That way the debug mode will still work in our development environment.
As of right now, this issue is a bug that Sitecore is aware of and should hopefully be fixed by the next update. There are basically 2 workarounds for it:
Set the addAspxExtension attribute to “false” value.
Manually write the .aspx extension to other URLs which are different from the home page.
Hope that helps..