Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Faust ExperimentalToolbar still causes 401 Unauthorized error #1924

Open
1 task done
jan-clockworkwp opened this issue Aug 2, 2024 · 0 comments
Open
1 task done
Labels
needs: reproduction This issue needs to be reproduced independently

Comments

@jan-clockworkwp
Copy link

Description

I know this topic was discussed already in various issues that are mainly closed. This is just to bring more attention to my previous comment and confirm that this issues is still present, and I have just reproduced it again with the latest packages and faust example setup on the front end (where ExperimentalToolbar is already set to true by default).

Steps to reproduce

  1. Set up vanilla Wordpress on http protocol and some example vhost.
  2. Install, activate and setup necessary plugins: FaustWp and WPGraphQL
  3. Set up FE by executing
    -e https://github.com/wpengine/faustjs/tree/canary \
    --example-path examples/next/faustwp-getting-started \
    --use-npm
  1. Set env values on the front end
  2. Log into the backend and click on view page link on pages list in the admin to see that page on the new tab, you should not see toolbar as you were not authenticated, and will get the mentioned console.error
  3. if you click on the preview link, you can see toolbar, as you were properly authenticated and there will be no console.error
  4. If you set ExperimentalToolbar: false you will not be able to replicate console.error

Additional context

No response

@faustwp/core Version

3.0.3

@faustwp/cli Version

3.0.2

FaustWP Plugin Version

1.3.2

WordPress Version

6.6.1

Additional environment details

No response

Please confirm that you have searched existing issues in the repo.

  • Yes
@josephfusco josephfusco added the needs: reproduction This issue needs to be reproduced independently label Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs: reproduction This issue needs to be reproduced independently
Projects
None yet
Development

No branches or pull requests

2 participants