bennieblvnco
Forum Replies Created
-
@thebengalboy I submitted a support ticket on Feb 1st. See #128259
Appreciate the quick response @thebengalboy .
I’ve done the following with no success:
1. Unchecked / unticked the show toolbar option under user profile
2. Confirmed that only Administrator is selected on the WPUF Show Admin bar settingSeparately, I’ve disabled WPUF to see if the Admin bar would go away for non-admin users – it did.
The solution appears to require the use of another plugin, which I’ve shared above.
I ended up installing the plugin called “Hide Admin Bar from Non-Admins“, which addressed the problem.
@damf77 Thank you for posting a workaround – I will implement it now.
@emazharulislam – Please advise as to when this issue will be resolved.
- This reply was modified 6 years, 1 month ago by bennieblvnco.
@emazharulislam You’re not listening… both @damf77 and I have the same issue – The latest update to the WP User Frontend plugin created the following problems.
1) The WordPress Admin panel /tool bar is NOW displayed to all users that are logged in, regardless of whether or not the tool bar setting is disabled.
2) The Post function is broken – when you click Post, a 404 error or Page Cannot Be Found error is displayed, which impacts Dokan Pro users too if they are running both plugins, which is what I’m doing.
The above two issues are as a result of the plugin update from January 31st or February 1st.
I have the same issue. Everything was fine until I updated to the latest version of WP User Frontend Pro. The only way to hide the wordpress nav bar is to deactivate the plugin – am running Dokan Pro as well. Please advise…
Hello @611shabnam,
Yes, could you please help me with hiding the contact information for the vendor and buyer on the aforementioned pages?
Thank you!
As I’ve stated in my initial post, I’ve only just installed Dokan, Dokan Pro and WooCommerce. All other plugins are disabled. I’ve already opened a support ticket as well.
Seeing as how I’m not the first person with this issue that you’ve supported before, please post the resolution to this issue here, so that others may benefit from the solution as well.
Seeing as how this is a prevalent issue, it would be wonderful if you could post the solution for all to see.
How was this problem resolved? Is it an issue with the code out of the box, or is it truly a conflict with the theme?