Home / FAQ
I have an error. What do I do?
a.) turn on global debugging for your Magento instance:
System > Configuration > Developer > Log > Yes
b.) turn on debugging for the Jirafe plugin:
System > Configuration > Jirafe Analytics > Debug > Yes
c.) You should now see additional actions next to the error message. Please click synchronise.
If the issue persists enter an issue (Issues menu above), or simply email us at firstname.lastname@example.org. Please attach the log file foomanjirafe.log from var/log/ and also any relevant information from the exception.log file.
I am not receiving an email. What now?
Make sure that the Magento cron job is set up correctly. More information can be found here.
The debug info shows Last Status: 500 Internal Server Error
One possibility is that you have chosen the timezone "US Eastern Standard Time (Etc/GMT+5)" which is not yet supported from our end. Please choose "Eastern Standard Time (America/New_York)" instead until we include a fix in the next release.
How do I get Jirafe running in Magento v1.3? After installing via Magento Connect please copy the following files: app/design/frontend/base/default/layout/foomanjirafe.xml to app/design/frontend/default/default/layout/foomanjirafe.xml and copy the folder app/design/frontend/base/default/template/fooman/jirafe to app/design/frontend/default/default/template/fooman/jirafe (note adjust 'default' to your theme name if you are using different package/theme names.
The Magento platform limits changes to behaviour of any core class to only 1 extension. This can lead to conflicts with other installed community extensions. Please see the below list of known conflicts and potential workarounds. Please let us know if you come across any others or can confirm/add to the workarounds.
As a workaround you can edit app/code/community/Fooman/Jirafe/etc/config.xml and remove
<log> <rewrite> <visitor>Fooman_Jirafe_Model_Log_Visitor</visitor> </rewrite> </log>
Save and refresh the cache. This change will over-report number of visitors in the daily emails since it will include search engine bots. The dashboard will still report the correct number of visitors.
Alternatively you can test installing this extension and implement the suggested fix.
Last edited by fooman,