You are not logged in Log in Join
You are here: Home » Members » ike » how to use Dreamweaver with Zope over DAV » Dreamweaver-Zope-notes » LittleIssues

Log in
Name

Password

 
 
FrontPage »

LittleIssues

**This is the page to collect notes on little issues.**

Please feel free to post issues as comments below:


ike (Jan 20, 2003 1:36 am; Comment #1)
Sometimes DW has issues when putting files, no matter what. It gives an error file not found, and won't put the files. Anybody have any ideas on why?

note- using Zope2.6 (with date-time patch) and Dreamweaver MX on MACOSX.

Anonymous User (Feb 16, 2003 2:08 pm; Comment #2)
In MM Dreamweaver 6.1, checking the check out files when opening checkbox in the Remote Info portion of your site definition when using DAV will enable the upload and download functions to operate normally as expected. The check-in and check-out functions also work as expected. This appears to be a bug fix by MM with the 6.1 update, whereas the 6.0 release didn't work well no matter what setting was selected.

Jeffery Mau

Anonymous User (Feb 16, 2003 4:24 pm; Comment #3)
Okay, I take my comment back. The checkbox does not help check-in issues. Until MM fixes their DAV support, you will still need to check files in for them to remain unlocked on the server. Its backwards!

Jeffery

Anonymous User (Jun 10, 2003 7:49 am; Comment #4)
Another issue:

Dreamweaver MX by default "cleans out" the code causing an error at runtime

it changes it from to (the / at the end disappeared)

That's because he does not recognize the tag So you need to go into (edit/tag libraries), add a new tag library called "TAL", and add new tags "metal:block" and "tal:block".

Also, for the file extension that DW does not recognize, there seems to be a way (i have not tested it) to change the webdav python script in zope so that the transaltion is done automatically. See http://mail.python.org/pipermail/zope-cmf/2003-April/018133.html

Regards, Nicolas.

Anonymous User (Jun 10, 2003 7:51 am; Comment #5)
it changes it from

it changes it from < tal:block tal:define="dummy python:request.set(disable_border,1)" /> to < tal:block tal:define="dummy python:request.set(disable_border,1)" > (the / at the end disappeared)