search

Thomas--F / BotTracker

BotTracker-Plugin for Piwik
GNU General Public License v3.0
33 stars 14 forks source link

Receiving this error "Error: Key "1" for array with keys "0" does not exist in "@CoreVisualizations/_dataTableViz_tagCloud.twig" at line 1" #43

Closed GitPuffy closed 8 years ago

GitPuffy commented 8 years ago

I am receiving this error when I navigate to the BotTracker link on my dashboard page (Visitors > BotTracker):

Error: Key "1" for array with keys "0" does not exist in "@CoreVisualizations/_dataTableViz_tagCloud.twig" at line 1

I do not believe I have made changes to Piwik recently. I did do a yum update on my server though in the past few days. I have deactivated and uninstalled the BotTracker plug-in and then re-installed it with no noticeable change.

Thomas--F commented 8 years ago

I got this error some months ago. It seems something in the widget-cache is wrong.

The only way to remove it was to delete the row "viewDataTableParameters_xxxxxxxxx_BotTracker.getBotTrackerPie" from the table piwik_option

Can you try this?

GitPuffy commented 8 years ago

Deleting that table row has solved the problem. BotTracker is now displaying information again. Unfortunately since I deleted the plugin and re-installed it, to attempt a fix to the problem, it is not reporting any bot activity at this time.

GitPuffy commented 8 years ago

As a follow up. This is what the row looked like before I deleted it:

viewDataTableParameters_xxxxx_BotTracker.getBotTrackerPie | {"columns":["value"],"columns_to_display":["value"],"rows":[],"rows_to_display":[],"isFooterExpandedInDashboard":true,"viewDataTable":"cloud"

And this is what it looks like now:

viewDataTableParameters_xxxxx_BotTracker.getBotTrackerPie | {"isFooterExpandedInDashboard":true,"viewDataTable":"graphPie"}

Does that help determine the root of why it stopped working?

Thomas--F commented 8 years ago

I really don't know. Somehow one of the options lead to this error and because Piwik remebers your last settings (the row you deleted) you get this error every time you hit the page.