Thanks for your work on this module. Exactly what I need....
Using the version from 2011-Dec-26, I get the following error when I try to use mypath/[term:name] as a path pattern for a vocabulary:
Undefined property: stdClass::$name in taxonomy_tokens() (line 105 of /www/mysite/modules/taxonomy/taxonomy.tokens.inc)
I'm using Views 3 to generate a list of top-level taxonomy terms in a block. This error is returned for each term output by the view.
It does not generate an error if If I use mypath/[term:tid] instead.
(Running a dev version of Drupal 7.11 from 2011-Dec-30. Have not tried it on Drupal 7.10 or earlier)
Comment | File | Size | Author |
---|---|---|---|
#16 | views_taxonomy_entity_uri-1388684-15.patch | 1.07 KB | derhasi |
Comments
Comment #1
derhasi CreditAttribution: derhasi commentedmillionleaves, I checked the path on my test installation. There everything goes fine.
This must be an error on a module calling the entity_uri() function, e.g. if the module does not load the whole taxonomy term object. Maybe you could find out, what module produces this error by looking on what page this occurs, or looking at the modules you use.
If you have any more information, maybe I could help you. But with the information above this is clearly no entity path problem ;)
Comment #2
millionleaves CreditAttribution: millionleaves commentedThanks. I think the error is arising in the Taxonomy module. The reason I updated to a dev version of 7.11 is that it includes a fix for a Taxonomy issue I was having; I'll wait until 7.11 is released and see if this issue is still occurring.
Comment #3
ykyuen CreditAttribution: ykyuen commentedHi millionleaves,
i got exactly the same problem. i update the entity path of a taxonomy to service?field_service_tag_tid=[term:name]
it works for node view but not for taxonomy view.
Notice: Undefined property: stdClass::$name in taxonomy_tokens() (line 105 of /var/www/d7/modules/taxonomy/taxonomy.tokens.inc).
is this fixed in 7.11-dev?
Comment #4
Julesmarie CreditAttribution: Julesmarie commentedI'm also getting this error when trying to use path/[term:name]. I'm using Drupal 7.11 and and Entity Path 7.x-1.x-dev
Comment #5
derhasi CreditAttribution: derhasi commentedykyuen and Julesmarie, could you list the modules you have activated? Or best, try if the error goes away if ou deactivate other modules.
Comment #6
ykyuen CreditAttribution: ykyuen commentedSorry for the late reply. I try to repeat the problem in a fresh new installed drupal. here is the configuration detail.
Drupal 7.12
Enabled modules
Disabled module
View setting
I create some terms in the default tags and add the following view which accept the term name as input parameter.
Entity path setting
Error
When i access the view with term name input say tags/apple, the following error is shown
I try disabled the modules Administration menu and Administration views but still get the same error.
Hope the above information is useful for you. =)
Comment #7
iajay CreditAttribution: iajay commentedsubscribe
Comment #8
derhasi CreditAttribution: derhasi commented@ykyuen, sorry for the late response. Is the "name" token listed in the replacement patterns?
If not - I guess- you must enable the EntityAPI.
@iajay, it was great you could provide some additional information instead of just "subscribe".
Comment #9
iajay CreditAttribution: iajay commentedI have opened another issue because I thought my problem was little different
http://drupal.org/node/1498560
Comment #10
ykyuen CreditAttribution: ykyuen commented@derhasi
i could find the [term:name] in the replacement patterns and i did have the entity api module enabled. the version is 7.x-1.0-rc1. sorry that i missed this information in the previous comments.
Kit
Comment #11
ascii122 CreditAttribution: ascii122 commentedI had the same problem with term:name
Notice: Undefined property: stdClass::$name in taxonomy_tokens() (line 105 of /site/modules/taxonomy/taxonomy.tokens.inc).
Since my view destination was using term name as a context I had wanted to pass the name (helps with readability). I switched the view to use tid and so it's functional now but it'd be sweet to be able to use the name so to make the urls readable
like
http://www.wildriverswool.com/showproduct/13
isn't as nice as
http://www.wildriverswool.com/showproduct/pets
thanks to anyone who can figure this out
-z
Comment #12
vood002 CreditAttribution: vood002 commentedSubscribing, this module seems to be working fine but it is throwing PHP notices on unexpected pages
Comment #13
alx22 CreditAttribution: alx22 commentedSubscribing.
I also have the problem when trying to use the token
[term:name] in a taxonomy to view redirect
same error message as above.
Notice: Undefined property: stdClass::$name in taxonomy_tokens() (line 105 of .... modules/taxonomy/taxonomy.tokens.inc).
Works nicely with [term:tid]
LOVE THIS MODULE!! Awesome!!
Comment #14
derhasi CreditAttribution: derhasi commentedComment #15
derhasi CreditAttribution: derhasi commentedI finally had time to have a look on that issue. I recognized that this is an issue for views itself, as that does only provide pseudo-objects to work with entity_uri(). In the case of taxonomy terms that is located in
views_handler_field_taxonomy:render_link()
.Attached there is a patch for the views module to temporarily fix that issue. I'd open a separate issue in the views issue queue later.
Postponed as long as the (missing) views issue is not fixed.
Comment #16
derhasi CreditAttribution: derhasi commentedArg, and there is the temp patch ... sorry.
Comment #17
derhasi CreditAttribution: derhasi commentedThe related views issue: #1806266: Complete entity_uri support for taxonomy_term
Comment #18
droog CreditAttribution: droog commentedThis patch did not fix the issue I am having - which is exactly what was reported originally:
"Notice: Undefined property: stdClass::$name in taxonomy_tokens() (line 105 of /modules/taxonomy/taxonomy.tokens.inc)."
Is any other info going to help? I used Drush to update all my models & core prior to patching.
Update:
1.
drupal.org ate my less than and greater than characters that I wrapped around my Drupal root in the above error. I suspect that's not a good thing and may even be exploitable.2. Turns out that "name" is not what I wanted to be using anyway. I've chosen another field from the taxonomy to use instead and the error's gone.
Testing: Tested the tags thing - drupal.org is at least stripping them entirely. Better than I had initially thought :)
Comment #19
jordan8037310 CreditAttribution: jordan8037310 commentedI can report that the patch helped with my implementation as well.
Comment #20
Sakhmed CreditAttribution: Sakhmed commentedPatch #16 solved my problem
Comment #21
asghaier CreditAttribution: asghaier commentedPatch #16 solved my problem
Comment #22
oriol_e9gPatch in #16 adds [term:name] token and works.