Download the PHP package klyp/wordpress without Composer

On this page you can find all versions of the php package klyp/wordpress. 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

klyp/wordpress

WordPress core for Composer, built and published by Klyp.

A scheduled GitHub Action checks wordpress.org every 15 minutes. When there's a new release on any branch, it publishes that release here as a Composer version, including security backports such as 6.9.9 while 7.1.x is current. It doesn't wait for a third party to repackage the release.

Every stable release from 4.7 onward is available.

Using it in a project

klyp/wordpress has the package type wordpress-core and depends on klyp/wordpress-core-installer. That Composer plugin installs core into extra.wordpress-install-dir (default wordpress/) instead of vendor/.

Switching from another WordPress core package

  1. In composer.json:
    • Replace your current WordPress core package in require with "klyp/wordpress": "^6.9", using the same version constraint.
    • Remove the old core installer plugin from config.allow-plugins, and add "klyp/wordpress-core-installer": true.
    • Leave extra.wordpress-install-dir unchanged.

  2. Update the new packages together with the ones you're replacing:

  3. Check that composer.lock lists klyp/wordpress and klyp/wordpress-core-installer, and no other package of type wordpress-core or WordPress core installer. Only one installer plugin should handle WordPress core.

Apply the same change to project skeletons such as 3equals/hummingbird-project, so new sites start on klyp/wordpress.

How it works

File Purpose
bin/build-release.sh Builds and pushes one version: download, verify sha1, add composer.json, tag, push.
bin/sync-releases.sh Compares the WordPress release list with the remote tags, builds what's missing and pushes it. Packagist picks up new tags through its GitHub integration.
.github/workflows/sync.yml Runs the sync every 15 minutes, or on demand. Also commits a monthly keepalive, because GitHub disables schedules after 60 idle days.
.github/workflows/test.yml Installs the newest release, and the newest release of the previous branch, from Packagist into a scratch project.

Publishing a release immediately

The schedule usually picks up a new release within 15 minutes. To publish one right away:

Other local options:

The scripts require bash, curl, jq, unzip and git.

One-time setup

  1. The repository must be public, so that Packagist can read it.
  2. Under Settings → Actions → General → Workflow permissions, choose Read and write permissions. The workflow needs this to push tags and the keepalive commit. If master has branch protection, allow GitHub Actions to push, or the keepalive fails.
  3. On packagist.org, submit https://github.com/klyp/wordpress from the Klyp account. Connect the GitHub integration (Profile → Settings → GitHub) so Packagist is notified on every tag push. No Packagist token is stored in this repo.
  4. Protect the tags. Under Settings → Rules → Rulesets → New tag ruleset, target all tags (*) and enable Restrict updates and Restrict deletions, with no bypass list. The sync never rewrites a tag, and this ruleset stops anyone else (or a leaked token) from replacing a published version with different code. Keep Restrict creations off, or the workflow can't publish new tags.
  5. After merging to master, run Sync WordPress releases once to backfill every version from 4.7 up. That's about 480 tags, and the run is safe to repeat if it times out.

License

WordPress is licensed under the GPLv2 or later. The build tooling in this repository uses the same license.

All versions of wordpress with dependencies

PHP Build Version
Package Version
Requires php Version >=7.4
klyp/wordpress-core-installer Version ^1.0
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 klyp/wordpress contains the following files

Loading the files please wait ...