Support » Plugin: Adminimize » Upgrade to 1.11.1 Issue – Prevents Users View/Edit Pages (prior worked fine)
Upgrade to 1.11.1 Issue – Prevents Users View/Edit Pages (prior worked fine)
-
Great plugin by the way! Here’s the issue synopsis, specific to what my sites are experiencing after upgrading to 1.11.1.
All my clients have editor role only with Adminimize settings so they can view all pages (by clicking Pages in menu. But they DO NOT have ability to ADD NEW PAGES
ISSUE
After upgrade to 1.11.1, they can no longer even access the pages (by clicking on Pages) , they all get the “Cheatin’ uh? Sorry can’t access page etc..)
WORKAROUND
Either downgrading back to 1.10.6 resolves the issue, or I have to uncheck the “ADD NEW PAGES” in Adminimize . But of course that defeats the purpose and allows them to create new pages.
Need any more info, let me know.
p.s. Seems like there’s been some decent workarounds/modifications regarding permission issues folks are having to do after upgrading 1.11.1. That will be quite a pain on dozens of sites if that’s the case.- This topic was modified 7 years, 3 months ago by nwdwp.
-
The new version have also new function to prevent access of pages. The plugin seems a bug with custom post types for this function. But you can deactivate this function, use the plugin settings area, last line to deactivate this functionality.
Seems to be the case with WooCommerce > Products as well. The same error is presented.
In 1.11.1 the last line in Plugin Settings reads “Activate this option to allow access to pages of the back end, even if it’s hidden to a user role. ”
That works as a workaround for now, but ideally all pages wouldn’t be accessible.
Hi Folks, due to the number of sites I built, I have to stay at the previous version. It’s not feasible to edit a line for them all. And I have multiple with the WooCommerce usage as well where this would also be a problem.
@bueltge, will this been looked at in a near future version so pages can still be edited while “Add New Pages” is still disabled?
Thanks for the responses, all appreciated!No, the deny allow for pages should only works for the pages there are hide in the settings of Adminimize, not more.
I am getting this error – Cheatin’ uh? Sorry, you are not allowed to access this site. Had to disable plugin after recent update. Unable to access woo commence products.
When will this be fixed? Please let me know
In the next version, patch release – I hope.
But you can easily deactivate this function, in the plugin settings area, last entry.A new version is ready for release, but a test would really fine. If you can test it, please do it and give me feedback.
The download is here: https://github.com/bueltge/Adminimize/releases/tag/1.11.2-RC1
Overwrite the current plugin installation and test.Thanks.
@bueltge, Installed 1.11.2-RC1 and tried it. Same result. For reference, editor role is restricted as follows:
menu > Pages unchecked
menu > Pages – Add New (checked/deactivate for editor role). As longs as the Add New is checked/dactivate for editor role, editor role users continue to get Cheatin huh when they click on Pages.
Thanks for checking into it.
-JHave you active another menu item for this role with the slug
edit.php?post_type
?There are others that use that slug (Testimonials, Projects, DIVI menu items) but even if I uncheck all those and just have the Add New checked its permission denied for root page menu item.
• Pages Group(edit.php?post_type=page)
— All Website Pages (Slug: edit.php?post_type=page)[__5]
— Add New (Slug: post-new.php?post_type=page)[__10]
It appears that if ANY item that hasedit.php?post_type
selected (to be hidden by Adminimize), it blocks every menu page with the slugedit.php?post_type
; which unfortuantly could be multiple depending on theme/plugins etc..
Hope this info helps.Please test again with the RC2 version – https://github.com/bueltge/Adminimize/releases/tag/1.11.2-RC2
Thanks four your help.
@bueltge, Good news, the RC2 did work. It removed the menu > Pages – Add New option, yet allowed main menu > page to be clicked and access all pages.
One note though, it did leave the “Add New” button on the pages summary as well as on the individual pages. But when clicked, it gets “cheatin huh”, which is expected.
I want it there for blog posts types of course, but not pages so I just set the following globally which removes the “add new” from page post types.
.post-type-page .page-title-action
I suppose you could implement that under the Pages section so it can just be a “checkbox” to remove “Add New” buttons on pages 🙂Thanks a lot again.
Great testing feedback. The “Add new” button on the page is much more different. If I implement this in depends of the menu item, it is much more complex and not really solid, works only if the class, id of this html area have no changes.I think much more easier and solid, easier to maintain is this via section post or page or other post types.
Sounds good. I think with the latest RC2, if released it resolves the issue been experiencing. I marked this as resolved.
- The topic ‘Upgrade to 1.11.1 Issue – Prevents Users View/Edit Pages (prior worked fine)’ is closed to new replies.