- 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:
Josef Glatz <josef.glatz@typo3.org> Tested-by:
Mona Muzaffar <mona.muzaffar@gmx.de> Tested-by:
TYPO3com <no-reply@typo3.com> Tested-by:
volker kemeter <volker@kemeter.de> Reviewed-by:
Andreas Fernandez <typo3@scripting-base.de> Tested-by:
-
Anders Kostending authored
New features/fixes: 4.4.4: * Fix calculation of clock skew when page is backgrounded before timers are scheduled. 4.5.0: * Add node.count. * Fix overlapping circles in d3.pack and d3.packSiblings. Resolves: #79713 Releases: master Change-Id: I1d2f4a323bddb4f25a2a5d680912e1f1bbbdb33a Reviewed-on: https://review.typo3.org/51611 Tested-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
-
Sascha Egerer authored
In PHP 7.1 it is not possible anymore to assign a value to a variable of type string with `[]` appended. In older PHP versions the variables was silently converted to an array but in PHP 7.1 a warning is thrown. Beside that the variable must be of type string anyway and not an array. Resolves: #79709 Releases: master Change-Id: Ie36dcf89cff23e7837d1f559cd05b3f9f448360e Reviewed-on: https://review.typo3.org/51608 Tested-by:
Johannes Kasberger <johannes.kasberger@reelworx.at> Tested-by:
-
Georg Ringer authored
Especially if setting links to records, the default size of the popup is just too small. Change it to 1000 px width. Resolves: #79702 Releases: master Change-Id: I63f0837b6fd53d74c4686822ab4d1c8618961454 Reviewed-on: https://review.typo3.org/51603 Tested-by:
Nicole Cordes <typo3@cordes.co> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
-
Christer Vindberg authored
Removed use of undefined variable. Resolves: #79622 Related: #79622 Releases: master Change-Id: I91935ec80e2ff2963dce5b6bbccbaaa52cd186c3 Reviewed-on: https://review.typo3.org/51607 Tested-by:
Thomas Hohn <thomas@hohn.dk> Reviewed-by:
-
Manuel Selbach authored
Add group "mysql" to select functional tests that require a MySQL Server as a database backend due to testing functionality that is only available on this platform. Resolves: #79509 Releases: master Change-Id: Ia4d653efc56673d666274dabdc86474ffafd4756 Reviewed-on: https://review.typo3.org/51438 Tested-by:
Morton Jonuschat <m.jonuschat@mojocode.de> Tested-by:
-
Jan Kiesewetter authored
php-cs-fixer added "no_alias_functions" to its ruleset of risky fixers. This patch allows risky fixers to be run. Change-Id: I50d01864733c3e0ab5d46cb09a5bb76a0a814561 Resolves: #79716 Releases: master Reviewed-on: https://review.typo3.org/51615 Reviewed-by:
-
Christian Kuhn authored
Unit testing user authentication is still a mess since the class does way too much to be well testable. The patch refactors a number of tests that came in with the session framework test to not rely on mocked $subject anymore, but it also marks a couple of tests to be skipped for now - those should be transferred to functional tests which will probably end up to be much easier to understand and maintainable. Change-Id: Ie57245abc75f92a5a1a44ab51079f523974e9818 Resolves: #79678 Related: #70316 Releases: master Reviewed-on: https://review.typo3.org/51620 Tested-by:
-
- Feb 09, 2017
-
-
Georg Ringer authored
Make life of editors easier by providing a value picker for the field 'target' of the page. An editor can now choose "new window" instead of typing "_blank". Resolves: #79705 Releases: master, 7.6 Change-Id: I43d0c5add037679ee7c99b6cf16efcd2079353fc Reviewed-on: https://review.typo3.org/51605 Reviewed-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Tested-by:
-
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:
-
Josef Glatz authored
Update bower dependency. Add 22 new icons via bower copy task and register them in the IconRegistry. Resolves: #79715 Releases: master Change-Id: I76fa9090e5a26bdea01afc52c3edba281bac2771 Reviewed-on: https://review.typo3.org/51612 Tested-by:
Benjamin Kott <benjamin.kott@outlook.com> Tested-by:
-
Frank Naegler authored
This patch add another icon for the „run on next cron“ button and add tooltips for a better and faster understanding of the buttons. Resolves: #79695 Related: #45537 Releases: master Change-Id: I0ba372f2f884af22c1f4fd74be99208493624971 Reviewed-on: https://review.typo3.org/51598 Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
-
Georg Ringer authored
By using mb_strlen for checking the length, the check counts multibyte values now correctly. Resolves: #79684 Releases: master Change-Id: Idcc9fc6e77d0cd42bc43986acb956af67da2453d Reviewed-on: https://review.typo3.org/51593 Reviewed-by:
Stephan Großberndt <stephan@grossberndt.de> Tested-by:
Philipp Gampe <philipp.gampe@typo3.org> Tested-by:
Mathias Brodala <mbrodala@pagemachine.de> Reviewed-by:
-
Josef Glatz authored
In addition to 16:9, 4:3, 1:1 and free another common image ratio "3:2" (DSLR default format) is introduced. Resolves: #79677 Releases: master Change-Id: Iac4aff754fe07216a6b956a47ac535eadacab553 Reviewed-on: https://review.typo3.org/51571 Tested-by:
Alexander Grein <alexander.grein@gmail.com> Reviewed-by:
Harry Glatz <glatz@analog.de> Tested-by:
-
Frank Naegler authored
Since the ImageManipulation wizard supports multiple crop variants, the GalleryProcessor is broken. This patch add support for multiple crop variants in the GalleryProcessor and MediaViewHelper Resolves: #79698 Related: #75880 Releases: master Change-Id: I588c5a4b3d44110fa8460094bd4c9fe950b5cc53 Reviewed-on: https://review.typo3.org/51596 Tested-by:
Helmut Hummel <typo3@helhum.io> Tested-by:
-
Susanne Moog authored
Class DocumentationFile compared a real path with a symlinked path resulting in an exception, even though both paths are the same. Now realpath is called for both paths. Change-Id: Ib1baf8a721ee2bafbba4b4bdeaefc996fdc9a6a8 Resolves: #79690 Releases: master Reviewed-on: https://review.typo3.org/51586 Tested-by:
Tobi Kretschmann <tobi@tobishome.de> Tested-by:
Daniel Goerz <ervaude@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:
Riccardo De Contardi <erredeco@gmail.com> Reviewed-by:
Michael Oehlhof <typo3@oehlhof.de> Tested-by:
-
- Feb 08, 2017
-
-
Kevin Appelt authored
When tabbing trough a form in frontend the honeypot textfield was reachable. Add a tabindex -1 which prevents the cursor to enter the hidden field. Resolves: #79688 Releases: master Change-Id: I0dbdb7911fe4c159236c53dd425a62c9404cd973 Reviewed-on: https://review.typo3.org/51581 Reviewed-by:
Ralf Zimmermann <ralf.zimmermann@tritum.de> Tested-by:
Bjoern Jacob <bjoern.jacob@tritum.de> Tested-by:
-
Benjamin Kott authored
The database field `section_frame` is only available if CSS Styled Content was installed previously, that needs to be respected by the upgrade wizard and only enable the wizard if the field is present in the database. Releases: master Resolves: #79622 Change-Id: I276dae3ea8ca8a07001b378ab8789e054d76c947 Reviewed-on: https://review.typo3.org/51561 Reviewed-by:
Frans Saris <franssaris@gmail.com> Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
-
Nicole Cordes authored
Due to change https://review.typo3.org/51283/ the defaultPaths in Fluid overwrite the configuration paths for the first (0-indexed) array item. This means currently it is not possible to define an own Fluid template path with index 0. This patch merges both arrays and ensures the configuration paths are added at last. This is needed because Fluid Standalone is using template paths from last to first. Resolves: #79681 Releases: master Change-Id: I84398c8218836b46583333bf64ba87ef4a55625d Reviewed-on: https://review.typo3.org/51575 Tested-by:
Claus Due <claus@phpmind.net> Reviewed-by:
-
Claus Due authored
This patch fixes an issue with TemplatePaths, where paths for a given extension key get used at two execution points: * Before TS becomes available * At any time after TS becomes available In this case, TemplatePaths holds on to the fallback paths which the first rendering detects (since TS is not availble, fallback paths get returned) and all subsequent rendering of any template in that extension context, yields only the fallback paths and ignores what is defined in TS. By not allowing fallback paths to be cached in runtime, the problem is prevented. Change-Id: Idd0216f67f9a7f875a4509b34c9a32f66208db93 Resolves: #79662 Releases: master Reviewed-on: https://review.typo3.org/51564 Tested-by:
Morten Pless <mpl@systime.dk> Tested-by:
-
- Feb 07, 2017
-
-
Georg Ringer authored
Enable linking to any record by migrating the code of EXT:linkhandler into the core. Resolves: #66373 Resolves: #66374 Releases: master Change-Id: I749103e201d387ae826575c6acb3cdcdf639e966 Reviewed-on: https://review.typo3.org/51526 Reviewed-by:
-
Wouter Wolters authored
Resolves: #79668 Releases: master Change-Id: I78b9b85a5af2170ddb725dee969f090be1d444e3 Reviewed-on: https://review.typo3.org/51566 Tested-by:
-
Thomas Hohn authored
Adds two new configuration options to Install Tool which are used when saving records using the DataHandler: * disable the validation of records after saving them * if validating, make a strict value comparison ('' !== 0) instead of the default loose comparison ('' == 0) Fixes: #79438 Releases: master Change-Id: I01dfae57b046db00a531dfdfc386e43fe32329e4 Reviewed-on: https://review.typo3.org/51405 Tested-by: -
Wouter Wolters authored
Status codes are only returned when running in dry-run mode. Resolves: #79641 Releases: master,7.6 Change-Id: I3ca770d3f8c0af5aba5793cd4155722b8b68298c Reviewed-on: https://review.typo3.org/51554 Tested-by:
-
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:
-
Marco Huber authored
With this patch you can set a customWidgetId parameter in the widget viewhelper. This id is used in the widget identifier in addition to the nextWidgetNumber. With this patch two equal widgets in different content elements don't influence each other. A good value for the customWidgetId is the {contentObjectData.uid}. Example: <f:widget.paginate customWidgetId="{contentObjectData.uid}" ... Resolves: #47006 Releases: master Change-Id: Ief1d38457da73a35e652f11d82f441898e0394d3 Reviewed-on: https://review.typo3.org/51518 Reviewed-by: -
Michael Oehlhof authored
Resolves: #12211 Releases: master Change-Id: I382945cd92dd8ca6c99ea200f93ea3ca2dfdef41 Reviewed-on: https://review.typo3.org/50926 Reviewed-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:
-
Philipp Kitzberger authored
Resolves: #79337 Releases: master Change-Id: Ib93ac38f944d6ca74f6162e705f6bfa4fa3214a9 Reviewed-on: https://review.typo3.org/51324 Tested-by:
Joerg Boesche <typo3@joergboesche.de> Reviewed-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:
Benni Mack <benni@typo3.org> Tested-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:
-
Claus Due authored
Given the assumption that this particular resource is not one that changes very often one can benefit from storing this in the cache_runtime in order to avoid fetching the same avator more than one in a request. Change-Id: Idc39c59dc8213f861ef4da7c9da4f5a95cfab9ac Resolves: #79547 Releases: master Reviewed-on: https://review.typo3.org/51467 Reviewed-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:
-
Frans Saris authored
Resolves: #79661 Releases: master Change-Id: I9639ad35764090aa38128671084e239b53639850 Reviewed-on: https://review.typo3.org/51563 Tested-by:
-
Philipp Gampe authored
Ignored files require the full path to a file for resurrection, not just the headline. Resolves: #79659 Releaes: master Change-Id: I7f4ea9a0b2080c71dcd7d708c1c0ffccb30f15be Reviewed-on: https://review.typo3.org/51562 Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> 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:
-
