@wolfstettler opened this Issue on July 9th 2014

For a Piwik installation with a lot of websites, it is inconvenient that only super-admins can edit the settings for enable_all_users, enable_only_idsite and auto_archive in the segment editor

piwik_segment_editor

The normal admins can not use those features (they don't even know they exist), so there are double and triple segments with more or less the same content and often complaints about slow segments, because they are processed in real time.

I would be useful, if the admins could set these settings themselves.

Regards,
Wolf Stettler

@fleish commented on July 30th 2014

I have a similar issue in my environment. "View" level users cannot create segments that are pre-processed as part of a regularly scheduled archive run. We do not want any reports created in real-time due to the unpredictable load & php memory constraints we enforce through the web server. So it would be very helpful to have the option for "View" level users to be able to set this. Alternatively, if an admin could change the global default setting so that all segments were pre-processed that would work too.

My current workaround is to edit a segment directly in the database so the following are set which seems to work:
enable_all_users: 1
enable_only_idsite: 0
auto_archive: 1

It appears all 3 options need to be set and the ts_last_edit field needs to be updated in order for archive.php to pick up on it.

@mattab commented on August 3rd 2014 Member

Thank you for the suggestion!

@mattab commented on October 11th 2014 Member

Can you try with latest Piwik beta 2.8.0-b3 ? we fixed #6373 which may help?

@wolfstettler commented on October 14th 2014

Thank you, I will set up a testserver asap and come back to you.

@mattab commented on July 1st 2019 Member

Thanks for contributing to this issue. As it has been a few months since the last activity and we believe this is likely not an issue anymore, we will now close this. If that's not the case, please do feel free to either reopen this issue or open a new one. We will gladly take a look again!

This Issue was closed on July 1st 2019
Powered by GitHub Issue Mirror