Closed (fixed)
Project:
Universally Unique IDentifier
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
29 May 2012 at 03:24 UTC
Updated:
21 Jul 2013 at 06:01 UTC
Jump to comment: Most recent file

Comments
Comment #1
populist commentedI am pretty sure this is an issue related to Fieldable Panels Panes. From my brief debugging, the UUID and VUUID is being provided as tokens but they are not also being defined as types.
Comment #2
merlinofchaos commentedIt's possible we're somehow incorrectly turning on uuid support but I think uuid module handles all of this?
Comment #3
populist commentedI did some more analysis and tracked this down to the UUID module. At issue here is the call in uuid_token_info() which defines the token types for all entities, but since FPP doesn't have any token it kicks out that error.
This could technically be fixed in FPP by adding a fieldable_panels_panes.tokens.inc file that defines some types, but think its easier to do it in the UUID module. I don't have a ton of UUID or token experience so this will likely take some review.
Comment #4
merlinofchaos commentedA token for the pane title would be sensible.
Comment #5
populist commentedHere is my patch from #3, sorry about that!
I also opened an issue in FPP around token support #1798482: Improved(?) Token support and referenced merlinofchaos' suggestion for a title token.
Comment #6
populist commentedI found a bit of trouble with the patch from #5, so I implemented a cleaner patch. This one adds a hook_token_info_alter() hook that removes any token types added by UUID that do *not* have tokens enabled. I tested this with Fieldable Panel Panes (which it removes since it doesn't have token), but it keeps the tokens from user / node and other entities.
Comment #7
gilgabar commentedMarked #1269918: token type not defined : $info['types']['field_collection_item'] as a duplicate of this issue as it affects other entities, e.g. field collections, as well.
The patch in #6 fixes the status message for me.
Comment #8
jaypark commentedhave latest uuid enabled, 7.x-1.x branch commit:
commit 4bbf92d8c07485492c0f1065cb3647db492e1029
Author: Dave Hall
Date: Sun Feb 3 12:06:50 2013 +1100
Add URI hooks to hook_info()
applied patch at #6, still receive status message, but for field_collection_item:
Comment #9
mgiffordPatch still applies nicely to the git repo. @populist have you bundled your patch into Panopoly? If so that's certainly had a lot of testing at this point.
How many of the uuid patches are you using in the Panopoly distro? Would be good to know what you're already using and what testing has already been done.
Ideally we'd just have a stable release so you don't have to patch uuid or use the dev release.
Comment #10
pangus commentedPatch #6 got rid of $info['types']['field_collection_item'] message for me - thanks!
Comment #11
populist commented@mgifford - I am only using the patch in #6 above for UUID support, but may remove UUID entirely as per #1995066: Remove UUID Module from Panopoly?
@pangus - Good to hear. I am marking this RTBC since it does solve a lot of problems for Panopoly users and works for Field Collection also.
Comment #12
temkin commentedJust applied patch from #6 and the status message is gone. Thank you!
Comment #13
dixon_Patch from #6 committed to 7.x-1.x-dev. Thanks all! I'll probably roll another release very soon.