Ulrich Pogson
Ulrich Pogson
  https://wordpress.org/plugins/admin-menu-manager/
- `[email protected]` This package has been deprecated - `[email protected]` This package has been deprecated, please use `@wordpress/eslint-plugin` or `@wordpress/scripts` - Upgrade to Basel 7.x
 
When I tried to activate the plugin I got the following error. > The theme you are currently using does not support the Message Board plugin. Please activate a theme...
I have read the [Reasons for a standard](https://github.com/justintadlock/content-type-standards#reasons-for-a-standard) but I still see a few issues. @reidpeifer brought up some interesting points in his https://github.com/justintadlock/content-type-standards/issues/4#issuecomment-50567713 Here are some points that I...
Package.json ```json "eslintConfig": { "extends": "plugin:wordpress/recommended", "plugins": [ "wordpress" ] }, "eslintIgnore": [ "js/**.min.js" ], ``` When I run the `eslint js/**` on `_s` I get the following error. ```...
Split off from #744 `Expected next thing to be an escaping function (see Codex for 'Data Validation'), not 'get_bloginfo'` Escaping of [`bloginfo`](https://github.com/WordPress/WordPress/blob/4.7-branch/wp-includes/default-filters.php#L99) via a filter. `get_bloginfo( 'name' )` should give...
Once https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/pull/633 has been merged I will work on a list of private WordPress functions that should not be used by themes and plugins. https://codex.wordpress.org/Category:Private_Functions and `WP_Internal_Pointers` which is not...
Split off from #744 With the following example we can be 100% sure that it is a correct error because it is a know WordPress function. `Expected next thing to...