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 don't see why a command like wp scaffold plugin-tests should require WordPress to be loaded. Using WP_Fileystem to copy/create a bunch of files seems unnecessary in this case IMO.
The text was updated successfully, but these errors were encountered:
The reason why commands like this use WP_Filesystem is because we want to adhere to all permissions/security settings on the server that were configured for WordPress. Otherwise, we might create files with too lax permissions that are directly accessible from the web.
So my original issue was that I wanted to scaffold a plugin in an arbitrary location, without having a WordPress install. But if WP is detected, using the filesystem functions make sense. Right now that's not possible though.
swissspidy
changed the title
Don't use WordPress filesystem functions
Allow scaffolding without WordPress being present
Jul 12, 2024
I don't see why a command like
wp scaffold plugin-tests
should require WordPress to be loaded. UsingWP_Fileystem
to copy/create a bunch of files seems unnecessary in this case IMO.The text was updated successfully, but these errors were encountered: