Download the PHP package webdevstudios/oops-wp without Composer

On this page you can find all versions of the php package webdevstudios/oops-wp. 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?

Example code of webdevstudios/oops-wp

Informations about the package oops-wp

OOPS-WP: Object Oriented Programming Structures for WordPress

This library provides a collection of abstract classes, interfaces, and traits to help promote object-oriented development in WordPress.

Installation

The preferred way to install the latest stable release of OOPS-WP is via Composer. From your project directory, you can run:

This will install the library relative to where you called the command, at /vendor/webdevstudios/oops-wp. You can navigate to that directory to look through the various classes, interfaces, and traits that are available for you to use. In order to make those structures available to WordPress, you'll need to require the Composer-generated autoload file:

Note: Details on why we include the is_readable() check is available in the wiki.

A Caveat

WordPress isn't designed to be compatible with Composer, and many plugins and themes may wind up using the same libraries. This library is recommended for use in agency-type projects where have full control over the development and installation environment. Including OOPS-WP as part of a packaged release may mean that multiple different copies could wind up getting installed and included in a project, thereby causing unforeseen errors in the system. This is a shortcoming of the way WordPress resolves dependencies, and not one of OOPS-WP. For more information about this issue, we recommend checking out this great article on by Peter Suhm on WPTavern.

Documentation and Development Roadmap

In its initial release, OOPS-WP contains very few structures to facilitate plugin and theme development. There are a handful of interfaces: Hookable, Runnable, and Registerable, and a few abstract classes, notably ServiceRegistrar, Service, EditorBlock, and PostType. These were borne around the need to quickly scaffold some basic structural entities at WebDevStudios, but they are not the only data structures supported by WordPress.

To see what WordPress structures are under development, you can visit the Issues page of this repo. For documentation and examples on how to use the structures this package provides, you can visit the Wiki.

Versioning

This project follows semantic versioning best practices. What this means is that PATCH releases (e.g., 0.1.1) will include only minor bugfixes or other non-functional updates, such as the text in this README. MINOR releases (e.g., 0.2.0) will include new features, such as additional class structures, and backward-compatible friendly changes. MAJOR releases (e.g., 1.0.0) will contain changes that break backward compatibility. As such, you should be able to safely run composer update webdevstudios/oops-wp on packages that are versioned to a major release (e.g., ^1) without worrying that the updates will break your site. Upgrading to the next major release will mean that you will likely have to make updates to all of the classes that make use of this library to ensure that they're adhering to the latest APIs.

Contributing

See the contributing doc for information on how to contribute to this project.

All versions of oops-wp with dependencies

PHP Build Version
Package Version
Requires php Version ^7 || ^8
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 webdevstudios/oops-wp contains the following files

Loading the files please wait ....