Expression >
Forums - Accueil
>
Expression Web and SuperPreview
>
EW3 SFTP Publishing and External Editors - issues.
EW3 SFTP Publishing and External Editors - issues.
- I used FP for publishing my sites for many years using the FrontPage server extensions. (I didn't use FP for editing since I hand code php in HomeSite)...I made the switch to EW2 earlier this year and have had no problems with it... continuing to publish all sites without issue using FPSEMy primary reasons for sticking with FP (and EW) have always been that the package made the task of managing the files within a site, and subsequently performing fast publishes which only changed edited files a breeze...well it's all changed.I bought EW3 a couple of days ago, having noticed that it offered publishing via SFTP such that I could have FTP disabled on my servers and finally get round to removing the FPSEs.So, what I want to know is whether I'm missing something with regard to the following;The Publish Site button is gone, replaced by the blue arrows between panes in publish view. With no files selected, clicking the publish button proceeds to upload (and therefore overwrite) EVERY file in the site. This is a major change from the default in EW2 which was publish changes only. Am I missing some kind of setting that I can select to control which files are uploaded in a publish command?When publishing via FPSE, EW2 and EW3 are ignorant of any files on the server which do not exist in the local web UNLESS they existed in the local METADATA and have been deleted locally. In this circumstance, deleting the file in the local web will prompt for the remote file to be deleted.Now, when publishing with SFTP, *ANY* file which exists on the remote server is prompted for deletion if it doesn't exist in the local site. This is massively frustrating since the vast majority of my sites are CMS systems into which clients load potentially hundreds and thousands of files via their CMS. I can cope with telling EW3 to not delete these files once, but why does it insist on prompting me every time I make a minor change and publish my revisions???When editing files in an external editor (eg TopStyle or Homesite) FP and EW2 both reflected the modified files in my folder list (and in the local window of the publishing screen) immediately the file was saved. To get EW3 to recognise the updated file, I have to click the REFRESH button. WHY??? Am I missing something? Additionally, when exiting, EW3 informs me that I still have items left on my import list!!!
Toutes les réponses
- <quote>
The Publish Site button is gone, replaced by the blue arrows between panes in publish view.
</quote>
Use control + Click to select the files you want published and then click the blue arrow.
If nothing is selected, everything is published.
<quote>
When publishing via FPSE, EW2 and EW3 are ignorant of any files on the server which do not exist in the local web UNLESS they existed in the local METADATA and have been deleted locally.
</quote>
Have you opened both the remote and local sites and recalculated hyperlinks?
That will ensure the sites match.
you can also use the Syncronize feature. ( double arrows )
<quote>
When editing files in an external editor (eg TopStyle or Homesite) FP and EW2 both reflected the modified files in my folder list (and in the local window of the publishing screen) immediately the file was saved. To get EW3 to recognise the updated file, I have to click the REFRESH button. WHY???
</quote>
Have you added the editors to list in the configure editors tab of application options, and if so are you opening the files by right clicking in folder view and selecting those editors?
<quote>
Am I missing something? Additionally, when exiting, EW3 informs me that I still have items left on my import list!!!
</quote>
The only time I have seen that is when editing live via ftp://
A note about " editing live with ftp:// "........ it is impossible.
EW downloads the file into a temporary direcotry and that is the working file, when you save it EW sends it back to the server.
I believe the issue with import ( left behind files ) as been fixed in the pending service pack.
Expression Web MVP The Publish Site button is gone, replaced by the blue arrows between panes in publish view. With no files selected, clicking the publish button proceeds to upload (and therefore overwrite) EVERY file in the site. This is a major change from the default in EW2 which was publish changes only. Am I missing some kind of setting that I can select to control which files are uploaded in a publish command?
The rules are:
1. If something is selected, that's what is published.
2. If nothing is selected, what gets published is controlled by the View dropdown. If you're viewing All Files, that's what gets published. If you're viewing Changed Files, that's what gets published. It's essentially what-you-see-is-what-you-publish.
And yes, we understand that this change has proven to be more confusing than we had hoped, so we will almost certainly be making changes in the next version.
This change was deliberate and it has nothing to do with SFTP. If you're publishing the entire site, the thinking is that you want to be notified of files that are on the destination site that aren't on the source site so that you can sync the two sites completely. In Expression Web 2, this happened when you published Changed Files. In Expression Web 3, that now happens when you publish All Files. If you switch to publishing Changed Files, you will not get prompted. This change was prompted by user complaints and research.Now, when publishing with SFTP, *ANY* file which exists on the remote server is prompted for deletion if it doesn't exist in the local site. This is massively frustrating since the vast majority of my sites are CMS systems into which clients load potentially hundreds and thousands of files via their CMS. I can cope with telling EW3 to not delete these files once, but why does it insist on prompting me every time I make a minor change and publish my revisions???
When editing files in an external editor (eg TopStyle or Homesite) FP and EW2 both reflected the modified files in my folder list (and in the local window of the publishing screen) immediately the file was saved. To get EW3 to recognise the updated file, I have to click the REFRESH button. WHY??? Am I missing something? Additionally, when exiting, EW3 informs me that I still have items left on my import list!!!
That's a known bug, one we've fixed in the upcoming service pack.
Paul Bartholomew
Microsoft Expression Web- Proposé comme réponsePaul Bartholomew,MSFT, Modérateurjeudi 5 novembre 2009 02:41
- Paul,
you're supposed to be at happy hour, or doing what ever makes you happy at this time of day.
;-)
Expression Web MVP - View changed files is useless while the timestamp bug exists. I sure hope that is fixed in the long promised patch.
Thank you for your responses Paul, most useful. I shall use the changed files view in the publishing window from now on.Paul Bartholomew
Microsoft Expression Web
This change was deliberate and it has nothing to do with SFTP. If you're publishing the entire site, the thinking is that you want to be notified of files that are on the destination site that aren't on the source site so that you can sync the two sites completely. In Expression Web 2, this happened when you published Changed Files. In Expression Web 3, that now happens when you publish All Files. If you switch to publishing Changed Files, you will not get prompted. This change was prompted by user complaints and research.
I reverse my earlier thanks as it appears to have been a little premature...
Paul Bartholomew
Microsoft Expression WebAs I said in my original post, the vast majority of my sites are CMS systems. The number of files in the cms system is dwarfed by the volume of files and the number of images a client will potentially upload to their site. Most are ecommerce sites so for every database record, there are typically 5 additional files written into the file system; 1 html file and 4 images. One of my sites has over 50,000 products, ie 250,000 extra files that are not in my local copy of the site... and which I do not need in my local copy since that aspect is taken care of by a regular backup and recovery plan. Most other sites have several thousand records so once again, a significant number of files on the server within the site which are not in my local EW copies.I do NOT want these files to be on my local machine... I don't need them. Is there *ANY* way in which I can get EW3 to stop doing this. If not, I will have to revert back to EW2 which does NOT exhibit this behaviour. If I did want them locally, I would pick the Synchronise option.I've just tried switching to Changed Files view and EW3 just hangs.Doing a complete publish site and EW3 just hangs.Both the above are when connected via SFTP. Is there some issue with EW3 and "large" sites? I haven't checked via any other method, though my ultimate aim was to switch off FTP and FPSE on my servers and solely publish via SFTP.Having to publish by manually selecting individual files that I've changed is not my idea of progress!View changed files is useless while the timestamp bug exists. I sure hope that is fixed in the long promised patch.
The code is quite complex and I cannot guarantee that we have solved every bug in that code but we have solved all of the known ones, including all of those where a customer was kind enough to give us access to their site.
Paul Bartholomew
Microsoft Expression WebThis is the first I've heard of any reports of Expression Web hanging while publishing. Would it be possible to give us access to your site so that we can try to repro this and see if there is something we can do to fix it? You can reach me at my microsoft.com alias of paulbart if this is something you'd be willing to let us do.
In the meantime, one thing I can suggest is that you make use of a new feature we added in Expression Web 3, and that is the ability to mark folders as Exclude from Publishing. This only works on the local site side, I believe, so what you would do is set up empty folders on your local site that correspond to the server folders you don't want us to look into or nag you about, then mark those local folders as Exclude from Publishing. It's a bit of a nuisance to set up if you have a lot of these folders but once set up should help alleviate the pain you're experiencing.
Paul Bartholomew
Microsoft Expression WebPaul,
What, and miss all this abuse? :)
you're supposed to be at happy hour, or doing what ever makes you happy at this time of day.
;-)
Paul Bartholomew
Microsoft Expression Web- You've got mail... (assuming I got your email address correct as paulbart [at] m........ dot com)
- Si,
Create a folder write the same name as your CMS folder(s) and right click on it and set not to publish. In earlier versions of EW you would convert it folders G Jobsites. That tells EW to ignore it.
MS MVP Expression Tutorials & Help http://by-expression.com and online instructor led Expression Classes - Hi Cheryl,thanks for your input.I've set the CMS content folder to "Excluded" however EW3 is still hanging when publishing...Paul is, however, on the case directly so fingers crossed.As it happens, each time I create a site, the initial folder structure is published with EW2 (as was) initially, and then I have to log on via SSH to set permissions anyway, so setting a folder to excluded AFTER initial publishing shouldn't be an issue... if we can get past the hang problem!
- Hopefully Paul will get you sorted.
MS MVP Expression Tutorials & Help http://by-expression.com and online instructor led Expression Classes View changed files is useless while the timestamp bug exists. I sure hope that is fixed in the long promised patch.
The code is quite complex and I cannot guarantee that we have solved every bug in that code but we have solved all of the known ones, including all of those where a customer was kind enough to give us access to their site.
Paul Bartholomew
Microsoft Expression Web
That is very good news Paul, I look forward to the patch.
Good for that customer, would that more were so co-operative :-)
