Deployment default mapping?

Hi, I'm using PHPStorm over a year and after upgrading to version 7 I've noticed new strange behavior in my deployment mappings. I have about 30 deployment configured in my deployment list and about 50 projects, with various combinations between them.
I was used to, that within the project, the deployments with setup mappings was listed first. This helps me easily switching the default deployment (because I sometimes need to).

After upgrade no.7, all my projects have setup default "web path" in all deployments/mappings to "/" (root) and it means every project is configured with every deployment and the sorting of deployments I liked is gone. I have tried to manualy delete all unwanted mappings (there were a lot), but after few days they setup again. Also every new project has the "web path" as "/" in every deployment.

I've tried to google this issue and l've looked all over the settings, but without result. I don't know if it's a bug or feature, but it's annoying. Has any one some advice for me?

Another issue I'm dealing with: When PHPS. finds out, that some file has changed on deployment server (I turned on the checking), it shows me a message to merege or download the file from server. If I click the "download" button, nothing happens and after I make some changes in the file and save it for upoad, message "local sorage and memory content are different" shows up. I had google this issue and deveplopers suggest to "invalidate caches and restart". It helps, but only for few days. Any advices?

Thanks a lot for every help.

2 comments
Comment actions Permalink

Hi there,

I've tried to google this issue and l've looked all over the settings, but without result. I don't know if it's a bug or feature, but it's annoying. Has any one some advice for me?

Originally any deployment entries had no default "mappings".

But since in most cases the web path would be "/" it was asked to be pre-filled with "/" by default -- http://youtrack.jetbrains.com/issue/WI-14827

This issue should be fixed by now: http://youtrack.jetbrains.com/issue/WI-22388  (fix will be available in NEXT v8 EAP build)

It helps, but only for few days. Any advices?

Sorry -- no advices.

I personally do not use such option (to check for remote notifications before editing local copy) as it did not worked well for me.

I'm only using option to check if remote file is different (timestamp and file size) before actual upload (just in case) -- that works good enough (depends on FTP server software and what supported features it supports -- e.g. does it support setting up precise file modification -- I'm mostly uploading to IIS 7.5 .. so it all good for me in this regard .. but some Linux hosts do have issues with that).

0
Comment actions Permalink

Thanks a lot, I couldn't find, that this is allready in issue tracker. I'm looking forward to this fix.

As for the second issue, I will try to setup deployment options by you recomendations and I'll see.

0

Please sign in to leave a comment.