Download the PHP package 32d/wordpress-project without Composer

On this page you can find all versions of the php package 32d/wordpress-project. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • 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.
Please rate this library. Is it a good library?

Informations about the package wordpress-project

WordPress Project

This is a WordPress project handled mostly by Composer.

Installation

Pre-requisites

Composer

To install the project on your local environment, make sure you have Composer installed on your machine, and from the project root folder in a terminal, run:

That command alone should handle most of what's necessary for the project to be able to run.

Database

Local Web Server

Whether you are using WAMP, MAMP, LAMP or something custom, you might need to configure it so you can access this project.

If your thing is to just have all your projects as subfolders and your URLs look like localhost/project1/, then it is very likely you will not have anything to do at all! Just know that the URL for this project will probably feature an extra "wp/", like localhost/project1/wp/.

If you'd rather configure a new vhost for each project, then you have two options:

  1. Create a classic Wordpress vhost configuration that points to the "public" folder. Your final URL will feature a "/wp" in it, that's normal
  2. If you don't want the "/wp" in your URL, you have to configure your vhost accordingly, and it can be very tricky depending on your level of knowledge. Here is an example of a working nginx configuration for this architecture:

Images and Stuff

If you fancy having pretty media showing on your local version of this project, then feel free to open Filezilla or equivalent and download the "uploads" folder to the "public/content" folder of this project. It is already gitignored.

All versions of wordpress-project with dependencies

PHP Build Version
Package Version
Requires php Version ^8.1
illuminate/support Version ^8.83
johnpbloch/wordpress-core Version @stable
johnpbloch/wordpress-core-installer Version ^2.0
johnpbloch/wp-cli-phar Version ^2.6
laravel/helpers Version ^1.5
vlucas/phpdotenv Version ^5.4
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package 32d/wordpress-project contains the following files

Loading the files please wait ....