Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Piwik 1.9.2 dashboard and widgets don't stick #3543

Closed
anonymous-piwik-user opened this Issue · 11 comments

3 participants

@anonymous-piwik-user

On a new installation of Piwik 1.9.2. After moving around the widgets on the default dashboard. Go to another tab or to the settings page. Now return to the dashboard. The layout and position of the widgets that were moved around default back to the original that came with the install. The dashboard does not save the widgets.

Example: remove the global map widget and the RSS widget. Go to a tab or settings page. Return to the dashboard and the global map widget and RSS widget are there again. Adding a new widget does the same thing. Go to another page and come back. The dashboard defaults to the original install widgets and layout.

In version 1.9.1 the dashboard customizing works and saves. In version 1.9.2 it does not. Please install a new version of 1.9.2 and see what actually works. I attempted to install 1.9.1 and was planning to update to 1.9.2 to get the dashboard with widget in a layout I like. I quickly realized the dashboard and widgets gets saved in 1.9.1 but the tracking does not work in 1.9.1. I am not sure if on a new install whether or not Piwik logs visits for 1.9.2. (Firefox was used and IE)

For future releases could you please do a new test installation to see if the dashboard/widgets save and if Piwik actually logs visits. Maybe if someone updates from a previous version it still works but from what I can tell on a brand new installation of Piwik there are some issues. Thanks a lot!

@mattab
Owner

Can you please email to matt@piwik.org your piwik URL + login + password + link to this bug + steps to reproduce? I will take a look and we'll get it fixed. thanks!

@sgiehl
Collaborator

the problem might be, that the layout parameter is passed as GET. That might make the URL very long, causing some servers to cut them off. I'll have a look at that later and change that to a POST parameter.

@anonymous-piwik-user

Please disregard the part about browser logging. It appears that may be an issue specific to how my system is setup. I'll look into what caused my browser to not get logged later. I have sent the email to you Matt. Thank you for your help Matt and Steve.

@mattab
Owner

Steve I think you're right. the server returns error "<p>The parameter layout isn't set in the Request, and a default value wasn't provided"

changing to POSt should fix it thanks in advance

@sgiehl
Collaborator

Changed to POST params in [7489].
@fish11: you could try the latest beta and report if it works there

@anonymous-piwik-user

Yes, I believe it works now. I tried piwik-1.9.3-b7. Thank you Steve.

@sgiehl
Collaborator

Closing this ticket for now as other users also reported that it works with latest beta. Please reopen the ticket if it should be broken within the next stable release.

@anonymous-piwik-user

Hi SteveG,

That changeset contains a lot of code.
Is it possible to give a patch for 1.9.2 that only solves this?

I don't want to risk my piwik with dozens of sites with a beta, but would very much like this bug to be solved.
(One of our bigger customers was using Google Analytics, and I was able to convince them using Piwik, until they ran into this bug. It would be a pity if they choose using Google Analytics again only because of this)

@mattab
Owner

please use latest beta, we don't do custom patches because beta work well :)

@anonymous-piwik-user

Thanks,

If I follow the FAQ and add

[Debug]
allow_upgrades_to_beta = 1

nothing happens.

It seems to be related to
http://builds.piwik.org/LATEST_BETA
which also says: 1.9.2

Is there a new generic way to get the latest Beta?

@mattab
Owner

there was a bug with beta releases now fixed!

@anonymous-piwik-user anonymous-piwik-user added this to the 1.10 - Piwik 1.10 milestone
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.