|
He Zhengrui
|
August 18, 2022 at 2:32 am
Hi there!
I am currently facing this issue on my attendee mover, everything else on EE is working perfectly.
I’ve tried troubleshooting and found that the link (error2 picture) is not reflecting the latest version of EE(I’m on 4.10.38, the link is 4.8.36)
Any possible solutions?
|
|
He Zhengrui
|
August 18, 2022 at 2:33 am
Updated picture links as it seems to be broken
https://ibb.co/SRGRMrz
https://ibb.co/92qtYMc
|
|
Tony
|
August 18, 2022 at 6:14 am
I’ve tried troubleshooting and found that the link (error2 picture) is not reflecting the latest version of EE(I’m on 4.10.38, the link is 4.8.36)
4.8.36 is the API version in that case, it should work fine.
Each time there is a change within the EE REST API we make it in the current version number of EE, meaning if we completely changed the output in say:
/wp-json/ee/v4.10.38/events/ (which doesn’t exists, this is just an example)
You could still use:
/wp-json/ee/v4.8.36/events/
to get the current output.
—
Having said that, are you using CloudFlare?
Have you checked the servers error logs for any errors during the above request?
|
|
He Zhengrui
|
August 18, 2022 at 6:55 am
Hi Tony,
I found the error code; it’s
net::ERR_HTTP2_PROTOCOL_ERROR 200
Again, scratching my head after troubleshooting for aeons :/
|
|
Tony
|
August 18, 2022 at 7:07 am
This reply has been marked as private.
|
|
He Zhengrui
|
August 18, 2022 at 7:29 am
Where are you getting this from?
I have gotten the error from before I moved to CloudFlare actually, yes it’s access log and output from devTools in Chrome
Check the servers PHP error logs, anything there? The above is not from the servers error logs, looks like an access log?
[18-Aug-2022 13:23:16 UTC] PHP Notice: Trying to get property 'ID' of non-object in /home/thebeve1/public_html/wp-content/plugins/wp-fusion/includes/integrations/class-ultimate-member.php on line 703
[18-Aug-2022 13:23:19 UTC] PHP Notice: Undefined index: info-url in /home/thebeve1/public_html/wp-content/plugins/ithemes-security-pro/lib/updater/updates.php on line 136
[18-Aug-2022 13:23:19 UTC] PHP Notice: Undefined index: info-url in /home/thebeve1/public_html/wp-content/plugins/ithemes-security-pro/lib/updater/updates.php on line 136
could it possibly be my .htaccess that’s preventing access to that link? because my website security plugin is active
|
|
Tony
|
August 18, 2022 at 7:39 am
I have gotten the error from before I moved to CloudFlare actually
Ok, first step.
Disable Cloudflare so we can see the error from the server itself, not from CloudFlare.
net::ERR_HTTP2_PROTOCOL_ERROR 200
The problem with this is it doesn’t give you any indication of why so the access logs don’t help in this case.
could it possibly be my .htaccess that’s preventing access to that link? because my website security plugin is active
Possibly, yes. IRght now i could literally be anything.
There are multiple reasons for Cloudflare to throw error 520, so start by disabling it and viewing the site directly.
The PHP notices displayed above won’t be causing the above.
|
|
He Zhengrui
|
August 18, 2022 at 8:45 am
Strange…
I’ve just tried another endpoint here and it’s working.
I’ve disabled cloudflare and the error persists.
i’ve also flushed my .htaccess and disabled my security plugin for now, to no avail
|
|
He Zhengrui
|
August 18, 2022 at 8:52 am
I know this is also separate but strangely the RSS feed also stopped working since awhile back and I thought it was nothing
https://ibb.co/XydN2wM
|
|
Tony
|
August 18, 2022 at 9:08 am
I know this is also separate but strangely the RSS feed also stopped working since awhile back and I thought it was nothing
Yeah, thats unrelated, it’s the connection to our RSS feed failing.
We can revisit that later, it won’t be causing any issues on your site.
—
For the current issue, enable WP_DEBUG on the site plz
In your wp-config.php file you’ll have:
define( 'WP_DEBUG', false );
Change that too:
define( 'WP_DEBUG', true );
Or, swap it for the code her to enable logging:
https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug
|
|
He Zhengrui
|
August 18, 2022 at 9:16 am
define( 'WP_DEBUG', true );
if ( WP_DEBUG ) {
@error_reporting( E_ALL );
@ini_set( 'log_errors', true );
@ini_set( 'log_errors_max_len', '0' );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
define( 'CONCATENATE_SCRIPTS', false );
define( 'SAVEQUERIES', true );
}
define('EE_REST_API_DEBUG_MODE',true);
define( 'MULTISITE', true );
define( 'SUBDOMAIN_INSTALL', true );
define( 'DOMAIN_CURRENT_SITE', 'thebeverageclique.com' );
define( 'PATH_CURRENT_SITE', '/' );
define( 'SITE_ID_CURRENT_SITE', 1 );
define( 'BLOG_ID_CURRENT_SITE', 1 );
define('COOKIE_DOMAIN', $_SERVER['HTTP_HOST'] );
I already have this in my wp-config and it’s above
/* That's all, stop editing! Happy publishing. */
I just tried disabling all the plugins on my site and only leaving EE
Not sure if it’s notable, but when I disabled all plugins on my site and reenabled it I was presented with this error
I have since reinstalled the plugin and it’s okay now, but the same root issue persists
|
|
Tony
|
August 18, 2022 at 9:19 am
define( 'WP_DEBUG_DISPLAY', false );
Temporarily change that to true so I can check the output.
Why do you have EE_REST_API_DEBUG_MODE enabled all the time?
|
|
He Zhengrui
|
August 18, 2022 at 9:25 am
Temporarily change that to true so I can check the output.
Done!
Why do you have EE_REST_API_DEBUG_MODE enabled all the time?
I just realized.. I turned it to false and it worked.
I recalled why I have it on, it was on a separate thread I had with you and I was embarking on building the code to interact with other sites 🙁
my apologies for the silly mistake :sweat:
thanks Tony this is now resolved, hopefully anyone who chanced upon this will remember to turn off debugging
|
|
Tony
|
August 18, 2022 at 9:25 am
I’m not sure what you’ve changed as of now, but just so you know currently I can now load the /events/ endpoint.
(Edit – cross-post with the above 🙂 )
|
|
Tony
|
August 18, 2022 at 10:38 am
Yeah on checking into this EE_REST_API_DEBUG_MODE EE adds some debug headers to the request.
In some instances the array it is using to loop over and add headers from can have spaces in the keys, those are causing the above error.
A fix for this will be included in the next version of Event Espresso although I don’t recommend leaving EE_REST_API_DEBUG_MODE enabled unless it is needed for debugging, then disabled again.
Nice find and I’m glad its working for you now 🙂
|
