Yes, it is version 1.6.9 of Subversion that is included in Dreamweaver CS5.5. (Sorry about the incorrect information in the above mentioned PDF! I have asked the appropriate party to get the documentation corrected.)
As for the issue you are facing, have you tried using the IP address (instead of the name) for the Server Address?
Thanks for your reply Carey! For now I went with Tortoise. But I will try to use the loopback address shortly and post the result.
About the documentation, there are many others on the Adobe website and Internet:
They may need to know -)
Once again, according to this information sheet 1.7 is supposed to be supported by the DW CS6 client.
However it is not, that is three versions CS5+ that should have been upgraded to support 1.7!
I have two questions here.....
1). Are there any plans to release an update for DW to support 1.7 so we can stop experiencing the following error?
SVN: #0, Path 'https://repodirectorypath' is not canonicalized; there is a problem with the client.
2). Do the Dreamweaver developers ever plan on enabling 'Git' or 'Mercurial' as additional options, or are we stuck with SVN?
Additional Information for those of you trying to use DW with SVN 1.7.
Apparently there is a line of code you can put in your SVN settings to help resolve this.
Additionally we found that removing the port from the SVN settings in the DW project can (sometimes) resolve the issue.
Thanks for bringing this to our attention, RoyalT.
The version included is 1.6.9, not 1.7, as you have likely discovered on your own. I'll let the team know so they can get the PDF updated.
Can you tell me how you located that PDF?
For example, by searching the web, or by clicking on a link to it from somewhere.
If you clicked a link, please include the URL of that page.
Regarding item #1: Please send a request to update Subversion in Dreamweaver directly to our development team: http://adobe.ly/DWwish
Be sure to include the fact that you get this error because the included version of Subversion is out-of-date, and anything else that is relevant to why you want Subversion updated.
The more the team hears such requests, the higher the priority they can give to working on it.
For item #2: Essentially the same thing... let our development team know directly that you want support for Git and/or Mercurial. (I know I use Git all the time, and would very much like to see it added to DW.)
And thanks for sharing the info about using DW with SVN 1.7; hopefully it will help others searching for answers.
You guys at Adobe are really screwing us over. On Nov 2, 2011 5:53 PM you replied DarkwingDuck and said you'd alert the team to update that doc that Subversion Client Version 1.7 was incorrect. I just downloaded that doc for the first time today and it STILL has the 1.7 reference.
Also, when I was researching whether to move to CS6 for Dreamweaver one of the things I looked for was the subversion client. DW 5.5 said on the website that 1.7 was supported and in the initial DW6 material it also stated support for 1.7.
So my question is how long can it take for you guys to "correct" information you are providing to developers who are trying to make these decisions? I already upgraded some of my repositories to 1.7 in prep for moving to DW 6. Now that it doesn't work (nevermind the fact that this breaks the workflow I was hopeing to benefit from) I have to back those repositories back down to 1.6.9 if I want to make it work and if I do that I won't be able to use the other tools used by other developers using SmartSVN 7 and the 1.7 client version.
Why can't the DW product be updated to add support for 1.7 and Git and Mercurial? Seems like a natural fit for a "professional" IDE tool that costs significantly more than alternatives like Aptana etc.Please add support for 1.7 at least so that your docs may be correct. Or at a minimum fix your docs. I will submit a request as you describe above but I doubt it will help at all.
I have an idea!
How about instead of changing the documentation, you get the developers to add the support for SVN 1.7 into CS6 as expected by us that purchased the software.
Dreamweaver CS6.1 with Subversion 1.7 support - - Brilliant!
Yes it would be better if they would just add the update. The 1.7 version has been in the documents and content on the website for several years. Hard to believe that Adobe can't add that support quickly. Again, we are not asking for a full client or even additional features (at this point), just add support for 1.7 with existing functionality.
I would also like SVN 1.7 support in CS6
It seems like a no brainer and the marketing and product documentation since back in CS5 have stated it would be there. With 1.7 it allows for greater performance and easier management. It seems like a good idea for Adobe to add it and tout the increased performance and abilities offered from an upgrade to the 1.7 version of Subversion.
After being embarrassed by the fact the DW CS6 does NOT support 1.7 by one of our source-control experts, I found the following reference:
Look on page 8. It says quite clearly under the heading "Still Using Dreamweaver CS5?" the following...
"...Support for Subversion 1.7. Store your files more securely with support for Subversion® software. Manage iterations of your web projects more efficiently"
What happened here?
Unfortunatly that information regarding the 1.7 support has been in documents and on the site at various times since CS5 was introduced. Others have linked to previous press material pages as you have for previous versions. One adobe rep said those docs would be updated but not only have they not, they have also continued to use that information in the CS6 documentation as you point out.
Adobe really should remedy this. They should include the support and allow the develoment community to keep pace with the changes in tech such as they have with HTML5 etc.
Would be great to hear from someone at Adobe with an update or more information on this as we all try to deal with this fragmented workflow since we can't use the 1.7 version in the program and must use another program to facility basic SVN commands.
You're Kidding me right!! cs5 FTP was broken when you were behind proxy and had to wait for cs6 to get that fixed and now I finally have a team together that wants to use SVN and thats busted!! It looks great in all the videos but IT WONT WORK!! has anybody been able to get this to work at all!!!???
Can't someone at Adobe respond to this issue for the DW community? Why can't Adobe respond and either tell us the issue and the time frame it will ACTUALLY be fixed and implemented or just release a patch to enable the 1.7 version and fix any compatabillity issues?
ADOBE PLEASE RESPOND!!!!
Not to divert the attention of the Dreamweaver team to living up to the documentation and releasing an update to fully support SVN 1.7, but now that Adobe has fully consumed PhoneGap, perhaps they could follow their lead and add GIT to the respository options for Dreamwaver as well.
That SVNweaver extension is very old now, and the link on the extension page does not work. The extension can be downladed from https://github.com/ChrisMcKee/svnweaver.
It looks like it's 32bit only. Last update (a readme file) is 9 months old, so I don't think this is developed any further.
I cannot believe this is still an issue.
Two versions and a few updates later, and I am still have the same issue.
This particular problem is all over the forums:
When is the Dreamweaver team going to get the hint?
I don't understand either why even Dreamweaver CS6 only supports SVN 1.6.9. A "professional" product that uses old technology and advertises wrongly. Is there a way to sue Adobe for compensation due to the false advertisement in the US? Maybe that's the only way to make them update either the product or the advertisement.
As I was told SVN client and SVN server can communicate even when the versions differ. We also use 1.7.x on the server side, but I am able to connect from Dreamweaver CS6 to the repository and are also able to commit changes or get newest repository versions. The problem is of course that the file structure between 1.7 and 1.6 has been changed. In 1.6. each folder has a .SVN folder and in 1.7. it is only in the root. So my local folder structure has all the .SVN files due to Dreamweaver only supporting 1.6.9. I have installed Tortoise 1.7.x, so I'm not able to access the repository from Explorer/Tortoise, because the local structure would need to be updated to 1.7, but then I won't be able to work with it from Dreamweaver anymore. I use a private/public key combination to access the repository. It works for me with CS6. I'm also not using a lot of the SVN features. I tried it on another machine running CS5.5 and I had problems. I had no tim to troubleshoot it, yet. I will do it later.
Thank you for letting us know of the error in the document. We are getting it corrected. As Carey correctly put it, Dreamweaver doesn't support Subversion versions later than 1.6.9.
Hi Preran, can you explain us why there is no support for 1.7? Two versions have passed. It is not understandable. Cheers Marcus
it is actually comical that this is still an issue...
lets all ask the development team to fix this, after almost 2 years, looks like they don't care that the product is virtually useless in a "MODERN" team work environment..
For gods sake, SVN version 1.8.0 is out now... Thats 1.1 more, yo!
Dreamweaver is totally awesome with a lot of things but wow, this is a major flaw. Now im stuck in VS2012 doing design work, yeah.
Additionally, to market it to the public as a included feature then 'thank us' for pointing out all the specific materials you published the lie in so you can then change it after everyone purchased it, is very classy... NICE work. there is a name for for those kinds of trade practices, what is that called... hummm i forget.
Wow, two years after the initial complaint, and 2 major revisions of both DW and Subversion, and this is STILL not fixed? I thought DW was the gold-standard of web site development environments. Does the phrase "resting on ones laurels" mean anything to anybody?
It an "Armutszeugnis" how we would say in German. Still nothing happened....
While the document itself has to be corrected, Dreamweaver does not support Subversion 1.7. Github is the way to go moving forward. If you would like to make your feature request heard, click Home
We are also trying to implement a polling widget on the forum for all such requests that don't fall directly in line with the team's current priorities.
I agree. CC2014 still on SVN 1.6.9, tortoise client is on 1.8 so now I cannot use DW SVN at all. It keeps bombing out.
I work on a mac most of the time, and have a windows laptop now I have wasted a week finding this out as we only just started using version control.
With all the money Adobe charges for their suite that they can't upgrade a business critical area of the product that is supposed to enhance the developer workflows rather than hinder it.
Adobe should definately be supporting GIT by now.
while I agree that GitHub might be the "more modern" solution, there are a ton of companies (including mine) still using svn, so instead of implementing a new functionality instead of bringing the existing one up-to-date (as promised by Adobe) won't make you any friends with people who have purchased a license expecting it to work as promised. I've only ever updated Dreamweaver from CS4 to get proper SVN functionality, now I'm blocked by Adobe being to lazy to update it...
From what I understand, we do not have SVN support in our immediate list of priorities. For me to make a case to the product team, I suggest that you Create An Idea and canvass for votes.
In the Overview page, under Feature Ideas, click Show All. In the page that appears, use Create an Idea.
I have a process with the product team wherein I share the Top Ideas of the month in my report. This will help provide visibility for the most popular ideas and thereby prioritize their importance in the feature list.