|
DeansFarm
|
November 29, 2017 at 9:05 am
I did the GetHub .httaccess fix nad added the REST API log. I continue to get that error and the log does not show anything at all. Am I missing something else? We’re on a VPS. Should I ask the host something? Our website is https://deansfarmmarket.com
|
|
Josh
|
November 29, 2017 at 9:15 am
Hi Dean,
Sometimes the Connection error is the result of a plugin conflict. In the troubleshooting guide, it explains what to do if you have the iThemes security plugin:
https://eventespresso.com/wiki/ee4-event-apps/#long-uri-strings
If you do not have a security plugin like iThemes security it may help to follow the general troubleshooting guide:
https://eventespresso.com/wiki/troubleshooting-checklist/
|
|
DeansFarm
|
November 29, 2017 at 9:53 am
I deactivated all the plugin and cut them on one by one. The only two that caused the error are WooCommerce and MailChimp for WooCommerce. I can live without the MailChimp, but we cannot abandon our store. Any idea what the issue is?
|
|
Josh
|
November 29, 2017 at 10:00 am
No idea because I have WooCommerce activated on a testing site and the Apps work there.
Can you try checking the REST API log entry for when you try the app with WooCommerce activated? There may be a specific error message that gets captured that will show what to check next.
|
|
DeansFarm
|
November 29, 2017 at 12:07 pm
Nothing shows up in the log at all when WooCommerce is activated. It’s as if it never gets the request.
|
|
Josh
|
November 29, 2017 at 12:19 pm
If that’s the case then you should make sure you have the current version of WooCommerce installed and if all else fails you can open a support ticket with WooCommerce:
https://woocommerce.com/contact-us/
|
|
DeansFarm
|
November 30, 2017 at 9:10 am
Please excuse my very limited knowledge of code, but I looked at the error log and this is what I get when I try to login to EE4 from my phone. Any ideas?
[30-Nov-2017 16:03:04 UTC] PHP Fatal error: Uncaught Error: Call to a member function get_page_permastruct() on null in /home/deansfarmmarket/public_html/wp-includes/link-template.php:357
Stack trace:
#0 /home/deansfarmmarket/public_html/wp-includes/link-template.php(320): _get_page_link(Object(WP_Post), false, false)
#1 /home/deansfarmmarket/public_html/wp-includes/link-template.php(144): get_page_link(Object(WP_Post), false, false)
#2 /home/deansfarmmarket/public_html/wp-content/plugins/woocommerce/includes/wc-page-functions.php(72): get_permalink(Object(WP_Post))
#3 /home/deansfarmmarket/public_html/wp-content/plugins/woocommerce/includes/wc-account-functions.php(30): wc_get_page_permalink(‘myaccount’)
#4 /home/deansfarmmarket/public_html/wp-includes/class-wp-hook.php(288): wc_lostpassword_url(‘https://deansfa…’)
#5 /home/deansfarmmarket/public_html/wp-includes/plugin.php(203): WP_Hook->apply_filters(‘https://deansfa…’, Array)
#6 /home/deansfarmmarket/public_html/wp-includes/general-template.php(508): apply_filters(‘lostpassword_ur…’, ‘https:/ in /home/deansfarmmarket/public_html/wp-includes/link-template.php on line 357
|
|
Tony
|
November 30, 2017 at 10:13 am
Hmm, so that error is thrown each time you try to log in and its not just shown once in the log?
|
|
DeansFarm
|
November 30, 2017 at 10:18 am
If I have WooCommerce activated that error shows in the error log if I try to login in from the EE4 mobile app. If I turn off (deactivate) WooCommerce the app will connect and no error is received in the log.
|
|
Josh
|
November 30, 2017 at 10:23 am
The stack trace shows a few functions where WooCommerce is interacting with WordPress core. Have you contacted WooCommerce for support? What this looks like is there’s some interference happening when the bundled Basic Authentication tries to authenticate the app.
|
|
DeansFarm
|
November 30, 2017 at 10:26 am
Yes, I submitted the same information on the WooCommerce support forum, but have not had any response from them.
|
|
Josh
|
November 30, 2017 at 11:28 am
The same symptom was reported here:
https://github.com/woocommerce/woocommerce/issues/8694
and it turned out to be a bug in the Yoast SEO plugin and was fixed. If you try temporarily switching to another theme, then have only WooCommerce and Event Espresso activated does the site allow the app to connect?
|
|
DeansFarm
|
November 30, 2017 at 11:52 am
We do not use Yoast SEO. So, I turned plugins off except for the EE4 ones. Swithched to Twenty-Seventeen theme and cut on plugins one by on and tested the mobile app till the login failed. Mobile app worked until WooCommerce was activated. I’m getting the same results on both Themes. I’m lost. We were relly looking forward to using the mobile app.
|
|
DeansFarm
|
November 30, 2017 at 12:43 pm
This thread may have something useful. https://github.com/WP-API/Basic-Auth/issues/33
Wish it were in laymen terms.
|
|
Josh
|
November 30, 2017 at 12:48 pm
I realize that you don’t use Yoast SEO, the reason I mentioned Yoast SEO was for clarity about the situation reported in similar issue. What could be happening is something similar within your site calling
current_user_can() too early.
A few ideas that may help:
1) Remove whatever you just added to .htaccess, it’s not helping nor is needed anyway.
2) You could try switching the option in WooCommerce > Settings > API so the REST API for WooCommerce isn’t enabled, then check to see if that makes a difference
3) You could try installing the Application Passwords plugin which does essentially the same thing as the bundled Basic Auth plugin within Event Espresso.
https://wordpress.org/plugins/application-passwords/
|
|
DeansFarm
|
November 30, 2017 at 1:08 pm
Thanks Josh. I turned off Application Passwords plugin and used my normal WP login credentials and the EE4 mobile app logged in perfectly. Not sure how that made a difference, but at least we can use the app now. Thanks again.
|
|
Josh
|
November 30, 2017 at 1:26 pm
The reason it made a difference is because there’s a bundled Basic Auth handler that’s built into Event Espresso 4. If Application Passwords is installed then the A.P. plugin will take over for Authenticating REST API calls from the app.
|
