I did an update to a site I have in development right now from 2.7 to 2.8 and found out it broke one of the views. Basically I have a couple of fields that need to be rewritten into one field. Specifically, Node:title, Content: Author, Taxonomy: All Terms, and another Taxonomy: All terms. They are being rewritten like so.

<div class="article-info">[title]
<div class="author-taxonomy">By: <em>[field_article_author_uid]</em> in: <em>[tid]</em></div>
<div class="topics">Topics: <em>[tid_1]</em></div>
</div>

The first taxonomy does not create any problems because it is only showing which category the article is in, but the second has multiple topics (tags) that the article has listed. With 2.7 it would list the terms with commas as expected, but with the upgrade to 2.8 this entire field including all of the code above is outputted for each term with a comma in between.

Example of what it looks like in 2.8 (the outputted code):

<div class="article-info">[title]
<div class="author-taxonomy">By: <em>[field_article_author_uid]</em> in: <em>[tid]</em></div>
<div class="topics">Topics: <em>[tid_1]</em></div>
</div>
,
<div class="article-info">[title]
<div class="author-taxonomy">By: <em>[field_article_author_uid]</em> in: <em>[tid]</em></div>
<div class="topics">Topics: <em>[tid_1]</em></div>
</div>
,
<div class="article-info">[title]
<div class="author-taxonomy">By: <em>[field_article_author_uid]</em> in: <em>[tid]</em></div>
<div class="topics">Topics: <em>[tid_1]</em></div>
</div>
...

It should only write all of the content once and then replace [tid_1] with the comma separated list of terms. Any more information can be provided.

CommentFileSizeAuthor
my view.txt6.9 KBjdwfly

Comments

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Closed (works as designed)

This was actually an improvement designed to allow people to rewrite the individual terms. In order to accomplish what you were previously doing, you will need to create a new field (There is a Global: Custom Text field), set your taxonomy field to exclude, and put the rewrite you have in the custom text.

jdwfly’s picture

jdwfly commented
Status: Closed (works as designed) » Active

Does this work the same for all fields or just this one field?

I already knew I could do that with a Custom Text field, but I wanted to make sure there wasn't some type of weird bug introduced by 2.8.

dawehner’s picture

dawehner
Primary language German
commented
Status: Active » Closed (works as designed)

Just what earl says this is by design

gillesv’s picture

gillesv commented

I'm facing the same problem.

On one hand, it's nice that you can rewrite each individual term, BUT on the other hand, it's annoying when you want to wrap it all in one tag.

You mention Custom Text Field; but there's a problem with that one:
Unlike the field itself, the custom textfield does not know if the targeted field/token is empty or not. So if I want to display all terms inside a container, but only if the there are terms available, I have a problem. The container element will always be displayed, whether there are terms to display inside or not.

Is there an easy solution for this?

merlinofchaos’s picture

merlinofchaos commented
Status: Closed (works as designed) » Active

We probably need multiple fields to provide a prefix/suffix field so you can wrap the rewrite.

gillesv’s picture

gillesv commented

Thanks for picking this up, Merlin.
(I'm using Views 3 on Drupal 7, btw.)

mustanggb’s picture

mustanggb commented
Status: Active » Closed (won't fix)