Am 09.04.2010, 13:38 Uhr, schrieb Jens Vagelpohl j...@dataflake.org:
Needless to say, this is more useful when using a CookieCrumbler as a
standalone object without a portal. The CMF does not need this, and I
would even say it only adds confusion and should be removed.
I'm ready to commit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/14/10 15:43 , Charlie Clark wrote:
Am 09.04.2010, 13:38 Uhr, schrieb Jens Vagelpohl j...@dataflake.org:
Needless to say, this is more useful when using a CookieCrumbler as a
standalone object without a portal. The CMF does not need this, and
Hi!
Charlie Clark wrote:
Am 07.04.2010, 14:27 Uhr, schrieb yuppiey.2...@wcm-solutions.de:
Maybe I should add them to CMFDefault? I guess they need just a few
changes to be ready for checkin.
Sounds great. As Tres has noted with ursine_globals - Views can have their
own tests. Oops, more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/9/10 13:29 , Charlie Clark wrote:
Any idea why CookieCrumbler is a Folder?
They can contain objects that can be used as login/logout pages, such as
DTML methods or Page Templates.
Needless to say, this is more useful when using a
Am 09.04.2010, 13:38 Uhr, schrieb Jens Vagelpohl j...@dataflake.org:
They can contain objects that can be used as login/logout pages, such as
DTML methods or Page Templates.
Ah, that's how exUserFolder works.
Needless to say, this is more useful when using a CookieCrumbler as a
standalone
Hi,
I'm currently working on a project which will hopefully have no TTW code
so I was hoping to be do without skins - currently I have a my skin on top
of CMFDefault but it is just main_template and some CSS. If I drop the CMF
skins entirely I hit some problems as quite a few forms exist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/7/10 13:09 , Charlie Clark wrote:
Hi,
I'm currently working on a project which will hopefully have no TTW code
so I was hoping to be do without skins - currently I have a my skin on top
of CMFDefault but it is just main_template and
Am 07.04.2010, 13:47 Uhr, schrieb Jens Vagelpohl j...@dataflake.org:
I think I would change the cookie crumbler to expect both: Either a page
with an ID that the cookie crumbler can traverse to (which is what it
does right now), or an ID for a view that you could traverse to using
the @@
Hi!
Charlie Clark wrote:
I'm currently working on a project which will hopefully have no TTW code
so I was hoping to be do without skins - currently I have a my skin on top
of CMFDefault but it is just main_template and some CSS. If I drop the CMF
skins entirely I hit some problems as quite
Am 07.04.2010, 14:27 Uhr, schrieb yuppie y.2...@wcm-solutions.de:
I have a LoginFormView and a MailPasswordFormView in my private
repository. They allow to insert the email address instead of the member
id. The views look up the first user that matches the email address.
No changes required
Hi!
Charlie Clark wrote:
Am 07.04.2010, 14:27 Uhr, schrieb yuppiey.2...@wcm-solutions.de:
I have a LoginFormView and a MailPasswordFormView in my private
repository. They allow to insert the email address instead of the member
id. The views look up the first user that matches the email
11 matches
Mail list logo
