-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Allow any plugin to extend and display data in the Visitor Log and Visitor Profile #6111
Comments
Example use case: Provider plugin to extend Visitor Log and Visitor Profile, covered #5341 |
This will be important for #7131 and #4734 . When a type (eg |
This would be very much useful in order to extend visitor profile popup for additional information. Right now the only hacky way seems to be to add the data to the Eventually, it would be great to have a way to add new rows (under the avatar) to the visitor profile popup, like |
Adding tentatively to 3.0.3 milestone, to be fixed along with:
Ideally we'd make both Visitor Log and Visitor Profile use same logic so that extending one extends the other too! |
+1 |
would be perfect if this solution not only works for plugins but also for Piwiks "own" base data, |
for reasons, details, ideas regarding extending informations in visitorlog see also #6416 |
when extending information in visitorprofile one maybe should take this into account to give new information the right position: |
does this also cover a possibility to extend visitor summary in visitor profile? |
Actually yes, that should be possible by implementing a VisitorDetails class in the plugin and adding a ProfileSummary. |
many thanks, awesome! |
Follow up for #6045 where we made it possible for any plugin to add data to the API. Now we want the plugins to extend Live widget, Visitor Log and Visitor profile.
This can be quite complex as we probably do not want loads of events there. Maybe we can start using AngularJS for this as a proof of concept. As they do not use the dataTable it is easier to rewrite this component. Maybe there are other, better solutions as well.
The text was updated successfully, but these errors were encountered: