Download the PHP package oceancodex/wpsp without Composer
On this page you can find all versions of the php package oceancodex/wpsp. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download oceancodex/wpsp
More information about oceancodex/wpsp
Files in oceancodex/wpsp
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package wpsp
WordPress Starter Plugin
A great framework that makes WordPress plugin development easier!
Before creating your first WPSP project, make sure you have the following applications installed on your local computer:
- PHP: 8.x
- PHP CLI: 8.x
- Composer
- Nodejs
- A website WordPress (A) running on Localhost with version 5.6 or higher
[!CAUTION] Please pay attention to whether the PHP version and PHP CLI running are suitable for the project WPSP will develop or not?!
After installing the above applications, go to the directory: /wp-content/plugins of the Website (A) to initialize a new WPSP project via the following Composer command:
The plugin project with the folder name my-new-plugin will be initialized and the dependencies will be downloaded.
Then, run the commands below to install the complete project:
The installer will ask you for some project information, fill in that information like the following example:
- Project name: Project name
(eg: My New Plugin) - Project short name: Short project name
(eg: mnp) - Root namespace: Namespace of the project
(eg: MyNewPlugin) - Prefix for environment key: Prefix for variables in the .env file
(eg: MNP_) - Prefix for database table: Prefix for the names of the project tables in the database
(e.g. mnp_) - Prefix for helper functions: Prefix for functions in the Helpers file
(eg: mnp_) - Prefix for cache key: Prefix for cache keys
(eg: mnp-cache) - Text domain: Text domain used for translation according to WordPress standards
(eg: my-new-plugin)
[!IMPORTANT] The above information must be declared correctly in writing style, uppercase and lowercase as in the example for the project to work best.\ Declare the above information to limit plugin conflicts and create an independent operating environment for each project using WPSP running on the same website.
The installer will automatically set up the project, installing dependencies.
If not, you can manually run the following commands to complete project setup:
That's it, you've completed setting up a new plugin project based on WPSP.
Go to the Plugins menu in /wp-admin to activate your: My New Plugin plugin.
Docs: https://docs.oceancodex.com/tai-lieu/wordpress-starter-plugin
OCEANCODEX.VN
