Package Data | |
---|---|
Maintainer Username: | neilcrookes |
Maintainer Contact: | neil.crookes@fivebyfiveuk.com (Neil Crookes) |
Package Create Date: | 2014-02-21 |
Package Last Update: | 2014-04-24 |
Language: | PHP |
License: | MIT |
Last Refreshed: | 2024-12-11 15:05:22 |
Package Statistics | |
---|---|
Total Downloads: | 527 |
Monthly Downloads: | 0 |
Daily Downloads: | 0 |
Total Stars: | 8 |
Total Watchers: | 8 |
Total Forks: | 4 |
Total Open Issues: | 0 |
A Laravel 4 package to add events listings to a site
Add the following to you composer.json file (Recommend swapping "dev-master" for the latest release)
"fbf/laravel-events": "dev-master"
Run
composer update
Add the following to app/config/app.php
'Fbf\LaravelEvents\LaravelEventsServiceProvider'
Run the package migration
php artisan migrate --package=fbf/laravel-events
Publish the config
php artisan config:publish fbf/laravel-events
Optionally tweak the settings in the many config files for your app
Optionally copy the administrator config file (src/config/administrator/events.php
) to your administrator model config directory.
Create the relevant image upload directories that you specify in your config, e.g.
public/uploads/packages/fbf/laravel-events/main_image/original
public/uploads/packages/fbf/laravel-events/main_image/thumbnail
public/uploads/packages/fbf/laravel-events/main_image/resized
The package comes with a seed that can populate the table with a whole bunch of sample events. There are some configuration options for the seeder in the seed config file. To run it:
php artisan db:seed --class="Fbf\LaravelEvents\FakeEventsSeeder"
See the many configuration options in the files in the config directory
You can use the excellent Laravel Administrator package by frozennode to administer your data.
http://administrator.frozennode.com/docs/installation
A ready-to-use model config file for the Event
model (events.php
) is provided in the src/config/administrator
directory of the package, which you can copy into the app/config/administrator
directory (or whatever you set as the model_config_path
in the administrator config file).
The package should work out the box (provided you have a master blade layout file, since the out-of-the-box views extend this) but if you want to add other content to the pages, such as your own header, logo, navigation, sidebar etc, you'll want to override the views provided.
The package views declare several sections that you may want to yield
in your app/views/layouts/master.blade.php
file, e.g.:
<!DOCTYPE html>
<html>
<head>
<title>@yield('title')</title>
<meta name="description" content="@yield('meta_description')">
<meta name="keywords" content="@yield('meta_keywords')">
</head>
<body>
<div class="content">
@yield('content')
</div>
</body>
</html>
The package's views are actually really simple, and most of the presentation is done in partials. This is deliberate so you can override the package's views in your own app, so you can include your own chrome, navigation and sidebars etc, yet you can also still make use of the partials provided, if you want to.
To override any view in your own app, just create the following directories and copy the file from the package into it, then hack away
app/views/packages/fbf/laravel-events/events
app/views/packages/fbf/laravel-events/partials
You can extend the model to add more fields, relations and even filter event listings by a relationship.
See the extending section in the readme on http://github.com/FbF/Laravel-Blog as it works the same way.