DPM cache duplication and FURL format issue

Response from Vignette about issues with DPM cache duplication and FURL format issue:

G’day,
Sorry that it has taken a little time to get back to you on these issues. I wanted to make to confirm my answers with the right ginger beers before replying

We have fixed the issue below in the productized version of furl.

You asked about 2 other things

1. The issue of duplicating the cache per-pre-loaded site. This behaviours remains the same

2. Support for Formats in only 1 of the two mappers. This behaviour is also the same , although we fixed a general problem with query parameters being stripped urls. So if you pass in a format as a query param we will honour it, you could use that as a workaround


The original query:

I wanted to ask for some input on a FURL issue that I am having concerning
formats.
The issue comes up when 2 templates share a common component on a channel
(for example: I have an image query component
on each presentation template) then it will use the default presentation
template's value instead of the format's.

Example:
I have a Channel named "Home Entertainment", that has 2 formats:
- default (Product Page)
- Support (Support Page)

both of these templates have a common image query component with different
values:
- default: Get Image From Channel [currentChannel]
- Support: Get Image From Channel Home > Support

when I use the following URL it displays the correct Layout but uses the
query
component value from the default template (Shows the image from
currentChannel
instead of Support).

/PUSA/Products/ch.Home+Entertainment.Support

however if I add the vgnextfmt variable to the URL it uses the correct
components.

/PUSA/Products/ch.Home+Entertainment.Support?vgnextfmt=Support

is this a known issue? is there a quick fix that you are aware of?

Let me know if you need more information on this.

Portal Form populate

Form populate in Portal's EndUserFormBean cannot handle any data type other than String, so cannot int, long etc.

Portalbean portlets get vs post

Portalbean portlets do not work with "GET" request on submitting to a process view. You get an error saying "java.lang.IllegalStateException: The URI of a single portlet request must either contain one and only one portlet UID or a target portlet UID.".

DPM cluster.nodes

Found this out as a result of ticket 201930. cluster.nodes needs to contain paths to each context defined for any web app thats based off vgn-ext-templating. So piocda, furl etc. need to be in there apart from vgn-ext-templating of course.