@dessant opened this Issue on July 24th 2016

There is a button for editing, but not for deleting.

@TomTheRock commented on February 14th 2018

yes this is really anoying!

@tsteur commented on February 14th 2018 Member

If I remember the problem is that if we added a delete custom dimension button, the previously tracked data for that dimension would still exist in the so called "log" tables which stores the raw data. If you then create another dimension, that slot would be used again and your old data mixed with new data.

Deleting this old data is not "trivial" as it may take a long time to delete this data, and obviously cannot be undone. Accidental delete would not be possible to be restored. Maybe we could start adding a command that allows users to actually delete a custom dimension and also deletes the data from the log table. This way it should not happen "accidentally" and as the script would not time out on the command line (since it could run for a very long time).

I presume the workaround is to add more custom dimension slots if needed.

@toredash commented on April 9th 2019 Contributor

Maybe we could start adding a command that allows users to actually delete a custom dimension and also deletes the data from the log table. This way it should not happen "accidentally" and as the script would not time out on the command line (since it could run for a very long time).

This please. When playing around with new sites it is a hassle to have delete it, as that is the only way to get a "clean state" for a site.

I'm waiting for the day someone added a couple of dimensions to a production site, not knowing there isn't an easy way to remove the dimension.

@magnus-eriksson commented on October 27th 2020

We're doing this right now, trying to figure out which dimensions we need to use and how they work. We've had to create multiple sites just to test different ways. We still have an old dimension for the real site that we want to get rid of.

If people "accidentally" delete their custom dimensions, they either need to pay more attention or the UI needs to be improved. Removing the feature isn't a good solution.

Adding a CLI command to do it is nice, but unfortunately, not everyone that manages Matomo are too familiar with CLI though. Marketing people don't tend to be interested in learning how to ssh to a docker container running on kubernetes just to be able to remove a custom dimension. And it isn't something that they should need a developer to help them with.

@tsteur commented on October 27th 2020 Member

If people "accidentally" delete their custom dimensions, they either need to pay more attention or the UI needs to be improved. Removing the feature isn't a good solution.

There could be a popup asking them to enter some text like the name of the custom dimension or type OK or something to confirm the deletion.

The problem be still generally that we would basically need to delete all the data from the log tables right away which can take quite anything from few seconds to few hours depending on the amount of data plus can cause down time. Not sure how this can be solved yet. It be probably more like a "delete from the UI" but keep it still in the DB meaning it wouldn't be possible to reuse the deleted slot.

Powered by GitHub Issue Mirror