Download the PHP package specshaper/calendar-bundle without Composer

On this page you can find all versions of the php package specshaper/calendar-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?

Example code of specshaper/calendar-bundle

Informations about the package calendar-bundle

SpecShaperCalendarBundle

Currently using this bundle for payments at (https://www.parolla.ie)](https://www.parolla.ie) and (https://tools.parolla.ie)](https://tools.parolla.ie)

The SpecShaperCalendarBundle provides a calendar and appointment package for the Symfony2 framework utilising the fullcalendar jquery plugin.

Features include:

Warning

Features road map:

Work to complete:

Documentation

The source of the documentation is stored in the Resources/doc/ folder in this bundle.

License

This bundle is under the MIT license. See the complete license in the bundle:

Resources/meta/LICENSE

About

CalendarBundle is a SpecShaper bundle for managing project appointments.

It is based on the adesigns/calendar-bundle modified and extended with additional functionality.

Reporting an issue or a feature request

Issues and feature requests are tracked in the Github issue tracker.

When reporting a bug, it may be a good idea to reproduce it in a basic project built using the Symfony Standard Edition to allow developers of the bundle to reproduce the issue by simply cloning it and following some steps.

Installation

Step 1: Download the bundle

Open a command console, enter your project directory and execute the following command to download the latest stable version of this bundle:

This command requires you to have Composer installed globally, as explained in the installation chapter of the Composer documentation.

Step 2: Enable the bundle

Then, enable the bundle by adding it to the list of registered bundles in the app/AppKernel.php file of your project:

Step 2: Create the entities

The bundle requires entities to interact with the database and store information.

Calendar entity

The bundle allows many calendars to be created with different properties such as:

The entity should extend the mapped superclass. You can provide any additional entity code as required to suit your application.

CalendarEvent entity

The CalendarEvent entity contains all the information about a particular event or event series. Information such as:

The entity should extend the mapped superclass. You can provide any additional entity code as required to suit your application.

CalendarReoccurance entity

An entity that contains the reoccurance information for a series of CalendarEvents.

CalendarAttendee entity

The entity contains information about an event attendee, such as:

The attendee should be modified to include a reference to your user entity if you have one.

The entity should extend the mapped superclass. You can provide any additional entity code as required to suit your application.

CalendarComment entity

The entity contains any comments or messages made about an event:

The entity should extend the mapped superclass. You can provide any additional entity code as required to suit your application.

Step 3: Create listeners

Create listeners in your application to intercept events fired by the bundle and modify / interact with the events.

CalendarLoadEventsListener

The event is thrown when an CalendarEvent is first loaded and whenever the user changes the view date range.

Used to query for and decorate CalendarEvents to be displayed in the calendar.

CalendarNewEventListener

The event is thrown when an CalendarEvent in the calendar.

Used to populate and decorate the new CalendarEvent to customise it for your application.

CalendarRemoveEventListener

The event is thrown when an CalendarEvent is deleted or removed.

Used to modify or remove the CalendarEvent to customise it for your application.

CalendarUpdateEventListener

The event is thrown when an CalendarEvent is updated.

Used to modify or remove the CalendarEvent to customise it for your application. For example:

See the documents section for more detail of the listeners available:

CalendarGetAddressListener

The event is thrown when a the calendar is loaded. It allows the opportunity to provide email addresses to the autocomplete attendee email input.

Step 4: Configure the bundle

To configure the minimum settings you need to define the orm. Only Doctrine is supported at the moment.

Then point the bundle at your custom Calendar entities.

See the full documentation for a full list of options.

You will also need to enable translations if not already configured:

Step 5: Define the routes

Define any routing that you prefer. The controller can be placed behind a firewall by defining a prefix protected by your security firewalls.

Step 6: Integrate into one of your twig templates

The bundle requires:

The links to css and js files are generated by including twig templates.

A typical twig template extending a bundle base.html.twig.

Step 7: Customise

Use the entities to customise the persisted information and integrate the calendars with your application entities.

Apply security via the route firewalls, or for more granular security control use the event listeners to manage access.

Overwrite the twig modal and calendar template in your own app\Resources\SpecShaperCalendarBundle directory to change the modal displays.

Copy and modify the fullcalendar-settings.js file to provide custom javascript functionality. Or simply extend your twig template javascript block.

All versions of calendar-bundle with dependencies

PHP Build Version
Package Version
Requires php Version >=5.3.9
symfony/framework-bundle Version ~2.8|~3.0
eluceo/ical Version ^0.9.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 specshaper/calendar-bundle contains the following files

Loading the files please wait ....