niolabs/chatter

A simple forum package for your laravel app

Thursday, December 14, 2017
by aaronranard
Repository
10 Watchers
0 Stars
9 Installations

PHP
0 Dependents
0 Suggesters
156 Forks
0 Open issues
40 Versions
0 % Grown

The README.md

, _(*1)

, _(*2)

Laravel Forum Package - Chatter

Installation

Quick Note: If this is a new project, make sure to install the default user authentication provided with Laravel. php artisan make:auth, _(*3)

Include the package in your project, _(*4)

composer require "devdojo/chatter=0.2.*"

Add the service provider to your config/app.php providers array:, _(*5)
```
DevDojo\Chatter\ChatterServiceProvider::class,
```
Publish the Vendor Assets files by running:, _(*6)
```
php artisan vendor:publish
```
Now that we have published a few new files to our application we need to reload them with the following command:, _(*7)
```
composer dump-autoload
```
Run Your migrations:, _(*8)
```
php artisan migrate
```
Quick tip: Make sure that you've created a database and added your database credentials in your .env file., _(*9)
Lastly, run the seed files to seed your database with a little data:, _(*10)
```
php artisan db:seed --class=ChatterTableSeeder
```
Inside of your master.blade.php file include a header and footer yield. Inside the head of your master or app.blade.php add the following:, _(*11)
```
@yield('css')
```
Then, right above the </body> tag of your master file add the following:, _(*12)
```
@yield('js')
```

Now, visit your site.com/forums and you should see your new forum in front of you!, _(*13)

Upgrading

Make sure that your composer.json file is requiring the latest version of chatter:, _(*14)

"devdojo/chatter": "0.2.*"

Then you'll run:, _(*15)

composer update

Next, you may want to re-publish the chatter assets, chatter config, and the chatter migrations by running the following:, _(*16)

php artisan vendor:publish --tag=chatter_assets --force
php artisan vendor:publish --tag=chatter_config --force
php artisan vendor:publish --tag=chatter_migrations --force

Next to make sure you have the latest database schema run:, _(*17)

php artisan migrate

And you'll be up-to-date with the latest version :), _(*18)

Markdown editor

If you are going to make use of the markdown editor instead of tinymce you will need to change that in your config/chatter.php:, _(*19)

'editor' => 'simplemde',

In order to properly display the posts you will need to include the graham-campbell/markdown library for Laravel:, _(*20)

composer require graham-campbell/markdown

Trumbowyg editor

If you are going to use Trumbowyg as your editor of choice you will need to change that in your config/chatter.php:, _(*21)

'editor' => 'trumbowyg',

Trumbowyg requires jQuery >= 1.8 to be included., _(*22)

VIDEOS

Introduction and Installation of Chatter, _(*23)

Configuration

When you published the vendor assets you added a new file inside of your config folder which is called config/chatter.php. This file contains a bunch of configuration you can use to configure your forums, _(*24)

Customization

CUSTOM CSS, _(*25)

If you want to add additional style changes you can simply add another stylesheet at the end of your @yield('css') statement in the head of your master file. In order to only load this file when a user is accessing your forums you can include your stylesheet in the following if statement:, _(*26)

@if(Request::is( Config::get('chatter.routes.home') ) || Request::is( Config::get('chatter.routes.home') . '/*' ))
    <!-- LINK TO YOUR CUSTOM STYLESHEET -->
    <link rel="stylesheet" href="/assets/css/forums.css" />
@endif

SEO FRIENDLY PAGE TITLES, _(*27)

Since the forum uses your master layout file, you will need to include the necessary code in order to display an SEO friendly title for your page. The following code will need to be added to the <head> of your master file:, _(*28)

@if( Request::is( Config::get('chatter.routes.home')) )
    <title>Title for your forum homepage -  Website Name</title>
@elseif( Request::is( Config::get('chatter.routes.home') . '/' . Config::get('chatter.routes.category') . '/*' ) && isset( $discussion ) )
    <title>{{ $discussion->category->name }} - Website Name</title>
@elseif( Request::is( Config::get('chatter.routes.home') . '/*' ) && isset($discussion->title))
    <title>{{ $discussion->title }} - Website Name</title>
@endif

OVERRIDING VIEWS, _(*29)

In order to override Chatter's built in views, simply create a chatter folder in your vendor views folder, i.e. ROOT/resources/views/vendor/chatter. Then simply drop in the Chatter view files you would like to override., _(*30)

Custom Function Hooks for the forum

Sometimes you may want to add some additional functionality when a user creates a new discussion or adds a new response. Well, there are a few built in functions that you can create in your script to access this functionality:, _(*31)

Before User Adds New Discussion Create a new global function in your script called:, _(*32)

function chatter_before_new_discussion($request, $validator){}

Note: that the $request object is passed with the user input for each webhook. You can use it if you would like :) If not, no worries just add your custom functionality., _(*33)

After User Adds New Discussion Create a new global function in your script called:, _(*34)

function chatter_after_new_discussion($request){}

Before User Adds New Response Create a new global function in your script called:, _(*35)

function chatter_before_new_response($request, $validator){}

After User Adds New Response Create a new global function in your script called:, _(*36)

function chatter_after_new_response($request){}

Laravel Events for the forum

This package provides a number of events allowing you to respond to user actions as they happen:, _(*37)

Event	Available properties	Description
`ChatterBeforeNewDiscussion`	`Illuminate\Http\Request ($request)`, `Illuminate\Validation\Validator ($validator)`	This event is fired before a discussion is validated and created
`ChatterAfterNewDiscussion`	`Illuminate\Http\Request ($request)`, `Models::discussion() ($discussion)`, `Models::post() ($post)`	This event is fired after a discussion has been validated and created
`ChatterBeforeNewResponse`	`Illuminate\Http\Request ($request)`, `Illuminate\Validation\Validator ($validator)`	This event is fired before a response is validated and created
`ChatterAfterNewResponse`	`Illuminate\Http\Request ($request)`, `Models::post() ($post)`	This event is fired after a response is validated and created

Listening for Events

To register your listeners for these events, follow the Laravel documentation for registering events and listeners. For example, to register a listener for the "before new discussion" event, add the following to your EventServiceProvider:, _(*38)

protected $listen = [
    'DevDojo\Chatter\Events\ChatterBeforeNewDiscussion' => [
        'App\Listeners\HandleNewDiscussion',
    ],
];

where App\Listeners\HandleNewDiscussion is a class in your application which handles the event when it's fired., _(*39)

You can access the object that triggered the event in your listener with, _(*40)

    public function handle(ChatterAfterNewDiscussion $event)
    {
        // $event->discussion
        // $event->post
    }

and, _(*41)

    public function handle(ChatterAfterNewResponse $event)
    {
        // $event->post
    }

Screenshots

, _(*42)

The Versions

14/12 2017

dev-master

9999999-dev

A simple forum package for your laravel app

library chatter

A simple forum package for your laravel app

niolabs/chatter

The README.md

Laravel Forum Package - Chatter

Installation

Upgrading

Markdown editor

Trumbowyg editor

VIDEOS

Configuration

Customization

Custom Function Hooks for the forum

Laravel Events for the forum

Listening for Events

Screenshots

The Versions

dev-master

The Requires

The Development Requires

by Aaron Ranard

0.3.0

The Requires

The Development Requires

by Aaron Ranard

dev-set-last-reply-on-create

The Requires

The Development Requires

by Aaron Ranard

0.2.8

The Requires

The Development Requires

by Tony Lea

dev-release/0.3

The Development Requires

by Tony Lea

0.2.7

The Development Requires

by Tony Lea

0.2.6

The Development Requires

by Tony Lea

0.2.5

The Development Requires

by Tony Lea

0.2.4

The Development Requires

by Tony Lea

0.2.3

The Development Requires

by Tony Lea

0.2.2

The Development Requires

by Tony Lea

0.2.1

The Development Requires

by Tony Lea

dev-develop

The Requires

The Development Requires

by Tony Lea

0.2

The Requires

The Development Requires

by Tony Lea

dev-analysis-zOxVG4

The Requires

The Development Requires

by Tony Lea

0.1.24

The Development Requires

by Tony Lea

0.1.23

The Development Requires

by Tony Lea

0.1.22

The Development Requires

by Tony Lea

0.1.21

The Development Requires