[RESOLVED] TV : really odd @EVAL result

Quote from: heliotrope at Sep 08, 2006, 10:32 AM

I must be an unlucky guy

Did your render the tv value in the Doc content in the front ??
In my case the @Eval is used to create options for a multiple select TV.

Anyway, if the getDocumentIdentifier function disappear I could get the id with $_REQUEST[’id’]
I don’t know why I haven’t thought earlier to check if ’doc’ was set to know where I was (backend or front end).

:-)

Front-end; this stuff doesn’t apply to the manager.

And REQUEST[’id’] will only reflect the proper ID if you are not using the friendly_alias_urls option; otherwise, it’s gonna be empty. I think the problem is trying to use an @EVAL in your default value for the multiple select TV. I don’t think that works, but I could be wrong...can you post a screenshot of the entire TV configuration view so I can see exactly what you are doing?

Here is the first one:
when select the second value is feed according its value




And the second One:



The snippet code called with @EVAL is post above.


The result in front end:
the first TV :



According the first TV choice here is the second One:



If I’m changing the value of the first one:



The second one is changing and reflects my choice for the first TV




About request[’id’], I guess even if friendly urls are on, that shouldn’t be a matter because the requested value only concers the back office where friendly urls are off.


Once again thx for your help.

:-)

Now I’m lost. What does this @EVAL have to do with the backoffice? The documentIdentifier and documentObject do not apply to the back office, so of course there would never be a value. Perhaps if you explained what you were trying to do in general, it might help the discussion...?