- Feb 27, 2017
-
-
Jasmina Liessmann authored
Use Bootstrap grid for arrangement of navigation items. Shorten the characters of the current page title in DocHeader to title length defined in user settings or default to '50'. Resolves: #79849 Releases: master Change-Id: I0825818cd961b8bb7f928cb1389537506d5ed40b Reviewed-on: https://review.typo3.org/51831 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Joerg Kummer <service@enobe.de> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
-
- Feb 26, 2017
-
-
Georg Ringer authored
The check if the list module is available for the user must be extended to check for false as well. Resolves: #79974 Releases: master, 7.6 Change-Id: Icd1e2c2cff3f37ce6763bc4f64d4011443226a68 Reviewed-on: https://review.typo3.org/51808 Tested-by:
Thomas Hohn <thomas@hohn.dk> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
-
Joerg Kummer authored
The notification js object gets "duration" as additional default value. This can be increased for acceptance tests to ensure notifications don't vanish before they are tested. Activate two ac tests again that were disabled for that reason. Resolves: #79963 Releases: master Change-Id: Ib7bf046e7de1999fc693e08eeefc7d4c420bddae Reviewed-on: https://review.typo3.org/51832 Tested-by:
Nicole Cordes <typo3@cordes.co> Reviewed-by:
Andreas Fernandez <typo3@scripting-base.de> Reviewed-by:
-
Helmut Hummel authored
The dynamic variable syntax does currently work in Fluid standalone, but not with the variable provider used for TYPO3 CMS (as promised) To fix this, we copy the necessary code to the CMS variable provider as it is only a few lines. Cover that with tests and apply it in the image cropper UI as one example. Resolves: #79997 Releases: master Change-Id: I3a811b0d496b12191d2ccbaa9c07525f4cf8f340 Reviewed-on: https://review.typo3.org/51841 Tested-by:
Anders Kostending <aha@systime.dk> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Joerg Boesche <typo3@joergboesche.de> Reviewed-by:
Morton Jonuschat <m.jonuschat@mojocode.de> Tested-by:
-
- Feb 25, 2017
-
-
Raphael Okon authored
The fix is to remove previously introduced CSS hacks and provide a cleaner and leaner base Resolves: #79998 Resolves: #79989 Releases: master Change-Id: Ic63b3acaf46f50f92a3c44578c28748dfca74351 Reviewed-on: https://review.typo3.org/51842 Tested-by:
Jasmina Ließmann <code@frauliessmann.de> Tested-by:
Helmut Hummel <typo3@helhum.io> Tested-by:
-
- Feb 24, 2017
-
-
jliessmann authored
Use bootstrap grid to arrange image thumbnails Resolves: #79960 Releases: master Change-Id: I99ef6fc159c1497ea5464ef33398cf799c91a534 Reviewed-on: https://review.typo3.org/51810 Reviewed-by:
-
Mads Jensen authored
Added CSS to ensure images are contained in parent element. Resolves: #79971 Releases: master Change-Id: I38a4038af067166d771d012e2ddc0e2983060513 Reviewed-on: https://review.typo3.org/51802 Reviewed-by:
Morten Pless <mpl@systime.dk> Tested-by:
Christer V <cvi@systime.dk> Reviewed-by:
Timo Hund <timo.hund@yahoo.com> Tested-by:
Josef Glatz <josef.glatz@typo3.org> Tested-by:
-
- Feb 22, 2017
-
-
Benni Mack authored
Streamlined EXT:about extension as a first step to clean up the whole TYPO3 Core base: - Moved locallang file to EXT:about, as it is only used in this extension - Removed usage of TYPO3_LOADED_EXT/ext_emconf.php in favor of PackageManager (needed to add the authors into each Package) - Fully added all external libraries in use (not including -dev requirements) - Moved EqualHeight.js to EXT:about as it is only used in this extension - Proper usage of Fluid layouts - Streamlined code, variables, imports and comments - Reviewed comments in PHP Resolves: #79948 Releases: master Change-Id: Ia6c2d6b519bc34847131f06908c2c441b9248a8b Reviewed-on: https://review.typo3.org/51790 Tested-by:
Frans Saris <franssaris@gmail.com> Tested-by:
Mona Muzaffar <mona.muzaffar@gmx.de> Reviewed-by:
-
Georg Ringer authored
- Use a div instead of an input field to avoid issues like tooltip not shown because of the disabled attribute. - Trigger onchange from LinkBrowser popup - If no value found, show the input field, which makes it easier to e.g. enter an external url. - Show helpful title for toggle button on hover Resolves: #79667 Related: #79670 Releases: master Change-Id: If00d892d0ae7aebe0dfc5f17f5d43af16d0ee730 Reviewed-on: https://review.typo3.org/51592 Reviewed-by:
-
- Feb 20, 2017
-
-
Josef Glatz authored
Improve visual differentiation of content and copyright notice. A visual hruler is added. Font-size and color is slightly adopted. Resolves: #79895 Releases: master Change-Id: Idd7190d860c6083d3333b82dba9a796a0bce0e2c Reviewed-on: https://review.typo3.org/51746 Tested-by:
Riccardo De Contardi <erredeco@gmail.com> Reviewed-by:
-
- Feb 19, 2017
-
-
Thomas Hohn authored
Currently it's hard to read the progress of tasks in the scheduler due to the combination of blue, white and light grey. Change of background color for progress from f5f5f5 to dedede makes it more readable. Resolves: #79844 Releases: master Change-Id: I896e66452e3093d729522c9ca7da6b597e0451c7 Reviewed-on: https://review.typo3.org/51710 Tested-by:
Tomas Norre Mikkelsen <tomasnorre@gmail.com> Reviewed-by:
Philipp Gampe <philipp.gampe@typo3.org> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
Sascha Egerer <sascha@sascha-egerer.de> Tested-by:
-
- Feb 17, 2017
-
-
Wouter Wolters authored
Resolves: #79880 Releases: master Change-Id: Ia4b240614ee2c1c1a220fcea7d0f7d13ad518acb Reviewed-on: https://review.typo3.org/51734 Tested-by:
Daniel Goerz <ervaude@gmail.com> Tested-by:
-
Frank Naegler authored
Remove usage of htmlEscape from core templates, because it is deprecated since #75575 Resolves: #79842 Related: #75575 Releases: master Change-Id: I62c53cb9cdba585f5ead920154dcef729c8c02eb Reviewed-on: https://review.typo3.org/51709 Tested-by:
Jigal van Hemert <jigal.van.hemert@typo3.org> Tested-by:
-
- Feb 15, 2017
-
-
Benni Mack authored
The Fluid namespace "core" is now available globally, making it obsolete to register the namespace manually in each file any core viewhelper is necessary. This is also a precursor for integrating Frontend Editing content editable ViewHelpers in all places of TYPO3 Frontend when fluid templates are in use. Resolves: #79817 Releases: master Change-Id: I7691107fa7c02e71b848cd8d0bb0eecdae5a8171 Reviewed-on: https://review.typo3.org/51688 Tested-by:
Mattias Nilsson <tollepjaer@gmail.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
-
- Feb 13, 2017
-
-
Frank Naegler authored
This patch removes the setTimeout hacks from FormEngineValidation.js. Since the removal of ExtJS from FormEngine this hacky solution could be removed and speed up the FormEngine validation process. Resolves: #79765 Releases: master Change-Id: I18f38a1641ea7916844cd464da3f31ad0fc22517 Reviewed-on: https://review.typo3.org/51643 Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
-
Helmut Hummel authored
Refactor rendering to use two templates, a layout and a partial to be more flexible. Now also force the crop to be applied, even when the editor does not open the image manipulation. This is important when only one aspect ratio is allowed to not allow the editor to save an invalid state. Eliminate several quirks in the TypeScript code, among them: * reset state when closing the cropper * reset state when modal is dismissed * correctly initialize all previews * show correct size of crop area for big images * avoid accidental dismiss of the modal Last but not least add the accidentally removed form engine wizard html fields again. Resolves: #79764 Resolves: #79731 Resolves: #79753 Resolves: #79674 Releases: master Change-Id: I0a24d6418d6263b00c3fbf31901fd7c67e9fc97e Reviewed-on: https://review.typo3.org/51642 Tested-by:
-
- Feb 12, 2017
-
-
Georg Ringer authored
To make the doc header nicer on smaller (13") screens, the following changes are applied: - Remove the label of the language select box - Remove the media query Resolves: #79701 Releases: master Change-Id: Ie3581c37f4169c89aa72aa3a429dbdf073901e0f Reviewed-on: https://review.typo3.org/51602 Tested-by:
-
- Feb 11, 2017
-
-
Andreas Fernandez authored
Resolves: #79729 Releases: master Change-Id: I689e8ecd0ffa2d005931e6162fb8df5d9694da3d Reviewed-on: https://review.typo3.org/51629 Tested-by:
Michael Oehlhof <typo3@oehlhof.de> Reviewed-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
-
- Feb 10, 2017
-
-
Tymoteusz Motylewski authored
Since context menu refactoring https://review.typo3.org/#/c/50124/ the context was not showing when right clicking on the page title in the page tree. Resolves: #79710 Releases: master Change-Id: Idcdb9a8afebe050bb0b409b7d475285d1a1d4419 Reviewed-on: https://review.typo3.org/51609 Reviewed-by:
volker kemeter <volker@kemeter.de> Reviewed-by:
-
- Feb 09, 2017
-
-
Tymoteusz Motylewski authored
Add the return url to the clickmenu option "'Create new' wizard". Resolves: #79683 Releases: master Change-Id: Ib38a4e2623d0b2d24597bfdca62f133714297584 Reviewed-on: https://review.typo3.org/51601 Reviewed-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Tested-by:
-
Josef Glatz authored
Add missing `bottom-margin` by only overriding `margin-top` of generic `h2` style. Resolves: #79699 Releases: master Change-Id: I9dc274305694aef3c526c3a342d7b994765094ec Reviewed-on: https://review.typo3.org/51597 Tested-by:
-
- Feb 07, 2017
-
-
Helmut Hummel authored
This feature extends the image cropping tool in the backend so that editors can now not only select one crop area, but multiple ones per image. Within the crop are now also a focus are can be selected and to preview areas that will be covered once the image is rendered in the frontend one or more cover areas can be configured to be shown inside the crop area. This change also adds a format.json view helper and a view helper to generate backend URIs that are used in the now fully Fluid rendered imageManipulation element. This is the TYPO3 integration part. TypeScript and CSS will be done in a second commit. Resolves: #75880 Releases: master Change-Id: I646f0f0a149d05d1f3d8283bcc92ab09aede768e Reviewed-on: https://review.typo3.org/51515 Tested-by:
-
Raphael Okon authored
This adds the necessary TypeScript and CSS changes for the new imageManipulation element. Resolves: #75880 Releases: master Change-Id: I56c5042c6e6de7141ba59014ab31051c5c9cc34f Reviewed-on: https://review.typo3.org/51565 Tested-by:
-
Michael Oehlhof authored
If a page is selected in page module which content is also shown on other pages, now a notice is shown with the titles and pid of these pages. Resolves: #69572 Releases: master Change-Id: Ie66564da98160825f5759c6ac4937fbbeaafdce0 Reviewed-on: https://review.typo3.org/51049 Tested-by:
-
Tymoteusz Motylewski authored
This change unifies the ClickMenu functionality of the pagetree (ExtJS) with the ClickMenu code given in other areas of the TYPO3 Backend. The following changes are made: * Unify the naming, it's "ContextMenu" not "ClickMenu" anymore * Configuration for record types are unified, the clickmenu shows the same entries in the same order in any place. * ExtJS-based ContextMenu is removed, all based on the new ContextMenu functionality. * A new way for extending the items inside the ContextMenu is handled via ItemProviders, which can easily be extended. * Configuring clickmenu items is not done based on PageTS (as it was handled with the ExtJS pagetree), however certain items can be disabled via PageTS. Resolves: #78192 Releases: master Change-Id: I380ac73ced10fdc7b1fdec7261e2d56da3d7d938 Reviewed-on: https://review.typo3.org/50124 Reviewed-by:
-
Jo Hasenau authored
Resolves: #13749 Releases: master Change-Id: Iba428acf25875479aa703ad4a93832331ed0b0be Reviewed-on: https://review.typo3.org/47135 Reviewed-by:
Jo Hasenau <info@cybercraft.de> Tested-by:
Bjoern Jacob <bjoern.jacob@tritum.de> Tested-by:
-
Oliver Hader authored
This feature introduces a new functionality called "allowLanguageSynchronization" which can be set on a field configuration of a TCA column. This is the successor of "l10n_mode=mergeIfNotBlank" as the old option had several conceptual downsides: 1) "mergeIfNotBlank" took the value of the default record during runtime, but only if the translation field was empty. This means it was not possible to see what the record actually contained without having all fields of the parent at hand. 2) It was not possible to have a value "santa" in the original record but remove the option in a translation (because an empty string "" implicitly triggered the runtime call in the frontend) 3) "mergeIfNotBlank" did not work on relations except for files fetched via the FileRepository API calls, but for no other inline elements. 4) "mergeIfNotBlank" did the overlay functionality in the frontend, but only FormEngine and DataHandler took care of the option. Custom backend modules had to implement the same functionality. 5) In FormEngine, there was an icon in the translation record that if the record kept empty the value of the original language was taken, but this is not optimal in terms of usability. 6) "mergeIfNotBlank" did not take the new l10n_source option into account, where localizations could be made from other records than the default language "0". The new feature can be set on any TCA column setting: $GLOBALS['TCA'][<table-name>]['columns'] [<field-name>]['config']['behaviour'] ['allowLanguageSynchronization'] = true; This brings an option to records with translations (both from l10n_parent and l10n_source) to have the value for all translations synchronized or explictly have a checkbox to use a custom value. The information whether a field is custom filled, or kept in sync from l10n_parent/l10n_source is stored in a separate field called "l10n_state" inside the database. The introduced upgrade wizard and TCA migration to remove "l10n_mode=mergeIfNotBlank" has been modified to migrate to this option and add a l10n_state database field if a TCA table used "mergeIfNotBlank" but did not add the l10n_state field manually via ext_tables.sql yet. New extensions can easily use the new option right away, extensions that need to stay compatible with v7 and v8 can add both options right away to have the same output. The main goals to achieve with this change is now: * Have consistent database values for all records regardless of l10n_mode=mergeIfNotBlank paving the way to fetch translated records without having to overlay (once l10n_mode=exclude is also copying values and relations) * Be more explicit for editors about records that have a different or the same state as their l10n_parent/l10n_source as a benefit for bigger instances with a lot of languages * Avoid hidden magic when retrieving localized records in the TYPO3 Frontend. Resolves: #79658 Related: #79243 Releases: master Change-Id: I6c2dbfeb09b47f958a536c9ab050c24ba4bbcbbd Reviewed-on: https://review.typo3.org/51291 Tested-by:
-
Andreas Fernandez authored
TypeScript is updated to at least version 2.2.0. Existing code is recompiled due do changes of defaults in TypeScript. Resolves: #79653 Releases: master Change-Id: Id656c0319ee021c8475e607e5dbe35a21074dd79 Reviewed-on: https://review.typo3.org/51560 Tested-by:
-
- Feb 06, 2017
-
-
Benjamin Kott authored
CSS Styled Content has been a long time the preferred way of rendering content in the frontend. Fluid Styled Content was introduced as successor of CSC, but the feature set diverged from the beginning. The lack of flexibility and incomplete feature set in comparision to CSC made it hard to migrate existing instances. Since TYPO3 CMS 7.6 Fluid-Templates are the defined standard and official recommendation for content rendering. The feature set of FSC is now matching CSC. Both content renderings are now streamlined to be fully compatible with each other. For the period of CMS 8 LTS CSC will share the same capabilities to make an transition as easy as possible. CSC is now deprecated and goes into maintenance mode and will be removed with CMS 9. For compatibility, CSC is now supporting Textmedia that was before exclusive to FSC. But also FSC has learned some tricks from CSC. Fluid Styled Content has now support for all content elements pr...
-
Andreas Fernandez authored
When validating input fields of the FormEngine fails, a button is now rendered into the least possible button bar in the module document header. Clicking the button renders a list of all input elements whose validation failed. Clicking onto a field in that list automatically focuses the field in the form. Resolves: #79521 Releases: master Change-Id: I9e232f4d1b27216ccf4a1c7b88d4a9c70b49f4f0 Reviewed-on: https://review.typo3.org/51452 Reviewed-by:
Frank Nägler <frank.naegler@typo3.org> Tested-by:
-
Georg Ringer authored
Render link information below a link field to help editors. Instead of 't3://page?uid=92 _top "a class" "a title"' the user will get relevant information. Resolves: #28171 Releases: master Change-Id: Ic285a10e1de67bf60dd5235885a8d0037792999a Reviewed-on: https://review.typo3.org/51479 Reviewed-by:
-
- Feb 05, 2017
-
-
Michael Oehlhof authored
Resolves: #67243 Releases: master Change-Id: Ic3d1bc45b9db9ae3eb6fd8f13a03fcf9125d7422 Reviewed-on: https://review.typo3.org/51037 Tested-by:
-
Christian Kuhn authored
Opening a collapsed inline relation containing null placeholders does not correctly initialize and both the value field as well as the placeholder field are shown. Easily reproducible with a FAL relation on a page record. Fix JavaScript to initialize correctly. Change-Id: I27b52b9f69beb24d0309422cbcf2b67cc8190e07 Resolves: #79632 Related: #79440 Releases: master Reviewed-on: https://review.typo3.org/51542 Tested-by:
Alex Kellner <alexander.kellner@einpraegsam.net> Tested-by:
-
- Jan 30, 2017
-
-
Andreas Fernandez authored
Currently, a warning sign is rendered next to field labels whose validation failed. Failed validations are errors and thus another icon should be rendered. With this patch, a red circle containing an exclamation mark is rendered. It’s the same icon as in the tabs holding affected fields. Resolves: #79537 Releases: master Change-Id: I01b783c36dfac551bf6e9f0cb8fc703290c3eb72 Reviewed-on: https://review.typo3.org/51460 Tested-by:
-
- Jan 26, 2017
-
-
Christian Kuhn authored
The patch introduces a new API on FormEngine element level that substitutes the old "wizards" / renderWizard() API with a more powerful system. Single wizards are now split into one of three categories: * An informational wizard * A control button / icon * A true wizard with additonal functionality Method renderWizards() is still called in elements for compatibility reasons if people added own scrip/popup/userFunc wizards, but all core wizards are migrated. The patch significantly cleans the HTML of single elements, especially HTML stuff that was added by the SingleFieldContainer is now put down to single elements, while main HTML wraps formerly done by renderWizards() is fetched "up" to single elements. This gives single elements full control about the main HTML it is producing, which is a must have preparation in order to further advance in this area and to switch single elements to fluid rendering in one of the next steps. The patch brings a pretty huge list of TCA changes and simplifications, all TCA changes are supported by TCA migration, so existing extensions should benefit out of the box and just get deprecations logged. Change-Id: I45083e14e45bbf40c06267b51c9d0b7c15e2f7ab Resolves: #79440 Resolves: #70032 Releases: master Reviewed-on: https://review.typo3.org/51151 Tested-by:
-
- Jan 25, 2017
-
-
Thorben Nissen authored
Changes the way the svg tree nodes are checked for "indeterminate" state after the data is loaded, so the initial state. Changes code using "rootNode" to using list of all nodes. Removes unused code. Resolves: #79246 Releases: master Change-Id: I7a076a6d3d2c29f0318598227af5d674caa3642f Reviewed-on: https://review.typo3.org/51237 Tested-by:
Thomas Maroschik <tmaroschik@dfau.de> Tested-by:
-
- Jan 23, 2017
-
-
Gianluigi Martino authored
Prevent the escaping of pidRecordTitle in click menu move element. The escaping is already done in the MoveElementController due to the usage of the third (prep) parameter in BackendUtility::getRecordTitle. Resolves: #79088 Releases: master Change-Id: Ib35e9d5a3da7fc76085db910927ada17dbdd0b06 Reviewed-on: https://review.typo3.org/51041 Reviewed-by:
Mathias Schreiber <mathias.schreiber@typo3.com> Tested-by:
-
Georg Ringer authored
As the description is a textarea, the rendering should support lines as well. Resolves: #79406 Releases: master, 7.6 Change-Id: I8774adb07c50aed24b3d3e94e0a0b913aedeb5a9 Reviewed-on: https://review.typo3.org/51379 Tested-by:
-
- Jan 18, 2017
-
-
Wouter Wolters authored
Heven't replaced with haven't Resolves: #79376 Releases: master,7.6 Change-Id: I85b252514378eb4db1eb63f93d9b746ca332602e Reviewed-on: https://review.typo3.org/51346 Reviewed-by:
Robert van Kammen <rvkammen@hotmail.com> Tested-by:
-
- Jan 11, 2017
-
-
Benni Mack authored
The ExtDirect component for fetching the state (for the pagetree) can be simplified by simply using the Storage.Persistent logic which does the same. For this, a simple inline ExtJS onReady code block is added. All functionality related to ExtDirect State Provider is removed. Resolves: #79227 Releases: master Change-Id: I464ffd0608c1fd38cd81c8324f044da6f4140847 Reviewed-on: https://review.typo3.org/51224 Tested-by:
-
