Skip to content
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

Disable WordPress Events and News Dashboard Widget #172

Open
1 task done
ipajen opened this issue Nov 11, 2024 · 1 comment
Open
1 task done

Disable WordPress Events and News Dashboard Widget #172

ipajen opened this issue Nov 11, 2024 · 1 comment
Labels
enhancement New feature or request needs triage needs to be discussed and worked on

Comments

@ipajen
Copy link
Collaborator

ipajen commented Nov 11, 2024

I have checked the following:

  • I've searched existing issues and found nothing related to my issue.

Describe the feature you want to add

I would like to have an option in AspireUpdate to disable the WordPress Events and News Dashboard Widget, similar to the functionality in the disable-wordpress-events-and-news-dashboard-widget plugin. This setting would allow users to toggle the widget on or off, with the default set to showing the widget (not ticked)

Option to add also a new Configuration Parameter for wp-config

The purpose of this feature is to prevent calls to WordPress.org, which may involve personal data. Until AspireCloud is equipped to manage these calls, having the option to disable them provides more control and avoids unnecessary content from official WordPress channels.

Mockups or Images of the feature

new setting
Settings

before
before

after
after

@ipajen ipajen added enhancement New feature or request needs triage needs to be discussed and worked on labels Nov 11, 2024
@asirota
Copy link
Member

asirota commented Nov 11, 2024

There are other plugins that allow these options to be set as you indicated. I think we need to be careful about turning on an option that calls w.org because that may change and we will need to catch up with WordPress team decision as to where/when Wordpress.org is called. This is better done as part of our telemetry documentation work to start identifying where w.org or api.org calls are made and explicitly letting customers who use AspirePress suite of software to determine what they would like to do.

Setting this at the AspireUpdate level is probably not the right place to do this. I would think this sort of policy should be better set at the AspireCloud level which would receive the telemetry information from WordPress installs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs triage needs to be discussed and worked on
Projects
None yet
Development

No branches or pull requests

2 participants