The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Entities that don't provide a proper entity URI from a placeholder entity (as used in salesforce_mapping_menu() to determine paths) end up with their SF mapping object pages in strange places. But the listing page doesn't account for these situations, so the operation links are all broken for objects that don't respond properly (like Commerce Orders, or any other object that doesn't pick up its "Salesforce Mapping" tab properly). This causes errors when using these functional links.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | management_ui_links-2833285-4.patch | 4.46 KB | gcb |
| #3 | management_ui_links-2833285-2.patch | 4.35 KB | mariacha1 |
| #2 | management_ui_links-2833285-1.patch | 2.21 KB | gcb |
Comments
Comment #2
gcbComment #3
mariacha1 commentedIt seems that the real issue is that hook_menu has to rely on different information than SalesforceMappingObject defaultUri() which is leading to re-checking the output values after every call to $salesforce_mapping_object->uri().
The following attached patch uses a helper function to ensure that the same code is called both places, so we don't have to litter our code with if/elses any time we call the uri() method.
Tested with:
Users,
Nodes,
Redhen Contacts,
Recurring Entities.
Comment #4
gcbLast patch has potential to call entity_extract_ids in cases where a mapping is point to a deleted object. This patch fixes that.
Comment #5
aaronbauman7.x is no longer supported