Feature #15575
closedInclude date selection widget into the TYPO3 Core
0%
Description
The extension date2cal provides a valuable usability improvement by adding a selection widget for dates to date fields in the back-end.
To avoid conflicts with different dependencies (JS frameworks, other core features, refactoring, etc.) a rewritten and well-planned variant of the extension date2cal shall be integrated into the TYPO3 Core.
(issue imported from #M2497)
Updated by Oliver Klee almost 19 years ago
Please note that the date2calendar extension has copied some TYPO3 code that contained issue 0001703 and that that issue still needs to get fixed in the extension's copy of that code.
Updated by Clemens Riccabona over 17 years ago
Which extension is meant? There are two extensions called 'date2calendar'.
The extension keys are: erotea_date2cal and date2cal.
Since Version 4.1 of typo3 I prefer using 'date2cal' because of the provided 't3skin' style of the dhtml calendar.
I vote for integrating to the core too!
Updated by Clemens Riccabona almost 17 years ago
I had a look at "date2cal" (NOT erotea_date2cal!!) behaviour, in correspondance to the behaviour described in #15139.
As far as I can see, its behaviour is exactly what you want.
If you click on the checkbox, the value of now() is inserted in the field.
So what is about integrating this extension into the core and getting rid of another xclassing extension?
The feature is very valuable to editors anyway!
Updated by Oliver Hader over 16 years ago
Currently date2cal was "refactored" between its major version 6 and 7. However, it does not work with TYPO3 4.2. To avoid this, we should integrate and maintain the functionalities (not the extension as it is!) into the TYPO3 Core.
Updated by Steffen Kamper over 16 years ago
version 7.0.1 does work with 4.2
I think it should integrated in core for 4.3 (not as extension)
Updated by Oliver Hader over 16 years ago
- the functionalities have to work with prototype (and have to be updated whenever we decide to upgrade prototype)
- the JavaScript labels (from date2cal in ./js/jscalendar/land/calendar-[language].js) have to come from the TYPO3 localization
Updated by Martin Holtz about 16 years ago
The caching mechanism does not take care of starttime/endtime of content elements. (which is not much important, if you can only add date into content elements, but you will notice it if you have date and time)
So if a page is inserted into cache with an default expire date (24hours), it is possible that there are some content elements on that page which have an starttime or an endtime within these 24hours.
(f.e.: at 2pm the page is cached, the starttime of an content element is 3pm but it will be first shown at 2pm at the next day - when the page cache is expired).
I wrote a extension which xclasses tslib_fe and checks on that page if there are content elements.
http://typo3.org/extensions/repository/view/cacheexpire/0.0.2/
I think it could be a first step - i did not check if it works with workspaces or versioning, and not with extensions like tt_news (where i think it is much more important).
It is on forge:
http://forge.typo3.org/projects/show/extension-cacheexpire
Btw.: date2cal 7.1.0 works with trunk (TYPO3 4.3-dev)
Updated by Steffen Gebert about 15 years ago
This can be dropped/closed (as #20829 fixed this)
Updated by Christian Kuhn about 15 years ago
Resolved as duplicate of #20829
This is now realized with ExtJS and will be included in TYPO3 4.3