infprt

Reinstalled woocomerce, this time on http connection. It did change the value of SITE URL to http, making it match the HOME URL value, but it did not resolved the issue. Non admin users get redirected from wp-admin to my-account (or a blank page is displayed, because if you uninstall woocomerce the right way the page assigned to my-acount should have become undefined).

Installed version 2.3.5 and it works very well so far, except it shows the warning messages to all users (like install woocomerce pages and recommended pulgins), which is kind of sloppy. Only users who can act upon warnings should see such warnings.

I already spotted which files have changed from 2.3.5 to 2.3.7 and which changes were made but I’ll need to get a hold on a local machine (and some time) to mess with the files and see if there’s a quick fix.

Here’s the file changes that might be responsible for the issue:

wp-content/plugins/woocommerce/includes/class-wc-session-handler.php

ver2.3.5
line 70: add_action( ‘clear_auth_cookie‘, array( $this, ‘destroy_session’ ) );
line 177: N/A

ver2.3.7
line 70: add_action( ‘wp_logout‘, array( $this, ‘destroy_session’ ) );~
line 177: $this->_dirty = false; // Mark session clean after saving

wp-content/plugins/woocommerce/includes/admin/class-wc-admin.php

ver2.3.5
line 95: if ( ‘yes’ == get_option( ‘woocommerce_lock_down_admin’ ) && ! is_ajax() && ! ( current_user_can( ‘edit_posts’ ) || current_user_can( ‘manage_woocommerce’ ) ) && basename( $_SERVER[“SCRIPT_FILENAME”] ) !== ‘admin-post.php’ ) {
96 $prevent_access = true; 96 $prevent_access = true;

ver2.3.7
line 95: if ( ‘yes’ === get_option( ‘woocommerce_lock_down_admin’, ‘yes’ ) && ! is_ajax() && ! ( current_user_can( ‘edit_posts’ ) || current_user_can( ‘manage_woocommerce’ ) ) && basename( $_SERVER[“SCRIPT_FILENAME”] ) !== ‘admin-post.php’ )

this one is odd, seems like a missing closing div tag (haven’t checked full file for html errors though!):
wp-content/plugins/woocommerce/includes/admin/class-wc-admin-profile.php

ver2.3.5
line 250:
<div class=”clear”>
<?php _e( ‘Permissions:’, ‘woocommerce’ ); ?><span id=”woocommerce_api_key_permissions”><select name=”woocommerce_api_key_permissions” id=”woocommerce_api_key_permissions”>

ver2.3.7
line 250:
<div class=”clear”></div>
<?php _e( ‘Permissions:’, ‘woocommerce’ ); ?><span id=”woocommerce_api_key_permissions”><select name=”woocommerce_api_key_permissions” id=”woocommerce_api_key_permissions”>

wp-content/plugins/woocommerce/includes/admin/class-wc-admin-menus.php

ver2.3.5
line 66: add_submenu_page( ‘woocommerce’, __( ‘Reports’, ‘woocommerce’ ), __( ‘Reports’, ‘woocommerce’ ) , ‘view_woocommerce_reports’, ‘wc-reports’, array( $this, ‘reports_page’ ) );

ver2.3.7
line 66: if ( current_user_can( ‘manage_woocommerce’ ) ) {add_submenu_page( ‘woocommerce’, __( ‘Reports’, ‘woocommerce’ ), __( ‘Reports’, ‘woocommerce’ ) , ‘view_woocommerce_reports’, ‘wc-reports’, array( $this, ‘reports_page’ ) );}

Other files were changed but these seem to be the sensitive ones regarding the problem. I’ll post any findings if I can find some time to run tests later on. Until then or woocommerce comes up with an update, I’ll be sticking to 2.3.5.

@sarangan12
There’s nothing wrong with the users of my site and their capabilities, I will not change them.

There’s also nothing wrong with my admin user, I always have admin/dashboard access. It’s the lower roles that get redirected from wp-admin to my-account.

Thus, changing the record of wp-capabilities as you suggest, is not going to solve anything unless I want all the users of my site to become admins, which I don’t want.

Even if I were to to make the changes you suggest, I’m not sure they are correct since most of the entries you write about are serialized in the BD.

I marked version 2.3.7 of woocommerce as being broken with WP 4.1.1 and will install and test woocommerce 2.3.5, as OP says it works.

—
EDIT: I found something odd I will test out. When going through threads searching for solutions I noticed that some people’s HOME URL and SITE URL (as displayed by woocommerce>system status) are the same, and mine’s are not. My HOME URL is HTTP while the SITE URL is HTTPS. I was on https when I installed woocommerce, although I later unchecked any options to force https on checkout or login, dunno if this affected it.

I’ll:
– see if I can mannually change SITE URL from HTTPS to HTTP and check if it has any impact.
– reinstall woocomerce, this time on http connection, and see what happens

I have the same issue, I never had woocommerce installed before. If I activate it, all my users can’t access any wp-admin page, they get redirected to my-account page (or whatever I define as the account page). My users were able to access wp-admin to post and access they account information, with woocommerce active they can’t post or access wp dashboard.

I use different plugins than OP for similar functions and I tried disabling them all except woocommerce but the problem still occurs, so I don’t think is a plugin conflict. Anyways, here are mine:

Adminimize
amr shortcode any widget
Capability Manager Enhanced
Contact Form 7
JP Widget Visibility
WPBakery Visual Composer
MailChimp for WordPress Lite
Types – Complete Solution for Custom Fields and Types
W3 Total Cache
WooCommerce
Wordfence Security
WordPress SEO
WordPress Social Login
WP Crontrol
WP User Avatar

Hello,

first of all I am very thankful about your work developing such a useful plugin, thank you!

I’ve not completely moved to qtransX due to this particular issue with visual composer but I hope to move soon as I like some of the improvements of qtransX over mqtrans.

I’ve been trying this and seems to work for the time being:
keep mqtrans installed but not active. Deactivate qtransX and switch to mqtrans if I need to edit a page. I only use visual composer for pages and most of my content are posts so this is minimal.

Anyone doing the same? Got a different experience?

+1

“I always get an error message in my WP admin concerning incompatibility with the XML Sitemap plugin. Even after I set the settings in the Yoast plugin to NOT create any XML Sitemaps, I still get this error message.”

Well this is quite awkward and reenforces the opinion I had about yoast when I first tried their plugin a couple of months ago. I was trying to give another go to yoast now as I finally got rid of jetpack and need something to manage my OG tags but it seems yoast are still full of themselves (in a bad way).

They diss qtranslate just because they’re not “particularly fans of it”, it seems they just bad/lazy coders or think their coding is so great everyone has to follow the same guide lines as they do.

I use Google XML Sitemaps plugin by Arne Brachold and it’s amazing! got it working flawless with qtranslate on pre-path mode and it gives multiple sitemaps accordingly to languages. Arne Brachold made it work with qtranslate so yoast excuses are just that, excuses.

So it seems I have to find OG management elsewhere as I do not wish to use yoast to manage my sitemaps and it seems they still like to force themselves onto people who use their plugins.