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
Dashboard is broken #714
Comments
Ohfuck. Forget to remove tmp/templates_c contents. This fixes loading data. Everything else but Dashboard main page works fine. Main page loads Widgets (default configuration, default widgets) but contents are just "Loading widget, please wait...". |
Fixed. Dashboard widget which shows visits per day (on left top, I think) showed 'Widget Not Found'. After that was deleted everything (?) works. Why whole dashboard fails if there is one missing widget? Last Visits Graph works after re-added. From my point of view upgrade process was a bit clunky:
|
Browser cache problem to be addressed in #712 (related to #660). We can call Smarty's clear_compiled_tpl() to clear the templates_c files (perhaps in Updater?), to force these to be recompiled. Yes, in [1072], getLastVisitsGraph was renamed to getEvolutionGraph. We could try to fix the piwik_user_dashboard table... |
Another question is that (already bolded at my previous comment) why whole dashboard completely fails (every widget just shows 'Loading...') when there is one missing widget installed? Should this be separate ticket? |
This is because your dashboard is trying to load a widget by name -- which in my comment stated had been renamed. When you added the widget back, the dashboard used the new name. |
I got the same problem after upgrading to 0.2.35. |
RHihn: as said, try to delete widgets that say 'Widget not found'. At least for me that helped (widgets can be added back using Add Widget) |
Note: [1119] is necessary because Smarty 2.6.22 does not recompile templates if there are one or more output filters. (Undocumented behaviour; determined this by code inspection.) |
Oops. Scratch that last comment. Digging further... |
[1119] is necessary because the files we distribute in last.zip may be older than the creation timestamps of compiled templates. This is problematic if a user extracts last.zip over an existing installation. |
Replying to joku:
The "Add Widget" function doesn't work here. |
Hi guys, Since I upgraded from 0.2.34 to 0.2.35, piwik is completely down (not only dashboard, but all pages). No data gets displayed and dashboard widgets are stuck to 'Loading widget, please wait...' message. I completely emptied /piwik/tmp directory but it did not change anything. How can I fix it? Regards, |
I get "Widget not found" as well. But can anyone please tell me how to update this? I don't know which widget I need to reinstall. |
To answer myself:
Now I get:
|
I had to clear the cache again and then the message disappeared. I see graphs. =) |
[1122] fixes widget hanging with "loading" message where non-native json_encode() double escapes the double quotes. |
matt: as a quick fix, what about deleting the rows in piwik_user_dashboard (during an update script). The dashboard plugin will recreate from a default layout. |
Or is this unnecessary now? Closing...let 0.2.36 feedback begin... |
Replying to vipsoft:
patched in [1128] |
re: [1128] I was thinking of dropping lastVisitsGraph. |
I had executed the above query and since I updated to 0.2.37 tonight, the dashboard is broken again. "Widget not found..." |
till: you still need to clear your browser cache. If that doesn't work, please open a new ticket. |
First off, I can't re-open the ticket ('no permission to change ticket fields'). ;-) Secondly, I cleared the browser cache. To fix it, I had to delete two orphaned widgets from my dashboard and then it worked. I couldn't figure out why they were not found -- e.g. name-wise. No idea what they were looking for. |
Replying to till:
Now everything looks fine. |
After upgrading to 0.2.35 dashboard just shows "Loading data" infinitely. Browser cache deleted and browser restarted. Not using any proxies. No reverse proxies or other caching mechanisms (even restarted apache2 to ensure that there is no caching). Tested with different browsers on different computers (Opera, Firefox 3.0, Ubuntu & Windows XP & Mac OS X).
Upgraded with following process:
The text was updated successfully, but these errors were encountered: