Ticket #161 (closed Bug: fixed)
Find out changes to make Piwik easy to integrate in third party CMS, blogs, Ecommerce cms
| Reported by: | matt | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | Piwik 0.7 - DigitalVibes |
| Component: | Core | Keywords: | |
| Cc: | Sensitive: | no |
Description (last modified by matt) (diff)
Piwik provides a great API to request raw data. We now have to provide such an API to request the generated HTML out of piwik:
- Provide an API to fetch piwik HTML
hideLogin() hideSites() hideLoggedUser() setLanguage( $lg ) getBody() // returns <body>XXX</body> getHead() // returns <head>XXX</head> getJavascriptIncludes() getCssIncludes()
- make sure the CSS doesn't change the <body> so it doesnt change the app design
- make sure piwik works when getting the pages in SSL https://
- the generated URLs could use a prefix or different values in order to handle the existing application path.
For example if the cms is at /dev/cms/ and piwik at /stats/piwik/ the piwik generated HTML should prefix all URL with /dev/cms/XYZ or /dev/cms/boot?mod=LoadApp&action=piwik
- Provide an API to log a user in
login(username, password) logout() isUserConnected(username)
- refs #24 Plugins should have easy access to their own configuration file
- refs #168 make it easy for plugins to install piwik from outside
- see also notes on phpmyvisites integration
Change History
Note: See
TracTickets for help on using
tickets.
