-
Notifications
You must be signed in to change notification settings - Fork 387
Ticketit initial configuration
Initial configuration is mandatory for Ticketit to work, and it is divided into two sections:
- Configuring the master view file
- Configuring the Ticketit config file (located at config/ticketit.php)
Ticketit views system is developed to integrate with the current project master view (Ticketit uses Bootstrap framwork). The master view file is the main view file that is using "yield" to call header, content, footer sections. It should be located at resources/views (ex. resources/views/app.blade.php), open it and make sure it yields for page, content, and footer.
@yield('page') Page section for passing the current page title
<header> ...
<title>My website - @yield('page')</title>
</header>@yield('content') Content section for the content
<body> ...
@yield('content')
...
</body>@yield('footer') Footer section for passing the jquery scripts, so make sure it is called after you call the jquery
<body> ...
@yield('content')
...
<script src="/js/jquery.min.js"></script>
..
@yield('footer')
</body>You can publish just create a new file 'config/ticketit.php' and replace only settings that you want to change from 'vendor/kordy/ticketit/src/Config/ticketit.php'
Or
Publish the config file (It will generate new file at config/ticketit.php) with all settings in it, and then edit necessary lines.
php artisan vendor:publish --provider="Kordy\Ticketit\TicketitServiceProvider" --tag="config"This step is optional only if you want to customize the settings, here are the settings available in the config file:
- main_route : Where to load the ticket system (ex. if main_route is 'tickets' then the Ticketit will be loaded at http://url/tickets)
- admin_route : Where to load the ticket administration dashboard (ex. if admin_route is 'tickets-admin' then the administration dashboard will be loaded at http://url/tickets-admin)
- master_template : The master blade template to be extended (ex. master_template is 'master' if the master template file is resources/views/master.blade.php)
- default_status_id : The default status for new created tickets, so let's say you created status 'Pending' and you want it to be the default status for any new ticket, then add its record id here
- admin_ids : Array of users ids who you want to grant access to admin dashboard
- paginate_items : How many items listed per page
- status_notification : send email notification to ticket owner/Agent when ticket status is changed
- comment_notification : Send notification when new comment is posted
- queue_emails : Use Queue method when sending emails (Mail::queue instead of Mail::send). Note that Mail::queue needs to be configured first http://laravel.com/docs/5.1/queues
- agent_notify : To notify assigned agent (either auto or manual assignment) of new assigned or transferred tickets
- agent_restrict : Restrict agents access to only their assigned tickets
- close_ticket_perm : Whose has a permission to close tickets
- reopen_ticket_perm : Whose has a permission to reopen tickets
- delete_confirmation : Choose which confirmation message type to use when confirming a deleting