lsascha/fullcalendar

Last activity on 5 May 2020
  • 4
  • 2
  • 45
composer require lsascha/fullcalendar

full calendar (fullcalendar.io) implementation package for Flow / Neos

2.0.0

full calendar (fullcalendar.io) implementation package for Flow / Neos

Homepage
https://github.com/lsascha/full-calendar/
Version
2.0.0
Type
neos-package
Release Date
21.05.2020 17:57:06
Source
git
Distribution
zip
Requires
Requires (dev)
None
Suggest
None
Provides
None
Conflicts
None
Replaces
None
MIT
  • #flow
  • #calendar
  • #neos
4a84bd7f43a851a315ba8dba695c0e45e1c50c36

full-calendar

full calendar implementation package for Flow / Neos CMS

Installation

Install using Composer:

composer require lsascha/fullcalendar

Run doctrine migrations:

./flow doctrine:migrate

Features

  • Usable with Neos CMS with Plugins + Backend Module or Standalone as Flow Package.
  • Multiple Event Sources (from DB, Neos Pages or Google Calendars).
  • Easy to use Neos CMS Backend Module with Drag&Drop support for Event Editing.

Usage

As standalone (Flow)

As Standalone Flow Package: The default Route is /calendar.html. By default, it shows all Events from all Event Sources. To limit display to specific sources, add ?sources[]=_IDENTIFIER_ arguments to it.

Event Sources and Events can be added per CLI command. see ./flow help calendar:addsource and ./flow help calendar:addevent for help.

In Neos CMS

Installed into a Neos CMS Installation it adds a Plugin, Page-Types and a Backend Module. Give the Backend User who should Edit Events the CalendarAdmin Role (Lsascha.FullCalendar:CalendarAdmin).

The Backend User should then See a new Backend Module named Calendar under Management.

For Google Calendars as Event Source, you need to set the Google Calendar API Key in your Settings.yaml Lsascha.FullCalendar.googleCalendarApiKey The Google Calendar needs to be Public accessible. See https://fullcalendar.io/docs/google-calendar for more Information.

The content of the readme is provided by Github
The same vendor provides 2 package(s).