Since updating to Views 2.9, my custom field markup output now displays the word "[markup]". I am rewriting the output as:

[image_image] <span class="client_center_icon_text">[field_display_text_value]</span>

I'm also outputting the field as a link and using a link class. The word [markup] is displaying after the image and before the display text. You can see the problem at http://205.186.128.246/client-center/products.

I have attached an export of the view.

CommentFileSizeAuthor
#3 customfield.txt21.35 KBLloyd
customfield.txt27.55 KBLloyd

Comments

Lloyd’s picture

Lloyd commented
Title: Custom Field not displays [markup] in the output » Custom Field displays [markup] in the output
merlinofchaos’s picture

merlinofchaos commented

You seem to have a WYSIWYG editor on the views export that has corrupted the output. Can you disable that prior to cut & paste? (Most of them have a way to get to the text behind the wysiwyg).

Lloyd’s picture

Lloyd commented
StatusFileSize
new customfield.txt21.35 KB

Sorry about that. Fixed.

merlinofchaos’s picture

merlinofchaos commented

Ok, looking at this, I think views_customfield is taking advantage of what was actually a bug in Views.

You can work around this for now by selecting "Rewrite the output of this field" on the field, and copying your 'value' into the "Text" area that it reveals.

Lloyd’s picture

Lloyd commented

I believe that's how it is now. For the customfield Markup field, I am rewriting the output as a field using:

[image_image] <span class="client_center_icon_text">[field_display_text_value]</span>

which is placed into the Text field.

I removed everything in that field other than [image_image] and it displays the image correctly but still displays "[markup]".

jpp’s picture

jpp commented

I've got the same issue - depending on the view is [title] or [tid] in the output. In my case it seemed that the output rewrite was being triggered even when the rewrite box wasn't checked. Enabling rewrite, clearing the contents, then disabling it again fixed it.

dawehner’s picture

dawehner
Primary language German
commented
Status: Active » Fixed

When you want to use a token in fieldA from another fieldB you have to define this fieldB before your fieldA.

That's not the case, see the export.

If this problem is still there please goto the customfield issue queue :) They might have a bug here.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.