Download the PHP package khromov/wp-vc-template-manager without Composer

On this page you can find all versions of the php package khromov/wp-vc-template-manager. 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 khromov/wp-vc-template-manager

Informations about the package wp-vc-template-manager

Visual Composer Template Manager

This plugin provides a framework for creating themes and plugins that utilize the built-in template function in Visual Composer (as of version 4.4)

It works by loading templates from files in your theme (and optionally plugin) folders, making it possible to version control templates in a simple way.

Building templates

Building a template is easy. Start out by creating a layout in Visual Composer. (For example, by creating a new page with the layout you want.)

When you are done, click the "Classic mode" button to return to the TinyMCE WYSISYG, and then click on the Text tab. Now you can copy the content of your layout into a template!

Workflow:
Visual workflow of text above

Using in a theme

To bundle templates with your theme, create the folder:

Then, create a file, for example:

The only requirement is that the file has a .php extension.

Paste the template you got from the "Building templates" section above, and you will see a new template called "My Template" after you click on Templates > Default Templates in Visual Composer. You're done!

Workflow:
Visual explanation of text above

Using in a plugin

If you want to use this in a plugin, use the vctm_template_locations filter to add a custom path in which templates will be searched.

If your plugin directory is:

Create the folder vc_templates/

Add the following code to your main plugin file:

Forking the base plugin

You can fork this plugin by simply changing the folder name and removing the row starting with "GitHub Theme URI" from the plugin header.

You can then add your templates in the vc_templates/ folder of the plugin.

The hook prefix can be modified by changing the $VCTM_PREFIX variable in the main plugin file.

The translation textdomain can be changed with the vctm_textdomain filter:

Removing default templates

Visual Composer ships with a lot of default templates. If you wish to remove these and only keep the ones you add with this plugin, add the following code in your themes functions.php file, or a plugin:

Known issues

Due to a bug in Visual Composer (as of 4.4.1), it is not possible to reorder the templates. They will always be ordered in alphabetical order. We hope to solve this with future versions of VC.

Hooks

This plugin exposes hooks to control almost anything.

vctm_disable_builtin_templates

Lets you disable VC:s own built-in templates

Parameters: $current_value - Boolean
Return value: Boolean

vctm_template_locations

Lets you register custom template locations for use in plugins and themes.

Parameters: $locations - Array of current paths which will be looked in for templates
Return value: Array of current locations (Append your location to existing array)

vctm_\<TEMPLATE_SOURCE>_name_\<TEMPLATE_NAME>

Lets you change the name that is displayed in VC for a given template

Dynamic value: <TEMPLATE_SOURCE> - The source of the template. "theme" if it came from the theme, "vctm" if it came from the VCTM plugin and "plugin" if it came from a third party plugin using the vctm_template_locations hook. (Don't register multiple paths where template names can collide - you won't be able to filter them.)
Dynamic value: <TEMPLATE_NAME> - The name of the template, without extension. Example: my_template
Parameters: $current_name - The auto-generated name
Return value: String - new name

vctm_\<TEMPLATE_SOURCE>_class_\<TEMPLATE_NAME>

Lets you change the HTML class which wraps the plugin in the VC modal. Lets you set the template icon through CSS.

Dynamic value: <TEMPLATE_SOURCE> - The source of the template. "theme" if it came from the theme, "vctm" if it came from the VCTM plugin and "plugin" if it came from a third party plugin using the vctm_template_locations hook. (Don't register multiple paths where template names can collide - you won't be able to filter them.)
Dynamic value: <TEMPLATE_NAME> - The name of the template, without extension. Example: my_template
Parameters: $current_class_name - The auto-generated class name
Return value: String - new name

vctm_\<TEMPLATE_SOURCE>_content_\<TEMPLATE_NAME>

Lets you dynamically alter the contents of a template, for example to perform pre-processing.

Dynamic value: <TEMPLATE_SOURCE> - The source of the template. "theme" if it came from the theme, "vctm" if it came from the VCTM plugin and "plugin" if it came from a third party plugin using the vctm_template_locations hook. (Don't register multiple paths where template names can collide - you won't be able to filter them.)
Dynamic value: <TEMPLATE_NAME> - The name of the template, without extension. Example: my_template
Parameters: $current_content - The template content
Return value: String - new template content

Miscellaneous

Template name generation

We generate a "nice" template name based on the file name. Dashes and underscores are replaced with spaces and each word is capitalized. You can override it with the vctm_\<TEMPLATE_SOURCE>_name_\<TEMPLATE_NAME> filter.

GitHub updater

This plugin supports GitHub updater.

Composer

This plugin supports Composer through the composer/installers package.

All versions of wp-vc-template-manager with dependencies

PHP Build Version
Package Version
Requires composer/installers 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 khromov/wp-vc-template-manager contains the following files

Loading the files please wait ....