CTools Contexts are missing UUID support.

I applied your patch and got EntityMalformedException: Missing bundle property on entity of type taxonomy_term. in entity_extract_ids() (line 7734 of /projects/cellfish/www/includes/common.inc)., it seems that $context->argument should receive the entity id instead of the uuid, after I made the modification, everything worked as expected.

RTBC++ , please commit

we're using uuid revision a7bf2db with this patch (and several others)

I was find few errors in patch #5.
For example, submission of settings form has an error, because function "entity_uuid_load" returns array keyed by ID? not by UUID.

function uuid_context_entity_uuid_settings_form_submit($form, &$form_state) {
  if ($form_state['values']['set_identifier']) {
    $entity_info = entity_get_info($form_state['values']['entity_type']);
    $entity = entity_uuid_load($form_state['values']['entity_type'], array($form_state['values']['uuid']));
    $entity = $entity[$form_state['values']['uuid']];
    $form_state['values']['identifier'] = $entity->{$entity_info['entity keys']['label']};
  }

  // This will either be the value set previously or a value set by the
  // validator.
  $form_state['conf']['uuid'] = $form_state['values']['uuid'];
}

In a function "uuid_context_create_entity_uuid" I also find errors. For example

  elseif (is_object($data)) {
    $uuids = entity_extract_ids($entity_type, $data);
    $uuid = $uuids[0];
  }

So, I have reviewed and fixed patch #5

Hi kyvour thanks for your new patch. See the next comment by Sylus

I think there is an issue with this latest patch. We just updated a site to the latest wetkit distro which has this latest version of this patch and now there are errors:

Warning: array_flip(): Can only flip STRING and INTEGER values! in entity_uuid_id_cache() (line 460 of /var/www/html/dev3.openplus.ca/profiles/wetkit/modules/contrib/uuid/uuid.entity.inc).

What we found was that in the create context code $data looks like:

identifier (String, 20 characters ) Taxonomy term (UUID)
keyword (String, 13 characters ) taxonomy_term
name (String, 25 characters ) entity_uuid:taxonomy_term
uuid (String, 36 characters ) 66fcf83c-3e49-43b0-9c21-98d796895fbe
id (Integer) 1

Now the code looks like:

     68   // Attempt to retain compatibility with broken uuid:
     69   if (is_array($data) && !isset($data['entity_id']) && isset($data['id'])) {
     70     $id = $data['id'];
     71     $uuids = entity_get_uuid_by_id($entity_type, array($data['id']));
     72     $uuid = !empty($uuids[$id]) ? $uuids[$id] : FALSE;
     73   } 
     74   elseif (is_array($data) && isset($data['uuid'])) {
     75     $uuid = $data['uuid'];
     76   }

I believe since we already have the uuid, we should land in the code lines 74-76, however, we seem to go into the code at 69-73 and try to load a uuid for id=1. Maybe, @kyvour can explain what the purpose of this code is... if I change the code to be like this my site works fine:

     68   // Attempt to retain compatibility with broken uuid:
     69   if (is_array($data) && isset($data['uuid'])) {
     70     $uuid = $data['uuid'];
     71   } 
     72   elseif (is_array($data) && !isset($data['entity_id']) && isset($data['id'])) {
     73     $id = $data['id'];
     74     $uuids = entity_get_uuid_by_id($entity_type, array($data['id']));
     75     $uuid = !empty($uuids[$id]) ? $uuids[$id] : FALSE;
     76   } 

For what it's worth, I noticed a warning: array_flip... recently using the same/similar code base as Joel_osc. Not sure if it's related but it could be; in my case it seemed to disappear after I had backed off a core patch that has to do with caching and performance, once I backed that one off I did a "rr --fire-bazooka". then after the fire-bazooka I reapplied the reversed patch and didn't seem to see this warning come up however I'd have to really do lots more testing/debugging to actually confirm this and test Joel_osc's code change. Early next week I'll try out what is suggested in #13 as it would be nice to confirm that this is the solution. I'll be watching this queue closely either way.

Here is the patch with my change. Cheers.

This patch appears to duplicate a lot of the functionality already in the Context UUID module. I am moving this to that project and the patch can be rerolled to implement any of the functionality that is missing from the existing module.

I would disagree with that, the context module framework is a parallel framework to panels/ctools. If you use panels you would not use the context module. I am going to move this back so the issue does not get lost and let some of the others chime in here...thx.

Sorry for the misunderstanding earlier.

I looked over the patch, the doxygen docs are missing, incomplete or misleading. Please review the docs and fix them as needed.

@joel_osc , tested your patch and we no longer get array_flip notices in watchdog. haven't noticed any regressions. Looks good and thanks!

It looks like the following functions require doxygen docs.
function uuid_context_entity_uuid_get_child
function uuid_context_entity_uuid_get_children
function uuid_context_entity_uuid_settings_form
function uuid_context_entity_uuid_settings_form_submit
function uuid_context_entity_uuid_convert

and I believe the others that do have docs in the patch could be improved with a description of the function parameters and return value.

Here's the notes on coding-standards for docs.
https://www.drupal.org/coding-standards/docs#general

I applied the patch but I still can't see term uuid option in contexts in selection rule for the term_view page.

Did you add an 'entity uuid' context to your variant first? This will bring in your term as a context and then you can use any of the existing selection rules.

It would be nice also to be able to autocomplete on the uuid itself, for example for a site with A LOT of content and duplicate title it may be difficult to find the right one. I included an or query that also makes the autocomplete match on the uuid value.

(Based on patch in #16)

Forgot to add interdiff.

Guys, it's important feature as for me. Why it doesn't committed to module? Is there a problem only in docblocks for the functions or something else?