Closed (works as designed)
Project:
Deploy - Content Staging
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Issue tags:
Reporter:
Created:
2 Feb 2017 at 23:04 UTC
Updated:
3 Feb 2017 at 18:10 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
dineshw commentedComment #3
dineshw commentedFollowing patch provides correct entity_type as type property for deploy_manager_entities
Providing
$entity->typeinstead$entity->entity_typehelps to get correct labels for entities stored in tabledeploy_manager_entitiesOriginally
$entity->entity_typeused to hold valuedeploy_manager_entitieswhich does not helps and throws PHP Error when we select 'Remove entity from deployment plan'I praposed to use method
deploy_manager_entities_get_by_idto fetch correctentity_typestored in tabledeploy_manager_entities.Comment #5
dineshw commentedRevised Patch is here, I'm able to test deletion of entities with this patch.
Comment #6
dineshw commentedComment #7
dineshw commentedAdded revised patch here, I'm able to test deletion of entities with this patch.
Comment #8
dan.munn commentedDinesh - as per conversation, the problem you're reporting is when used with personalize_fields as it sets entity_type attribute on the entity when loaded, overwriting any information already present. The conclusion was that the deploy module is operating as it intends, but its behaviour from personalize_fields that should be patched - so not to force entity_type attribute on the entity, but only do so when it does not exist.
I think this otherwise should be closed as its not a bug with deploy, or contrib modules deploy is leveraging directly.
Comment #9
dineshw commentedClosing this bug as highlighted by @dan.munn fix should goes to https://www.drupal.org/node/2849573
Bug exisit only when
personalize_fieldsis enabled. Hence closing this as 'works as designed1'Thanks For Quick review @dan.munn