genyus

@arielk-1 Thanks! Latest versions of Elementor and Pro are now working properly with WP 5.5 for me

@mschouten I just updated to 1.0.4 and can confirm that it fixes the bug as reported, so grab the latest and you should be all set.

Thanks for addressing this, @mplusb

Sure, I will try my best.

1. You need to check if this scenario even applies to your site. The easiest way is to navigate to a URL on your site, e.g. https://mysite.com/about-us and see if a trailing slash is appended, i.e. the final URL ends up looking like https://mysite.com/about-us/.
   If it does, read on. If it doesn’t, this solution won’t apply to you and you should try the other fixes that have been proposed elsewhere.
2. You’ll have to ascertain exactly how your trailing slashes are being enforced and this may require someone with with technical expertise. There are a few ways this may be implemented: .htaccess file configuration, PHP code or even with a custom plugin. I would expect .htaccess to be the most likely and is the mechanism that was in place on my own site. If you have custom code or a plugin managing this, then you’ll have to implement a relevant solution that I can’t provide here.
3. Assuming .htaccess is the mechanism in use, simply add a RewriteCond condition excluding the /wp-json path to the relevant RewriteRule: RewriteCond %{REQUEST_URI} !^/wp-json/

@takayukister please see my comment on this thread. while the switch to REST API in 4.8 seems to have presented a number of common conflicts with themes, security plugins, etc – the cause in my case is one that I suspect might affect a fair few number of other sites, but isn’t easy to spot and I haven’t seen mentioned anywhere else. Perhaps there should be a “Known Issues” list or FAQ to address some of these factors?

Tested your contact form, seems to work fine

I discovered a different cause and solution for this problem, which I’m sharing as it may benefit others with a similar setup to myself.

After trying all the proposed fixes above without success, I was examining the AJAX request using the browser developer tools and noticed that the request to /wp-json/contact-form-7/v1/contact-forms/[ID]/feedback was being submitted as a GET, although the code indicated it should be sent as a POST.

Some Googling led me to this article: https://blog.arvixe.com/why-is-jquery-ajax-sending-a-get-instead-of-a-post/ and I realised that my site was indeed appending a trailing slash, due to the configuration I have in place to maintain consistent URLs.

Once I modified the relevant RewriteRule to exclude any API URLs, my forms started working as expected.

Hi @corylamleorg,
Apologies for the slow reply. I installed the 1.2.9 update and while it was then able to complete the validator scan, package builds still failed with the same error.

After some further experimentation, I found an out-of-memory error being raised and realising that WordFence was activated (this being an instance migrated from a live site), I disabled that and then all was good!

Thanks for your assist, much appreciated.