Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Another 500 error bug in regards to Live data #12033

Closed
Power2All opened this issue Sep 12, 2017 · 16 comments
Closed

Another 500 error bug in regards to Live data #12033

Power2All opened this issue Sep 12, 2017 · 16 comments
Labels
duplicate For issues that already existed in our issue tracker and were reported previously.

Comments

@Power2All
Copy link

Found another issue after upgrade, looks like a twig issue.

image

@sgiehl
Copy link
Member

sgiehl commented Sep 12, 2017

That does not seem to be a twig problem. The visitor data provided for rendering seems to be incorrect. Could you try to open this url and check if the response contains an error:
method=Live.getLastVisitsDetails&idSite=1&filter_limit=10&format=php&serialize=0&disable_generic_filters=1 (you may need to adjust the idSite param)

@Power2All
Copy link
Author

Power2All commented Sep 12, 2017

Bug found.
Seems something changed with the upgrade process, and MySQL is not properly updated:

{result: "error",…}
message
:
"Mysqli prepare error: Unknown column 'log_link_visit_action.idpageview' in 'field list'"
result
:
"error"

Any idea how to fix this?
Did something change in tables?

@sgiehl
Copy link
Member

sgiehl commented Sep 12, 2017

Could you please paste the result of this query:

SELECT option_value FROM piwik_option WHERE option_name = 'version_log_link_visit_action.idpageview';

@Power2All
Copy link
Author

image

@sgiehl
Copy link
Member

sgiehl commented Sep 12, 2017

Could you check if this file exists on your Piwik:
piwik/plugins/Actions/Columns/IdPageview.php

@Power2All
Copy link
Author

-rw-r--r-- 1 09-webstats www-data 896 Sep 12 10:17 plugins/Actions/Columns/IdPageview.php

@sgiehl
Copy link
Member

sgiehl commented Sep 12, 2017

You can run the SQL DELETE FROM piwik_option WHERE option_name = 'version_log_link_visit_action.idpageview';
Afterwards Piwik should automatically create the missing coulmn when you open it.

@tsteur
Copy link
Member

tsteur commented Sep 12, 2017

@Power2All do you remember from which Piwik version you updated?

@tsteur
Copy link
Member

tsteur commented Sep 12, 2017

@sgiehl we are getting similar error on demo.piwik.org on an ecommerce website (Marketplace)

A fatal error occurred

The following error just broke Piwik (v3.1.0-rc1):

Key "icon" for array with keys "type, url, pageTitle, pageIdAction, idpageview, serverTimePretty, timeSpentRef, pageId, contentName, contentPiece, contentTarget, contentInteraction, interactionPosition, timestamp" does not exist.
in
/storage/piwik-demo/www/demo.piwik.org/plugins/Live/templates/getLastVisitsStart.twig line 148

image

edit: noticed this is different issue and created #12037

@sgiehl
Copy link
Member

sgiehl commented Sep 12, 2017

guess that is caused by content actions. Seems I missed to have them correctly handled in real time widget

@Power2All
Copy link
Author

You can run the SQL DELETE FROM piwik_option WHERE option_name = 'version_log_link_visit_action.idpageview';
Afterwards Piwik should automatically create the missing coulmn when you open it.

When I did this, it came finally with a "update your database" when accessing piwik again.
After the upgrade, it still showed the above red text error, but when it parsed some stuff, it started to work again.
So far now it looks good.

@sgiehl
Copy link
Member

sgiehl commented Sep 13, 2017

@Power2All do you remember from which Piwik version you updated?

@mattab mattab modified the milestones: 3.1.1, 3.2.0 Sep 14, 2017
@mattab
Copy link
Member

mattab commented Sep 21, 2017

Hi @sgiehl is this issue maybe fixed?

@mattab mattab modified the milestones: 3.2.0, 3.1.2 Sep 21, 2017
@sgiehl
Copy link
Member

sgiehl commented Sep 21, 2017

No. This is unrelated to the last release. Sure, the error now pops up, as the idpageview column is now used. But it should have been created in an update before. Not sure why I wasn't.

@mattab mattab removed this from the 3.1.2 milestone Sep 21, 2017
@mattab
Copy link
Member

mattab commented Sep 21, 2017

Might be duplicate of #11981 and probably other issues

@mattab
Copy link
Member

mattab commented Jun 26, 2018

this should be fixed, if you still experience this please open a new issue.

@mattab mattab closed this as completed Jun 26, 2018
@mattab mattab added the duplicate For issues that already existed in our issue tracker and were reported previously. label Jun 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate For issues that already existed in our issue tracker and were reported previously.
Projects
None yet
Development

No branches or pull requests

4 participants