Download the PHP package yivi/wp_optional without Composer

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

WP Optional

Library to help in generating option pages for plugins and themes.

Work in progress, but the basic usage is as follows:

PageSettings object

Subpages

When settings are long enough or complex enough, you may want to separate them in different "subpages" (or tabs) to make access easier. You always need at least one subpage

Sections

Each page should have 1 or more "sections" to group settings

Fields

Fields are added to each of the sections, directly.

Field Types

Field Configuration

Description

Sets the optional value for a field description. If provided, will be rendered close to the field

$field->setDescription('This field rocks and rolls');
Default

Default value for the field, if the user doesn't provide one

 $field->setDefault('1');

Class

If provided, this string will be rendered in the class attribute of the field

 $field->setClass('mucho-clase very-nav');
Extra Attributes

This should be a associative array. Each key => value combination will be rendered as an additional attribute for the field

 $field->setAttributes(['rows' => '30', 'data-value' => $whatever ]);

Choices

This is a list of values and labels, generally used for <select> or <radio>

 $field->setChoices('WS' => 'Washington', 'NY', 'New York', 'MAD' => 'Madrid');

Example

Since these calls are chainable, you could do:


All versions of wp_optional with dependencies

PHP Build Version
Package Version
Requires php Version ^7.1
yivi/very-simple-html-writer Version ~0.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 yivi/wp_optional contains the following files

Loading the files please wait ....