This package provides a calendar integration in to cone.app. It utilizes jQuery Fullcalendar (https://github.com/fullcalendar/fullcalendar).
Currently, version 6.1 is included (see package.json). See (https://github.com/fullcalendar/fullcalendar/releases).
Calendar Widget
The calendar widget integration is done via cone.calendar.browser.CalendarTile which is registered by name calendar.
The overall calendar configuration is done via model properties.
from cone.app.model import BaseNode
from cone.app.model import Properties
class MyCalendar(BaseNode):
@property
def properties(self):
props = Properties()
props.default_content_tile = 'calendar'
props.calendar_header = {
'left': 'month,agendaWeek,agendaDay',
'center': 'title',
'right': 'today prev,next'
}
return props
For a full list of available calendar options read cone.calendar.browser.CalendarTile documentation.
A calendar rendered on several kinds of nodes can say what it shows. Set calendar_title on a CalendarTile subclass, it is rendered as card header above the calendar. None by default, no header then.
from cone.calendar.browser import CalendarTile
from cone.tile import tile
@tile(
name='calendar',
path='cone.calendar.browser:calendar.pt',
interface=IMyCalendar,
permission='view')
class MyCalendarTile(CalendarTile):
@property
def calendar_title(self):
return f'Calendar: {self.model.metadata.title}'
Calendar Events
In order to display events in the calendar, one or more event data sources must be provided.
Concrete event data implementation must derive from cone.calendar.browser.CalendarEvents and provide events function.
The default event data source is expected as JSON view registered by name calendar_events for a dedictaed model context.
from cone.calendar.browser import CalendarEvents
from datetime import datetime
from pyramid.view import view_config
import uuid
@view_config(
name='calendar_events',
context=MyCalendar,
accept='application/json',
renderer='json',
permission='view')
class MyEvents(CalendarEvents):
def events(self, start, end):
events = [{
'id': uuid.uuid4(),
'title': 'Title',
'start': datetime(2020, 4, 29, 17, 40),
'end': datetime(2020, 4, 29, 18, 0),
}]
return events
For a full list of available event options read cone.calendar.browser.CalendarEvents documentation.
Multiple event data sources are defined via model properties.
class MyCalendar(BaseNode):
@property
def properties(self):
props = Properties()
props.calendar_sources = [{
'events': 'event_data_1',
'color': 'green'
}, {
'events': 'event_data_2',
'color': 'red'
}]
return props
For a full list of available event source options read cone.calendar.browser.CalendarTile documentation.
Locales
The calendar locale can be set via calendar_locale on model properties.
class MyCalendar(BaseNode):
@property
def properties(self):
props = Properties()
props.calendar_locale = 'de'
return props
Default calendar locale is en. The desired locales must be delivered to the browser in order to work correctly. Locales to deliver are defined in the application ini config as comma separated list of locale names.
cone.calendar.locales = de,fr
For a complete list of available locales see browser/static/fullcalendar/locales folder of this package.
Contributors
Robert Niederreiter
Johannes Raggam
Changes
2.0.1 (2026-10-31)
Fix the calendar context menu being cut off at the bottom and staying in place while the calendar scrolled beneath it. The menu is rendered beside the calendar instead of in body and scrolls along with it, so it stays at the date it was opened for. It opens below and right of the click position if it fits into the visible part of the page - the viewport cut by the scrolling ancestors of the calendar, the content area of cone.app - else above or left of it, else as far inside as its size allows. The wrapper and its overlay are gone: the overlay caught the wheel events. A click or right click outside closes the menu. [rnix]
Add disabled, tooltip and cssclass to calendar actions, and Calendar.prepare_actions, which prepares the targets of actions for a menu opened by the caller. Calendar.add_menu_item takes the menu and the action only. [rnix]
Fix the calendar context menu closing on a click on its padding. Closing the menu by an item click, a click outside of it, opening another menu or destroying the calendar unregisters the outside click listener now. [rnix]
Fix HTML injection via icon and title of calendar context menu actions. The icon is set as CSS class, the title as text. [rnix]
Fix the outside click handler of the calendar context menu treating clicks inside the menu as outside clicks. The menu was compared as jQuery object with the DOM nodes of the event path. [rnix]
Extend the JS tests to 100 % coverage, all modules including bundles are loaded by the tests now. [rnix]
Lint and format the JS code with biome. make check runs biome check, make format runs biome check --write (see include.mk). Behavior unchanged. [rnix]
JS tooling: Commit pnpm-lock.yaml. Upgrade @web/test-runner to 1.0 and run the JS tests headless in Chromium via Playwright, installed in the JS CI workflow. Pin patched versions of vulnerable transitive dependencies via pnpm.overrides. [rnix]
Replace the deprecated datetime.utcfromtimestamp. [rnix]
Sort the imports with ruff (one per line, from imports first, no sections) and format the code with ruff format (90 characters per line, single quotes). [rnix]
Add import sorting (I rules) and the formatter settings to the ruff configuration in pyproject.toml. [rnix]
2.0.0 (2026-10-24)
Add optional CalendarTile.calendar_title, rendered as card header above the calendar. For a calendar shown on several kinds of nodes, where what it shows depends on the node. None by default, the markup is unchanged then. [rnix]
Modernise the code ruff flags as outdated: class X(object). Remove unused import. Behaviour unchanged. super(Class, self) is kept, see cone.app. [rnix]
Add qa.ruff domain to Makefile and pin the ruff rule selection in pyproject.toml, make check runs ruff check. [rnix]
Bootstrap 5 Styles.
1.1.1 (2026-04-28)
Fix span tag receiving icon class in calendar contextmenu. [lenadax]
1.1.0 (2026-02-03)
Refactor package layout to use pyproject.toml and implicit namespace packages. [rnix]
Setup Makefile. [lenadax]
Run tests with pytest. [lenadax]
1.0a1 (2023-05-15)
Use webresource for resource registration. [rnix]
0.4 (2025-10-25)
Pin upper versions of dependencies. [rnix]
0.3 (2022-10-06)
Modernize JavaScript. [rnix]
0.2 (2020-07-09)
Add show_contextmenu to CalendarTile. Defaults to False. [rnix]
Also check for action length when handling actions dropdown in JS. [rnix]
0.1 (2020-05-30)
Initial. [rnix, thet]
License
Copyright (c) 2017-2021, BlueDynamics Alliance, Austria Copyright (c) 2021-2025, Cone Contributors All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Metadata
Release files for cone.calendar 2.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cone_calendar-2.0.1.tar.gz | 227.6 kB | Without provenance | Details for cone_calendar-2.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cone_calendar-2.0.1-py3-none-any.whl | Python 3 | none | any | Details for cone_calendar-2.0.1-py3-none-any.whl |
Total release size: 458.3 kB
Release files / cone_calendar-2.0.1.tar.gz
| Download URL | cone_calendar-2.0.1.tar.gz |
|---|---|
| Size | 227.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eda46075a2e5887984c16c7858ed97139e902f26387b24dbecaf2c5de8861b84
|
|
BLAKE2b-256 checksum How to use checksums |
76f5206eaa017995da4f1087696c68d647f8cd856291971694ddabfd3ef1621b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.2
|
Release files / cone_calendar-2.0.1-py3-none-any.whl
| Download URL | cone_calendar-2.0.1-py3-none-any.whl |
|---|---|
| Size | 230.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
57e3cb866a21a5862c444169b1a25d67122d6c616c2c06bcdd1fc213ca1daac1
|
|
BLAKE2b-256 checksum How to use checksums |
eb4ecfae4cf9e6e71f4242d86f91ca2b11ea1f87915bafaffde33c8d74fb96f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.2
|
Security for cone.calendar 2.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.