You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 23, 2024. It is now read-only.
The text was updated successfully, but these errors were encountered:
kmanijak
added
priority: high
The issue/PR is high priority—it affects lots of customers substantially, but not critically.
category: tests
and removed
priority: high
The issue/PR is high priority—it affects lots of customers substantially, but not critically.
labels
Jan 25, 2023
I managed to run the tests and overcome the issue, but with a weird manual step as per Stack Overflow comment:
Go to admin, settings, permalinks, choose "Post Name"
Click "Save Changes"
After this step, http://localhost:8889/wp-json/* endpoints wouldn't return 404 anymore and the tests are running normally.
The weirdest thing, though, was that "Post Name" was already chosen in the admin. So I didn't change the setting and just clicked "Save Changes" and that helped.
Leaving the comment for anyone that may encounter that in the future and closing the issue.
Steps to reproduce
Prerequisites - optional
You may want to setup fresh testing environment:
wp-env destroy
to confirm everything's gonewp-env start
to start a fresh environmentSteps
npm run test:e2e
Expected:
tests are running and passing
Actual:
there's a 404 error thrown:
POST http://localhost:8889/wp-json/wc/v3/settings/general/batch
Notes:
.wp-env.override.json
file was necessary for the issue to occur.add/convert-classic-template
) no changes to.wp-env.json
, nor.wp-env.override.json
was created in order for the issue to occur.cc: @gigitux, @Aljullu
The text was updated successfully, but these errors were encountered: