May 20, 2015 at 10:23 am 44557
|towhid||Hi there, I am using Ignitewoo Vendors Stores with WP User front end pro and was wondering if you had any advice for compatibility? I think there may be a conflict because both plugins allow backend access. The Vendors Stores plugin backend access does not work when WP User front end pro is enabled but does work when disabled. I am happy to disable WP User front end pro's backend access for users, and instead have them use Vendors Stores backend as users need to be able to configure their payment settings. I have tried disabling editing for users and chosen > admin area access > admin only, but the problem still persists. Do you have any advice, or is there some custom CSS code to disable backend access for users. I have contacted Ignitewoo about this problem as well. Thanks for your help in advance. Regards, Michael|
May 21, 2015 at 1:33 pm 44773
Make sure you login as a contributor.
I have disabled admin area access > admin only, After login as a contributor I was not allowed to see the admin bar for me. This proved me it is working for me.
Please check yourself and let me know the result.
May 22, 2015 at 2:25 pm 44880
Thanks for your email.
Therefore, it seems I have disabled the backend for WP User Front End Pro successfully. However it is still preventing the backend access for the Vendors Stores plugin.
May 23, 2015 at 4:41 pm 44964
Can you please provide me a screenshot.
May 23, 2015 at 6:44 pm 44982
1 – WPUF general settings
Let me know if you need anything else.
May 24, 2015 at 1:24 pm 45046
I did not yet get any screenshot. If you send screenshot in this forum I can see it immediately.
May 24, 2015 at 2:34 pm 45049
Thanks for the image solution. Here are the URL’s
May 27, 2015 at 4:28 pm 45343
Please provide your login details by using this form: http://wedevs.com/provide-login-details/. I will have a look what is going wrong.
Thank you 🙂
May 27, 2015 at 5:24 pm 45352
I thought if deactivating the back-end wasn’t working, maybe allowing all access to the back-end would work so I changed admin area access > default, and that fixed the issue 🙂
If others have plugin conflicts with back-end access you may be able to recommend this too.
May 27, 2015 at 5:36 pm 45354
|towhid||This reply has been marked as private.|