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

[DOC REQUEST] Setup issues #689

Closed
jwrobbs opened this issue Jan 20, 2024 · 4 comments
Closed

[DOC REQUEST] Setup issues #689

jwrobbs opened this issue Jan 20, 2024 · 4 comments
Labels

Comments

@jwrobbs
Copy link

jwrobbs commented Jan 20, 2024

Did you search the documentation first?
You can find it at https://wpbrowser.wptestkit.dev/.
Yes.

What do you think is missing from the documentation?
Describe the general argument and, if applicable, what details you would like to see in there.

More info related to pre-init requirements or init troubleshooting.

Do you have any examples of what you'd like to see added to the documentation?
Please provide citations or links if applicable.

The docs make setup look easy:

  1. Navigate to the directory
  2. Add files via composer
  3. Initialize with the provided script

But what if it doesn't work?
If I run it with an existing WP installation, it says that it's installing WordPress then throws an error. https://share.zight.com/kpueYPPr

If I run it in an empty directory, it throws an error saying that WordPress is missing. https://share.zight.com/Z4u25ddn

@lucatume lucatume changed the title [DOC REQUEST] [DOC REQUEST] Setup issues Jan 22, 2024
@lucatume
Copy link
Owner

lucatume commented Jan 22, 2024

Hi @jwrobbs,

Thank you for taking the time to report an issue.

I understand the frustration of getting stuck at the very start, and I'm open to improving the documentation where possible.

The docs make setup look easy

Because it should. If it's not, it's likely a bug, not a feature.

If I run it in an empty directory, it throws an error saying that WordPress is missing.

This is expected, for a "WordPress" project to exist, something should exist: a plugin file, a theme file, or a site.
In the documentation, I assume that as a given, but I agree with you here this could be improved.

If I run it with an existing WP installation, it says that it's installing WordPress then throws an error.

This looks like a bug. Would you mind sharing the structure and setup of the WordPress installation you're trying to set up wp-browser on? If you cannot share too many details, could you point to a structure or template I could use to reproduce and debug?

I've changed the title of your issue to better reflect the nature of it and help me reference it.

@jwrobbs
Copy link
Author

jwrobbs commented Jan 22, 2024

Thanks for taking care of that.

I am running the commands in the root WordPress directory next to wp-admin, wp-content, etc.

If I use composer require --dev lucatume/wp-browser, then vendor/bin/codecept init wpbrowser will fail.

But it works if I use composer require --dev lucatume/wp-browser ^3.

FYI: now the error message is "could not find driver".

@lucatume
Copy link
Owner

I've added a Requirements section to the README.md file that should improve things and extended the site project failure information in #690 and version 4.0.18.

now the error message is "could not find driver"

This is not a wp-browser issue, PHP is likely missing the sqlite3 extension.

Do you still have the issue after installing, or activating, the sqlite3 extension?

Copy link

This issue is marked stale because it has been open 20 days with no activity. Remove stale label or comment or this will be closed in 5 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants