[Piwik-hackers] Question: How to get the actions>pages widget to also display the domain name?

[Stephen Stroup]

Ok, quick update. I'm a little closer to my goal but not all the way there
yet. I changed
*piwik_action_name = '';
*to
*piwik_action_name = document.location;*
in the piwik javascript code that's inserted into pages.

I managed to get it from showing the following
http://i292.photobucket.com/albums/mm34/sabin126/Piwik/piwik1.png
to showing http://i292.photobucket.com/albums/mm34/sabin126/Piwik/piwik2.png

I now have the domain name showing up. However, everything under the host
name in the tree structure still contains the host name rather than the part
which appends to it. It makes the user have to roll over each entry to
actually see what page it's talking about. Is there any way to combine the
displaying of the host name with the nice tree structure that truncates off
the text of the parent?

I hope that makes sense. Sometimes I don't know the proper technical
names/terms so if you need more clarification I'll be happy to provide it.

-Stephen

On Thu, Jul 10, 2008 at 9:48 AM, Stephen Stroup <sstroup at gmail.com> wrote:

> Hi,
> I'm new to the analytics scene. I'm helping set up an apache reverse proxy
> server for the sites hosted by our college within our university, and
> decided to go with Piwik as the analytics software. It shows a lot of
> promise. After getting everything up and running with the reverse proxy and
> the proper code injection, I ran into the following problem for our setup.
>
> All domain names will go to the proxy server, and it will dynamically send
> the requests to the correct server and site on our back end. One of the uses
> is for a content management system where professors and others can have a
> simple interface to create their own sites within ours. These sites however
> will be seen by the client as a specific domain name. With piwik analytics
> so far, when I view the pages widget, I only see the part of the URL after
> the domain name. So, the problem exists that all these visits are not
> separated by the domains. This is even worse when domains have the same
> pages (for example, index.html) as we can't distinguish them from one
> another. We hope to be able to have an aggregate piwik site for all data
> coming through and still be able to break it apart by the domains that were
> requested.
>
> For some of you experienced folks I'm sure this is a very simple and easy
> problem. If anyone can help with the easiest/simplest solution, I would be
> much obliged. If more information is needed let me know.
>
>
> Sincerely,
> Stephen Stroup




-- 
Stephen Stroup
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.piwik.org/pipermail/piwik-hackers/attachments/20080710/4c8498a3/attachment.htm