humanmade / humanmade/altis-core

Add ability to disable segment telemetry globally

Open
#1,236 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug should have
Dominant language
PHP
Stars
19
Forks
3
Avg merge
4d 13h
Merged PRs (30d)
3

Description

Description

The telemetry feature gives users the option to opt-in or out of having data sent back from their local or Altis Cloud environment to Vantage via a popup. It is a sub-module in Altis core called telemetry. This is per-user, it pops up per for each person.

Image

We had a request to allow disabling telemetry globally via composer.json, current one workaround is to hook the get_user_meta call to disable it.

Image
How to reproduce
  • Create a new local server environment
  • Login to /wp-admin
  • You'll see the message to help us develop Altis, we would like to collect data on your usage of the software. This will help us build a better product for you. displayed
Acceptance Criteria
  • The telemetry feature can be disabled via a composer.json configuration (the popup should no longer be visible)
  • The profile telemtry opt-in option no longer appears
  • This configuration is documented in the Altis docs

For Altis Team Use

Ready for Work Checklist

Is this ticket ready to be worked on? See
the Play Book Definition of Ready

  • Is the title clear?
  • Is the description clear and detailed enough?
  • Are acceptance criteria listed?
  • Have any dependencies been identified? (Optional)
  • Have any documentation/playbook changes been identified? (Optional)
  • Is an estimate or time box assigned?
  • Is a priority label assigned?
  • Is this ticket added to a milestone?
  • Is this ticket added to an epic? (Optional)
Completion Checklist

Is this ticket done? See
the Play Book Definition of Done

  • Has the acceptance criteria been met?
  • Is the documentation updated (including README)?
  • Do any code/documentation changes meet project standards?
  • Are automatic tests in place to verify the fix or new functionality?
    • Or are manual tests documented (at least on this ticket)?
  • Are any Playbook/Handbook pages updated?
  • Has a new module release (patch/minor) been created/scheduled?
  • Have the appropriate backport labels been added to the PR?
  • Is there a roll-out (and roll-back) plan if required?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the telemetry sub-module and its existing per-user opt-in handling, then inspect how composer.json configuration is defined and loaded. Check the wp-admin popup and profile option entry points, and identify the Altis documentation location; done means the global setting suppresses both UI options and the documented configuration works.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend, documentation
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.