PHPackages                             upperdog/hide-updates - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. upperdog/hide-updates

ActiveWordpress-plugin

upperdog/hide-updates
=====================

This plugin hides update notifications for WordPress core, plugin, and theme updates in WordPress admin for all users except first registered user or specified users.

v1.1.5(6y ago)5523GPL-2.0-or-laterPHP

Since Oct 21Pushed 5y ago2 watchersCompare

[ Source](https://github.com/Upperdog/hide-updates)[ Packagist](https://packagist.org/packages/upperdog/hide-updates)[ Docs](https://github.com/upperdog/hide-updates)[ RSS](/packages/upperdog-hide-updates/feed)WikiDiscussions master Synced 3d ago

READMEChangelogDependencies (1)Versions (8)Used By (0)

Hide Updates
============

[](#hide-updates)

This plugin hides update notifications for core, plugin, and theme updates in the WordPress admin. It's useful for developers and agencies who manage updates through Composer or remote management services like ManageWP, and therefore wants to hide update notices for other users.

Features
--------

[](#features)

- Hides Wordpress core update notices.
- Hides plugin update notices.
- Hides theme update notices.
- Hides updates link in admin menu and admin bar.
- Blocks access to the updates page for users who are not allowed to see updates.
- Enables developers to specify which users can see updates.

Worth noting
------------

[](#worth-noting)

This plugin is intended for developers and agencies who have good reasons for hiding the updates, for example if they manage updates through Composer or remote management services like ManageWP. This plugin has been tested with ManageWP and ManageWP needs to connect to the site with a user account that is allowed to see updates.

Specify who can see updates
---------------------------

[](#specify-who-can-see-updates)

By default, the plugin allows the first registered user (the one who installed the site) to see updates. Developers can use the `hide_updates_allowed_users` filter to specify which users are allowed to see update notifications.

The following example will allow only users with usernames bill and melinda to see updates:

```
function site_hide_updates_allowed_users() {
    $allowed_users = array( 'bill', 'melinda' );
    return $allowed_users;
}
add_filter( 'hide_updates_allowed_users', 'site_hide_updates_allowed_users' );

```

Manual installation
-------------------

[](#manual-installation)

1. Upload the `hide-updates` directory to the `/wp-content/plugins/` directory.
2. Activate the plugin through the 'Plugins' menu in WordPress.

Frequently Asked Questions
--------------------------

[](#frequently-asked-questions)

### Who is this plugin for?

[](#who-is-this-plugin-for)

This plugin is aimed for developers and agencies who manage core, plugin, and translation updates through Composer or remote management services like ManageWP.

### Why would you want to hide updates?

[](#why-would-you-want-to-hide-updates)

If you're a developer or agency responsible for updating client sites, you may want to hide updates for other users who should not install updates.

### Can I choose to hide only some types of updates?

[](#can-i-choose-to-hide-only-some-types-of-updates)

No. All updates will be hidden.

Changelog
---------

[](#changelog)

### 1.1.6

[](#116)

- Release date: 2020-
- Simplify return statement in allow\_current\_user(). Thanks Vincent Klaiber (@vinkla) for the help!
- Minor refactoring and coding standards overhaul.

### 1.1.5

[](#115)

- Release date: 2019-12-18
- Minor refactoring and coding standards overhaul.
- Align Github and WordPress.org version release numbers.

### 1.1.4

[](#114)

- Release date: 2019-05-28
- Check if user is logged in before enqueuing plugin CSS. Thanks Vincent Klaiber (@vinkla) for the help!

### 1.1.3

[](#113)

- Release date: 2018-10-28
- Avoid error if default user with ID 1 doesn't exist.

### 1.1.2

[](#112)

- Release date: 2018-10-21
- Add first registered user (usually the one who installed the site) as default user allowed to see updates.
- Add more precise CSS selector for hiding plugin updates in admin menu to avoid breaking other plugins using the .update-plugins class on other notifications.

### 1.1.1

[](#111)

- Release date: 2018-10-21
- Remove include of wp-includes/pluggable.php to be able to use wp\_get\_current\_user(). Unnecessary to include file.

### 1.1

[](#11)

- Release date: 2018-10-21
- Add filter to define users allowed to see updates.
- Hide update notifications using CSS to enable usage of remote management services like ManageWP and others. Previous solution used pre\_site\_transient\_update\_\* filters and nulled all values making it impossible for remote management services to read updates.

### 1.0

[](#10)

- Initial release.

###  Health Score

31

—

LowBetter than 68% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity15

Limited adoption so far

Community12

Small or concentrated contributor base

Maturity66

Established project with proven stability

 Bus Factor1

Top contributor holds 97.7% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~84 days

Recently: every ~105 days

Total

6

Last Release

2340d ago

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/3427505?v=4)[Upperdog](/maintainers/upperdog)[@Upperdog](https://github.com/Upperdog)

---

Top Contributors

[![gesen](https://avatars.githubusercontent.com/u/2316984?v=4)](https://github.com/gesen "gesen (42 commits)")[![vinkla](https://avatars.githubusercontent.com/u/499192?v=4)](https://github.com/vinkla "vinkla (1 commits)")

---

Tags

wordpressupdates

### Embed Badge

![Health badge](/badges/upperdog-hide-updates/health.svg)

```
[![Health](https://phpackages.com/badges/upperdog-hide-updates/health.svg)](https://phpackages.com/packages/upperdog-hide-updates)
```

###  Alternatives

[wp-media/wp-rocket

Performance optimization plugin for WordPress

7431.3M3](/packages/wp-media-wp-rocket)[roots/wp-stage-switcher

WordPress plugin that allows you to switch between different environments from the admin bar

382435.0k3](/packages/roots-wp-stage-switcher)[vinkla/wordplate

The WordPlate boilerplate

2.2k5.1k](/packages/vinkla-wordplate)[pods-framework/pods

Pods is a development framework for creating, extending, managing, and deploying customized content types in WordPress.

1.1k1.7k](/packages/pods-framework-pods)[mindkomm/timmy

Advanced image manipulation for Timber.

17735.6k](/packages/mindkomm-timmy)[wp-pay-extensions/gravityforms

Gravity Forms driver for the WordPress payment processing library.

1133.3k2](/packages/wp-pay-extensions-gravityforms)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)