Download the PHP package kdrmklabs/ticket-bundle without Composer

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

Getting started with KdrmklabsTicketBundle in Symfony2.

This bundle allows you to integrate in your Symfony2 project a basic system of customer support by tickets. You can create, edit and respond tickets instantly after installing this bundle .

Needs a minimum configuration and the whole procedure is very simple.

Installation.

I. Installing the bundle in two different ways.

a) Automatically.

You can install the last version of this bundle with composer running the command from your command line:

b) By composer.json .

Or you can install this bundle by adding next code line to your project in the composer.json file and after update it with the command composer update

file: /composer.json

Now, update the bundle with composer:

II. Enable and register the Bundle in the AppKernel

III. Install Gedmon Doctrine2 extensions

Requirements:

Check if gedmo doctrine extensions are downloaded.

/vendor/gedmo/doctrine-extensions/lib/Gedmo

if not download it:

a. Add dependency to composer.json

file: /composer.json

b. Update with composer in the command line:

Configure Gedmo:

III.I. Create a DoctrineExtensionListener

III.II. Create file doctrine_extensions.yml and locate it in your app/config directory

Don't forget change 'AppBundle\Listener\DoctrineExtensionListener' to your DoctrineExtensionListener namespace.

Finally, Do not forget to import doctrine_extensions.yml in your app/config/config.yml :

More details of Gedmo Doctrine2 extensions in Symfony2: https://github.com/Atlantic18/DoctrineExtensions/blob/master/doc/symfony2.md

IV. (optional) If you want paginate results with KNPPaginatorBundle you can install and configure it.

More details: https://github.com/KnpLabs/KnpPaginatorBundle#configuration-example

V. Configure the bundle.

V.I. Add kdrmklabs_ticket configuration to you config.yml

Where user_primay_key is the name of your primary key in the user table.

V.II. Add resolve_target_entities to your doctrine configuration

Do not forget change 'AppBundle\Entity\User' to your User Entity namespace

More details about resolve_target_entities: http://symfony.com/doc/current/cookbook/doctrine/resolve_target_entity.html

V.III. Implements Kdrmklabs\Bundle\TicketBundle\Model\UserInterface from your User entity.

VII. Finally, create database tables and update the schema

Update your database schema with the command:

Now, you need to populete the database tables kdrmklabs_ticket_status and kdrmklabs_ticket_category

Example of SQL to populete the tables:

Statuses

You can add to the database table kdrmklabs_ticket_status all states that you want to use to identify the tickets, for example:

image

Categories

You can add to the database table kdrmklabs_ticket_category all categories that you want to use to classify the tickets, for example:

image

Available services

Examples of implementation of kdrmklabs_ticket.ticket_service from a controller

Create a ticket

createTicket -> Return a Kdrmklabs\Bundle\TicketBundle\Entity\Ticket object

Description

Delete

deleteTicket -> Return boolean

Description:

Reply

replyTicket -> Return a Kdrmklabs\Bundle\TicketBundle\Entity\Ticket object

Description:

get a ticket

getTicket -> Return a Kdrmklabs\Bundle\TicketBundle\Entity\Ticket object

Description:

list tickets

getTickets -> return DQL QUERY

Description:

close ticket

closeTicket -> Return boolean

Description:

User repository from UserInterface

Example complete of Controller implementation


All versions of ticket-bundle with dependencies

PHP Build Version
Package Version
Requires php Version >=5.3.2
symfony/framework-bundle Version ~2.1
gedmo/doctrine-extensions Version ~2.3.1
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 kdrmklabs/ticket-bundle contains the following files

Loading the files please wait ....