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
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
Set up vanilla Wordpress on http protocol and some example vhost.
Install, activate and setup necessary plugins: FaustWp and WPGraphQL
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
if you click on the preview link, you can see toolbar, as you were properly authenticated and there will be no console.error
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
The text was updated successfully, but these errors were encountered:
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
ExperimentalToolbar: false
you will not be able to replicate console.errorAdditional 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.
The text was updated successfully, but these errors were encountered: