.. You may want to use the usual include line. Uncomment and adjust the path. .. include:: ../Includes.txt ============= Weekly Events ============= :Created: 2010-02-18T17:33:18 :Changed: 2012-02-14T20:09:57 :Classification: t3leweeklyevents :Description: The keywords help with categorizing and tagging of the manuals. You can combine two or more keywords and add additional keywords yourself. Please use at least one keyword from both lists. If your manual is NOT in english, see next tab "language" ---- forEditors (use this for editors / german "Redakteure") forAdmins (use this for Administrators) forDevelopers (use this for Developers) forBeginners (manuals covering TYPO3 basics) forIntermediates (manuals going into more depth) forAdvanced (covering the most advanced TYPO3 topics) see more: http://wiki.typo3.org/doc_template#tags ---- :Keywords: events, appointments, calendar :Author: Sven Reuter :Email: t3le-extensions@t3le.de :Info 4: :Language: en, de |img-1| |img-2| Weekly Events - t3leweeklyevents .. _Weekly-Events: Weekly Events ============= Extension Key: t3leweeklyevents Language: en, de Keywords: events, appointments, calendar Copyright 2011-2012, Sven Reuter, This document is published under the Open Content License available from http://www.opencontent.org/opl.shtml The content of this document is related to TYPO3 \- a GNU/GPL CMS/Framework available from www.typo3.org .. _Table-of-Contents: Table of Contents ----------------- `Weekly Events 1 <#__RefHeading__8179_85638380>`_ **`Introduction 3 <#__RefHeading__8181_85638380>`_** `What does it do? 3 <#__RefHeading__8183_85638380>`_ `Screenshots 3 <#__RefHeading__8189_85638380>`_ **`Users manual 4 <#__RefHeading__8197_85638380>`_** `Creating an event 4 <#__RefHeading__8401_85638380>`_ `Creating appointments 5 <#__RefHeading__9239_85638380>`_ `Creating exception days 5 <#__RefHeading__9241_85638380>`_ **`Administration 6 <#__RefHeading__8201_85638380>`_** **`Configuration 7 <#__RefHeading__8205_85638380>`_** `Use your own fluid templates 7 <#__RefHeading__8207_85638380>`_ `Reference 7 <#__RefHeading__8209_85638380>`_ **`Tutorial 8 <#__RefHeading__8211_85638380>`_** **`Known problems 9 <#__RefHeading__8213_85638380>`_** **`To-Do list 10 <#__RefHeading__8215_85638380>`_** **`ChangeLog 11 <#__RefHeading__8217_85638380>`_** .. _Introduction: Introduction ------------ .. _What-does-it-do: What does it do? ^^^^^^^^^^^^^^^^ This extension allows you to manage periodical, weekly events with multiple appointments. You can display them in event list, week view or a today's appointment view. If you are a little familiar with fluid, you can easily customize the integrated views. .. _Screenshots: Screenshots ^^^^^^^^^^^ This is the today's view: |img-3| This is the week view: |img-4| In the backend you can easily manage events and appointments: |img-5| .. _Users-manual: Users manual ------------ .. _Creating-an-event: Creating an event ^^^^^^^^^^^^^^^^^ First create a sys folder as storage folder. Then in list view you can add your first event. Therefore click “create new record”. Choose “event” and fill out required fields: |img-6| .. _Creating-appointments: Creating appointments ^^^^^^^^^^^^^^^^^^^^^ You can manage events appointment inline at the bottom of the record. Appointments are stored automatically in the same sys folder. .. _Creating-exception-days: Creating exception days ^^^^^^^^^^^^^^^^^^^^^^^ On exception days there are no events. The appointments of this day are skipped. Create an exception day on the same sys folder. .. _Administration: Administration -------------- Create an own sys folder for storing extensions records. By adding these lines of code in your PageTSConfig of this sys folder the editor only can add events and exception days. Appointments are allowed only via an event: :: mod.web_list.allowedNewTables = tx_t3leweeklyevents_domain_model_event, tx_t3leweeklyevents_domain_model_exceptionday mod.web_list.hideTables = tx_t3leweeklyevents_domain_model_appointment Keep in mind that there is a line break in first line of code. .. _Configuration: Configuration ------------- - install extensions via Extension Manager - in your template include extensions static template: “Weekly Events (t3leweeklyevents)” - go to constants editor, choose PLUGIN.TX\_T3LEWEEKLYEVENTS (4) and set storage pid - when you want to use your own fluid templates you can set the directories on this page .. _Use-your-own-fluid-templates: Use your own fluid templates ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ You can copy extensions templates from EXT:t3leweeklyevents/Resources/Private/. There are three directories you have to copy to your own location (mostly in fileadmin). There you can modify the templates. In constants editor set the new paths. .. _Reference: Reference ^^^^^^^^^ There is no complex TypoScript to write for this extension. Just set constants as described. You can overwrite language labels in your TypoScript Setup like this: :: plugin.tx_mmorganization._LOCAL_LANG { de { label = new translation } } Check t3leweeklyevents/Resources/Private/Language/locallang.xml for available labels. .. _Tutorial: Tutorial -------- - install extensions via Extension Manager - create a sys folder for the events - create some events and appointments (storage pid) - in your template include extensions static template: “Weekly Events (t3leweeklyevents)” - go to constants editor, choose PLUGIN.TX\_T3LEWEEKLYEVENTS (4) and set storage pid - go to the page where you want to display your events - insert plugin and choose your favorite view - that's it :-) .. _Known-problems: Known problems -------------- None at the moment .. _To-Do-list: To-Do list ---------- Add view “upcoming events” - events from now on, fix number of events, respecting exception days .. _ChangeLog: ChangeLog --------- .. ### BEGIN~OF~TABLE ### .. _2-0-1: 2.0.1 ^^^^^ .. container:: table-row Version 2.0.1 Changes Fixed fluid template, when no event picture uploaded. .. _2-0-0: 2.0.0 ^^^^^ .. container:: table-row Version 2.0.0 Changes Added to TER .. ###### END~OF~TABLE ###### |img-2| 11 .. ######CUTTER_MARK_IMAGES###### .. |img-1| image:: img-1.png .. :align: left .. |img-2| image:: img-2.png .. :border: 0 .. :height: 21 .. :hspace: 9 .. :id: Grafik2 .. :name: Grafik2 .. :width: 87 .. |img-3| image:: img-3.png .. :align: left .. :border: 0 .. :height: 115 .. :id: Grafik1 .. :name: Grafik1 .. :width: 198 .. |img-4| image:: img-4.png .. :align: left .. :border: 0 .. :height: 460 .. :id: Grafik3 .. :name: Grafik3 .. :width: 520 .. |img-5| image:: img-5.png .. :align: left .. :border: 0 .. :height: 320 .. :id: Grafik4 .. :name: Grafik4 .. :width: 493 .. |img-6| image:: img-6.png .. :align: left .. :border: 0 .. :height: 641 .. :id: Grafik5 .. :name: Grafik5 .. :width: 433