Subscribe via rss
Guest
or Ask a Question
Discussions
Add a reply View Replies (2)

Content Statistics Admin Component - An error has occurred

General
Wednesday, September 25 2013, 05:31 AM
Icemedia
Icemedia
Offline
0
Hello,
I have installed this component (extended version) and enabled all nessesary components/modules ect. Clicked components -> content-statistics and all actions were being recorded as desired. I then clicked for the page to be sorted by ID and I am now faced with this error message:

An error has occurred.
0 SQL=SELECT st.*, u.name as username FROM zooarc_content_statistics as st LEFT JOIN zooarc_users as u ON u.id = st.user_id WHERE st.component = "com_content" AND st.type = 1 AND st.reference_id = 5 ORDER BY al.id asc

With a button to return to the control panel. I am unable to diagnose the issue. Please help as as this is an impatient client.

Dion
Extension content statistics components

Accepted Answer

Germinal Camps
Germinal Camps
Offline
Wednesday, September 25 2013, 09:38 AM - #Permalink
0
Hello,

this occurs only when sorting by the ID column, I guess..
it turns out is a small bug that can cause this issue.
I have just re-packed content statistics component. Please, download it again on My Downloads area and reinstall (only the component). this issue should be gone.

let me know!
The reply is currently minimized Show
Responses (1)

  • Accepted Answer

    Icemedia
    Icemedia
    Offline
    Wednesday, September 25 2013, 11:22 PM - #Permalink
    0
    Hello!

    5 Minutes before I got your response I managed to look on our production instance of this site which had never had the ID column clicked and still worked. I then clicked the username column and copied everything after the domain name in the URL:

    eg. domain.com/administrator/index.php?keywords=&component_id=0&type_id=&item_id=&user_id=&date_in=&date_out=&country_id=0&limitstart=0&option=com_contentstats&task=&boxchecked=0&controller=items&filter_order=st.reference_id&filter_order_Dir=asc

    ..and appended it to the domain of our live site and this managed to get the component out of the initial rut and working normally again, followed by re-installing the new component which fixed the problem for good and prevented it from happening again. Although, in curiosity, I had another instance which was still experiencing the problem so I tried installing the new component straight away and this did not get the component out of the rut.

    I then appended the above which worked and your new component kept it from happening agian.

    Sorry for the novel!

    Thank you so much for managing to do this so quickly.

    Much Appreciated!
    The reply is currently minimized Show
Your Reply