Download the PHP package kohana-modules/phery without Composer

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

Phery Kohana

Kohana module with tight integration for Phery.js library

Working with AJAX (including file uploads) never been simpler. Just add the phery.js (like `) file on your page (or if you are using an assets manager, addPHERY_JSconstant to the bunch), and instead of usingController, use Phery_Controllerand instead ofController_TemplateusePhery_Template`.

Also, you should notice that the $ajax variable is available in ALL views (but you shouldn't do logic in your views though). This is mainly useful because you need to do a ` in your head, so you can install CSRF that comes enabled by default, otherwise your AJAX calls will fail (CSRF stands forCross Site Request Forgery` to avoid remote attacks to your AJAX forms and/or links)

For a full documentation of the phery.js library, check https://github.com/pocesar/phery

Just follow these conventions:

When you want to make a PHP function available for just one action, you namespace it:

When you want to reuse a callback for all actions, just don't namespace it:

You may change the AJAX options per controller, by passing configuration to the ajax function inside your controller:

Your AJAX function will be processed AFTER your after() function, so you can place all the transformations, cleanups, in there.

Also, inside the Phery_Controller or Phery_Template, there is the same $ajax variable, so you can mess with Phery youself:

This make it highly flexible, so you don't need to be tied to convention.

If any exception happens when using AJAX, it will go 'silently' to your application/logs and it will fail with an empty JSON response {}

Coming soon


All versions of phery with dependencies

PHP Build Version
Package Version
Requires php Version >=5.3.0
phery/phery 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 kohana-modules/phery contains the following files

Loading the files please wait ....