when outputting a field as a link and specifying the [tid]; if the [tid] is greater than 1000 the output includes a comma which then translates to a "%2C" in the URL. For example, my output link is: cities/[tid]. When I hover over a link with a tid of 1962, I see ".../reviews/1,962". when I click the link, the URL reads: ".../reviews/1%2C962".

screenshots attached.

CommentFileSizeAuthor
#11 views-export.txt5.22 KBbdsl
p2.png6.91 KBtrapper-1
p1.png67.85 KBtrapper-1

Comments

bojanz’s picture

bojanz commented
Status: Needs work » Active

There's no patch in here (hence the "needs work" status is wrong).

trapper-1’s picture

trapper-1 commented

go to: EDIT(XXXXX) to see in live environment. click a state and then remove the "%2C" from the URL to get to the intended page.

EDIT: site updated and now functioning using the taxonomy menu module, issue remains with views module.

dawehner’s picture

dawehner
Primary language German
commented
Status: Active » Postponed (maintainer needs more info)

It would help here, too to have an export to know which kind of field you use here.

Once we know the field it's possible to fix this this bug much easier.

trapper-1’s picture

trapper-1 commented
Status: Postponed (maintainer needs more info) » Active

the field is of type 'term'. I have a list of parent terms in a block view. When a term is clicked I parse the [tid] of the term as an argument, and I display another term block which shows the children terms for the selected parent term. When a child term is clicked, the [tid] is parsed as an argument to a page view which displays items that are tagged with that term. The items are a custom content type with a CCK field defined type of 'term'. When the [tid] value is greater than 1000, a comma is inserted (ie, "1,000"). This is a major issue because the view reads the parsed arguments as a comma-separated list.

I have reworked my site to get the functionality I want, using the taxonomy menu module, but this is still an issue for others who may have be parsing a [tid] with a value greater than 1000.

dawehner’s picture

dawehner
Primary language German
commented
Status: Active » Postponed (maintainer needs more info)

So you use fieldapi fields? Probably but as always ... an export would give clear informations about this. Anyway. Please provide an export.

One information which would be part of the export is: which formatter did you used.

Views only uses the core methods to render a field.

So again please provide an export

trapper-1’s picture

trapper-1 commented
Status: Postponed (maintainer needs more info) » Active

I will provide export this evening.

So you use fieldapi fields?

Yes I use apifields, but they don't have anything to do with this issue. The view is a term view, not a node view.

my views parse the [tid] from the term table. it is a parent-child term relationship, so when you click the parent term in the view block, the parent [tid] is parsed and the child terms are displayed in a new block with an argument on [tid] from the term table. i repeat, the [tid] is parsed from the term table and the argument is placed on the [tid] in the term table, NOT the node table.

dawehner’s picture

dawehner
Primary language German
commented
Status: Active » Postponed (maintainer needs more info)

As long you didn't provide an export you didn't provided an export. It's really critical to understand what you did. We just all want to fix this issue ....
Additional the evening is over for me :)

esmerel’s picture

esmerel commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)
twiik’s picture

twiik commented
Status: Closed (cannot reproduce) » Closed (duplicate)

Encountered this myself and it took me a while to realize it's the "Thousands separator" that defaults to a comma even when you're dealing with tids, nids or uids.

Pretty sure this issue is related to the same thing.

Here's an open issue which explains the "problem": http://drupal.org/node/1144896

esculcar’s picture

esculcar commented

in other case Whith ","

../taxonomy/term/8,9#overlay=node/7/edit%3Fdestination%3Dtaxonomy/term/8C9

should be
../taxonomy/term/8,9#overlay=node/7/edit%3Fdestination%3Dtaxonomy/term/8%2C9

thanks

bdsl’s picture

bdsl commented
StatusFileSize
new views-export.txt5.22 KB

Here's an export of a view with this issue.

Line 53 is:
'path' => 'blog/[tid]',

The path gets presented with a comma as a thousands separator, failing to make a working link to another view that takes a tid as an argument.

bdsl’s picture

bdsl commented

As a workaround its possible to do something like the following in a template (e.g. I used
views-view--BlogEvents--block.tpl.php), to delete the comma but of course this is very much not an ideal solution:

print preg_replace('|(/blog/[0-9]+)%2C|','$1',$rows);

This sort of thing should keep working as long as the term ID doesn't go over one million.

strick’s picture

strick commented

I had this problem, but it was just a matter of changing the "ID" fields thousand separator to nothing...