This project is mirrored from Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer or owner.
Last successful update .
  1. 16 Jul, 2015 2 commits
  2. 19 Jan, 2015 1 commit
  3. 16 Dec, 2014 1 commit
  4. 13 Dec, 2014 1 commit
  5. 08 Dec, 2014 1 commit
  6. 06 Dec, 2014 1 commit
  7. 14 Sep, 2014 1 commit
  8. 22 Jun, 2014 1 commit
    • Michael Schams's avatar
      [TASK] Re-work/simplify copyright header in PHP files - Part 2 · 02670b20
      Michael Schams authored
      This patch replaces the copyright/license header in PHP files with a
      new, simplified one. The new header does not show the year figure, nor
      an author name, and refers to the LICENSE.txt file for the full
      copyright information. License is: GPL2 or any later version.
      This is a multi-part commit due to the huge number of changed files.
      See issue #59778 for further details.
      Resolves: #59778
      Releases: 6.3, 6.2
      Change-Id: I155df27e66ec103a4f83356adef7dc441585b54a
      Reviewed-by: Krzysztof Adamczyk
      Tested-by: Krzysztof Adamczyk
      Reviewed-by: Markus Klein
      Tested-by: Markus Klein
  9. 21 Mar, 2014 1 commit
  10. 20 Mar, 2014 1 commit
  11. 15 Mar, 2014 1 commit
    • Ernesto Baschny's avatar
      [TASK] Install Tool: Optimize permission checking and fixing · 18a8f444
      Ernesto Baschny authored
      * Adjust default permissions back to "world readable" (775/664)
      * Do not attempt to fix permissions on an existing folder structure
      * Streamline the separation of Notices, Warnings and Errors
      * Cosmetical optimizations in the "Folder Structure" item
      * Also report if the default permissions are too insecure (i.e.
        world writeable / readable).
      Note that the new defaults (775/664) are set to make the system work
      by default on almost most scenarios, but the recommended secure setup
      is still 770/660. This is on purpose to make the administrator aware
      of it but will require manual intervention (i.e. "thinking") if this
      setup will work or not (we cannot detect that automatically).
      Resolves: #52668
      Releases: 6.2
      Change-Id: I77c72617fa58fd808ebc5fd818e94b48c2644102
      Reviewed-by: Christian Kuhn
      Reviewed-by: Wouter Wolters
      Reviewed-by: Stefan Neufeind
      Reviewed-by: Philipp Gampe
      Reviewed-by: Anja Leichsenring
      Tested-by: Anja Leichsenring
      Reviewed-by: Ernesto Baschny
      Tested-by: Ernesto Baschny
  12. 10 Feb, 2014 1 commit
    • Christian Kuhn's avatar
      [TASK] Reduce memory footprint of unit tests · 2d05837d
      Christian Kuhn authored
      Running the whole unit test suite on cli can eat up a significant
      amount of memory. Most of that can not be mitigated due to phpunit
      itself, but we can at least hint the PHP garbage collection by
      unsetting test class properties in tearDown().
      The patch introduces a generic tearDown() method that reflects the
      test class and unsets all temporary properties of the class. In
      effect, tests do not need to take care of unsetting properties.
      The patch removes all tearDown() methods that only unset() stuff
      and keeps others that do additional things but adds a call to
      parent::tearDown(). Private properties are changed to protected,
      so parent::tearDown can reach them. The additional computing
      effort of the reflection is insignificant, the suite is nearly as
      fast as before.
      php 5.3: 1056MB -> 851MB
      php 5.4: 870MB -> 670MB
      php 5.5.: 876MB -> 674MB
      Resolves: #55850
      Related: #51436
      Releases: 6.2
      Change-Id: Ie665c53a3ab35e4808677e483d2099e0511c393f
      Reviewed-by: Helmut Hummel
      Reviewed-by: Anja Leichsenring
      Tested-by: Anja Leichsenring
      Reviewed-by: Christian Kuhn
      Tested-by: Christian Kuhn
  13. 01 Oct, 2013 1 commit
  14. 30 Sep, 2013 1 commit
    • Ernesto Baschny's avatar
      [TASK] Folder not writeable should be an "Error" not a "Warning" · 6f1bbb33
      Ernesto Baschny authored and Wouter Wolters's avatar Wouter Wolters committed
      The Install Tool checks for permissions in it's folder structure.  A
      folder (typo3temp, uploads, fileadmin) not being writeable now is an
      Error and not only a Warning thus displaying a red badge in the Install
      Tool main menu.
      Resolves: #52407
      Releases: 6.2
      Change-Id: I6de5f2eace4ecdf089848efbf063a82302aea093
      Reviewed-by: Christian Kuhn
      Tested-by: Christian Kuhn
      Reviewed-by: Wouter Wolters
      Tested-by: Wouter Wolters
  15. 28 Sep, 2013 2 commits
    • Christian Kuhn's avatar
      [FEATURE] ext:install Relaxed permission check · b869f754
      Christian Kuhn authored
      The document root folder may not have correct permissions and
      they can not be fixed if the owner is not the executing webserver
      This is a common issue during installation, currently the first
      step breaks if permission on document root are not 2770 and the
      folder is not owned by the executing webserver user.
      The patch adds a new option "targetPermissionRelaxed" to
      DirectoryNodes and uses it on the RootNode to lower the severity
      if permissions are not correct. The installation will proceed
      then as long as sub folders can be created.
      Change-Id: Ibde9f7ff0dde14502ac24fdb73c0a2ed384119a6
      Resolves: #52356
      Releases: 6.2
      Reviewed-by: Anja Leichsenring
      Tested-by: Anja Leichsenring
      Reviewed-by: Susanne Moog
      Tested-by: Susanne Moog
    • Christian Kuhn's avatar
      [TASK] ext:install Protect some methods in FolderStructure · 38ace218
      Christian Kuhn authored
      Some methods within FolderStructure class hierachy are public
      but should be used internally only. The patch protects them.
      Change-Id: I273f829f29ca4f5a6da1d03f028be7a8500e222b
      Resolves: #52354
      Releases: 6.2
      Reviewed-by: Wouter Wolters
      Tested-by: Wouter Wolters
      Reviewed-by: Susanne Moog
      Tested-by: Susanne Moog
  16. 19 Jun, 2013 1 commit
    • Christian Kuhn's avatar
      [!!!][TASK] Rewrite install tool · 2e3c9d5e
      Christian Kuhn authored
      Main features:
      * The god class "Installer" is gone and split into two major parts.
      A step controller handling major upgrade and install tasks, and a
      tool controller handling the known install tool actions.
      * The step controller is designed to be always called prior to the
      tool controller, if a step needs execution, it comes up, otherwise
      the tool controller will be executed.
      * The entry point typo3/install/index.php is gone and substituted
      by typo3/sysext/install/Start/Install.php. The file contains a
      lengthy comment to document the main request flow and used GET/POST
      * Most parts of the install tool do not bootstrap the whole system
      anymore, in general only the base bootstrap, dbal (if loaded),
      extbase and fluid ext_localconf.php are loaded. This makes sure
      the install tool can not fatal if some extensions ext_localconf
      is broken. The whole install tool runs without any caching, so a fatal
      in some cache file can not kill the install tool execution.
      * Installing TYPO3 CMS on a dbal enabled system is now handled in
      the step installer directly to make the according code easier to
      * Rendering is done with a simplified fluid standalone view.
      * All install tool forms are CSRF protected.
      * A new and fully unit tested class structure is introduced, designed
      to take care of the basic file and folder structure of the instance.
      It is used during installation to create the needed structure and
      can be called in the install tool to compare and fix the current
      instance structure with the expected structure. In effect, the
      "dummy" package is obsolete. An instance can be created by just
      linking index.php, typo3_src/ and typo3/ within the document root,
      the installer takes care of creating everything else.
      * The installation procedure is released from the package handling.
      Packages will be handled by the extension manager after initial
      installation with another patch.
      Loose ends:
      * The whole package handling needs to be implemented in the
      extension manager.
      * Not all upgrade wizards work, this code area needs some love.
      * A 'core' auto updater could be implemented now. A GSoC project
      is currently running to realize this.
      * The SQL schema migration API is a mess and should be refactored.
      For now, another helper class is introduced to encapsulate some
      of the nasty details.
      * An auto configuration and configuration suggestion system is
      planned and needs to be done. It should suggest best configuration
      options in the install tool, and should auto configure the system
      during installation in the last install step.
      * If the backend or frontend fatals due to some extension that
      triggers a fatal in ext_localconf or ext_tables (for example
      due to a require() of a no longer existing file), a small helper
      action in the install tool could find those extensions and suggest
      to unload them.
      Change-Id: Ice3248caa903449ad6a83ea4f234c7bd125bdb66
      Resolves: #49162
      Releases: 6.2
      Reviewed-by: Anja Leichsenring
      Tested-by: Anja Leichsenring
      Tested-by: Alexander Opitz
      Reviewed-by: Stefan Froemken
      Tested-by: Stefan Froemken
      Reviewed-by: Christian Kuhn
      Tested-by: Christian Kuhn