Hi There;
We are constructing a Nav bar that includes a link to "Members". Ideally
once a member logs in this label would change to their given name (as per
Amazon).
We are thinking about tackling this in one of the 2 ways described below. It
seems to us this might be a useful feature so we have
On Thursday 14 July 2005 11:27 am, yuppie wrote:
> Hi Alec!
>
> Alec Mitchell wrote:
> > I recently noticed that the recent addition of default type profiles to
> > CMFDefault (e.g. CMFDefault/profiles/default/types/Topic.xml), has the
> > very unwelcome side-effect of adding extra unwanted actions
Hi Alec!
Alec Mitchell wrote:
I recently noticed that the recent addition of default type profiles to
CMFDefault (e.g. CMFDefault/profiles/default/types/Topic.xml), has the very
unwelcome side-effect of adding extra unwanted actions to the ATCT types in
plone 2.1. Perhaps these customization
Hello all,
I recently noticed that the recent addition of default type profiles to
CMFDefault (e.g. CMFDefault/profiles/default/types/Topic.xml), has the very
unwelcome side-effect of adding extra unwanted actions to the ATCT types in
plone 2.1. Perhaps these customizations should check the me
On 14 Jul 2005, at 17:33, yuppie wrote:
I don't think we should try to maintain code compatibility on HEAD.
All we should promise is that imports of old profiles work and that
we don't break the persistent SetupTool.
I suppose right now we're all a little bit in the air about what CVS
HEA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Piotr Kopszak wrote:
> Can you recommend any Silva related discussion list which is open to anyone? I
> tried to subscribe to the main one but haven't heard from them. Also would be
> grateful for any hints about Silva related resources (apart from do
Hi!
CMFSetup is fast changing code and maintaining full backwards
compatibility is a pain, slowing down development.
I don't think we should try to maintain code compatibility on HEAD. All
we should promise is that imports of old profiles work and that we don't
break the persistent SetupToo
On 14 Jul 2005, at 11:53, yuppie wrote:
So I propose a different approach:
- move the 'Configured CMF Site' factory to CMFDefault (it is
anyway CMFDefault specific because it uses a hardcoded CMFDefault
CMFSite)
- make 'CMF Site' behave like CMF 1.5's 'Configured CMF Site'
If there are
Hi!
CMF 1.5 registers 2 Site factories:
- CMFDefault the old and deprecated factory for meta type 'CMF Site'
- CMFSetup the new factory for meta type 'Configured CMF Site'
On CMF HEAD the old factory should no longer be used TTW, but
manage_addCMFSite should still be available for backwards
The following supporters have open issues assigned to them in this collector
(http://www.zope.org/Collectors/CMF).
Assigned and Open
efge
- "CMFSetup: provide non-ascii im- and exports",
[Accepted] http://www.zope.org/Collectors/CMF/292
- "CMFSetup doesn't correctly detect DCWo
Jens Vagelpohl wrote:
On Apr 13, 2005, at 18:45, sureshvv wrote:
Is there a reason for this? Would you be interested in a patch?
It does. Look at CMF CVS HEAD.
I looked at the code in DirectoryView.py and it appears that the setting of
properties will work only for sub-directories but no
11 matches
Mail list logo
