New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking lead manipulator #5379
Tracking lead manipulator #5379
Conversation
* @param string|null $objectName | ||
* @param int|null $objectId | ||
*/ | ||
public function __construct($bundleName = null, $objectName = null, $objectId = null) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the reason why the first 2 params are nullable?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because in database, they can be nullable. I thought maybe there is use case when it's possible
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. I was thinking we should write the code as strict as possible.
@@ -199,6 +200,9 @@ class Lead extends FormEntity implements CustomFieldEntityInterface | |||
*/ | |||
private $color; | |||
|
|||
/** @var LeadManipulator */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this annotation use the new lines as all of the annotations above and bellow?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, it's just so long..
$lead->setManipulator(new LeadManipulator( | ||
'lead', | ||
'lead' | ||
)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe I'm not understanding the task right, but how can you tell if the source of the lead is import over manual creation over UI? This code is called 4 times on 4 different places.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's already long time, so I did not fully recalled what is bundle name and what is object name. Where do you see problem? It's manipulated from lead bundle, lead model so it's lead-lead if I'm right.
I'm not sure if it says something about UI
…ipulated lead if it is new or identified
I did a little work to this to address the follow issues:
|
Wasnt able to test with landing pages. CRM, Forms and embedded forms, Creating contacts and importing work properly Maybe I am missing something in testing with landing pages... |
Was able to test it and its working properly |
@javjim-mautic So landing pages work or no? I removed the needs documentation label because this is just a minor UI change as far as the frontend goes. We don't have existing documentation for the timeline to append to. |
@npracht What documentation are you looking for? All this does is display the source of the contact's identification and creation in the lead's History tab. There's not much to document. |
I added the label because some valuable info can be documented about this:
|
Description:
Log source of lead creation and identification
Steps to test this PR:
php app/console doctrine:migrations:migrate