I noticed this module does not work well together with the module views_customfield. I have tried to add the token value [phpcode] to the row class attributes (at style options), but then the row class just becomes [phpcode] instead of the value of the field.

I have taken a look at the code and noticed when semanticviews_get_token_replacements() got called, $row does not contain the value result of the field phpcode. So I'm not sure whether this is a Semantic Views issue or a Views Custom Field issue, but I think this is a Semantic Views issue.

Comments

milos.kroulik’s picture

milos.kroulik commented

+1

TimG1’s picture

TimG1 commented

+1 subscribing.

ahallez’s picture

ahallez commented

+1 subscribing

sarhugo’s picture

sarhugo commented

+1 subscribing

Anonymous’s picture

Anonymous (not verified) commented

I am happy to review a patch, but I will not be making one myself. I don't use PHP custom fields. Anytime I need to do something like this, I implement a field theme function or write a views hook (like pre_render).

Do PHP custom fields work as tokens in other field output? For instance, when you rewrite the output of a later field, can you use the token output of the PHP custom field?

nicholasthompson’s picture

nicholasthompson
Primary language English
commented

I have been trying to get the tokens working and, although I also could not get [phpcode] working, I have noticed that it seems to be "excluded" fields don't get replaced.

Apparently, if a field is excluded from output we cannot use it's token as a replacement in a Semantic View style (eg, for a row)...

oferrero’s picture

oferrero commented

+1 ... Would be nice to have this functionality.

Scyther’s picture

Scyther commented
Category: Bug report » Feature request
Issue summary: View changes
Status: Active » Closed (outdated)