{"id":79042,"date":"2012-05-31T10:00:41","date_gmt":"2012-05-31T14:00:41","guid":{"rendered":"http:\/\/wpmu.org\/?p=79042"},"modified":"2012-05-31T05:29:33","modified_gmt":"2012-05-31T09:29:33","slug":"easy-admin-notification","status":"publish","type":"post","link":"https:\/\/wpmudev.com\/blog\/easy-admin-notification\/","title":{"rendered":"Keep Your WordPress Clients in Check with Easy Admin Notification"},"content":{"rendered":"

\"EasyWorking with clients who are perhaps less WordPress savvy than you’d like them to be can be frustrating at times. They have a habit of fiddling where they should not fiddle. Under many circumstances, granting them limited access is the right thing to do.<\/p>\n

But there will always be a chance of them screwing something up, and that is where Easy Admin Notification<\/a> may be able to help. As you might expect, this plugin allows you to easily place a customized message within the WordPress backend.<\/p>\n

\"Easy
Like this.<\/figcaption><\/figure>\n

The settings give you some control over the message, namely:<\/p>\n

    \n
  1. Whether it is displayed as an error or notification<\/li>\n
  2. Whether the end user has an option to hide the message<\/li>\n
  3. Where the message is displayed (either all pages, or dashboard only)<\/li>\n<\/ol>\n

    There are numerous potential application for this plugin – keeping rogue clients in check is just one of them. What would be nice to see from this plugin is the ability to include messages on particular pages only – for instance, you could include a pre-publishing checklist on the post screen.<\/p>\n

    As it is, the plugin offers up functionality that is relatively easy to put in place manually, but it has the potential to offer a lot more. For that reason, I gave it a three star rating in the plugins repository<\/a>.\u00a0It is a brand new release, so here’s hoping that future updates will extend its functionality.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Sometimes all it takes is a simple message to dissuade a rogue client from inadvertently breaking their own site.<\/p>\n","protected":false},"author":84405,"featured_media":79044,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"blog_reading_time":"","wds_primary_category":0,"wds_primary_tutorials_categories":0,"footnotes":""},"categories":[4],"tags":[10211],"tutorials_categories":[],"class_list":["post-79042","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-plugins","tag-admin"],"_links":{"self":[{"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/posts\/79042","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/users\/84405"}],"replies":[{"embeddable":true,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/comments?post=79042"}],"version-history":[{"count":0,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/posts\/79042\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/media\/79044"}],"wp:attachment":[{"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/media?parent=79042"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/categories?post=79042"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/tags?post=79042"},{"taxonomy":"tutorials_categories","embeddable":true,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/tutorials_categories?post=79042"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}