PPPlan or PPCaps Conflicting with ASE Hide Admin Notices

Hi There! I’m experiencing what appears to be a conflict with PublishPress Planner AND/OR PublishPress Capabilities (free versions of both) and Admin & Site Enhancements (aka ASE, also free version). Within ASE, I’ve got the Admin Interface > Hide Admin Notices toggled ON. This function of ASE works perfectly on all Admin pages EXCEPT several PublishPress-related Admin pages. I suspect you’ve got some CSS class issues. Specifically publishpress-admin and/or press shack -admin-wrapper classes seem to be conflicting with ASE’s asenha-admin-notices-menu class. Screenshot below. I mention PublishPress Capabilities as potential root cause, as the Pro Version seems to have overlapping functionality to ASE’s Hide Admin Notices function. However, because I’m on the free version of PPCap, I can’t access the screens displayed in PublishPress Capabilities documentation. More Info: This is most evident on all PP Planner and PP Status admin pages that I’ve got enabled. It does not manifest itself on PP Capabilities nor PP Future admin pages. Hi @seandbf , Thank you for using our plugin. Could you try to disable Admin Notice in PublishPress Capabilities to see if a similar function is perhaps conflicting with each other? Hi Riza, Admin Notices (in PP Cap => Dashboard) was always turned OFF, as I have been a longtime ASE user. I suppose THAT is why I wasn’t seeing an “Admin Notices” tab in PP Cap => Settings (rather than my earlier suspicion of Free/Paid). Upon turning ON Admin Notices in PP Cap => Dashboard, I now see “Admin Notices” tab in PP Cap => Settings. Upon checking ALL checkboxes on that Settings Tab, my Admin Notices are correctly collapsed into the Admin Bar. This holds true throughout the various Admin screens, including regular Posts, Pages, etc. AND PublishPress-related plugins Settings, and ASE’s admin screens. I suppose I can use PP Cap’s Hide Admin Notices functionality over ASE’s, but I am bothered by PP’s overly broad behavior when Admin Notices is OFF in PP Cap => Dashboard. Thanks for your insight! Sean Hi @seandbf , Could you share more specific information regarding “ I am bothered by PP’s overly broad behavior when Admin Notices is OFF in PP Cap => Dashboard “? Are you trying to use both PublishPress Capabilities features and Admin & Site Enhancements (aka ASE, also free version). If so, which features are you concerned about, or which you still do not find the result to be as you expected? Hi @rizaprihananto , Thank you for asking about the clarification. I’m NOT trying to use BOTH PublishPress Capabilities feature to Hide Admin Notifications AND ASE’s similar functionality at the same time. While I had PPCap’s “Hide Admin Notifications” turned OFF but ASE’s similar function ON, I’d expect PPCap’s behavior to passively defer to ASE’s “Hide Admin Notifications” feature’s ON setting, and still NOT display them. Instead, PPCap seems to Force-SHOW Admin Notifications (but only on most PP Admin screens) if you’re not using PPCap’s (and only PPCap’s) “Hide Admin Notifications” function. I hope this clarifies the problem for you. Thanks! Sean Hi @seandbf , I want to clarify, in PublishPress Capabilities, the feature is called “Admin Notice”, not “Hide Admin Notification”. Did you intend to turn off Admin Notice in PublishPress or turn off “Hide Admin Notification”? Because the result will be different, if you turn off the “Hide Admin Notification” feature, it means that you allow the system to show the Admin Notification. However, if you turn off “Admin Notice”, it means that the notification will be off. @seandbf Thanks for using several PublishPress plugins. This is something we’ve tested carefully but haven’t been able to replicate yet. If there are clear steps to reproduce this, we’ll proceed. But it’s difficult for us to spend too much time tracking down relatively minor plugin conflicts like this. Thanks, @stevejburge and @rizaprihananto . I understand the challenge in replicating challenges, and I apologize for my lack of precision in terminology. I just attempted to replicate (and record precise steps for doing so), and I, too, was unable to recreate the original problem I described. I do notice that at least 2 minor revs of ASE have been released since I originally posted this issue ( https://www.wpase.com/documentation/changelog/ ), so I will presume that something in one of those revs of ASE removed the suspected conflict with PublishPress Capabilities. Thanks!