Obsolete portal events

[Jean-Baptiste Quenot <jb...@anyware-tech.com>]

Hello,

Before updating Cocoon 2.1 today, all forms were correctly working
when posting  to action="", ie  the current request  URL including
references to portal events used for producing the form.

After posting the form, the URL looks like this:

http://vision/portal/portal?cocoon-portal-event=0

Now, I  have to set action="portal"  to get rid of  every obsolete
event parameter otherwise when posting the form a random layout is
used for my coplet.  I get a random page, the form pipeline is not
called.

After posting the form, the URL now looks like this:

http://vision/portal/portal

However,  we have  about 400  forms and  multiple branches  in our
application so modifying all of them seems overkill.

Any input will be appreciated,
-- 
Jean-Baptiste Quenot
Systèmes d'Information
ANYWARE TECHNOLOGIES
Tel : +33 (0)5 61 00 52 90
Fax : +33 (0)5 61 00 51 46
http://www.anyware-tech.com/

Re: [portal] Disable action counter by default

[Carsten Ziegeler <cz...@apache.org>]

Jean-Baptiste Quenot wrote:
> An update on this annoying problem:
> 
> Before updating I had URLs like:
> 
> /portal/portal?cocoon-portal-action=7&cocoon-portal-event=0&cocoon-portal-event=1
> 
> With a fresh Cocoon 2.1 I have:
> 
> /portal/portal?cocoon-portal-event=0&cocoon-portal-event=1
> 
> Request parameter « cocoon-portal-action »  has disappeared, which
> causes URLs to be identical at every request, whereas we based our
> application on the very fact that the URL was always different.
> 
> After digging into the bowels of  the beast, we found out that the
> « action  counter aspect »  has been  removed from  default portal
> configuration without notice by revision 232222.
> 
> Oooch!  It hurts!  Seriously, can we imagine to be informed of
> such critical changes?  Or am I missing something?
> 
Yes, you're missing the fact, that this is just a portal sample! You're
own application should not rely on the configuration of a sample. Use
the block for your own development as if there is no sample at all.
There are so many different things turned on in the sample which you
rarely need all in your own application, so it's absolutely recommended
to have an own configuration.

Carsten
-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/

Re: [portal] Disable action counter by default

[Jean-Baptiste Quenot <jb...@anyware-tech.com>]

An update on this annoying problem:

Before updating I had URLs like:

/portal/portal?cocoon-portal-action=7&cocoon-portal-event=0&cocoon-portal-event=1

With a fresh Cocoon 2.1 I have:

/portal/portal?cocoon-portal-event=0&cocoon-portal-event=1

Request parameter « cocoon-portal-action »  has disappeared, which
causes URLs to be identical at every request, whereas we based our
application on the very fact that the URL was always different.

After digging into the bowels of  the beast, we found out that the
« action  counter aspect »  has been  removed from  default portal
configuration without notice by revision 232222.

Oooch!  It hurts!  Seriously, can we imagine to be informed of
such critical changes?  Or am I missing something?

Thanks in advance,
-- 
Jean-Baptiste Quenot
Systèmes d'Information
ANYWARE TECHNOLOGIES
Tel : +33 (0)5 61 00 52 90
Fax : +33 (0)5 61 00 51 46
http://www.anyware-tech.com/