Download the PHP package cnp/wp-theme-wrapper without Composer

On this page you can find all versions of the php package cnp/wp-theme-wrapper. 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-theme-wrapper

WP-Theme-Wrapper

A wrapper function that intercepts WordPress' template_include function, allowing us to use base.php instead.

Say you've got two template files for a post type, archive-book.php and single-book.php. The way that WordPress normally works, you'd have to repeat at least get_header() and get_footer() in each of these files. Perhaps there's more structural HTML to it. The trouble is, now you have some amount of duplicated code that is not specific to the layout.

The WP Theme Wrapper functions intercept WordPress template selection. Every template uses base.php. It then takes the file that would have been selected and puts it into base.php. This way, archive-book.php and single-book.php only have markup that is specific to the specific view and nothing more.

This also helps us visualize how the template files fit together from start to end; that is, we're not splitting open and close div tags across multiple PHP files.

Note: normally, we don't resort to using a WordPress template file, because doing this also overrides index.php, The Loop, and all the theme Actions that we've placed around The Loop. You can probably achieve the same effect by using a file structure like ui/book/book-content-archive.php and ui/book/book-content-singular.php.

Reference

All versions of wp-theme-wrapper with dependencies

PHP Build Version
Package Version
Requires php Version >=5.3.3
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 cnp/wp-theme-wrapper contains the following files

Loading the files please wait ....