[Zope] ZopeLDAP 1.1.0 release

2000-12-18 Thread Jeffrey P Shell

"ZopeLDAP 1.1.0", http://www.zope.org/Members/jshell/ZopeLDAP/ is released,
bringing in a bevy of changes, including:

 o New ability to run in a non-transactional mode (this is critical to avoid
   a known bug when updating more than one entry object per transaction)

 o Much improved Entry object API that is Python Scripting\DTML Scripting
   friendly

 o Some new documentation (not yet in help system format though) about
   programming Entry objects.

The *manage_* style of programming Entry objects has not changed, but the
core API has.  Anything using methods like '_set()', '_addSubentry()' will
be affected.


___
Zope maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope-dev )




[Zope] re: requests for some dtml tags

2000-11-14 Thread Jeffrey P Shell

> From: jacintha menezes  <[EMAIL PROTECTED]>
> 
> Hi,
>  Is there any dtml tags for creating a new work space also for locking
> some page.Locking some page in the sense for second user the operations in
> that page should not be processed
> unless the process for first user is completed.If there dtml tags for these
> kindly give me
> those tags.
> 
> waiting for your reply.

Regarding locking:

Do you mean in the sense that if person A wants to edit a page (like a Wiki
page), person B shouldn't be able to update the page until person A clicks
"Submit changes"?  The WriteLocking project (see the Projects area on
http://dev.zope.org/) will include an API that can be called, even from DTML
(with proper permissions), to grant an exclusive write lock to a user.

If you mean you want to protect against two HTTP requests that are operating
on the same page\object from overwriting each other in process, the built in
ZODB\ZPublisher transaction handling that's been in Zope before there was
Zope takes care of this automatically.  A REQUEST->RESPONSE cycle is treated
as a single transaction.

Jeffrey P Shell, [EMAIL PROTECTED]
http://www.digicool.com/ | http://www.zope.org



___
Zope maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope-dev )




[Zope] re: uploading to Zope with Mac Browser

2000-11-07 Thread Jeffrey P Shell

> Zope list: 
> 
> This zope method for uploading images to server:
> 
>  expr="manage_addImage( id=title, file=file, title=title)">
> 
> ...works great from a PC. But from a Mac (netscape And IE) it does not work.
> 

Netscape doesn't work?  That's odd.  IE had some problems before 5.0, some
of which could be fixed in the Internet control panel (in recent Mac OS
versions) or in Internet Config (I'm not sure how deeply Netscape uses
these).

Since the Mac OS has the benefit\curse of the forked file system, almost any
file on the system has extra data about it stuffed in the Resource Fork (ie
- information about which app to designate as 'creator', allowing you to
have JPEGs that open in different applications for example).  Most of the
universe operates on a single forked system, which contains just the data.
So there are sometimes problems sharing Mac files with the rest of the
world.  Usually it works fine as only the Data fork is used, but some
programs tend to botch the handling of this.  IE was one of them.

The settings to try to fix this are usually found in the preferences that
handle File Mappings (or File Helpers) (which lets the OS know how to deal
with incoming data).  It's a preference panel in both browsers, and can be
found on the Advanced tab of the Internet control panel.  Find the mapping
for .gif and other extensions or mime types you're interested in and look at
the settings for handling it.  There should be an option for how to treat
the data, with at least the two options of "Text" and "Binary".  There
should also be an option to specify whether it's Macintosh data.  **Turn
this option off**.  Make sure that the "Map Outgoing" option is checked if
it's available.  If the browser is working properly, it should only send the
data fork at that point.

This is broken in MacIE 4.x for images and text, but works for other file
types (like mp3).  I've had no problems with IE 5 that weren't fixable by
checking on my settings.  For file uploads, Netscape has never been a
problem for me since the file upload option showed up (1.x?).  But again, I
practically never use Navigator anymore.  This was the critical issue
keeping me away from MacIE, and MS finally fixed it in 5.

Jeffrey P Shell, [EMAIL PROTECTED]
http://www.digicool.com/ | http://www.zope.org



___
Zope maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope-dev )