Home
TeamSite
Possible to use Synchronize feature of Dreamweaver
System
Hi,
My work has just started using TeamSite for our Intranet websites.
I maintain a fairly large site, where I daily need to create/modify/delete files from the site. Many of these pages have hyperlinks to other pages within the site, so when I make changes I need to update all the hyperlinks too. I have the entire site off-line, so I can use dreamweaver to verify all the hyperlinks in the site, and update them as needed. So a deletion of a page, can cause hyperlinks of many pages within the site to change.
Before we started using TeamSite I was able to use Dreamweavers 'synchronize' function, and it would go out and only upload the pages that had changes to the webserver.
But now that we have TeamSite, the only way I have been able to match my off-line site to the server is too delete all the directories off my workspace. Then re-import each one. To ensure that all the changes (modification and deletions) are reflected in TeamSite. The problem with this is, it takes so much more time to do this, when before I could have all my changes uploaded to the webserver within a minute. Another nice thing about the synchronize feature was I could 'cloak' certain directories or files of certain types from being uploaded to the server. For example, I could prevent my original image files from being uploaded (.psd, .fla).
So my question, is there any way to use the synchronize function built into Dreamweaver and connect to TeamSite?
I really hope this is possible,
Thanks in advance
Find more posts tagged with
Comments
Migrateduser
I admit I'm not that familiar with Dreamweaver, but I have a few questions:
1. Is there an FTP server listening on your TeamSite box?
2. Are you utilizing TeamSite's extended attributes feature? It sounds as though you're not, since you routinely upload everything fresh.
3. Please describe your architecture a bit more and why you're even using TeamSite. It sounds as though you're basically using DW for everything and using TS as a go-between.
Regards
Dave
Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 6.1 SP2 on Win2K
Migrateduser
I think for others in the company, Team Site might be a good tool. Those who have a smaller site, or a site they don't update very often.
Yes, I am using Dreamweaver for everything. This was sort of thrown at me a couple months ago, and I didn't have much choice to use it or not. Our Unix Intranet webserver is suppose to be taken offline in the next few months, so I've been trying desperately to find a way to get this to work before it's turned off.
I really don't know much about Team Site, I went to the 'about' tab and looks like we are using version 6.1.0 Service Pack 1
How can I find out if I have extended attributes feature?
I believe that FTP is possible, because if I setup my FTP program and just type in the IP address of the TeamSite server. I can connect to my 'home' directory on the server and even move files back and forth.
The problem I'm running into is, I can't find my workspace directory anywhere on the server. In TeamSite, it says the directory to my workspace would be //uslcweb03/xxxxxxx/xxxx/etc
Yet, with my ftp program, I can't find any directory with this name?
It doesn't make any sense.
any ideas?
thanks again for your help.
Migrateduser
I wasn't clear with one of my questions, but you answered it for me. I was asking if you were using extended attributes for anything -- this is a native feature to TS and these attributes can be lost if you FTP files in to replace the older ones. The fact that you're just using TS only as a repository actually lends a lot of flexibility to this situation.
The path to your workspace can be very ugly, but once you're familiar with the navigation to it, you really shouldn't have to think about it anymore. It SOUNDS like your TS box is running on Unix... in this case, the path to your workspace directory should start with something like /.iwmnt/default/main -- try that first. If the TS box is running on Windows, your workspace directory will be mounted on a virtual file system (as with Unix), but will most likely be mounted on the Y drive. In that case, your path would start with Y:\default\main.
I'm hoping that at least allows your FTP program to "see" your TS space.
Let me know what happens,
Dave
Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 6.1 SP2 on Win2K
Migrateduser
THAT'S IT :-)
Thank You!!!
I just tried it, and it worked great!
Thanks again!!
Adam Stoller
You should probably invest in some training - at least web-based stuff to get a sense of what TeamSite is about, terminology, basic architecture etc. before you go about trying to maintain it.
For instance //uslcweb03/xxxxxxx/xxxx/etc - is a fully-qualified virtual path (vpath) in which the first element of the path is the name of your TeamSite server (uslcweb03), the second path element is the name of the 'store' or 'archive' (usually "default") the next path element will, I believe, always be "main" and after that is where your site-specific branch names, workarea names, directories and files will appear.
On Unix - there is usually a symlink of /default that points to /iwmnt/default, and there is another path like /.iwmnt/default. The /iwmnt is a cached mount-point for the contents in the backing store. The /.iwmnt is a non-cached mount-point for the backing store. Most of the time you should be referencing files through the cached mount-point /iwmnt; more often than not you'll be referencing things through the symlink /default.
There's a whole bunch more that you probably would find useful to know/learn and while you can pick up some of it from reading the manuals - I'd still recommend taking one or more web-based training classes from IWOV to get yourself "grounded" in the basics of TeamSite.
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com