From michael.stucki at typo3.org Wed Feb 1 13:33:21 2012 From: michael.stucki at typo3.org (Michael Stucki) Date: Wed, 01 Feb 2012 13:33:21 +0100 Subject: [TYPO3-dev] [rfc] Support for ImageMagick PHP module ? In-Reply-To: References: Message-ID: Hi Sebastian, > To my understanding Typo3 uses ImageMagick by execution of new processes > because some hosters do not have the imagick PGP Module installed. > However, with my current favorite hoster the opposite is true: the > imagick modules is present but execution of processes is not granted to > PHP. I had a brief look at the code of Type3 4.6.6 and did not find any > support for the PHP imagick module as an alternative. > > I am wondering: If I started working on a patch to support both > ImageMagick as process invocations as well as PHP module would there be > a chance to get that included in later Typo3 releases? Also, do you > know of any issues that could make this impossible to implement? Has > this been decided against before? If so, what where the reasons? I think nobody will object to this, the reason why it's not there is simply that nobody needed it (and I expect it to be less powerful than using the stock binary). So go ahead if you think it's worth it, but I honestly recommend you to consider changing the hoster instead (because you will not only miss ImageMagick but also unzip, pdftotext, etc.) - michael -- Use a newsreader! Check out http://typo3.org/community/mailing-lists/use-a-news-reader/ From olivier.dobberkau at dkd.de Wed Feb 1 15:22:53 2012 From: olivier.dobberkau at dkd.de (Olivier Dobberkau) Date: Wed, 01 Feb 2012 15:22:53 +0100 Subject: [TYPO3-dev] [rfc] Support for ImageMagick PHP module ? In-Reply-To: References: Message-ID: Am 01.02.12 13:33, schrieb Michael Stucki: > So go ahead if you think it's worth it, but I honestly recommend you to > consider changing the hoster instead (because you will not only miss > ImageMagick but also unzip, pdftotext, etc.) jfi. i started to play with phpfog and typo3. i see definetly a need for a more clowd server friendly non system exec using TYPO3 edition. see: https://phpfog.com/ Olivier From sebastian at pipping.org Wed Feb 1 19:49:54 2012 From: sebastian at pipping.org (Sebastian Pipping) Date: Wed, 01 Feb 2012 19:49:54 +0100 Subject: [TYPO3-dev] [rfc] Support for ImageMagick PHP module ? In-Reply-To: References: Message-ID: On 02/01/2012 01:33 PM, Michael Stucki wrote: > (because you will not only miss ImageMagick but also unzip, pdftotext, etc.) Interesting. Best, Sebastian From peter.russ at 4many.net Wed Feb 1 22:08:38 2012 From: peter.russ at 4many.net (Peter Russ) Date: Wed, 01 Feb 2012 22:08:38 +0100 Subject: [TYPO3-dev] [rfc] Support for ImageMagick PHP module ? In-Reply-To: References: Message-ID: --- Original Nachricht --- Absender: Michael Stucki Datum: 01.02.2012 13:33: > Hi Sebastian, > >> To my understanding Typo3 uses ImageMagick by execution of new processes >> because some hosters do not have the imagick PGP Module installed. >> However, with my current favorite hoster the opposite is true: the >> imagick modules is present but execution of processes is not granted to >> PHP. I had a brief look at the code of Type3 4.6.6 and did not find any >> support for the PHP imagick module as an alternative. >> >> I am wondering: If I started working on a patch to support both >> ImageMagick as process invocations as well as PHP module would there be >> a chance to get that included in later Typo3 releases? Also, do you >> know of any issues that could make this impossible to implement? Has >> this been decided against before? If so, what where the reasons? > > I think nobody will object to this, the reason why it's not there is > simply that nobody needed it (and I expect it to be less powerful than > using the stock binary). > > So go ahead if you think it's worth it, but I honestly recommend you to > consider changing the hoster instead (because you will not only miss > ImageMagick but also unzip, pdftotext, etc.) > > - michael > Futher IM has a lot of problems on different OS distributions. We use for example GM on RH. So supporting IM directly would force us to upgrade to an other ECMS. Peter -- Fiat lux! Docendo discimus. _____________________________ uon GbR http://www.uon.li http://www.xing.com/profile/Peter_Russ From sebastian at pipping.org Wed Feb 1 22:55:00 2012 From: sebastian at pipping.org (Sebastian Pipping) Date: Wed, 01 Feb 2012 22:55:00 +0100 Subject: [TYPO3-dev] [rfc] Support for ImageMagick PHP module ? In-Reply-To: References: Message-ID: On 02/01/2012 10:08 PM, Peter Russ wrote: > Futher IM has a lot of problems on different OS distributions. We use > for example GM on RH. > So supporting IM directly would force us to upgrade to an other ECMS. Why? We are discussing introducing an alternative, not moving away from something, right? Best, Sebastian From jigal at xs4all.nl Thu Feb 2 07:33:10 2012 From: jigal at xs4all.nl (Jigal van Hemert) Date: Thu, 02 Feb 2012 07:33:10 +0100 Subject: [TYPO3-dev] [rfc] Support for ImageMagick PHP module ? In-Reply-To: References: Message-ID: Hi, On 1-2-2012 13:33, Michael Stucki wrote: > I think nobody will object to this, the reason why it's not there is > simply that nobody needed it (and I expect it to be less powerful than > using the stock binary). Imagick and Gmagick are PECL extensions and are not bundled with PHP. We can only speculate about the reasons for not including support for it in the core, but it might have something to do with the fact that the first stable release of Imagick appeared in 2007 and that Gmagick is still in beta. Both are wrappers around the IM and GM binaries [1] [2] and have loads of functions; in fact you need the binaries to make Imagick an Gmagick work. The main reasons for hosters to offer these instead of the executables is of course that they can block functions like exec() and feel a little safer (I won't argue if that is correct or not). > So go ahead if you think it's worth it, but I honestly recommend you to > consider changing the hoster instead (because you will not only miss > ImageMagick but also unzip, pdftotext, etc.) I agree with Michael about changing hoster; if you are not allowed to call exec() chances are that you won't have other necessary features (enough memory or CPU resources, cron jobs, ssh, ...) to use TYPO3 in a comfortable way. About adding support for Imagick/Gmagick, I still feel that building a general graphics library for the core with handlers for GD, IM, GM, Imagick, Gmagick, ... would be the best way for the future. Adding support for Imagick/Gmagick in the core directly would mean extra checks all over the place and would make image processing slower overall. [1] http://www.php.net/imagick [2] http://www.php.net/gmagick -- Kind regards / met vriendelijke groet, Jigal van Hemert. From jigal at xs4all.nl Thu Feb 2 07:44:08 2012 From: jigal at xs4all.nl (Jigal van Hemert) Date: Thu, 02 Feb 2012 07:44:08 +0100 Subject: [TYPO3-dev] [rfc] Support for ImageMagick PHP module ? In-Reply-To: References: Message-ID: Hi, On 1-2-2012 22:08, Peter Russ wrote: > Futher IM has a lot of problems on different OS distributions. We use > for example GM on RH. > So supporting IM directly would force us to upgrade to an other ECMS. Nobody is talking about dropping support for the IM or GM executables. I personally prefer GM over IM too. GM was a fork of IM and turned out faster, more stable and needed less memory. During the past years IM introduced loads of fixes which were at least 'inspired' by GM code. -- Kind regards / met vriendelijke groet, Jigal van Hemert. From typo3 at t3node.com Thu Feb 2 11:46:01 2012 From: typo3 at t3node.com (=?UTF-8?B?U3RlZmZlbiBNw7xsbGVy?=) Date: Thu, 02 Feb 2012 11:46:01 +0100 Subject: [TYPO3-dev] Security announcement for css_filelinks extension Message-ID: Hi. After noticing todays security bulletin and reviewing my installations for vulnerable extensions, I stumbled upon this one: CSS styled Filelinks (css_filelinks) is announced as insecure in versions 0.2.18 and below. The issue should have been fixed in 0.2.19. But 0.2.19 is released since 2010/10/04. Does that mean the vulnerability is already fixed since > 1 year? Can you please explain that? [1] http://typo3.org/teams/security/security-bulletins/typo3-extensions/typo3-ext-sa-2012-001/ [2] http://typo3.org/extensions/repository/view/css_filelinks/current/ -- cheers, Steffen TYPO3 Blog: http://www.t3node.com/ Twitter: @t3node - http://twitter.com/t3node From helmut.hummel at typo3.org Thu Feb 2 13:32:25 2012 From: helmut.hummel at typo3.org (Helmut Hummel) Date: Thu, 02 Feb 2012 13:32:25 +0100 Subject: [TYPO3-dev] Security announcement for css_filelinks extension In-Reply-To: References: Message-ID: Hi Steffen, Steffen M?ller wrote: > CSS styled Filelinks (css_filelinks) is announced as insecure in > versions 0.2.18 and below. The issue should have been fixed in 0.2.19. > > But 0.2.19 is released since 2010/10/04. > > Does that mean the vulnerability is already fixed since> 1 year? unfortunately this is all true. While restructuring and cleaning up our internal issue tracker, we stubled over this old one. We had two alternatives: 1. Ignore 2. Mention it anyway We went for 2. Kind regards, Helmut -- Helmut Hummel TYPO3 Security Team Leader, TYPO3 v4 Core Team Member TYPO3 .... inspiring people to share! Get involved: typo3.org From typo3 at t3node.com Thu Feb 2 15:43:20 2012 From: typo3 at t3node.com (=?UTF-8?B?U3RlZmZlbiBNw7xsbGVy?=) Date: Thu, 02 Feb 2012 15:43:20 +0100 Subject: [TYPO3-dev] Security announcement for css_filelinks extension In-Reply-To: References: Message-ID: Hi Helmut. On 02.02.2012 13:32 Helmut Hummel wrote: >> >> Does that mean the vulnerability is already fixed since> 1 year? > > unfortunately this is all true. Thanks for clarification. Could you add this notice to the bulletin, please? I was confused by reading about vulnerable extension and then not to find any update in the extension manager. -- cheers, Steffen TYPO3 Blog: http://www.t3node.com/ Twitter: @t3node - http://twitter.com/t3node From typo3 at ringerge.org Thu Feb 2 15:49:37 2012 From: typo3 at ringerge.org (Georg Ringer) Date: Thu, 02 Feb 2012 15:49:37 +0100 Subject: [TYPO3-dev] Security announcement for css_filelinks extension In-Reply-To: References: Message-ID: Hi Steffen, Am 02.02.2012 15:43, schrieb Steffen M?ller: > I was confused by reading about vulnerable extension and then not to > find any update in the extension manager. just as a followup: It isn't that unusual that something like that happens. Another example: Someone notices a security issue in his own extension (or gets notified by a 3rd party) and fixes it without notifying the security team. the next bulletin will also mention this extension and which versions are secure. Georg From typo3 at t3node.com Thu Feb 2 16:21:52 2012 From: typo3 at t3node.com (=?UTF-8?B?U3RlZmZlbiBNw7xsbGVy?=) Date: Thu, 02 Feb 2012 16:21:52 +0100 Subject: [TYPO3-dev] Security announcement for css_filelinks extension In-Reply-To: References: Message-ID: Hi Gerog, On 02.02.2012 15:49 Georg Ringer wrote: > : It isn't that unusual that something like that happens. Another > example: Someone notices a security issue in his own extension (or gets > notified by a 3rd party) and fixes it without notifying the security > team. the next bulletin will also mention this extension and which > versions are secure. These things happen of course. A short notice, when the fixed version was released would avoid confusion. Thanks. -- cheers, Steffen TYPO3 Blog: http://www.t3node.com/ Twitter: @t3node - http://twitter.com/t3node From typo3 at t3node.com Thu Feb 2 16:22:24 2012 From: typo3 at t3node.com (=?UTF-8?B?U3RlZmZlbiBNw7xsbGVy?=) Date: Thu, 02 Feb 2012 16:22:24 +0100 Subject: [TYPO3-dev] Security announcement for css_filelinks extension In-Reply-To: References: Message-ID: On 02.02.2012 16:21 Steffen M?ller wrote: > Hi Gerog, > sorry, I meant Georg. -- cheers, Steffen TYPO3 Blog: http://www.t3node.com/ Twitter: @t3node - http://twitter.com/t3node From ernst at cron-it.de Fri Feb 3 09:07:22 2012 From: ernst at cron-it.de (Ernesto Baschny [cron IT]) Date: Fri, 03 Feb 2012 09:07:22 +0100 Subject: [TYPO3-dev] Security announcement for css_filelinks extension In-Reply-To: References: Message-ID: Steffen M?ller schrieb am 02.02.2012 16:21: > Hi Gerog, > > On 02.02.2012 15:49 Georg Ringer wrote: >> : It isn't that unusual that something like that happens. Another >> example: Someone notices a security issue in his own extension (or gets >> notified by a 3rd party) and fixes it without notifying the security >> team. the next bulletin will also mention this extension and which >> versions are secure. > > These things happen of course. A short notice, when the fixed version > was released would avoid confusion. Thanks. +1 From kestutis1a at gmail.com Fri Feb 3 10:16:29 2012 From: kestutis1a at gmail.com (kestutis) Date: Fri, 03 Feb 2012 11:16:29 +0200 Subject: [TYPO3-dev] Disabling a subtype of the TYPO3 service Message-ID: Hello, Is it possible to disable a subtype of the service? I have created a new service with authUserBE subtype and Priority:51,Quality:51, but still tx_sv_auth authUserBE exists with Priority:50,Quality:50, which runs if my custom service fails. I tried to erase 'getUserBE' subtype of 'tx_sv_auth' by putting these lines to ext_localconf.php of my custom extension: $GLOBALS['T3_SERVICES']['auth']['tx_sv_auth']['serviceSubTypes']['getUserBE']= ''; and $GLOBALS['T3_SERVICES']['auth']['tx_sv_auth']['subtype'] = 'authUserBE,getUserFE,authUserFE,getGroupsFE'; But after looking to Admin tools->Reports I see whole 'tx_sv_auth' service disabled. And comma ahead before all subtypes in Subtypes column: ', authUserBE, getUserFE, authUserFE, getGroupsFE' Am I doing something wrong or it is not possible to disable subtypes of the service without disabling a service itself? Thank you in advance, Kast From xavier at typo3.org Fri Feb 3 10:21:55 2012 From: xavier at typo3.org (Xavier Perseguers) Date: Fri, 03 Feb 2012 10:21:55 +0100 Subject: [TYPO3-dev] Disabling a subtype of the TYPO3 service In-Reply-To: References: Message-ID: Hi, > Is it possible to disable a subtype of the service? Actually, you don't *really* want to actually disable the subtype, but you don't want to fall back to it... > I have created a new service with authUserBE subtype and > Priority:51,Quality:51, > but still tx_sv_auth authUserBE exists with Priority:50,Quality:50, > which runs if my custom service fails. Read the authentication business logic, you have to play with 100 or 200 as return value to let TYPO3 fall-back (or not) to the next available authentication service. Kind regards -- Xavier Perseguers Release Manager TYPO3 4.6 TYPO3 .... inspiring people to share! Get involved: http://typo3.org From steffen.ritter at typo3.org Sat Feb 4 11:16:30 2012 From: steffen.ritter at typo3.org (Steffen Ritter) Date: Sat, 04 Feb 2012 11:16:30 +0100 Subject: [TYPO3-dev] [TYPO3-core] TYPO3 4.7 Feature freeze coming closing Message-ID: Dear developers, this is a short reminder that the feature freeze for the Upcoming version is coming close. There are 9 days to go, until wewill release TYPO3 4.7beta1 Please check the state of your projects and developments and submit your pending features to the Gerrit Review system on review.typo3.org As the Introduction Package and the Government Package have to get a facelift according the new features and functionality within 4.7 as well as a last testing is to be done we most likely will announce a Merge Freeze as of monday, 13th February. If you have stuff, you consider to add on last minute please get in touch with me soon. Anyhow: If there are pending features on Gerrit, or you just pushed something new feel free to add it to this thread, giving others a better overview about what to come. You have any further questions left? Feel free to ask me directly! kind regards Steffen Ritter -- Steffen Ritter Release Manager TYPO3 4.7 TYPO3 .... inspiring people to share! Get involved: http://typo3.org From steffen.gebert at typo3.org Sat Feb 4 12:08:11 2012 From: steffen.gebert at typo3.org (Steffen Gebert) Date: Sat, 04 Feb 2012 12:08:11 +0100 Subject: [TYPO3-dev] [TYPO3-t3dd] Workshops at T3DD12 Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, inside the v4 Core Team we started collecting ideas for workshops at the upcoming developer days. Is anybody willing to contribute with ideas, or maybe even take over the lead of one of them (maybe not alone..)? http://wiki.typo3.org/T3DD12/WorkshopsBrainstorming Feel free to add your already submitted workshops - maybe they're inspiring for others (for own workshops or just join forces)! CfP ends Feb 12th, so hurry up ;) Kind regards Steffen - -- Steffen Gebert TYPO3 v4 Core Team Member TYPO3 Server Administration Team Member TYPO3 .... inspiring people to share! Get involved: http://typo3.org I work for TYPO3 solely in my spare time. If you think that my work helps you running your business, you are invited to send me a donation via PayPal to this email address. Thanks -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPLRGbAAoJEIskG/rSlyw4VMYIAL0oZ2PViCx+Gq1SLzl7AAGE yhEPyCdJ275kf6p79U7BfBdldD827KcHbDIUSKNhViH8fNEybqRk9684nMPORleM LtKI8mj5u99muWHyBS3mpmpOuz6lXa/3tWnjiLNIVqlLGGo/70AoGmsw0DOLPXHZ lUvdfxVjO11JGqe441emlIYsa2OHlmEMcyH3hda/2ipE7wLOvuS7rEs6GtKr6CjG xL60+r22f9D8/EhLPdiIRCQuZ5OvRD37ydCIZE5bhUmKsOjEoFd7xzdni/4mGyyF FG/ElWGM+PXRNYwVtArBpvFTA2H3M0FNd+V7JG65xQDZF8skcLPDwYU7tVxWQt0= =bqzK -----END PGP SIGNATURE----- From typo3.lists at philippgampe.info Sat Feb 4 18:19:32 2012 From: typo3.lists at philippgampe.info (Philipp Gampe) Date: Sat, 04 Feb 2012 18:19:32 +0100 Subject: [TYPO3-dev] Security announcement for css_filelinks extension References: Message-ID: Steffen M?ller wrote: > Hi Gerog, ... > These things happen of course. A short notice, when the fixed version > was released would avoid confusion. Thanks. Same for sysutils. I was rather confused too. Best regards -- Philipp Gampe ? PGP-Key 0AD96065 From thorsten.kahler at dkd.de Mon Feb 6 09:40:17 2012 From: thorsten.kahler at dkd.de (Thorsten Kahler [dkd]) Date: Mon, 06 Feb 2012 09:40:17 +0100 Subject: [TYPO3-dev] [TYPO3-core] [TYPO3-v4] This Week's "Friendly Ghost" Message-ID: Hi, for this week I'm the TYPO3 Core Team "Friendly Ghost". My primary goal for this week will probably be to coordinate all the last minute issues ususally rushing in just before feature freeze of a new TYPO3 version (). Besides that I'll focus on taking care of new bug reports and reporters and further cleaning up the issue tracker. Feel free to contact me in case of core related issues via Mail: thorsten.kahler at dkd.de Twitter: @_phoTTo_ Skype: thorstenkahler A wiki page describing the friendly ghost's tasks: Cheers, Thorsten -- Thorsten Kahler thorsten.kahler at dkd.de From tomasnorre at gmail.com Mon Feb 6 16:24:20 2012 From: tomasnorre at gmail.com (Tomas Norre Mikkelsen) Date: Mon, 06 Feb 2012 16:24:20 +0100 Subject: [TYPO3-dev] RealURL - Indexing problem Message-ID: Hi, I have a problem with my RealURL / Crawler, my 1. level in menu is not indexed, but i don't know why. I Have following realurl_conf.php from: http://www.dmitry-dulepov.com/2008/06/realurl-made-easy-part-2.html array( 'enableCHashCache' => true, 'appendMissingSlash' => 'ifNotFile', 'enableUrlDecodeCache' => true, 'enableUrlEecodeCache' => true, 'emptyUrlReturnValue' => '/', ), 'preVars' => array( ), 'postVarSets' => array( '_DEFAULT' => array( ), ), 'pagePath' => array( 'type' => 'user', 'userFunc' => 'EXT:realurl/class.tx_realurl_advanced.php:&tx_realurl_advanced->main', 'spaceCharacter' => '-', 'languageGetVar' => 'L', 'expireDays' => 3, ), ); $TYPO3_CONF_VARS['EXTCONF']['realurl'] = array( 'www.domain2.tld' => $tx_realurl_config, 'domain2.tld' => 'www.domain2.tld', ); $TYPO3_CONF_VARS['EXTCONF']['realurl']['www.domain2.tld']['pagePath']['rootpage_id'] = 31; Any hints, what i could have been missing, when visiting pages eg. http://domain2.tld/content/about/heritage/ the error is: The requested URL /content/about/heritage/ was not found on this server. So i think its related to my missing index of the page with name "content". ps: I'm not that greath painter either with mouse or pensil =) -- Venlig Hilsen / Best Regards Tomas Norre Mikkelsen Tomasnorre at gmail.com TYPO3 Developer @netimage.dk TYPO3 Profile: http://forge.typo3.org/users/4289 Follow me at twitter Twitter.com/tomasnorre From steffen.ritter at typo3.org Tue Feb 7 09:22:35 2012 From: steffen.ritter at typo3.org (Steffen Ritter) Date: Tue, 07 Feb 2012 09:22:35 +0100 Subject: [TYPO3-dev] [TYPO3-v4] Minutes of the 11th meeting of the 4.7 Release Team Message-ID: Hi dear TYPO3 community, These are the minutes of the 11th TYPO3 Release Team Meeting for version 4.7. The minutes are also available in the wiki of TYPO3 4.7: http://forge.typo3.org/projects/typo3v47-projects/wiki/11th_Release_Team_Meeting_TYPO3_47 ---------------------------------------------------------------------- *11th Release Team Meeting TYPO3 4.7* The 4.7 release team meets weekly for a Skype discussion round on the current activities. If you find this report interesting or have some comment or question about a particular topic, don't hesitate to follow-up on the thread in the v4 mailing list. On Monday, February 6th 2012 we held our 11th meeting with the following participants: * Steffen Ritter (4.7 Release Manager) * Xavier Perseguers (4.6 Release Manager) * Oliver Hader (Core Team Leader) Critisism on Leadership, Product-Management and Project-Management ======================================================================= In an posting to the v4 Minutes of last week Jigal addressed and explained that he is not satisfied with the current solution[1], and how things have been handled during the last year. We discussed most of the issues mentioned in the post, reviewed and revised them to give our statement on them. The conclusion will be published as a more detailed reply to that thread by Oliver Hader. TYPO3 4.7 =========== Open Issues, Problems to be tackled, "Remaining BLE stuff" ------------------------------------------------------------ 1. *FAL* *FAL was not merged*, yet. It always has been kept in private as it should have been released when it is done done to not block further development which would have to go through Gerrit. This behaviour as of today is cut off! Olly will take care of pushing the current state to Gerrit immediately. The reason of keeping things "private" is, that a team currently is working on an external project, with requirements currently not able to completely fulfill with the FAL layer. Dealing with that, we agreed that new Hooks or Signal/Slot as well internal refactoring are allowed within FAL even after feature freeze, as long as the Public API does not break. *Problems*: the remaining Problems will be reported on Gerrit and can be worked on by everyone - Upgrade Wizards not completely tested, quite difficult - Image-Rendering currently in some parts is ugly - stdWrap behaviour changed in uploads element (file-data instead of cObj-Data) and needs to be checked 2. *Console-Application* - is a standalone product, and therefore not touched by the feature-freeze - the endpoint needed for that application will be shipped as extension to TER - many stuff has been developed for core (in terms of cleanup) in scope of this developement. These developments neither are part of the project nor as reliable as they could go to core right now - we have to think for a place on typo3.org how to announce and promote this additional tool for admins 3. *Media-Extension* - has been planned as "DAM 2.0", FAL based - the main feature of current DAM already got to FAL (like references to File, Meta-Data, File-Type detection and so on) - Media "only" added - scheduled indexing - end-point for registering meta-data extraction services - many detailed additional meta-data fields - categorizing of files - An module for creation of file collections from categories or static files - with ExtJS 4 revert the User Interface broke - collections by category cannot be created anymore - Indexing Module never seemed to work correctly - will not be part of the Core, but TER released, somehow "A-Class" - *needs very much TLC (tender loving care) and people who want to finish that one until final release* 4. *Old behaviour of Media-Element* It has been reported, that the old behaviour of using external flash-videos does not work with refactored media element. We have to deal with that. Steffen Ritter will check this out before Beta1. Introduction Package / Government Package ------------------------------------------- The Introduction Package and the Government Package should represent the current featureset and "best practices" of the version it is build for. With 4.7 there will be many new stuff - the packages have to be adapted. To have some time for that a merge freeze already has been announced to happen one day prior to the Beta1 release, to have time to adapt the packages. Oliver Hader will take of adapting the scripts so that the changes there are reflected. Steffen Ritter will start on upgrading the packages within master branch. Especially the following topics are on the agenda: * database upgrades like e.g. for file abstraction layer * HTML5 video integration examples * use "new" indexed search [1] http://lists.typo3.org/pipermail/typo3-project-v4/2012-February/003297.html If you have any further questions according to the development of TYPO3 4.7, feel free to contact me or just leave your comment within this thread. Regards -- Steffen Ritter Release Manager TYPO3 4.7 TYPO3 .... inspiring people to share! Get involved: http://typo3.org From oliver.salzburg at googlemail.com Tue Feb 7 11:47:04 2012 From: oliver.salzburg at googlemail.com (Oliver Salzburg) Date: Tue, 07 Feb 2012 11:47:04 +0100 Subject: [TYPO3-dev] [TYPO3-v4] Minutes of the 11th meeting of the 4.7 Release Team In-Reply-To: References: Message-ID: On 2012-02-07 09:22, Steffen Ritter wrote: > 2. *Console-Application* > > - is a standalone product, and therefore not touched by the feature-freeze > - the endpoint needed for that application will be shipped as extension > to TER > - many stuff has been developed for core (in terms of cleanup) in scope > of this developement. These developments neither are part of the project > nor as reliable as they could go to core right now > - we have to think for a place on typo3.org how to announce and promote > this additional tool for admins Is there some place to get more info on this project? Cheers Oliver From woehlken at quadracom.de Tue Feb 7 15:49:49 2012 From: woehlken at quadracom.de (=?ISO-8859-15?Q?Marc_W=F6hlken?=) Date: Tue, 07 Feb 2012 15:49:49 +0100 Subject: [TYPO3-dev] PHP 5.4 performace / memory improvements? Message-ID: Hi, stumbled over this quite impressive benchmark: http://news.php.net/php.internals/57760 If those values are realistic TYPO3 would benefit greatly: 14% performance boost [req/sec] 33% less memory usage [memory_get_peak_usage] Anyone already tried out PHP 5.4 and can verify those results? CU Marc -- ........................................................... Marc W?hlken TYPO3 certified integrator Quadracom - Proffe & W?hlken Rembertistra?e 32 WWW: http://www.quadracom.de D-28203 Bremen E-Mail: woehlken at quadracom.de ______________ PGP-Key: http://pgp.quadracom.de From tomasnorre at gmail.com Tue Feb 7 21:14:14 2012 From: tomasnorre at gmail.com (Tomas Norre Mikkelsen) Date: Tue, 07 Feb 2012 21:14:14 +0100 Subject: [TYPO3-dev] RealURL - Indexing problem In-Reply-To: References: Message-ID: On 02/06/2012 04:24 PM, Tomas Norre Mikkelsen wrote: > Hi, > > I have a problem with my RealURL / Crawler, my 1. level in menu is not > indexed, but i don't know why. Problem solved, typo in my .htaccess made my realurl crash and therefor not indexed. Sorry to disturb you =) -- Best Regards Tomas Norre Mikkelsen TYPO3 Profile: http://forge.typo3.org/users/4289 TYPO3 Developer @ netimage.dk Follow me at twitter.com/tomasnorre From v-tyok at mail.ru Wed Feb 8 11:35:06 2012 From: v-tyok at mail.ru (Victor Livakovsky) Date: Wed, 8 Feb 2012 12:35:06 +0200 Subject: [TYPO3-dev] RTE POST-vars in custom TCEFORMS Message-ID: Hi, List. Here is my situation in short: I'm developing a BE module for custom records processing. Records are defined in TCA, so I decided to use TCEFORMS API for edit forms rendering. So far so good - form fields are rendering correctly, and RTE fields as well, but when I submit the form all the field values are coming to $_POST variable, except RTE fields - they stay same as before. I call initDefaultBEmode() method of t3lib_TCEforms class, load all the necessary JS files, like 'jsfunc.tbe_editor.js', 'tceforms.js'. Every field is generated by getSingleField() method of t3lib_TCEforms class, where I supply correct tablename, fieldname, record, processed by t3lib_transferData with 'uid' and 'pid' set as well (otherwise RTE was not loading), and special field configuration, like "richtext[]:rte_transform[mode=ts_css]", taken from "types". And this makes RTE load and function correctly, except fact, that it doesn't POST changed data (only original one). What may be the problem? Thank you in advance. From tomita.militaru at gmail.com Wed Feb 8 16:39:20 2012 From: tomita.militaru at gmail.com (=?UTF-8?B?VG9tacWjxIMgTUlMSVRBUlU=?=) Date: Wed, 8 Feb 2012 17:39:20 +0200 Subject: [TYPO3-dev] Overwrite sheetTitle with TCEFORM Message-ID: Hello, I'm trying to overwrite a label in the flexform configuration of the tt_news, more specifically the first tab with *General Settings*: TCEFORM.tt_content.pi_flexform.tx_ttnews.sDEF.sheetTitle = New Label Any idea where I go wrong? Thanks. -- Engr. Tomi?? MILITARU Certified TYPO3 Integrator Tel. +40741064681 From kai.vogel at speedprogs.de Wed Feb 8 16:45:07 2012 From: kai.vogel at speedprogs.de (Kai Vogel) Date: Wed, 8 Feb 2012 16:45:07 +0100 (CET) Subject: [TYPO3-dev] Overwrite sheetTitle with TCEFORM Message-ID: Hi Tomi??, it must be "TCEFORM.tt_content.pi_flexform.9.sDEF.sheetTitle", because "9" is the historical key for the tt_news extension. Use The configuration module to determine the key: $TCA['tt_content']['columns']['pi_flexform']['config']['ds'] Best regards -- Kai Vogel >---- Original Message ---- >From: Tomi?? MILITARU >To: "List for Core-/Extension development" >Sent: Mi, Feb 8, 2012, 16:40 PM >Subject: [TYPO3-dev] Overwrite sheetTitle with TCEFORM > >Hello, > >I'm trying to overwrite a label in the flexform configuration of the >tt_news, more specifically the first tab with *General Settings*: >TCEFORM.tt_content.pi_flexform.tx_ttnews.sDEF.sheetTitle = New Label > >Any idea where I go wrong? > >Thanks. > >-- >Engr. Tomi?? MILITARU >Certified TYPO3 Integrator >Tel. +40741064681 >_______________________________________________ >TYPO3-dev mailing list >TYPO3-dev at lists.typo3.org >http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev From tomita.militaru at gmail.com Wed Feb 8 16:58:57 2012 From: tomita.militaru at gmail.com (=?UTF-8?B?VG9tacWjxIMgTUlMSVRBUlU=?=) Date: Wed, 8 Feb 2012 17:58:57 +0200 Subject: [TYPO3-dev] Overwrite sheetTitle with TCEFORM In-Reply-To: References: Message-ID: Many thanks, worked. On Wed, Feb 8, 2012 at 5:45 PM, Kai Vogel wrote: > Hi Tomi??, > > it must be "TCEFORM.tt_content.pi_flexform.9.sDEF.sheetTitle", because "9" > is the historical key for the tt_news extension. > > Use The configuration module to determine the key: > $TCA['tt_content']['columns']['pi_flexform']['config']['ds'] > > Best regards > -- > Kai Vogel > > > > >---- Original Message ---- > >From: Tomi?? MILITARU > >To: "List for Core-/Extension development" > >Sent: Mi, Feb 8, 2012, 16:40 PM > >Subject: [TYPO3-dev] Overwrite sheetTitle with TCEFORM > > > >Hello, > > > >I'm trying to overwrite a label in the flexform configuration of the > >tt_news, more specifically the first tab with *General Settings*: > >TCEFORM.tt_content.pi_flexform.tx_ttnews.sDEF.sheetTitle = New Label > > > >Any idea where I go wrong? > > > >Thanks. > > > >-- > >Engr. Tomi?? MILITARU > >Certified TYPO3 Integrator > >Tel. +40741064681 > >_______________________________________________ > >TYPO3-dev mailing list > >TYPO3-dev at lists.typo3.org > >http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev > > _______________________________________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev > -- Engr. Tomi?? MILITARU Certified TYPO3 Integrator Tel. +40741064681 From g4-lisz at tonarchiv.ch Wed Feb 8 18:38:46 2012 From: g4-lisz at tonarchiv.ch (g4-lisz at tonarchiv.ch) Date: Wed, 08 Feb 2012 18:38:46 +0100 Subject: [TYPO3-dev] Dispatch Error after adding Boolean Property to Demand Class Message-ID: He there In my extbase project i'm using a non-persistent object "Demand" for a search form. Everything worked fine... Now i added a new property "isLocalKanton" to this Demand class: /* * Local to Kanton * * @var boolean $isLocalKanton */ protected $isLocalKanton = false; /** * @param boolean $isLocalKanton * @return void */ public function setIsLocalKanton($isLocalKanton) { $this->isLocalKanton = (boolean)$isLocalKanton; } /** * @return boolean isLocalKanton */ public function getIsLocalKanton() { return $this->isLocalKanton; } In the view i added a checkbox to the form: [...] Before this change, everything worked flawlessly with other boolean properties. Now i get the error: "Could not ultimately dispatch the request after 101 iterations. Most probably, a @dontvalidate annotation is missing on re-displaying a form with validation errors." Why is this? I can't see any mistake in my code... The action for displaying the search form looks like this: /** * Displays Fachabteilung Search Form * * @param Tx_Hplusinfo_Domain_Model_SearchDemand $demand The optional default values * @return void * @dontvalidate $demand */ public function abteilungAction(Tx_Hplusinfo_Domain_Model_SearchDemand $demand = NULL) { if ($demand === NULL) { $demandSession = unserialize($GLOBALS["TSFE"]->fe_user->getKey("ses", "demand")); if ( ($demandSession instanceof Tx_Hplusinfo_Domain_Model_SearchDemand) && ($demandSession->getPageId() == $GLOBALS["TSFE"]->id) ) { $demand = $demandSession; } else { $demand = new Tx_Hplusinfo_Domain_Model_SearchDemand(); $GLOBALS["TSFE"]->fe_user->setKey("ses", "demand", NULL); } } $this->view->assign('demand', $demand); $this->view->assign('abteilungs', $this->abteilungRepository->findAll()); } If i the form checkbox is commented out, the error disappears. Again, all other checkboxes work fine! I commented out the catch {} in the dispatcher loop (typo3_src-4.6.1/typo3/sysext/extbase/Classes/MVC/Dispatcher.php:93). Now it throws a Tx_Extbase_MVC_Exception_StopAction in /typo3_src-4.6.1/typo3/sysext/extbase/Classes/MVC/Controller/AbstractController.php:277: public function forward($actionName, $controllerName = NULL, $extensionName = NULL, array $arguments = NULL) { $this->request->setDispatched(FALSE); $this->request->setControllerActionName($actionName); if ($controllerName !== NULL) $this->request->setControllerName($controllerName); if ($extensionName !== NULL) $this->request->setControllerExtensionName($extensionName); if ($arguments !== NULL) $this->request->setArguments($arguments); throw new Tx_Extbase_MVC_Exception_StopAction(); } The request is forwarded to another action? Maybe that's a hint for someone who knows the mechanisms.. Any help will be much appreciated! Cheers, Till From peter.russ at 4many.net Thu Feb 9 00:25:47 2012 From: peter.russ at 4many.net (Peter Russ) Date: Thu, 09 Feb 2012 00:25:47 +0100 Subject: [TYPO3-dev] [TYPO3-t3dd] Workshops at T3DD12 In-Reply-To: References: Message-ID: --- Original Nachricht --- Absender: Steffen Gebert Datum: 04.02.2012 12:08: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > inside the v4 Core Team we started collecting ideas for workshops at the > upcoming developer days. > > Is anybody willing to contribute with ideas, or maybe even take over the > lead of one of them (maybe not alone..)? > > http://wiki.typo3.org/T3DD12/WorkshopsBrainstorming > > Feel free to add your already submitted workshops - maybe they're > inspiring for others (for own workshops or just join forces)! > > CfP ends Feb 12th, so hurry up ;) > > Kind regards > Steffen > > - -- > Steffen Gebert > TYPO3 v4 Core Team Member > TYPO3 Server Administration Team Member > > TYPO3 .... inspiring people to share! > Get involved: http://typo3.org > > I work for TYPO3 solely in my spare time. If you think that > my work helps you running your business, you are invited to > send me a donation via PayPal to this email address. Thanks > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.17 (Darwin) > Comment: GPGTools - http://gpgtools.org > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iQEcBAEBAgAGBQJPLRGbAAoJEIskG/rSlyw4VMYIAL0oZ2PViCx+Gq1SLzl7AAGE > yhEPyCdJ275kf6p79U7BfBdldD827KcHbDIUSKNhViH8fNEybqRk9684nMPORleM > LtKI8mj5u99muWHyBS3mpmpOuz6lXa/3tWnjiLNIVqlLGGo/70AoGmsw0DOLPXHZ > lUvdfxVjO11JGqe441emlIYsa2OHlmEMcyH3hda/2ipE7wLOvuS7rEs6GtKr6CjG > xL60+r22f9D8/EhLPdiIRCQuZ5OvRD37ydCIZE5bhUmKsOjEoFd7xzdni/4mGyyF > FG/ElWGM+PXRNYwVtArBpvFTA2H3M0FNd+V7JG65xQDZF8skcLPDwYU7tVxWQt0= > =bqzK > -----END PGP SIGNATURE----- May be some one could give a talk why this excellent new form wizzard is not capable to send a confirmation email to the applicant. Or is this just not configured correctly ;-) jm2c. Peter -- Fiat lux! Docendo discimus. _____________________________ uon GbR http://www.uon.li http://www.xing.com/profile/Peter_Russ From typo3.lists at philippgampe.info Thu Feb 9 01:32:38 2012 From: typo3.lists at philippgampe.info (Philipp Gampe) Date: Thu, 09 Feb 2012 01:32:38 +0100 Subject: [TYPO3-dev] Re: [TYPO3-t3dd] Workshops at T3DD12 References: Message-ID: Hi Steffen Gebert, Steffen Gebert wrote: > inside the v4 Core Team we started collecting ideas for workshops at the > upcoming developer days. > > Is anybody willing to contribute with ideas, or maybe even take over the > lead of one of them (maybe not alone..)? > > http://wiki.typo3.org/T3DD12/WorkshopsBrainstorming > > Feel free to add your already submitted workshops - maybe they're > inspiring for others (for own workshops or just join forces)! > > CfP ends Feb 12th, so hurry up ;) This list is already quite long, but some suggestions * Hacking around EM (3rd party repositories, code cleanup, bug fixing) * fixing/writing unit test * creating documentation server tools/infrastructure/setup/rendering chain (especially because folks from v4 and v5 are there ?!) * if somebody else is interested: kickstarting linkvalidator-ng with queue and smart processing and more settings, new interface * fix workspace issues Best regards -- Philipp Gampe ? PGP-Key 0AD96065 From tomita.militaru at gmail.com Thu Feb 9 11:30:54 2012 From: tomita.militaru at gmail.com (=?UTF-8?B?VG9tacWjxIMgTUlMSVRBUlU=?=) Date: Thu, 9 Feb 2012 12:30:54 +0200 Subject: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet Message-ID: Hello, I'm using TYPO3 4.6.4 with tt_news 3.1.0 and I want to change the BE labels from the tt_news flexform via page tsconfig. I've managed to change the sheet title of the flexform, but I see instruction for changing the fields are missing from the documentation: http://typo3.org/documentation/document-library/references/doc_core_tsconfig/4.6.0/view/1/5/#id2620800 For example, to change the flexform field catImageMode I've tried, but with no effect: TCEFORM.tt_content.pi_flexform.9.catImageMode.label = Some text I guess there is no feature implemented yet to change flexform fields? Thank you! -- Engr. Tomi?? MILITARU Certified TYPO3 Integrator Tel. +40741064681 From kai.vogel at speedprogs.de Thu Feb 9 12:07:18 2012 From: kai.vogel at speedprogs.de (Kai Vogel) Date: Thu, 9 Feb 2012 12:07:18 +0100 (CET) Subject: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet Message-ID: Hi Tomi??, the sheet name ("s_category") is missing in your setup. You can pick it out from the flexform file. This works: TCEFORM.tt_content.pi_flexform.9.s_category.catImageMode.label = Some text And it is quite possible to configure a flexform field. If you for example want to change the field type, then it goes like this: TCEFORM.tt_content.pi_flexform.9.s_category.catImageMode.config.type = input Best regards -- Kai Vogel >---- Original Message ---- >From: Tomi?? MILITARU >To: "List for Core-/Extension development" >Sent: Do, Feb 9, 2012, 11:31 AM >Subject: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet > >Hello, > >I'm using TYPO3 4.6.4 with tt_news 3.1.0 and I want to change the BE labels >from the tt_news flexform via page tsconfig. I've managed to change the >sheet title of the flexform, but I see instruction for changing the fields >are missing from the documentation: >http://typo3.org/documentation/document-library/references/doc_core_tsconfig/4.6.0/view/1/5/#id2620800 > >For example, to change the flexform field catImageMode I've tried, but with >no effect: >TCEFORM.tt_content.pi_flexform.9.catImageMode.label = Some text > >I guess there is no feature implemented yet to change flexform fields? > >Thank you! > >-- >Engr. Tomi?? MILITARU >Certified TYPO3 Integrator >Tel. +40741064681 >_______________________________________________ >TYPO3-dev mailing list >TYPO3-dev at lists.typo3.org >http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev From tomita.militaru at gmail.com Thu Feb 9 12:12:59 2012 From: tomita.militaru at gmail.com (=?UTF-8?B?VG9tacWjxIMgTUlMSVRBUlU=?=) Date: Thu, 9 Feb 2012 13:12:59 +0200 Subject: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet In-Reply-To: References: Message-ID: Great! Thanks & have a great day! On Thu, Feb 9, 2012 at 1:07 PM, Kai Vogel wrote: > Hi Tomi??, > > the sheet name ("s_category") is missing in your setup. You can pick it > out from the flexform file. This works: > > TCEFORM.tt_content.pi_flexform.9.s_category.catImageMode.label = Some text > > And it is quite possible to configure a flexform field. If you for example > want to change the field type, then it goes like this: > > TCEFORM.tt_content.pi_flexform.9.s_category.catImageMode.config.type = > input > > Best regards > -- > Kai Vogel > > > > >---- Original Message ---- > >From: Tomi?? MILITARU > >To: "List for Core-/Extension development" > >Sent: Do, Feb 9, 2012, 11:31 AM > >Subject: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet > > > >Hello, > > > >I'm using TYPO3 4.6.4 with tt_news 3.1.0 and I want to change the BE > labels > >from the tt_news flexform via page tsconfig. I've managed to change the > >sheet title of the flexform, but I see instruction for changing the fields > >are missing from the documentation: > > > http://typo3.org/documentation/document-library/references/doc_core_tsconfig/4.6.0/view/1/5/#id2620800 > > > >For example, to change the flexform field catImageMode I've tried, but > with > >no effect: > >TCEFORM.tt_content.pi_flexform.9.catImageMode.label = Some text > > > >I guess there is no feature implemented yet to change flexform fields? > > > >Thank you! > > > >-- > >Engr. Tomi?? MILITARU > >Certified TYPO3 Integrator > >Tel. +40741064681 > >_______________________________________________ > >TYPO3-dev mailing list > >TYPO3-dev at lists.typo3.org > >http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev > > _______________________________________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev > -- Engr. Tomi?? MILITARU Certified TYPO3 Integrator Tel. +40741064681 From kai.vogel at speedprogs.de Thu Feb 9 12:17:44 2012 From: kai.vogel at speedprogs.de (Kai Vogel) Date: Thu, 9 Feb 2012 12:17:44 +0100 (CET) Subject: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet Message-ID: Hi all, maybe the attached image helps to understand the configuration of flexforms via TSconfig. For more information, see my presentation on slidehare: http://www.slideshare.net/kaivogel/flexforms-made-simple Best regards -- Kai Vogel >---- Original Message ---- >From: "Kai Vogel" >To: "List for Core-/Extension development" >Sent: Do, Feb 9, 2012, 12:07 PM >Subject: Re: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet > >Hi Tomi??, > >the sheet name ("s_category") is missing in your setup. You can pick it out from the flexform file. This works: > >TCEFORM.tt_content.pi_flexform.9.s_category.catImageMode.label = Some text > >And it is quite possible to configure a flexform field. If you for example want to change the field type, then it goes like this: > >TCEFORM.tt_content.pi_flexform.9.s_category.catImageMode.config.type = input > >Best regards >-- >Kai Vogel > > > >>---- Original Message ---- >>From: Tomi?? MILITARU >>To: "List for Core-/Extension development" >>Sent: Do, Feb 9, 2012, 11:31 AM >>Subject: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet >> >>Hello, >> >>I'm using TYPO3 4.6.4 with tt_news 3.1.0 and I want to change the BE labels >>from the tt_news flexform via page tsconfig. I've managed to change the >>sheet title of the flexform, but I see instruction for changing the fields >>are missing from the documentation: >>http://typo3.org/documentation/document-library/references/doc_core_tsconfig/4.6.0/view/1/5/#id2620800 >> >>For example, to change the flexform field catImageMode I've tried, but with >>no effect: >>TCEFORM.tt_content.pi_flexform.9.catImageMode.label = Some text >> >>I guess there is no feature implemented yet to change flexform fields? >> >>Thank you! >> >>-- >>Engr. Tomi?? MILITARU >>Certified TYPO3 Integrator >>Tel. +40741064681 >>_______________________________________________ >>TYPO3-dev mailing list >>TYPO3-dev at lists.typo3.org >>http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev > >_______________________________________________ >TYPO3-dev mailing list >TYPO3-dev at lists.typo3.org >http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev From kai.vogel at speedprogs.de Thu Feb 9 12:20:49 2012 From: kai.vogel at speedprogs.de (Kai Vogel) Date: Thu, 9 Feb 2012 12:20:49 +0100 (CET) Subject: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet Message-ID: Damn, the attachment was removed :-( Therefore please see page 10 of the presentation for the TSconfig overview ;-) Best regards -- Kai Vogel >---- Original Message ---- >From: "Kai Vogel" >To: "List for Core-/Extension development" >Sent: Do, Feb 9, 2012, 12:18 PM >Subject: Re: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet > >Hi all, > >maybe the attached image helps to understand the configuration of flexforms via TSconfig. > >For more information, see my presentation on slidehare: >http://www.slideshare.net/kaivogel/flexforms-made-simple > >Best regards >-- >Kai Vogel > > >>---- Original Message ---- >>From: "Kai Vogel" >>To: "List for Core-/Extension development" >>Sent: Do, Feb 9, 2012, 12:07 PM >>Subject: Re: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet >> >>Hi Tomi??, >> >>the sheet name ("s_category") is missing in your setup. You can pick it out from the flexform file. This works: >> >>TCEFORM.tt_content.pi_flexform.9.s_category.catImageMode.label = Some text >> >>And it is quite possible to configure a flexform field. If you for example want to change the field type, then it goes like this: >> >>TCEFORM.tt_content.pi_flexform.9.s_category.catImageMode.config.type = input >> >>Best regards >>-- >>Kai Vogel >> >> >> >>>---- Original Message ---- >>>From: Tomi?? MILITARU >>>To: "List for Core-/Extension development" >>>Sent: Do, Feb 9, 2012, 11:31 AM >>>Subject: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet >>> >>>Hello, >>> >>>I'm using TYPO3 4.6.4 with tt_news 3.1.0 and I want to change the BE labels >>>from the tt_news flexform via page tsconfig. I've managed to change the >>>sheet title of the flexform, but I see instruction for changing the fields >>>are missing from the documentation: >>>http://typo3.org/documentation/document-library/references/doc_core_tsconfig/4.6.0/view/1/5/#id2620800 >>> >>>For example, to change the flexform field catImageMode I've tried, but with >>>no effect: >>>TCEFORM.tt_content.pi_flexform.9.catImageMode.label = Some text >>> >>>I guess there is no feature implemented yet to change flexform fields? >>> >>>Thank you! >>> >>>-- >>>Engr. Tomi?? MILITARU >>>Certified TYPO3 Integrator >>>Tel. +40741064681 >>>_______________________________________________ >>>TYPO3-dev mailing list >>>TYPO3-dev at lists.typo3.org >>>http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev >> >>_______________________________________________ >>TYPO3-dev mailing list >>TYPO3-dev at lists.typo3.org >>http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev_______________________________________________ >TYPO3-dev mailing list >TYPO3-dev at lists.typo3.org >http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev From tomita.militaru at gmail.com Thu Feb 9 12:29:26 2012 From: tomita.militaru at gmail.com (=?UTF-8?B?VG9tacWjxIMgTUlMSVRBUlU=?=) Date: Thu, 9 Feb 2012 13:29:26 +0200 Subject: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet In-Reply-To: References: Message-ID: Thanks for sharing the document! But I still got one question, for this part of the flexform: select LLL:EXT:tt_news/locallang_tca.xml:tt_news.pi_flexform.catLinkMode_TS LLL:EXT:tt_news/locallang_tca.xml:tt_news.pi_flexform.catLinkMode_dontshow 0 LLL:EXT:tt_news/locallang_tca.xml:tt_news.pi_flexform.catLinkMode_shownolink 1 LLL:EXT:tt_news/locallang_tca.xml:tt_news.pi_flexform.catLinkMode_catshortcut 2 LLL:EXT:tt_news/locallang_tca.xml:tt_news.pi_flexform.catLinkMode_catsel 3 0 1 1 I would like to change the label values in items, for example replace all labels from locallang_tca.xml with values in page tsconfig. So far: TCEFORM.tt_content.pi_flexform.9.s_category.catImageMode { label = Tag Image Link Mode: config { type = select items = .... } } Thanks. On Thu, Feb 9, 2012 at 1:20 PM, Kai Vogel wrote: > Damn, the attachment was removed :-( > > Therefore please see page 10 of the presentation for the TSconfig overview > ;-) > > Best regards > -- > Kai Vogel > > > > >---- Original Message ---- > >From: "Kai Vogel" > >To: "List for Core-/Extension development" > >Sent: Do, Feb 9, 2012, 12:18 PM > >Subject: Re: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet > > > >Hi all, > > > >maybe the attached image helps to understand the configuration of > flexforms via TSconfig. > > > >For more information, see my presentation on slidehare: > >http://www.slideshare.net/kaivogel/flexforms-made-simple > > > >Best regards > >-- > >Kai Vogel > > > > > >>---- Original Message ---- > >>From: "Kai Vogel" > >>To: "List for Core-/Extension development" > >>Sent: Do, Feb 9, 2012, 12:07 PM > >>Subject: Re: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet > >> > >>Hi Tomi??, > >> > >>the sheet name ("s_category") is missing in your setup. You can pick it > out from the flexform file. This works: > >> > >>TCEFORM.tt_content.pi_flexform.9.s_category.catImageMode.label = Some > text > >> > >>And it is quite possible to configure a flexform field. If you for > example want to change the field type, then it goes like this: > >> > >>TCEFORM.tt_content.pi_flexform.9.s_category.catImageMode.config.type = > input > >> > >>Best regards > >>-- > >>Kai Vogel > >> > >> > >> > >>>---- Original Message ---- > >>>From: Tomi?? MILITARU > >>>To: "List for Core-/Extension development" > >>>Sent: Do, Feb 9, 2012, 11:31 AM > >>>Subject: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet > >>> > >>>Hello, > >>> > >>>I'm using TYPO3 4.6.4 with tt_news 3.1.0 and I want to change the BE > labels > >>>from the tt_news flexform via page tsconfig. I've managed to change the > >>>sheet title of the flexform, but I see instruction for changing the > fields > >>>are missing from the documentation: > >>> > http://typo3.org/documentation/document-library/references/doc_core_tsconfig/4.6.0/view/1/5/#id2620800 > >>> > >>>For example, to change the flexform field catImageMode I've tried, but > with > >>>no effect: > >>>TCEFORM.tt_content.pi_flexform.9.catImageMode.label = Some text > >>> > >>>I guess there is no feature implemented yet to change flexform fields? > >>> > >>>Thank you! > >>> > >>>-- > >>>Engr. Tomi?? MILITARU > >>>Certified TYPO3 Integrator > >>>Tel. +40741064681 > >>>_______________________________________________ > >>>TYPO3-dev mailing list > >>>TYPO3-dev at lists.typo3.org > >>>http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev > >> > >>_______________________________________________ > >>TYPO3-dev mailing list > >>TYPO3-dev at lists.typo3.org > >> > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev_______________________________________________ > >TYPO3-dev mailing list > >TYPO3-dev at lists.typo3.org > >http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev > > _______________________________________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev > -- Engr. Tomi?? MILITARU Certified TYPO3 Integrator Tel. +40741064681 From oliver.salzburg at googlemail.com Thu Feb 9 12:30:51 2012 From: oliver.salzburg at googlemail.com (Oliver Salzburg) Date: Thu, 09 Feb 2012 12:30:51 +0100 Subject: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet In-Reply-To: References: Message-ID: On 2012-02-09 12:20, Kai Vogel wrote: > Damn, the attachment was removed :-( > > Therefore please see page 10 of the presentation for the TSconfig overview ;-) > > Best regards How are you replying to these messages? You're making a mess out of my inbox. Nothing gets threaded anymore :( From kai.vogel at speedprogs.de Thu Feb 9 14:10:36 2012 From: kai.vogel at speedprogs.de (Kai Vogel) Date: Thu, 9 Feb 2012 14:10:36 +0100 (CET) Subject: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet Message-ID: Hi, @Oliver: I only answer the emails with my webmailer. :-/ @Tomi??: With the following setup you can rename all entries in the select field which have a non-empty value: TCEFORM.tt_content.pi_flexform.9.s_category.catImageMode { altLabels { 0 = First entry 1 = Second entry } } Only the first entry "Defined by TypoScript" can not be translated. One idea will be to simply "keep" only the items with a value, but that will disable the configuration via TypoScript: TCEFORM.tt_content.pi_flexform.9.s_category.catImageMode { keepItems = 0,1,2,3,4 } Best regards -- Kai Vogel >---- Original Message ---- >From: Tomi?? MILITARU >To: "List for Core-/Extension development" >Sent: Do, Feb 9, 2012, 12:31 PM >Subject: Re: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet > >Thanks for sharing the document! > >But I still got one question, for this part of the flexform: > > > > > > select > > >index="0">LLL:EXT:tt_news/locallang_tca.xml:tt_news.pi_flexform.catLinkMode_TS > > > >index="0">LLL:EXT:tt_news/locallang_tca.xml:tt_news.pi_flexform.catLinkMode_dontshow > 0 > > >index="0">LLL:EXT:tt_news/locallang_tca.xml:tt_news.pi_flexform.catLinkMode_shownolink > 1 > > >index="0">LLL:EXT:tt_news/locallang_tca.xml:tt_news.pi_flexform.catLinkMode_catshortcut > 2 > > >index="0">LLL:EXT:tt_news/locallang_tca.xml:tt_news.pi_flexform.catLinkMode_catsel > 3 > > >0 >1 > 1 > > > > >I would like to change the label values in items, for example replace all >labels from locallang_tca.xml with values in page tsconfig. >So far: >TCEFORM.tt_content.pi_flexform.9.s_category.catImageMode { >label = Tag Image Link Mode: >config { > type = select >items = .... >} >} > >Thanks. > >On Thu, Feb 9, 2012 at 1:20 PM, Kai Vogel wrote: > >> Damn, the attachment was removed :-( >> >> Therefore please see page 10 of the presentation for the TSconfig overview >> ;-) >> >> Best regards >> -- >> Kai Vogel >> >> >> >> >---- Original Message ---- >> >From: "Kai Vogel" >> >To: "List for Core-/Extension development" >> >Sent: Do, Feb 9, 2012, 12:18 PM >> >Subject: Re: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet >> > >> >Hi all, >> > >> >maybe the attached image helps to understand the configuration of >> flexforms via TSconfig. >> > >> >For more information, see my presentation on slidehare: >> >http://www.slideshare.net/kaivogel/flexforms-made-simple >> > >> >Best regards >> >-- >> >Kai Vogel >> > >> > >> >>---- Original Message ---- >> >>From: "Kai Vogel" >> >>To: "List for Core-/Extension development" >> >>Sent: Do, Feb 9, 2012, 12:07 PM >> >>Subject: Re: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet >> >> >> >>Hi Tomi??, >> >> >> >>the sheet name ("s_category") is missing in your setup. You can pick it >> out from the flexform file. This works: >> >> >> >>TCEFORM.tt_content.pi_flexform.9.s_category.catImageMode.label = Some >> text >> >> >> >>And it is quite possible to configure a flexform field. If you for >> example want to change the field type, then it goes like this: >> >> >> >>TCEFORM.tt_content.pi_flexform.9.s_category.catImageMode.config.type = >> input >> >> >> >>Best regards >> >>-- >> >>Kai Vogel >> >> >> >> >> >> >> >>>---- Original Message ---- >> >>>From: Tomi?? MILITARU >> >>>To: "List for Core-/Extension development" >> >>>Sent: Do, Feb 9, 2012, 11:31 AM >> >>>Subject: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet >> >>> >> >>>Hello, >> >>> >> >>>I'm using TYPO3 4.6.4 with tt_news 3.1.0 and I want to change the BE >> labels >> >>>from the tt_news flexform via page tsconfig. I've managed to change the >> >>>sheet title of the flexform, but I see instruction for changing the >> fields >> >>>are missing from the documentation: >> >>> >> http://typo3.org/documentation/document-library/references/doc_core_tsconfig/4.6.0/view/1/5/#id2620800 >> >>> >> >>>For example, to change the flexform field catImageMode I've tried, but >> with >> >>>no effect: >> >>>TCEFORM.tt_content.pi_flexform.9.catImageMode.label = Some text >> >>> >> >>>I guess there is no feature implemented yet to change flexform fields? >> >>> >> >>>Thank you! >> >>> >> >>>-- >> >>>Engr. Tomi?? MILITARU >> >>>Certified TYPO3 Integrator >> >>>Tel. +40741064681 >> >>>_______________________________________________ >> >>>TYPO3-dev mailing list >> >>>TYPO3-dev at lists.typo3.org >> >>>http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev >> >> >> >>_______________________________________________ >> >>TYPO3-dev mailing list >> >>TYPO3-dev at lists.typo3.org >> >> >> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev_______________________________________________ >> >TYPO3-dev mailing list >> >TYPO3-dev at lists.typo3.org >> >http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev >> >> _______________________________________________ >> TYPO3-dev mailing list >> TYPO3-dev at lists.typo3.org >> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev >> > > > >-- >Engr. Tomi?? MILITARU >Certified TYPO3 Integrator >Tel. +40741064681 >_______________________________________________ >TYPO3-dev mailing list >TYPO3-dev at lists.typo3.org >http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev From fsu-lists at cobweb.ch Thu Feb 9 14:18:14 2012 From: fsu-lists at cobweb.ch (=?UTF-8?B?RnJhbsOnb2lzIFN1dGVy?=) Date: Thu, 09 Feb 2012 14:18:14 +0100 Subject: [TYPO3-dev] [TYPO3-t3dd] Workshops at T3DD12 In-Reply-To: References: Message-ID: Hi, > * creating documentation server tools/infrastructure/setup/rendering chain > (especially because folks from v4 and v5 are there ?!) Martin Bless has submitted a proposal for a workshop about reST and Sphinx. Cheers -- Francois Suter Cobweb Development Sarl - http://www.cobweb.ch From dmitry.dulepov at gmail.com Thu Feb 9 14:36:27 2012 From: dmitry.dulepov at gmail.com (Dmitry Dulepov) Date: Thu, 09 Feb 2012 15:36:27 +0200 Subject: [TYPO3-dev] RealURL - Indexing problem In-Reply-To: References: Message-ID: Hi! Tomas Norre Mikkelsen wrote: > I have a problem with my RealURL / Crawler, my 1. level in menu is not > indexed, but i don't know why. This is not a problem with RealURL. RealURL has nothing to do with indexing at all. It only encodes/decodes URL. Please, do not post wrong information to mailing lists. -- Dmitry Dulepov TYPO3 core team member Blog: http://dmitry-dulepov.com/ Twitter: http://twitter.com/dmitryd Simplicity will save the world. From dmitry.dulepov at gmail.com Thu Feb 9 14:37:41 2012 From: dmitry.dulepov at gmail.com (Dmitry Dulepov) Date: Thu, 09 Feb 2012 15:37:41 +0200 Subject: [TYPO3-dev] RealURL - Indexing problem In-Reply-To: References: Message-ID: Hi! Tomas Norre Mikkelsen wrote: > Problem solved, typo in my .htaccess made my realurl crash and therefor > not indexed. This is incorrect too. RealURL may not "crash" due to .htaccess. It may refuse to work but it may not crash due to .htaccess. -- Dmitry Dulepov TYPO3 core team member Blog: http://dmitry-dulepov.com/ Twitter: http://twitter.com/dmitryd Simplicity will save the world. From typo3.lists at philippgampe.info Thu Feb 9 18:53:14 2012 From: typo3.lists at philippgampe.info (Philipp Gampe) Date: Thu, 09 Feb 2012 18:53:14 +0100 Subject: [TYPO3-dev] [TYPO3-t3dd] Workshops at T3DD12 References: Message-ID: Hi Fran?ois Suter, Fran?ois Suter wrote: > Hi, > >> * creating documentation server tools/infrastructure/setup/rendering >> chain (especially because folks from v4 and v5 are there ?!) > > Martin Bless has submitted a proposal for a workshop about reST and > Sphinx. Good to know :) Best regards -- Philipp Gampe ? PGP-Key 0AD96065 From tomasnorre at gmail.com Fri Feb 10 08:30:02 2012 From: tomasnorre at gmail.com (Tomas Norre Mikkelsen) Date: Fri, 10 Feb 2012 08:30:02 +0100 Subject: [TYPO3-dev] RealURL - Indexing problem In-Reply-To: References: Message-ID: On 02/09/2012 02:36 PM, Dmitry Dulepov wrote: > This is not a problem with RealURL. RealURL has nothing to do with > indexing at all. It only encodes/decodes URL. I were not at aware that it wasn't the right solution, but it affected my setup, and now it works, therefore i asumed that it was the problem. > Please, do not post wrong information to mailing lists. I never had the intension to mislead or give wrong information, that should be implied in every anserw in the TYPO3 community, will all try to contribute and share knowlegde. My maillist etics says: If you find your anserw your self please prost a comment for others to see. (And i thought i got the anserw.) -- Venlig Hilsen / Best Regards Tomas Norre Mikkelsen Tomasnorre at gmail.com TYPO3 Developer @netimage.dk TYPO3 Profile: http://forge.typo3.org/users/4289 Follow me at twitter Twitter.com/tomasnorre From loek at netcoop.nl Fri Feb 10 14:27:45 2012 From: loek at netcoop.nl (Loek Hilgersom) Date: Fri, 10 Feb 2012 14:27:45 +0100 Subject: [TYPO3-dev] Workshops at T3DD12 In-Reply-To: References: Message-ID: Hi Steffen and others, I've submitted a proposal for a workshop about automatic build procedures for TYPO3v4. I want to present what we use to deploy our work on development, test, acceptation and production environments using Ant, Jenkins, and shell scripts. From this workshop I hope to achieve two things (but actually getting near 1 would already be great!): - I expect many others to have worked out their own methods for this, and want to work together on a generic way to do this, possible evolving into a TYPO3 project - maybe we could come up with some brilliant ideas to tackle the most problematic issues with TYPO3v4 for automatic building, especially the problem of duplicate record id's (you add a new page or content record for the new feature you're making, but meanwhile editors have also added content with the same id's) I hope there is some interest for this. Loek From ernst at cron-it.de Fri Feb 10 15:03:45 2012 From: ernst at cron-it.de (Ernesto Baschny [cron IT]) Date: Fri, 10 Feb 2012 15:03:45 +0100 Subject: [TYPO3-dev] Workshops at T3DD12 In-Reply-To: References: Message-ID: Hi Loek, sounds interesting. At first I did not understood what you mean with "automatic build". I was thinking you were refering to "packaging the TYPO3 sources" (for which we - the release team - use phing). But I guess you are refering to "automatic deployment" (keeping different TYPO3 instances in "sync"), is this correct? Go for it (even though I sadly won't be able to visit the T3DD12). Cheers, Ernesto Loek Hilgersom schrieb am 10.02.2012 14:27: > Hi Steffen and others, > > I've submitted a proposal for a workshop about automatic build > procedures for TYPO3v4. I want to present what we use to deploy our work > on development, test, acceptation and production environments using Ant, > Jenkins, and shell scripts. > > From this workshop I hope to achieve two things (but actually getting > near 1 would already be great!): > - I expect many others to have worked out their own methods for this, > and want to work together on a generic way to do this, possible evolving > into a TYPO3 project > - maybe we could come up with some brilliant ideas to tackle the most > problematic issues with TYPO3v4 for automatic building, especially the > problem of duplicate record id's (you add a new page or content record > for the new feature you're making, but meanwhile editors have also added > content with the same id's) > > I hope there is some interest for this. > > Loek From g4-lisz at tonarchiv.ch Fri Feb 10 15:17:21 2012 From: g4-lisz at tonarchiv.ch (g4-lisz at tonarchiv.ch) Date: Fri, 10 Feb 2012 15:17:21 +0100 Subject: [TYPO3-dev] Dispatch Error after adding Boolean Property to Demand Class In-Reply-To: References: Message-ID: On 08.02.2012 18:38, g4-lisz at tonarchiv.ch wrote: > He there > > In my extbase project i'm using a non-persistent object "Demand" for a > search form. Everything worked fine... > > Now i added a new property "isLocalKanton" to this Demand class: > > /* > * Local to Kanton > * > * @var boolean $isLocalKanton > */ > protected $isLocalKanton = false; > > /** > * @param boolean $isLocalKanton > * @return void > */ > public function setIsLocalKanton($isLocalKanton) { > $this->isLocalKanton = (boolean)$isLocalKanton; > } > > /** > * @return boolean isLocalKanton > */ > public function getIsLocalKanton() { > return $this->isLocalKanton; > } > > In the view i added a checkbox to the form: > > action="results" pageUid="26"> > > [...] > > > Before this change, everything worked flawlessly with other boolean > properties. > > Now i get the error: "Could not ultimately dispatch the request after > 101 iterations. Most probably, a @dontvalidate annotation is missing > on re-displaying a form with validation errors." > > Why is this? I can't see any mistake in my code... > > The action for displaying the search form looks like this: > /** > * Displays Fachabteilung Search Form > * > * @param Tx_Hplusinfo_Domain_Model_SearchDemand $demand The optional > default values > * @return void > * @dontvalidate $demand > */ > public function abteilungAction(Tx_Hplusinfo_Domain_Model_SearchDemand > $demand = NULL) { > if ($demand === NULL) { > $demandSession = > unserialize($GLOBALS["TSFE"]->fe_user->getKey("ses", "demand")); > if ( ($demandSession instanceof > Tx_Hplusinfo_Domain_Model_SearchDemand) > && ($demandSession->getPageId() == $GLOBALS["TSFE"]->id) > ) { > $demand = $demandSession; > } > else { > $demand = new Tx_Hplusinfo_Domain_Model_SearchDemand(); > $GLOBALS["TSFE"]->fe_user->setKey("ses", "demand", NULL); > } > } > > $this->view->assign('demand', $demand); > $this->view->assign('abteilungs', > $this->abteilungRepository->findAll()); > } > > If i the form checkbox is commented out, the error disappears. Again, > all other checkboxes work fine! > > I commented out the catch {} in the dispatcher loop > (typo3_src-4.6.1/typo3/sysext/extbase/Classes/MVC/Dispatcher.php:93). > Now it throws a Tx_Extbase_MVC_Exception_StopAction in > /typo3_src-4.6.1/typo3/sysext/extbase/Classes/MVC/Controller/AbstractController.php:277: > > public function forward($actionName, $controllerName = NULL, > $extensionName = NULL, array $arguments = NULL) { > $this->request->setDispatched(FALSE); > $this->request->setControllerActionName($actionName); > if ($controllerName !== NULL) > $this->request->setControllerName($controllerName); > if ($extensionName !== NULL) > $this->request->setControllerExtensionName($extensionName); > if ($arguments !== NULL) > $this->request->setArguments($arguments); > throw new Tx_Extbase_MVC_Exception_StopAction(); > } > > The request is forwarded to another action? Maybe that's a hint for > someone who knows the mechanisms.. > > Any help will be much appreciated! > Cheers, Till Still not solved... Should i file a bug report? Till From loek at netcoop.nl Fri Feb 10 16:39:00 2012 From: loek at netcoop.nl (Loek Hilgersom) Date: Fri, 10 Feb 2012 16:39:00 +0100 Subject: [TYPO3-dev] Workshops at T3DD12 In-Reply-To: References: Message-ID: Hi Ernesto, Correct, I mean automatic deployment. We're 'building' TYPO3-based websites and applications, but you're right, maybe deployment is the better word. Cheers, Loek On 02/10/2012 03:03 PM, Ernesto Baschny [cron IT] wrote: > Hi Loek, > > sounds interesting. At first I did not understood what you mean with > "automatic build". I was thinking you were refering to "packaging the > TYPO3 sources" (for which we - the release team - use phing). > > But I guess you are refering to "automatic deployment" (keeping > different TYPO3 instances in "sync"), is this correct? > > Go for it (even though I sadly won't be able to visit the T3DD12). > > Cheers, > Ernesto > > Loek Hilgersom schrieb am 10.02.2012 14:27: >> Hi Steffen and others, >> >> I've submitted a proposal for a workshop about automatic build >> procedures for TYPO3v4. I want to present what we use to deploy our work >> on development, test, acceptation and production environments using Ant, >> Jenkins, and shell scripts. >> >> From this workshop I hope to achieve two things (but actually getting >> near 1 would already be great!): >> - I expect many others to have worked out their own methods for this, >> and want to work together on a generic way to do this, possible evolving >> into a TYPO3 project >> - maybe we could come up with some brilliant ideas to tackle the most >> problematic issues with TYPO3v4 for automatic building, especially the >> problem of duplicate record id's (you add a new page or content record >> for the new feature you're making, but meanwhile editors have also added >> content with the same id's) >> >> I hope there is some interest for this. >> >> Loek > From t33k at prolabium.com Fri Feb 10 16:57:12 2012 From: t33k at prolabium.com (Krystian Szymukowicz) Date: Fri, 10 Feb 2012 16:57:12 +0100 Subject: [TYPO3-dev] Workshops at T3DD12 In-Reply-To: References: Message-ID: W dniu 2012-02-10 14:27, Loek Hilgersom wrote: > Hi Steffen and others, > > I've submitted a proposal for a workshop about automatic build > procedures for TYPO3v4. I want to present what we use to deploy our work > on development, test, acceptation and production environments using Ant, > Jenkins, and shell scripts. > > From this workshop I hope to achieve two things (but actually getting > near 1 would already be great!): > - I expect many others to have worked out their own methods for this, > and want to work together on a generic way to do this, possible evolving > into a TYPO3 project > - maybe we could come up with some brilliant ideas to tackle the most > problematic issues with TYPO3v4 for automatic building, especially the > problem of duplicate record id's (you add a new page or content record > for the new feature you're making, but meanwhile editors have also added > content with the same id's) > > I hope there is some interest for this. > If you want to make it generic then the problem is always the PRODUCTION. You must assume one of two: 1) PRODUCTION is dedicated server where you can install almost everything you need vs 2) PRODUCTION is pure php / ftp only. The best would be to have it for second option of course :) -- grtz Krystian Szymukowicz From steffen.gebert at typo3.org Fri Feb 10 19:12:25 2012 From: steffen.gebert at typo3.org (Steffen Gebert) Date: Fri, 10 Feb 2012 19:12:25 +0100 Subject: [TYPO3-dev] Workshops at T3DD12 In-Reply-To: References: Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10.02.12 14:27, Loek Hilgersom wrote: > Hi Steffen and others, > > I've submitted a proposal for a workshop about automatic build > procedures for TYPO3v4. I want to present what we use to deploy our work > on development, test, acceptation and production environments using Ant, > Jenkins, and shell scripts. Nice topic, Loek! Happy to see you offering such a workshop! I've talked to Phillip Bergsmann about this few weeks ago. I also know that AOEmedia is doing such stuff through Jenkins (e.g. for new typo3.org). I will at least point Phillip and Tolleiv to your post, maybe one of then wants to share his experience with you and the participants! Kind regards Steffen - -- Steffen Gebert TYPO3 v4 Core Team Member TYPO3 Server Administration Team Member TYPO3 .... inspiring people to share! Get involved: http://typo3.org I work for TYPO3 solely in my spare time. If you think that my work helps you running your business, you are invited to send me a donation via PayPal to this email address. Thanks -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPNV4IAAoJEIskG/rSlyw4XwMIAI91H/WjBhHSP9YXRorjnSKI kt8VIhsZS4QQJtmxHgdoczoOAAzw1FBg6oGPS3wci5aNVbxI7fBJt5fUAziC563p YV5AwHr75sQyhy/YZ0J74vSMynp1g5dVH0wb1N60ghTGqKldZ7dT04ozmgAd3Mve Czr4fosQ84sEyzpctY05TdPuAbofRWYGWwEmf6nz0mdgcZk7jmX6/YYEh3CYyIai qkvjkpJHZ28X7rto7rc8cF4S7Apvsj3AU5K/ZIlspxXkYIfMKNDBVKNESTMFfLSw InD9JASBec65AcKLEFIW7qRExtRjPi1GotEqyW4emquoY5QurVh/zKGLnvQ8Kts= =okKg -----END PGP SIGNATURE----- From simonschaufi at jesus.de Sun Feb 12 14:14:13 2012 From: simonschaufi at jesus.de (Simon Schaufelberger (Schaufi)) Date: Sun, 12 Feb 2012 14:14:13 +0100 Subject: [TYPO3-dev] TCEFORM_flexform & TCEFORM_flexformSheet In-Reply-To: References: Message-ID: > I only answer the emails with my webmailer. use thunderbird with the mailing lists feature ;) Regards, Schaufi Am 09.02.2012 14:10, schrieb Kai Vogel: > Hi, > > @Oliver: I only answer the emails with my webmailer. :-/ > > @Tomi??: > > With the following setup you can rename all entries in the select field which have a non-empty value: > > TCEFORM.tt_content.pi_flexform.9.s_category.catImageMode { > altLabels { > 0 = First entry > 1 = Second entry > } > } > > Only the first entry "Defined by TypoScript" can not be translated. One idea will be to simply "keep" only the items with a value, but that will disable the configuration via TypoScript: > > TCEFORM.tt_content.pi_flexform.9.s_category.catImageMode { > keepItems = 0,1,2,3,4 > } > > > Best regards From georg.schoenweger at gmail.com Sun Feb 12 15:19:07 2012 From: georg.schoenweger at gmail.com (=?ISO-8859-15?Q?Georg_Sch=F6nweger?=) Date: Sun, 12 Feb 2012 15:19:07 +0100 Subject: [TYPO3-dev] backColor=transparent GIFUBILDER In-Reply-To: References: Message-ID: Hi Jigal, for a project i need fully supported alpha transparency (several image layers, text (without niceText ;), masks, rotation). Do you think it is possible and makes sense to patch Typo3? Or is it wiser/easier to create my own php gd implementation? regards, Georg Am 20.12.2011 19:10, schrieb Jigal van Hemert: > Hi, > > On 20-12-2011 18:36, Georg Sch?nweger wrote: >> I tried it out a little bit and it seems that it is not really stable >> yet. > > It's incomplete and the reason is the lack of support for transparency > in various PHP GD functions. > >> E.g. if i try to put an image on the "transparent layer", the >> transparency is gone, the background becomes black. Same thing happens >> when using the option niceText. > > Don't use niceText :-) Seriously, if your text doesn't look good with a > TrueType font try to get the Type1 version. Chances are that it looks > better (I'll skip the technical story about aliasing) > > No errors on your part or misconfiguration. > From georg at grossberger.at Sun Feb 12 15:58:19 2012 From: georg at grossberger.at (Georg Grossberger) Date: Sun, 12 Feb 2012 15:58:19 +0100 Subject: [TYPO3-dev] backColor=transparent GIFUBILDER In-Reply-To: References: Message-ID: Actually, a patch is pending that should make that work - at least it did in my case https://review.typo3.org/7622 Don't know when or if it's going to be merged though. I'll push a 4.7 patch once this one is applied. If you need 4.7 support right away, simply apply the same patch to the master branch. If it cannot be applied directly, just copy the lines into the files. It's just a small patch, so it's no problem to do it manually. > Hi Jigal, > > for a project i need fully supported alpha transparency (several image > layers, text (without niceText ;), masks, rotation). Do you think it is > possible and makes sense to patch Typo3? > Or is it wiser/easier to create my own php gd implementation? > > regards, > Georg > > Am 20.12.2011 19:10, schrieb Jigal van Hemert: >> Hi, >> >> On 20-12-2011 18:36, Georg Sch?nweger wrote: >>> I tried it out a little bit and it seems that it is not really stable >>> yet. >> >> It's incomplete and the reason is the lack of support for transparency >> in various PHP GD functions. >> >>> E.g. if i try to put an image on the "transparent layer", the >>> transparency is gone, the background becomes black. Same thing happens >>> when using the option niceText. >> >> Don't use niceText :-) Seriously, if your text doesn't look good with a >> TrueType font try to get the Type1 version. Chances are that it looks >> better (I'll skip the technical story about aliasing) >> >> No errors on your part or misconfiguration. >> From Eric.Thibault at dc.ulaval.ca Sun Feb 12 16:44:37 2012 From: Eric.Thibault at dc.ulaval.ca (=?iso-8859-1?Q?=C9ric_Thibault?=) Date: Sun, 12 Feb 2012 10:44:37 -0500 Subject: [TYPO3-dev] TR : eid extension listing In-Reply-To: <3DB26A871F5010499F7999CE4CF7D3E685BC9EA680@EXCH-MBX-A.ulaval.ca> References: <3DB26A871F5010499F7999CE4CF7D3E685BC9EA680@EXCH-MBX-A.ulaval.ca> Message-ID: Hello to all! Is there a way to list all extensions with eid configuration setup? I've done eid setup before with no problems but I have an old extension that I want to "eid enable" but with no success...!? If I could list all eid extensions I would know if I've done it write on not. 1. I've changed the ext_localconf.php: // eID $GLOBALS['TYPO3_CONF_VARS']['FE']['eID_include'][my_ext'] = 'EXT:my_ext/pi1/class.tx_my_ext_eid.php'; 2. And in the eid class file (my_ext/pi1/class.tx_my_ext_eid.php): main(); ?> Thanks! From mail at wouterwolters.nl Sun Feb 12 17:17:47 2012 From: mail at wouterwolters.nl (Wouter Wolters) Date: Sun, 12 Feb 2012 17:17:47 +0100 Subject: [TYPO3-dev] TR : eid extension listing In-Reply-To: References: <3DB26A871F5010499F7999CE4CF7D3E685BC9EA680@EXCH-MBX-A.ulaval.ca> Message-ID: Hi, Maybe this extension can help you: additional_reports http://typo3.org/extensions/repository/?tx_terfe_pi1[view]=search&no_cache=1&tx_terfe_pi1[sword]=additional_reports Greetz, Wouter Op 12-2-2012 16:44, ?ric Thibault schreef: > Hello to all! > > Is there a way to list all extensions with eid configuration setup? I've done eid setup before with no problems but I have an old extension that I want to "eid enable" but with no success...!? If I could list all eid extensions I would know if I've done it write on not. > > 1. I've changed the ext_localconf.php: > > // eID > $GLOBALS['TYPO3_CONF_VARS']['FE']['eID_include'][my_ext'] = 'EXT:my_ext/pi1/class.tx_my_ext_eid.php'; > > 2. And in the eid class file (my_ext/pi1/class.tx_my_ext_eid.php): > > require_once(PATH_tslib.'class.tslib_pibase.php'); > class tx_my_ext_eID extends tslib_pibase { > > function main() { > print('Hello'); > } > > } > > $SOBE = t3lib_div::makeInstance('tx_my_ext_eID'); > $SOBE->main(); > ?> > > > Thanks! From jigal at xs4all.nl Sun Feb 12 17:44:32 2012 From: jigal at xs4all.nl (Jigal van Hemert) Date: Sun, 12 Feb 2012 17:44:32 +0100 Subject: [TYPO3-dev] TR : eid extension listing In-Reply-To: References: <3DB26A871F5010499F7999CE4CF7D3E685BC9EA680@EXCH-MBX-A.ulaval.ca> Message-ID: Hi, On 12-2-2012 16:44, ?ric Thibault wrote: > Is there a way to list all extensions with eid configuration setup? > I've done eid setup before with no problems but I have an old > extension that I want to "eid enable" but with no success...!? If I > could list all eid extensions I would know if I've done it write on > not. Sure! - ADMIN TOOLS > Configuration, - select "$TYPO3_CONF_VARS (Global Configuration)" in the select box on top, - navigate to: FE > eID_include Now you see the list of extensions in your installation which have registered an eID script. 1. I've changed the ext_localconf.php: > // eID > $GLOBALS['TYPO3_CONF_VARS']['FE']['eID_include'][my_ext'] = 'EXT:my_ext/pi1/class.tx_my_ext_eid.php'; I hope the missing single quote in [my_ext'] was lost during copy/paste? > 2. And in the eid class file (my_ext/pi1/class.tx_my_ext_eid.php): > > require_once(PATH_tslib.'class.tslib_pibase.php'); > class tx_my_ext_eID extends tslib_pibase { Hmm... the point of having an eID script is to have a light weight version of TYPO3. No need to do this. You can use the functions in tslib_eidtools to initialize a database connection, an fe_user, etc. if you need those. > > function main() { > print('Hello'); > } > > } > > $SOBE = t3lib_div::makeInstance('tx_my_ext_eID'); > $SOBE->main(); > ?> That should work. Try it without the tslib_pibase stuff. -- Kind regards / met vriendelijke groet, Jigal van Hemert. From jigal at xs4all.nl Sun Feb 12 19:19:29 2012 From: jigal at xs4all.nl (Jigal van Hemert) Date: Sun, 12 Feb 2012 19:19:29 +0100 Subject: [TYPO3-dev] backColor=transparent GIFUBILDER In-Reply-To: References: Message-ID: Hi, On 12-2-2012 15:58, Georg Grossberger wrote: > Don't know when or if it's going to be merged though. I'll push a 4.7 > patch once this one is applied. Patches should go to the highest version they are targetted at first. Regarding the challenge for transparency support, the problem is really in GD: - imagealphablending(), it supports two blending modes: * blending mode : the alpha transparency of the colour applied to a pixel is used to determine how much of the underlying colour should shine through. The resulting pixel is opaque (!) * non-blending mode : the drawing colour with transparency replaces the underlying pixel. The resulting pixel (partly) transparent We like to have a third mode actually, where the resulting pixel is (partly) transparent and the colour and transparency are calculated from the original pixel and the applied colour. - imagesavealpha(), this enables the resulting image to be saved with an alpha channel. You have to unset imagealphablending to use this. So, there is no way to combine two transparent images and have an image with transparency as result. To combine two transparent images we need to enable blending mode, but the result is an opaque image. If we want an image with an alpha channel we have to disable the blending mode. Now we can't combine two transparent images any more. If you read the comments below the imagealphablending() documentation [1] you'll see that a lot of people try to solve the problem of combining two transparent images into a transparent result. The only solution seems to be to calculate the transparency for every pixel in the images. With larger images this can take "forever". The only way out is a rewrite of the graphics functions and let GM/IM (with possibly a GD fallback) do these operations. -- Kind regards / met vriendelijke groet, Jigal van Hemert. From loek at netcoop.nl Mon Feb 13 00:16:44 2012 From: loek at netcoop.nl (Loek Hilgersom) Date: Mon, 13 Feb 2012 00:16:44 +0100 Subject: [TYPO3-dev] Hook request for t3lib_userauth Message-ID: Hi, I'm making an extension that should block or mitigate brute force password attacks. I tried to achieve that by setting up an auth-service, but there is no place where I can hook into the authentication process: 1. which is called at every login attempt 2. where I can see whether a login attempt has been successful or not 3. that has the login and user data at hand. The authentication process is quite a jungle, maybe I overlooked something? Otherwise, a hook near the end of the checkAuthentication method seems the right place. What do you think? Loek From typo3 at sjbr.ca Mon Feb 13 05:57:35 2012 From: typo3 at sjbr.ca (Stanislas Rolland) Date: Sun, 12 Feb 2012 23:57:35 -0500 Subject: [TYPO3-dev] [TYPO3-v4] This Week's "Friendly Ghost" Message-ID: Hi, I'll be your Core Team friendly ghost for this week, trying to clean up the issue tracker and keeping an eye on new issues as they enter the tracker. Please do not hesitate to get in touch with me: Email: typo3 at sjbr.ca The friendly ghost's tasks are described in this Wiki page: http://forge.typo3.org/projects/typo3v4-core/wiki/FriendlyGhost Have a nice week, Stanislas From typo3 at ringerge.org Mon Feb 13 08:02:34 2012 From: typo3 at ringerge.org (Georg Ringer) Date: Mon, 13 Feb 2012 08:02:34 +0100 Subject: [TYPO3-dev] Experience from usergroup meeting about core development Message-ID: Hi guys & girls, I just wanna share a part of the experience / result from the last austrian usergroup meeting. The common opinion was that there is no direction of development which is then followed by the whole core team. Everybody does the features which are nice for himself but nobody checks the requirements of an enterprise cms or from the competitors. There was a nice comparison to the red cross and the voluntary fire brigade ("freiwillige feuerwehr"): In both and TYPO3, it is an own decision to work for those and you do it in your spare time *but* what you do there then exactly is told by the captain and everybody follows. It would be impossible to extinguish a fire if everbody wants to drive the truck or at the same time nobody wants to This leadership is kind of missing and hindering for development. I would be happy to get your impression, feedback, whatsoever Georg From F.Gerards at esolut.de Mon Feb 13 09:53:46 2012 From: F.Gerards at esolut.de (Frank Gerards) Date: Mon, 13 Feb 2012 09:53:46 +0100 Subject: [TYPO3-dev] Experience from usergroup meeting about core development In-Reply-To: References: Message-ID: Hi, I share your impression mostly and I add, that communication of core-team development lacks a bit of transparency. For myself I would like less features, but stable maintenance by the core-team dedicated to a feature. I also think, that due to the FLOW3 and Phoenix development, the vision of TYPO3 v4 has gradually blurred and that tends to affect team-spirit here and there. I think the Developer Days are a very good event to get momentum on important subjects of core-development again and I hope there can be like a voteable wishlist or sth for TYPO3 users, that don't have the know-how or time to code features TYPO3 is missing for practical enterprise use. Each voted feature could then be added as a task to a core-team or a new team could be built up, if enough devs are interested. Finally, I tend to see the future of TYPO3 like this: TYPO3 v4 will continue to be developed after Phoenix comes up, but will be more focused on the "KMU" segment than on really big enterprise sites. These sites will be developed with the OO-toolset of Phoenix (and FLOW3). The success of Phoenix for the average TYPO3 Integrator/developer will depend mainly on Typoscript and good tutorials on the plugin development. Only few devs will take full advantage of DI or AOP as the majority of integrators or devs esp. for small and mid-sized TYPO3 projects will continue thinking procedural or Typoscript-driven. Regards, Frank -----Urspr?ngliche Nachricht----- Von: typo3-dev-bounces at lists.typo3.org [mailto:typo3-dev-bounces at lists.typo3.org] Im Auftrag von Georg Ringer Gesendet: Montag, 13. Februar 2012 08:03 An: typo3-dev at lists.typo3.org Betreff: [TYPO3-dev] Experience from usergroup meeting about core development Hi guys & girls, I just wanna share a part of the experience / result from the last austrian usergroup meeting. The common opinion was that there is no direction of development which is then followed by the whole core team. Everybody does the features which are nice for himself but nobody checks the requirements of an enterprise cms or from the competitors. There was a nice comparison to the red cross and the voluntary fire brigade ("freiwillige feuerwehr"): In both and TYPO3, it is an own decision to work for those and you do it in your spare time *but* what you do there then exactly is told by the captain and everybody follows. It would be impossible to extinguish a fire if everbody wants to drive the truck or at the same time nobody wants to This leadership is kind of missing and hindering for development. I would be happy to get your impression, feedback, whatsoever Georg _______________________________________________ TYPO3-dev mailing list TYPO3-dev at lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev From typo3 at t3node.com Mon Feb 13 12:44:21 2012 From: typo3 at t3node.com (=?UTF-8?B?U3RlZmZlbiBNw7xsbGVy?=) Date: Mon, 13 Feb 2012 12:44:21 +0100 Subject: [TYPO3-dev] Experience from usergroup meeting about core development In-Reply-To: References: Message-ID: Hi. On 13.02.2012 08:02 Georg Ringer wrote: > This leadership is kind of missing and hindering for development. > Well, the answer for me is simple: fighting fire is a different business than software development [1]. Anyway, in the past the TYPO3 project more an more followed the bazaar paradigm and left the cathedral [2]. Even the king(tm) did never rule as absolute monarch. I don't believe turning back to cathedral would work out. Not even if the king returns. [1] except for having burndown charts :) [2] http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ -- cheers, Steffen TYPO3 Blog: http://www.t3node.com/ Twitter: @t3node - http://twitter.com/t3node From typo3 at ringerge.org Mon Feb 13 18:06:41 2012 From: typo3 at ringerge.org (Georg Ringer) Date: Mon, 13 Feb 2012 18:06:41 +0100 Subject: [TYPO3-dev] Experience from usergroup meeting about core development In-Reply-To: References: Message-ID: Am 13.02.2012 12:44, schrieb Steffen M?ller: > Well, the answer for me is simple: fighting fire is a different business > than software development [1]. true but same thing is still that working as a team brings a result faster than as a crowd. I am feeling more like in a flashmob ;) Georg From steffen.gebert at typo3.org Mon Feb 13 18:35:19 2012 From: steffen.gebert at typo3.org (Steffen Gebert) Date: Mon, 13 Feb 2012 18:35:19 +0100 Subject: [TYPO3-dev] Experience from usergroup meeting about core development In-Reply-To: References: Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> There was a nice comparison to the red cross and the voluntary fire >> brigade ("freiwillige feuerwehr"): In both and TYPO3, it is an own >> decision to work for those and you do it in your spare time *but* what >> you do there then exactly is told by the captain and everybody follows. > Well, the answer for me is simple: fighting fire is a different business > than software development [1]. Yes, it's a different business. But both is volunteer work and in both cases (being a team member), you should feel responsible, when you are needed. I only see this from a few people here, which demotivates me. Kind regards Steffen - -- Steffen Gebert TYPO3 v4 Core Team Member TYPO3 Server Administration Team Member TYPO3 .... inspiring people to share! Get involved: http://typo3.org I work for TYPO3 solely in my spare time. If you think that my work helps you running your business, you are invited to send me a donation via PayPal to this email address. Thanks -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPOUnWAAoJEIskG/rSlyw4bWcH/jgseNIefiTspBAzbFVaWx5/ dPVhD7EdUyS4hZ6CkcJ/gHL97vXKiRSr7+OoEXLcGP83eqN8Cjry3Fnrgxh6BVNg XfMUsiigeyHov8qVhRFbb6YXBSVINggW/WPAniw0Ag+R1xs22xAujHVnm/KlfbHk w4QmYPmWadDCuV/m+foSJjvIQNr0A3c3XiF7uELZ0i80F6QMJk35fF4Gbiis6gE9 IqXm6wayDVrn2j/S7gLIAVIAVScXFylXoR0LzrEWrNTqnejw2Teqa3KeDYPxi4o9 /x5N1hh58gHpGCykvTxIw0FfIEfr8UQO9HhkMIhTkzCMNkteDp+epjp86+Pvp2Y= =zOVt -----END PGP SIGNATURE----- From steffen.gebert at typo3.org Mon Feb 13 18:44:56 2012 From: steffen.gebert at typo3.org (Steffen Gebert) Date: Mon, 13 Feb 2012 18:44:56 +0100 Subject: [TYPO3-dev] Experience from usergroup meeting about core development In-Reply-To: References: Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > The common opinion was that there is no direction of development which > is then followed by the whole core team. Everybody does the features > which are nice for himself but nobody checks the requirements of an > enterprise cms or from the competitors. I think the idea came from Benni some time ago: Ask the Platinum + Gold sponsors, what features they are missing most in TYPO3. Taking this as a starting point, we could also ask the broad community for their votings. I think, when such a wish-list exists, some developers will take care of these issues - at least most of them (it's motivating to implement *the* most-wished killer feature, isn't it? ;)). Other than that, I hope that more developments happens in teams. One-man-shows turn out to fail or to get merged untested, because of nobody is able to review everything. I'm clearly against presenting a roadmap of the great features of the next version, from which maybe one or two are really implemented. I'm happy that we stopped this since 4.5 (?). Instead, I would like to see more teams being formed, especially for bigger features. Present an idea at the devdays or a new-version-kickoff and ask for co-authors. On the other hand, what information about TYPO3's direction do people expect? "TYPO3v4 will die in favor of Phoenix" or "The next version will focus on this and that"? I'd say, it's not possible to make everybody focus on a single topic per release (and makes no sense IMHO), instead - as said - I'd like to see several people joining forces. Sometimes this works very well and - like for FAL - will hopefully be crowned with big success. And for the general "feeling responsible" thing: I really hope that Ben has his suggestions for "Team rules" finished until the DevDays. I think that's really overdue, to have some guide lines, how an official TYPO3 team has to operate (frequent meetings, public protocols, regular team reports (2-4x per year), etc.). Kind regards Steffen - -- Steffen Gebert TYPO3 v4 Core Team Member TYPO3 Server Administration Team Member TYPO3 .... inspiring people to share! Get involved: http://typo3.org I work for TYPO3 solely in my spare time. If you think that my work helps you running your business, you are invited to send me a donation via PayPal to this email address. Thanks -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPOUwYAAoJEIskG/rSlyw4d8MH/RCZb3No2xf0Utg7xGwXX7RQ eeRNeRZO3GlWa6BoOrDArmnAihto759XjMtR5zYRcmppzbUNvs6b3o8f0S/20UT2 ZNrfw5Sdf2QjJ4fSnyYucl3xB/fMWxU3G0pUowsFS1+9ULin9pm7UiuhSNCbcno6 5RG6QOgRO9Oa+5CLE8YMzCWLq8hbOulhdEyN9koWTVD/W3QcpTvmeyQKCUEaA7d/ C5k6Ja6XdN2UgutDxV3uGnQIyts9MEN5HrnijXt2Jf/2WMhqQFpAd5pABcYEKHGo Qyx8wHG3RRp6Vm8spooDjd++I+Ed4i8DWXOPgSOqzKq+GxzbvUVrxLMkXD4dIYs= =MZjf -----END PGP SIGNATURE----- From typo3 at ringerge.org Mon Feb 13 19:21:05 2012 From: typo3 at ringerge.org (Georg Ringer) Date: Mon, 13 Feb 2012 19:21:05 +0100 Subject: [TYPO3-dev] Experience from usergroup meeting about core development In-Reply-To: References: Message-ID: Am 13.02.2012 18:44, schrieb Steffen Gebert: > I think the idea came from Benni some time ago: Ask the Platinum + Gold > sponsors, what features they are missing most in TYPO3. Taking this as a > starting point, we could also ask the broad community for their votings. +1 > Other than that, I hope that more developments happens in teams. > One-man-shows turn out to fail or to get merged untested, because of > nobody is able to review everything. +0.5, see below > I'm clearly against presenting a roadmap of the great features of the > next version, from which maybe one or two are really implemented. I'm > happy that we stopped this since 4.5 (?). don't need to be big features. could be someting like "with 4-8 the core team concentrates on an awesome logging" and the whole team works together - everbody with his own knowledge like UI, performance, ... I am not sure if those 2-3 teams hold longer than a oneman show? > Instead, I would like to see more teams being formed, especially for > bigger features. Present an idea at the devdays or a new-version-kickoff > and ask for co-authors. This asking is the problem I have. If there a goald everybody should work on those and not just the ones which like that as personal taste. This is still fine for all other features except the one from the R&D-Team, platinum members, ... > I'd say, it's not possible to make everybody > focus on a single topic per release (and makes no sense IMHO), why no sense? Of course 100 lines of code don't need 10 people but if it is a bit bigger, how fast is something like that finished if you throw all this knowledge in one room? How many bugfixes/unit tests can be written in one day for one single feature? I would love to have those 100% features which can be integrated and just work out of the box. > And for the general "feeling responsible" thing: I really hope that Ben > has his suggestions for "Team rules" finished until the DevDays. I think > that's really overdue, to have some guide lines, how an official TYPO3 > team has to operate (frequent meetings, public protocols, regular team > reports (2-4x per year), etc.). + a big one Georg From steffen.gebert at typo3.org Mon Feb 13 19:35:02 2012 From: steffen.gebert at typo3.org (Steffen Gebert) Date: Mon, 13 Feb 2012 19:35:02 +0100 Subject: [TYPO3-dev] Experience from usergroup meeting about core development In-Reply-To: References: Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > don't need to be big features. could be someting like "with 4-8 the core > team concentrates on an awesome logging" and the whole team works > together - everbody with his own knowledge like UI, performance, ... > > I am not sure if those 2-3 teams hold longer than a oneman show? Too many cooks spoil the broth ;) Chance for somebody being available for a longer time frame is bigger. And I expect code quality do be higher, as people (hopefully) look at the others' code, talk about it etc. And I really think you can't motivate everybody to work on a particular topic. I expect TYPO3 development to be driven by a personal itch also in the future. I'd only like to get the best out of it. Kind regards Steffen - -- Steffen Gebert TYPO3 v4 Core Team Member TYPO3 Server Administration Team Member TYPO3 .... inspiring people to share! Get involved: http://typo3.org I work for TYPO3 solely in my spare time. If you think that my work helps you running your business, you are invited to send me a donation via PayPal to this email address. Thanks -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPOVfWAAoJEIskG/rSlyw4BGEIAK7IzxRvIutDs2SoxGuvR3rw i24Bcvnle+kQEn5lXWr3xemVjqVv1QM5fFlymNucBROBWjqcpJOXjG00US9Cre2Z rW1btJOHB4iKqMFiO2rBx4nz9lpC2SUYmSatCf+T7qqUI3lwTewx26vrX6OqyhVt Rcg5utUdvqGevYElX6AfRo3k+9uxiri8fX5HGLHCrXfnDVbHpeeXFFh96o5C6cW3 YkuDnyhnVOf+sB+xU8B0Jh72AE3VZP7uiucCzi4Y7Sx3QKcfuSdmB/Sra3uECeV0 pYbF6/5EsndCfOQ5g2sNNvwilU9GKpSHCcRneiEBkyFsYfIFox/QwQFNQBrAA5c= =ioUc -----END PGP SIGNATURE----- From cordes at cps-it.de Mon Feb 13 22:48:01 2012 From: cordes at cps-it.de (Nicole Cordes) Date: Mon, 13 Feb 2012 22:48:01 +0100 Subject: [TYPO3-dev] Hook request for t3lib_userauth In-Reply-To: References: Message-ID: Hi Loek, Did you have a look at t3lib/class.t3lib_userauth.php (line 293) // Hook for alternative ways of filling the $this->user array (is used by the "timtaw" extension) if (is_array($TYPO3_CONF_VARS['SC_OPTIONS']['t3lib/class.t3lib_userauth.php'][' postUserLookUp'])) { foreach ($TYPO3_CONF_VARS['SC_OPTIONS']['t3lib/class.t3lib_userauth.php']['postUserL ookUp'] as $funcName) { $_params = array( 'pObj' => &$this, ); t3lib_div::callUserFunction($funcName, $_params, $this); } } Hopes this can help you a bit. Nicole -----Urspr?ngliche Nachricht----- Von: typo3-dev-bounces at lists.typo3.org [mailto:typo3-dev-bounces at lists.typo3.org] Im Auftrag von Loek Hilgersom Gesendet: Montag, 13. Februar 2012 00:17 An: typo3-dev at lists.typo3.org Betreff: [TYPO3-dev] Hook request for t3lib_userauth Hi, I'm making an extension that should block or mitigate brute force password attacks. I tried to achieve that by setting up an auth-service, but there is no place where I can hook into the authentication process: 1. which is called at every login attempt 2. where I can see whether a login attempt has been successful or not 3. that has the login and user data at hand. The authentication process is quite a jungle, maybe I overlooked something? Otherwise, a hook near the end of the checkAuthentication method seems the right place. What do you think? Loek _______________________________________________ TYPO3-dev mailing list TYPO3-dev at lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev From typo3 at ringerge.org Tue Feb 14 06:08:25 2012 From: typo3 at ringerge.org (Georg Ringer) Date: Tue, 14 Feb 2012 06:08:25 +0100 Subject: [TYPO3-dev] Experience from usergroup meeting about core development In-Reply-To: References: Message-ID: Hi, Am 13.02.2012 19:35, schrieb Steffen Gebert: > And I really think you can't motivate everybody to work on a particular > topic. I doubt that and the big question is: How can then be those bugs from platinum members or things which are just needed as an enterprise cms solvable without somebody telling "we need this as an enterprise cms" and the possibility to move to that direction? > I expect TYPO3 development to be driven by a personal itch also > in the future. I'd only like to get the best out of it. of course! Most of us are here because of this personal itch and this won't change. Just talking for myself: I got no problem if the goal for next version would be "we need something better for translators" and put every effort in that. Georg From v-tyok at mail.ru Tue Feb 14 11:09:25 2012 From: v-tyok at mail.ru (Victor Livakovsky) Date: Tue, 14 Feb 2012 12:09:25 +0200 Subject: [TYPO3-dev] RTE POST-vars in custom TCEFORMS In-Reply-To: References: Message-ID: > And this makes RTE load and function correctly, except fact, that it > doesn't POST changed data (only original one). > What may be the problem? Ok, I found an issue: I had to add 'onsubmit' event on
-tag and put there value of additionalJS_submit property of t3lib_TCEforms class instance after all of my fields are rendered. From loek at netcoop.nl Tue Feb 14 15:05:03 2012 From: loek at netcoop.nl (Loek Hilgersom) Date: Tue, 14 Feb 2012 15:05:03 +0100 Subject: [TYPO3-dev] Hook request for t3lib_userauth In-Reply-To: References: Message-ID: Hi Nicole, I did see that hook, but it's too late in the process because the sessioncookie has already been set there. But maybe I can combine that hook with a service: a service to block illegal attempts and the hook for further processing... that will be a kind of funny implementation but it might work. I'll first see if that works and postpone the hook request. Loek Op 13-02-12 22:48, Nicole Cordes schreef: > Hi Loek, > > Did you have a look at t3lib/class.t3lib_userauth.php (line 293) > > // Hook for alternative ways of filling the $this->user array (is used by > the "timtaw" extension) > if > (is_array($TYPO3_CONF_VARS['SC_OPTIONS']['t3lib/class.t3lib_userauth.php'][' > postUserLookUp'])) { > foreach > ($TYPO3_CONF_VARS['SC_OPTIONS']['t3lib/class.t3lib_userauth.php']['postUserL > ookUp'] as $funcName) { > $_params = array( > 'pObj' => &$this, > ); > t3lib_div::callUserFunction($funcName, $_params, $this); > } > } > > Hopes this can help you a bit. > > > Nicole > From peter.russ at 4many.net Tue Feb 14 21:38:10 2012 From: peter.russ at 4many.net (Peter Russ) Date: Tue, 14 Feb 2012 21:38:10 +0100 Subject: [TYPO3-dev] t3lib_db update column, increment, decrement Message-ID: As it's commonly said that this can't be done or not well known SET = +/- here the solution how it works: $GLOBALS['TYPO3_DB']->exec_INSERTquery( 'cachingframework_cache_hash', array( 'identifier'=>'supertest', 'content' =>1 ) ); $offset = 1; $GLOBALS['TYPO3_DB']->exec_UPDATEquery( 'cachingframework_cache_hash', array( 'content' => 'content + ' .$offset ), '', '', '', 'content' ); Hopes this helps. -- Fiat lux! Docendo discimus. _____________________________ uon GbR http://www.uon.li http://www.xing.com/profile/Peter_Russ From robertwildling at gmail.com Tue Feb 14 23:03:56 2012 From: robertwildling at gmail.com (Robert Wildling) Date: Tue, 14 Feb 2012 23:03:56 +0100 Subject: [TYPO3-dev] Typo3 4.5 LTS - "New" Extension Manager Message-ID: Hi, List, I am working on T3 4.5 LTS and I think since it is an LTS, it should work good. Unfortunately the new extension manager is still very, very buggy. I would like to post bugs, but don't find the proper list on forge. Can anybody help me out, please? The issues: 1a. Usability: Things like "UPDATE!" are not really easily reachable. One needs to click on the install/uninstall button, toggling the actual install status. Only then, in the lightbox window, those menues like "UPDATE" show up. 1b. Error: Clicking around in that lightbox window, the old ext manager festures show up within that respective window, among them the well-known back-arrow. Clicking that very button, the new ext manager shows up completely within the lightbox window... not good... 2. There is still the error with the "window close. Re-check dependency"-feature, when ext need other ext. The "Window close" button still doesn't work. Tested with the installation of tinymce_rte, which requires the deinstallation of htmlare: the deinstallation process opens a totally new window, where the mentionen windo close button doesn't work. If anybody could confirm...? Thanks! Robert From typo3 at sjbr.ca Tue Feb 14 23:38:57 2012 From: typo3 at sjbr.ca (Stanislas Rolland) Date: Tue, 14 Feb 2012 17:38:57 -0500 Subject: [TYPO3-dev] Typo3 4.5 LTS - "New" Extension Manager In-Reply-To: References: Message-ID: Hi Robert, > > I am working on T3 4.5 LTS and I think since it is an LTS, it should > work good. Unfortunately the new extension manager is still very, very > buggy. I would like to post bugs, but don't find the proper list on > forge. Can anybody help me out, please? You can report these issues in the bugtracker: http://forge.typo3.org/projects/typo3v4-core/issues Make sure to set the TYPO3 version to 4.5 and the category to "Extension Manager". Please make sure also that any specific issue is not already reported. > > The issues: > 1a. Usability: Things like "UPDATE!" are not really easily reachable. > One needs to click on the install/uninstall button, toggling the actual > install status. Only then, in the lightbox window, those menues like > "UPDATE" show up. For example, I think this is reported in: http://forge.typo3.org/issues/27157 Kind regards, Stanislas From robertwildling at gmail.com Tue Feb 14 23:49:13 2012 From: robertwildling at gmail.com (Robert Wildling) Date: Tue, 14 Feb 2012 23:49:13 +0100 Subject: [TYPO3-dev] Typo3 4.5 LTS - "New" Extension Manager In-Reply-To: References: Message-ID: Thanks, Stanislas! Best regards, Robert > Hi Robert, >> >> I am working on T3 4.5 LTS and I think since it is an LTS, it should >> work good. Unfortunately the new extension manager is still very, very >> buggy. I would like to post bugs, but don't find the proper list on >> forge. Can anybody help me out, please? > > You can report these issues in the bugtracker: > http://forge.typo3.org/projects/typo3v4-core/issues > > Make sure to set the TYPO3 version to 4.5 and the category to "Extension > Manager". > > Please make sure also that any specific issue is not already reported. >> >> The issues: >> 1a. Usability: Things like "UPDATE!" are not really easily reachable. >> One needs to click on the install/uninstall button, toggling the actual >> install status. Only then, in the lightbox window, those menues like >> "UPDATE" show up. > For example, I think this is reported in: > http://forge.typo3.org/issues/27157 > > Kind regards, > Stanislas > From christian.lerrahn at cerebrum.com.au Wed Feb 15 03:01:31 2012 From: christian.lerrahn at cerebrum.com.au (Christian Lerrahn (Cerebrum)) Date: Wed, 15 Feb 2012 13:01:31 +1100 Subject: [TYPO3-dev] Password expiry and blacklists Message-ID: Hi guys, I've been meaning to write to the list about this for a long time but never really got around to doing it. So, here I go now... :) As TYPO3 is referred to as an Enterprise CMS, I really think it should have a password expiry (particularly for the backend) and password blacklists. This is a very common feature in corporate environments but completely absent in TYPO3. I've written an extension before for a client and hacked the core for that but it was all very messy so I decided against publishing it. What would really be needed is a proper approach to this problem from the core's end. While it is quite simple to lock out users with expired passwords, it is very hard to make users change their passwords instead because they are expired. Here is what I believe is necessary around password expiry and blacklisting. 1. Users with expired passwords should either be locked out or made change their password at the TYPO3 administrators discretion. 2. If forced password change is to occur, authentication needs to be completed before allowing password change or even disclosing that the password is expired. 3. Upon successful authentication, no session should be initiated but the user should be redirected to a password change form instead. 4. The password change form needs to authenticate the user again before accepting the password change. If authentication and password change were both completed successfully, the session is initiated. 5. It should be possible to blacklist the last x passwords used and ideally password rules should be definable as well. Blacklists and rules also need to be enforced when the password is changed voluntarily in the backend to ensure forced password change cannot be reverted. These are my thoughts on the issue. Any additions or objections to the procedure and constraints I am suggesting? In my former core hack, I just added fields for password setting to the login form which were enabled by a redirect after authentication. That worked but had the downside that I couldn't really react to a wrong "old password" in the password setting process and the user would be logged out, have to log back in and then type the old password again when changing the password. I think the best way would be to have the whole password changing process handled by an extension which could still use a skin provided by the core (to not risk inconsistencies). But, to come to my real point, I'm happy to implement all that. The question I want to ask here is how to approach the problem. As I'm not familiar with core development in general, I am worried that I might approach this in a way as to never get my patches approved. This is why I am presenting my thoughts about how to approach this in order to get some feedback. Are there any strong opinions about how this should be handled or how I am suggesting to handling it? Cheers, Christian From peter.russ at 4many.net Wed Feb 15 07:28:58 2012 From: peter.russ at 4many.net (Peter Russ) Date: Wed, 15 Feb 2012 07:28:58 +0100 Subject: [TYPO3-dev] Password expiry and blacklists In-Reply-To: References: Message-ID: --- Original Nachricht --- Absender: Christian Lerrahn (Cerebrum) Datum: 15.02.2012 03:01: > Hi guys, > I've been meaning to write to the list about this for a long time but > never really got around to doing it. So, here I go now... :) > > As TYPO3 is referred to as an Enterprise CMS, I really think it should > have a password expiry (particularly for the backend) and password > blacklists. This is a very common feature in corporate environments but > completely absent in TYPO3. > > I've written an extension before for a client and hacked the core for > that but it was all very messy so I decided against publishing it. What > would really be needed is a proper approach to this problem from the > core's end. While it is quite simple to lock out users with expired > passwords, it is very hard to make users change their passwords instead > because they are expired. > > Here is what I believe is necessary around password expiry and > blacklisting. > > 1. Users with expired passwords should either be locked out or made > change their password at the TYPO3 administrators discretion. > > 2. If forced password change is to occur, authentication needs to be > completed before allowing password change or even disclosing that the > password is expired. > > 3. Upon successful authentication, no session should be initiated but > the user should be redirected to a password change form instead. > > 4. The password change form needs to authenticate the user again before > accepting the password change. If authentication and password change > were both completed successfully, the session is initiated. > > 5. It should be possible to blacklist the last x passwords used and > ideally password rules should be definable as well. Blacklists and > rules also need to be enforced when the password is changed > voluntarily in the backend to ensure forced password change cannot be > reverted. > > These are my thoughts on the issue. Any additions or objections to the > procedure and constraints I am suggesting? > > In my former core hack, I just added fields for password setting to the > login form which were enabled by a redirect after authentication. That > worked but had the downside that I couldn't really react to a wrong > "old password" in the password setting process and the user would be > logged out, have to log back in and then type the old password again > when changing the password. > > I think the best way would be to have the whole password changing > process handled by an extension which could still use a skin provided > by the core (to not risk inconsistencies). > > But, to come to my real point, I'm happy to implement all that. The > question I want to ask here is how to approach the problem. As I'm not > familiar with core development in general, I am worried that I might > approach this in a way as to never get my patches approved. This is why > I am presenting my thoughts about how to approach this in order to get > some feedback. > > Are there any strong opinions about how this should be handled or how I > am suggesting to handling it? In an enterprise you use LDAP. There the company's password policy is defined. I see now need to add this into TYPO3. May be the extension to connect to the LDAP could be improved to handle the few error codes getting from LDAP correctly. Further in companies it is a security risk to store passwords in TYPO3. Peter. -- Fiat lux! Docendo discimus. _____________________________ uon GbR http://www.uon.li http://www.xing.com/profile/Peter_Russ From typo3 at ringerge.org Wed Feb 15 08:02:27 2012 From: typo3 at ringerge.org (Georg Ringer) Date: Wed, 15 Feb 2012 08:02:27 +0100 Subject: [TYPO3-dev] Password expiry and blacklists In-Reply-To: References: Message-ID: Hi Christian, first of all thanks for your input! Am 15.02.2012 03:01, schrieb Christian Lerrahn (Cerebrum): > As TYPO3 is referred to as an Enterprise CMS, I really think it should > have a password expiry (particularly for the backend) and password > blacklists. This is a very common feature in corporate environments but > completely absent in TYPO3. certainly true. > I've written an extension before for a client and hacked the core for > that but it was all very messy so I decided against publishing it. maybe you wanna still share it and post the diffs somewhere? > Here is what I believe is necessary around password expiry and > blacklisting. sounds all interesting and plausible. > But, to come to my real point, I'm happy to implement all that. great! > The > question I want to ask here is how to approach the problem. As I'm not > familiar with core development in general, I am worried that I might > approach this in a way as to never get my patches approved. IMO this should be started as an extension as it makes it far easier to test things, react better on bugs/features and at the end it can be still talked about having it as sysextension shipped with the core. As a member of the security team I would like to have all those features and would be happy to help you developing the extension! Feel free to contact me in private Georg From typo3 at kay-strobach.de Wed Feb 15 10:03:48 2012 From: typo3 at kay-strobach.de (Kay Strobach) Date: Wed, 15 Feb 2012 10:03:48 +0100 Subject: [TYPO3-dev] Password expiry and blacklists In-Reply-To: References: Message-ID: Hello Christian, thanks for taking care - i would like to test your result. How this could be achieved: 1. React on userpassword changes with a hook: $TYPO3_CONF_VARS['SC_OPTIONS']['t3lib/class.t3lib_tcemain.php']['processDatamapClass'][] In this hook you can change the processed values (contact me for details, made something similar for fe_users). Checking the new password is a bit harder, but there must be a hook for serverside validation as well. 2. Check in the backend.php, if the password has been expired and show form: 2.1 There are several suitable hooks, which can serve what you need: e.g.: $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS'] ['typo3/backend.php']['constructPostProcess'] The hook must than do a http redirect to your password change form and stop the execution of the script. 2.2 Another approach would be to add an additional BE item and do the password change with ExtJS and AJAX (like the relogin window in TYPO3 4.5) I would like to see 2.2, as this just stops the interaction for some seconds, but lets the be load the stores needed for further work. Thanks Kay Am 15.02.2012 08:02, schrieb Georg Ringer: > Hi Christian, > > first of all thanks for your input! > > Am 15.02.2012 03:01, schrieb Christian Lerrahn (Cerebrum): >> As TYPO3 is referred to as an Enterprise CMS, I really think it should >> have a password expiry (particularly for the backend) and password >> blacklists. This is a very common feature in corporate environments but >> completely absent in TYPO3. > > certainly true. > >> I've written an extension before for a client and hacked the core for >> that but it was all very messy so I decided against publishing it. > > maybe you wanna still share it and post the diffs somewhere? > >> Here is what I believe is necessary around password expiry and >> blacklisting. > > sounds all interesting and plausible. > >> But, to come to my real point, I'm happy to implement all that. > > great! > >> The >> question I want to ask here is how to approach the problem. As I'm not >> familiar with core development in general, I am worried that I might >> approach this in a way as to never get my patches approved. > > IMO this should be started as an extension as it makes it far easier to > test things, react better on bugs/features and at the end it can be > still talked about having it as sysextension shipped with the core. > > As a member of the security team I would like to have all those features > and would be happy to help you developing the extension! > > Feel free to contact me in private > Georg -- http://www.kay-strobach.de - Open Source Rocks TYPO3 .... inspiring people to share! Get involved: http://typo3.org Answere was usefull: https://flattr.com/profile/kaystrobach From steffen.ritter at typo3.org Wed Feb 15 14:49:59 2012 From: steffen.ritter at typo3.org (Steffen Ritter) Date: Wed, 15 Feb 2012 14:49:59 +0100 Subject: [TYPO3-dev] [TYPO3-core] TYPO3 4.7 Feature Freeze postponed Message-ID: Dear readers, On last minute the TYPO3 Core Team decided to postpone the release of TYPO3 4.7 beta 1 which had been scheduled for yesterday. Traditionally beta versions always mark the feature freeze major version currently being developed. As we sometimes get to know with open source development and mostly free time working developers not all of our targets always can be fulfilled. In the last few weeks we already had a hot topic you already might have heart about: the ?lesson learned? issue with the ExtJS 4 migration. But in addition to that we are dealing with another hot topic - the file abstraction layer. There have been aims already about one year ago, to get a first rudimentary version of that enhancement into the release of TYPO3 4.5 LTS - however that initiative was postponed back then to re-evaluate and improve the whole concepts a lot. Focussing on TYPO3 4.7, a lot of work as been put into this particular project, as well as in side-projects like a completely new media management component (formerly known as digital asset management - DAM). To cut a very long story short, development on the file abstraction layer feature got delayed - one of the major reasons for sure was the fact that ExtJS 4 was dropped (as already mentioned above) and a series of other new components had to be cleaned up again. So, we are a bit too late to keep the feature freeze, but still want to deliver the final release with FAL. Since TYPO3 4.0, the file abstraction layer is considered to be the first again with an incredible impact for editors, integrators and developers. It is self-evident that we do not put work to the TYPO3 Core, that we don?t consider to be stable and finished. Even by putting a lot of efforts in working on moving the current state of the File Abstraction Layer to the TYPO3 core GIT-repository the FAL Team informed us on last notice, that they consider the current state not to be stable enough for core merge and asked for a two week grace period with exception of Feature Freeze for the FAL. As for me as Release Manager on the one hand I am not in favour of such exceptions. It was and is a common rule, features not being ready until the scheduled feature freeze, just get postponed to the next release - in this case it would have been 4.8 in about six months instead of 4.7. As we have promised to bring the File Abstraction Layer into 4.7 this decision in this case would not have been an easy one. The pros and cons of the possibilities we had, have been discussed with the TYPO3 Core Development Team. Based on the support and opinion of them I decided to agree to the request of the FAL team. Anyhow to ensure that the second FAL related delay in our Roadmap will finally fulfill its aims, there are some pre-assumptions taken care of: Core-Team Members which have not been involved in the FAL project yet, jump in and promise to spend some additional hours on the FAL all the issues / problems and tasks are cleaned up and moved and updated on forge, categorized and prioritized as well as split up to smaller tasks to easily keep track of them all these pressing issues are assigned to people. Currently the following issues are considered as blockers to have FAL integrated to the TYPO3 Core (find the updated list of blockers here: http://forge.typo3.org/projects/typo3v4-fileabstractionlayer/issues?query_id=299 ): - Review and fix code in csc-uploads to stay backwards-compatible (registers), http://forge.typo3.org/issues/33929 taken care of by Steffen Ritter - Check existing functionality with TCA=>type=db,internal_type=file http://forge.typo3.org/issues/33253 - New TypoScript cObject for FAL files http://forge.typo3.org/issues/32800 - Remove old publishing infrastructure http://forge.typo3.org/issues/32791 taken care of by Benjamin Mack - Carefully check behaviour of upgrade wizards http://forge.typo3.org/issues/33951 - Reviews, restructuring and merge preparations by Oliver Hader (get a collection of relevant issues at http://forge.typo3.org/issues/33745 ) In addition you can find more issues on Forge: http://forge.typo3.org/projects/typo3v4-fileabstractionlayer/issues. As a result, the Beta 1 release of TYPO3 4.7 will be released on February 28th 2012 but the final release date will remain the same. I hope you all can understand and support our decisions and if you have any questions about this decision feel free to contact me via email. regards Steffen Ritter -- Steffen Ritter Release Manager TYPO3 4.7 TYPO3 .... inspiring people to share! Get involved: http://typo3.org From typo3 at kay-strobach.de Wed Feb 15 16:30:27 2012 From: typo3 at kay-strobach.de (Kay Strobach) Date: Wed, 15 Feb 2012 16:30:27 +0100 Subject: [TYPO3-dev] Authenticating BE User correctly Message-ID: Hello guys, perhaps you know my webdav extension EXT:webdav. During the last day i found, that it's incompatible to saltedpasswords :( I do currently authenticate users with the following code: $BE_USER->setBeUserByName($result[0]); if (!$result || md5($result[1])!=$BE_USER->user['password']) { Which assumes, that the user has an md5 encrypted password stored in the database. How is the correct way of authenticating a user with known plaintext password (http basic auth) independent of the use of any salting extension?! Is $BE_USER->processLoginData the right function? Thanks Kay -- http://www.kay-strobach.de - Open Source Rocks TYPO3 .... inspiring people to share! Get involved: http://typo3.org Answere was usefull: https://flattr.com/profile/kaystrobach From typo3 at ringerge.org Wed Feb 15 16:37:14 2012 From: typo3 at ringerge.org (Georg Ringer) Date: Wed, 15 Feb 2012 16:37:14 +0100 Subject: [TYPO3-dev] Authenticating BE User correctly In-Reply-To: References: Message-ID: Hi, this is for FE but should be same for BE when you change FE to BE ;) From typo3 at ringerge.org Wed Feb 15 16:37:29 2012 From: typo3 at ringerge.org (Georg Ringer) Date: Wed, 15 Feb 2012 16:37:29 +0100 Subject: [TYPO3-dev] Authenticating BE User correctly In-Reply-To: References: Message-ID: Am 15.02.2012 16:37, schrieb Georg Ringer: > Hi, > > this is for FE but should be same for BE when you change FE to BE ;) /** * Check password of user with a given one * * @param array $userRecord * @param string $password * @return boolean */ private function compareUserRecordWithPassword(array $userRecord, $password) { t3lib_div::requireOnce(t3lib_extMgm::extPath('saltedpasswords', 'classes/salts/class.tx_saltedpasswords_salts_factory.php')); $this->objInstanceSaltedPW = tx_saltedpasswords_salts_factory::getSaltingInstance($userRecord['password'], 'FE'); if (!is_object($this->objInstanceSaltedPW)) { $isValid = md5($password) == $userRecord['password']; return $isValid; #throw new Exception ('No Password-Factory found'); } $validPassword = $this->objInstanceSaltedPW->checkPassword($password, $userRecord['password']); return $validPassword; } From lists at ptw.taurus.uberspace.de Wed Feb 15 16:38:03 2012 From: lists at ptw.taurus.uberspace.de (Philipp Wintermantel) Date: Wed, 15 Feb 2012 16:38:03 +0100 Subject: [TYPO3-dev] Extbase Storage Backend Message-ID: Hi all, I want to implement a custom storage backend for a specific extension (Some data types have to be loaded directly from a REST API and i want to keep a compatible interface to use fluid widget like paginate). The wiki states that DI via Typoscript setup works only on a global scope. Are there other ways to implement this? I'd be glad to get some hints... Thanks in advance, Philipp From typo3 at kay-strobach.de Wed Feb 15 18:17:16 2012 From: typo3 at kay-strobach.de (Kay Strobach) Date: Wed, 15 Feb 2012 18:17:16 +0100 Subject: [TYPO3-dev] Authenticating BE User correctly In-Reply-To: References: Message-ID: Hello Georg, MANY thanks ;) Wouldn't it be sensefull to have this function in the class t3lib_tsfeBeUserAuth or it's parent? I think this function is used in many extensions and this should be part of the public API. Regards Kay Am 15.02.2012 16:37, schrieb Georg Ringer: > Am 15.02.2012 16:37, schrieb Georg Ringer: >> Hi, >> >> this is for FE but should be same for BE when you change FE to BE ;) > > /** > * Check password of user with a given one > * > * @param array $userRecord > * @param string $password > * @return boolean > */ > private function compareUserRecordWithPassword(array $userRecord, > $password) { > t3lib_div::requireOnce(t3lib_extMgm::extPath('saltedpasswords', > 'classes/salts/class.tx_saltedpasswords_salts_factory.php')); > > $this->objInstanceSaltedPW = > tx_saltedpasswords_salts_factory::getSaltingInstance($userRecord['password'], > 'FE'); > if (!is_object($this->objInstanceSaltedPW)) { > $isValid = md5($password) == $userRecord['password']; > return $isValid; > #throw new Exception ('No Password-Factory found'); > } > $validPassword = $this->objInstanceSaltedPW->checkPassword($password, > $userRecord['password']); > return $validPassword; > } -- http://www.kay-strobach.de - Open Source Rocks TYPO3 .... inspiring people to share! Get involved: http://typo3.org Answere was usefull: https://flattr.com/profile/kaystrobach From typo3 at kay-strobach.de Wed Feb 15 18:34:53 2012 From: typo3 at kay-strobach.de (Kay Strobach) Date: Wed, 15 Feb 2012 18:34:53 +0100 Subject: [TYPO3-dev] Extbase Storage Backend In-Reply-To: References: Message-ID: Hello Philipp, should be quite easy, just put the logic into your repository ;) Then you can get the data from wherever you want it ;) Regards Kay Am 15.02.2012 16:38, schrieb Philipp Wintermantel: > Hi all, > > I want to implement a custom storage backend for a specific extension > (Some data types have to be loaded directly from a REST API and i want > to keep a compatible interface to use fluid widget like paginate). > > The wiki states that DI via Typoscript setup works only on a global > scope. Are there other ways to implement this? > > I'd be glad to get some hints... > > Thanks in advance, > Philipp -- http://www.kay-strobach.de - Open Source Rocks TYPO3 .... inspiring people to share! Get involved: http://typo3.org Answere was usefull: https://flattr.com/profile/kaystrobach From lists at ptw.taurus.uberspace.de Wed Feb 15 19:51:08 2012 From: lists at ptw.taurus.uberspace.de (Philipp Wintermantel) Date: Wed, 15 Feb 2012 19:51:08 +0100 Subject: [TYPO3-dev] Extbase Storage Backend In-Reply-To: References: Message-ID: Hello Kay, thanks for your reply :-) Sure, putting the data access logic to the repository would be an option. But this would lead to a) treating the returned data in a different manner than the rest (i'd like to avoid that since chances are that a subset of the data may be stored/cached in a corresponding database table, which would lead to further changes...) OR b) implementing the result set with Tx_Extbase_Persistence_QueryResultInterface (and even Tx_Extbase_Persistence_QueryInterface for the pagination widget to work i guess) Besides, from my understanding the proper and clean way to implement the data access would be within a storage backend. Regards, Philipp Kay Strobach schrieb: > Hello Philipp, > > should be quite easy, just put the logic into your repository ;) > > Then you can get the data from wherever you want it ;) > > Regards > Kay > > Am 15.02.2012 16:38, schrieb Philipp Wintermantel: >> Hi all, >> >> I want to implement a custom storage backend for a specific extension >> (Some data types have to be loaded directly from a REST API and i want >> to keep a compatible interface to use fluid widget like paginate). >> >> The wiki states that DI via Typoscript setup works only on a global >> scope. Are there other ways to implement this? >> >> I'd be glad to get some hints... >> >> Thanks in advance, >> Philipp > > From Eric.Thibault at dc.ulaval.ca Wed Feb 15 20:07:34 2012 From: Eric.Thibault at dc.ulaval.ca (=?utf-8?B?w4lyaWMgVGhpYmF1bHQ=?=) Date: Wed, 15 Feb 2012 14:07:34 -0500 Subject: [TYPO3-dev] BE search string Message-ID: Hello to all. I've juste upgraded my site to 4.6.4 and my contributers told me that the search feature in the BE is not working anymore... I've tested it and no results are returned! I've tried english letters, accents, ... nothing! Is it a known issue? My language packs are all up to date. Here is the error log of Typo3 when I do a search : Core: Error handler (BE): PHP Warning: Invalid argument supplied for foreach() in /data2/html/typo3_src-4.6.4/typo3/class.db_list.inc line 833 From typo3 at t3node.com Wed Feb 15 20:24:24 2012 From: typo3 at t3node.com (=?UTF-8?B?U3RlZmZlbiBNw7xsbGVy?=) Date: Wed, 15 Feb 2012 20:24:24 +0100 Subject: [TYPO3-dev] Authenticating BE User correctly In-Reply-To: References: Message-ID: Hi. On 15.02.2012 18:17 Kay Strobach wrote: > Wouldn't it be sensefull to have this function in the class > t3lib_tsfeBeUserAuth or it's parent? no, because it depends on system extension saltedpasswords, which core cannot rely on. -- cheers, Steffen TYPO3 Blog: http://www.t3node.com/ Twitter: @t3node - http://twitter.com/t3node From helmut.hummel at typo3.org Wed Feb 15 20:32:57 2012 From: helmut.hummel at typo3.org (Helmut Hummel) Date: Wed, 15 Feb 2012 20:32:57 +0100 Subject: [TYPO3-dev] Authenticating BE User correctly In-Reply-To: References: Message-ID: Hi, On 15.02.12 16:30, Kay Strobach wrote: > perhaps you know my webdav extension EXT:webdav. nope. > During the last day i found, that it's incompatible to saltedpasswords :( In theory the right way to authenticate is implementing a service and letting init.php the do all the hard work for you. If you describe a bit what excatly you try do to I probably can help. Kind regards, Helmut -- Helmut Hummel TYPO3 Security Team Leader, TYPO3 v4 Core Team Member TYPO3 .... inspiring people to share! Get involved: typo3.org From xavier at typo3.org Wed Feb 15 23:03:25 2012 From: xavier at typo3.org (Xavier Perseguers) Date: Wed, 15 Feb 2012 23:03:25 +0100 Subject: [TYPO3-dev] Extbase Storage Backend In-Reply-To: References: Message-ID: Hi, > I want to implement a custom storage backend for a specific extension > (Some data types have to be loaded directly from a REST API and i want > to keep a compatible interface to use fluid widget like paginate). > > The wiki states that DI via Typoscript setup works only on a global > scope. Are there other ways to implement this? > > I'd be glad to get some hints... Not sure if this is something that may help you but I wrote an article on how to create an LDAP backend: http://xavier.perseguers.ch/en/tutorials/typo3/articles/ldap-backend-for-extbase.html Perhaps it helps you figuring out a way to create your REST backend... HTH -- Xavier Perseguers Release Manager TYPO3 4.6 TYPO3 .... inspiring people to share! Get involved: http://typo3.org From lists at ptw.taurus.uberspace.de Thu Feb 16 06:32:34 2012 From: lists at ptw.taurus.uberspace.de (Philipp Wintermantel) Date: Thu, 16 Feb 2012 06:32:34 +0100 Subject: [TYPO3-dev] Extbase Storage Backend In-Reply-To: References: Message-ID: Hi Xavier, i found your article during your research. Much appreciated, thanks :-) In your case you've set the Tx_Extbase_Persistence_Storage_BackendInterface.className setting with an extension template an write "...feel free to narrow it down to your extension solely". How exactly would i be doing that? As i need both the REST and DB Backends on the same Page. Cheers, Philipp Xavier Perseguers schrieb: > Hi, > >> I want to implement a custom storage backend for a specific extension >> (Some data types have to be loaded directly from a REST API and i want >> to keep a compatible interface to use fluid widget like paginate). >> >> The wiki states that DI via Typoscript setup works only on a global >> scope. Are there other ways to implement this? >> >> I'd be glad to get some hints... > > Not sure if this is something that may help you but I wrote an article > on how to create an LDAP backend: > > http://xavier.perseguers.ch/en/tutorials/typo3/articles/ldap-backend-for-extbase.html > > Perhaps it helps you figuring out a way to create your REST backend... > > HTH > From typo3 at kay-strobach.de Thu Feb 16 07:53:24 2012 From: typo3 at kay-strobach.de (Kay Strobach) Date: Thu, 16 Feb 2012 07:53:24 +0100 Subject: [TYPO3-dev] Authenticating BE User correctly In-Reply-To: References: Message-ID: Hello Helmut, Georgs Solution worked so far. What i'm doing is the following: Hook into tslib/index_ts.php to catch uri's like, in [1]: http(s)://domain/index.php/dav/(.*) Then i use the controller to check wether the user is authenticated or not [2] around line 98: This way there needs to be a function to authenticate the user with known username and password ;) The current trunk is available on Forge [3] Thanks in advice Kay [1] http://forge.typo3.org/projects/extension-webdav/repository/entry/trunk/ext_localconf.php [2] http://forge.typo3.org/projects/extension-webdav/repository/entry/trunk/Classes/Controller/WebdavController.php [3] http://forge.typo3.org/projects/extension-webdav/repository/entry/trunk/ Am 15.02.2012 20:32, schrieb Helmut Hummel: > Hi, > > On 15.02.12 16:30, Kay Strobach wrote: > >> perhaps you know my webdav extension EXT:webdav. > > nope. > >> During the last day i found, that it's incompatible to saltedpasswords :( > > In theory the right way to authenticate is implementing a service and > letting init.php the do all the hard work for you. > > If you describe a bit what excatly you try do to I probably can help. > > Kind regards, > Helmut > -- http://www.kay-strobach.de - Open Source Rocks TYPO3 .... inspiring people to share! Get involved: http://typo3.org Answere was usefull: https://flattr.com/profile/kaystrobach From xavier at typo3.org Thu Feb 16 08:17:52 2012 From: xavier at typo3.org (Xavier Perseguers) Date: Thu, 16 Feb 2012 08:17:52 +0100 Subject: [TYPO3-dev] Extbase Storage Backend In-Reply-To: References: Message-ID: Hi Philipp, > i found your article during your research. Much appreciated, thanks :-) > > In your case you've set the > Tx_Extbase_Persistence_Storage_BackendInterface.className setting with > an extension template an write "...feel free to narrow it down to your > extension solely". How exactly would i be doing that? As i need both the > REST and DB Backends on the same Page. To be honest, I tried really quickly but could not make it work but according to Bastian, it should be possible. However I fear that nobody so far tried actually to do that. As in my case I could make it "global" in a subtree, that was fine for my use-case. If you come up with a bug report and possibly a patch (if it actually does not work as advertised), count me in to review it. Kind regards -- Xavier Perseguers Release Manager TYPO3 4.6 TYPO3 .... inspiring people to share! Get involved: http://typo3.org From typo3 at kay-strobach.de Thu Feb 16 10:39:10 2012 From: typo3 at kay-strobach.de (Kay Strobach) Date: Thu, 16 Feb 2012 10:39:10 +0100 Subject: [TYPO3-dev] Authenticating BE User correctly In-Reply-To: References: Message-ID: Hello Georg, to work also with saltedpasswords disabled, i changed the code to the following one: private function checkUserCredentials(array $userRecord, $password) { if(t3lib_extMgm::isLoaded('saltedpasswords', false)) { t3lib_div::requireOnce(t3lib_extMgm::extPath('saltedpasswords', 'classes/salts/class.tx_saltedpasswords_salts_factory.php')); $this->objInstanceSaltedPW = tx_saltedpasswords_salts_factory::getSaltingInstance($userRecord['password'], 'BE'); if (is_object($this->objInstanceSaltedPW)) { return $this->objInstanceSaltedPW->checkPassword($password, $userRecord['password']); } } return md5($password) == $userRecord['password']; } Regards Kay Am 15.02.2012 16:37, schrieb Georg Ringer: > Am 15.02.2012 16:37, schrieb Georg Ringer: >> Hi, >> >> this is for FE but should be same for BE when you change FE to BE ;) > > /** > * Check password of user with a given one > * > * @param array $userRecord > * @param string $password > * @return boolean > */ > private function compareUserRecordWithPassword(array $userRecord, > $password) { > t3lib_div::requireOnce(t3lib_extMgm::extPath('saltedpasswords', > 'classes/salts/class.tx_saltedpasswords_salts_factory.php')); > > $this->objInstanceSaltedPW = > tx_saltedpasswords_salts_factory::getSaltingInstance($userRecord['password'], > 'FE'); > if (!is_object($this->objInstanceSaltedPW)) { > $isValid = md5($password) == $userRecord['password']; > return $isValid; > #throw new Exception ('No Password-Factory found'); > } > $validPassword = $this->objInstanceSaltedPW->checkPassword($password, > $userRecord['password']); > return $validPassword; > } -- http://www.kay-strobach.de - Open Source Rocks TYPO3 .... inspiring people to share! Get involved: http://typo3.org Answere was usefull: https://flattr.com/profile/kaystrobach From typo3.lists at philippgampe.info Thu Feb 16 13:15:59 2012 From: typo3.lists at philippgampe.info (Philipp Gampe) Date: Thu, 16 Feb 2012 13:15:59 +0100 Subject: [TYPO3-dev] BE search string References: Message-ID: Hi ?ric Thibault, ?ric Thibault wrote: > Hello to all. > > I've juste upgraded my site to 4.6.4 and my contributers told me that the > search feature in the BE is not working anymore... I've tested it and no > results are returned! I've tried english letters, accents, ... nothing! >From which version did you upgrade? > Is it a known issue? My language packs are all up to date. What have language packs to do with the search? > Here is the error log of Typo3 when I do a search : Core: Error handler > (BE): PHP Warning: Invalid argument supplied for foreach() in > /data2/html/typo3_src-4.6.4/typo3/class.db_list.inc line 833 Looking at that line shows that this tries to traverse the TCA array. So it seems you are either missing some entries or you have a malformed TCA entry somewhere. Best thing you can do is to try to debug that function to find out which extension triggers the error message. BTW: Did you compare your database in the Install Tool? Viele Gr??e -- Philipp Gampe ? PGP-Key 0AD96065 From typo3 at kay-strobach.de Thu Feb 16 21:01:11 2012 From: typo3 at kay-strobach.de (Kay Strobach) Date: Thu, 16 Feb 2012 21:01:11 +0100 Subject: [TYPO3-dev] Featurerequest TER Message-ID: Hello guys, it would be nice to have an option in TER to send a mail after a successfull upload to TER. Why i do request this feature? - Because the new EM always throws an error on my slow internet connect, even if the upload succeded ;) Thanks in advice Kay -- http://www.kay-strobach.de - Open Source Rocks TYPO3 .... inspiring people to share! Get involved: http://typo3.org Answere was usefull: https://flattr.com/profile/kaystrobach From typo3 at t3node.com Fri Feb 17 13:32:17 2012 From: typo3 at t3node.com (=?UTF-8?B?U3RlZmZlbiBNw7xsbGVy?=) Date: Fri, 17 Feb 2012 13:32:17 +0100 Subject: [TYPO3-dev] Extbase Storage Backend In-Reply-To: References: Message-ID: On 16.02.2012 08:17 Xavier Perseguers wrote: > you come up with a bug report and possibly a patch (if it actually > does not work as advertised), count me in to review it. +1 -- cheers, Steffen TYPO3 Blog: http://www.t3node.com/ Twitter: @t3node - http://twitter.com/t3node From dmitry.dulepov at gmail.com Fri Feb 17 16:16:16 2012 From: dmitry.dulepov at gmail.com (Dmitry Dulepov) Date: Fri, 17 Feb 2012 17:16:16 +0200 Subject: [TYPO3-dev] Authenticating BE User correctly In-Reply-To: References: Message-ID: Hi! Kay Strobach wrote: > Georgs Solution worked so far. > > What i'm doing is the following: > > Hook into tslib/index_ts.php to catch uri's like, in [1]: > > http(s)://domain/index.php/dav/(.*) Make a service. The right way is to authenticate there because it takes care of sessions, clean ups, hooks, etc. -- Dmitry Dulepov TYPO3 core team member Blog: http://dmitry-dulepov.com/ Twitter: http://twitter.com/dmitryd Simplicity will save the world. From typo3 at kay-strobach.de Sat Feb 18 11:18:43 2012 From: typo3 at kay-strobach.de (Kay Strobach) Date: Sat, 18 Feb 2012 11:18:43 +0100 Subject: [TYPO3-dev] Authenticating BE User correctly In-Reply-To: References: Message-ID: Hello Dimitry, a service has a massive drawback on webdav performance, as more of the backend is initialized, than i actually need :( Also this would mean, that users of the normal backend can authenticate like: http://user:password at domain/typo3 That's something i definitly don't want ;) Thanks in advice, for your idea Kay Am 17.02.2012 16:16, schrieb Dmitry Dulepov: > Hi! > > Kay Strobach wrote: >> Georgs Solution worked so far. >> >> What i'm doing is the following: >> >> Hook into tslib/index_ts.php to catch uri's like, in [1]: >> >> http(s)://domain/index.php/dav/(.*) > > Make a service. The right way is to authenticate there because it takes > care of sessions, clean ups, hooks, etc. > -- http://www.kay-strobach.de - Open Source Rocks TYPO3 .... inspiring people to share! Get involved: http://typo3.org Answere was usefull: https://flattr.com/profile/kaystrobach From typo3.lists at philippgampe.info Sat Feb 18 15:56:00 2012 From: typo3.lists at philippgampe.info (Philipp Gampe) Date: Sat, 18 Feb 2012 15:56 +0100 Subject: [TYPO3-dev] Authenticating BE User correctly References: Message-ID: Hi Kay, Kay Strobach wrote: > a service has a massive drawback on webdav performance, as more of the > backend is initialized, than i actually need :( > Also this would mean, that users of the normal backend can authenticate > like: > > http://user:password at domain/typo3 > > That's something i definitly don't want ;) You could still check the request URI in your service and just return 100 or whatever is the return value for "I can't decide". What you are doing is to bypass the API which is acceptable for speed, but also means that you might not get security fixes and that your extension will break if the user uses another authentication service, e.g. some LDAP provider. Also, sending the password plaintext does not seem to be a smart solution to my, but if the is the only way for webdav ... still feels so 90's. Best regards -- Philipp Gampe ? PGP-Key 0AD96065 From lists at ptw.taurus.uberspace.de Sat Feb 18 15:31:58 2012 From: lists at ptw.taurus.uberspace.de (Philipp Wintermantel) Date: Sat, 18 Feb 2012 15:31:58 +0100 Subject: [TYPO3-dev] Extbase Storage Backend In-Reply-To: References: Message-ID: Hey, finally found the time to look into it... I submitted a bug report with a possible patch. http://forge.typo3.org/issues/34060 Cheers, Philipp Xavier Perseguers schrieb: > Hi Philipp, > >> i found your article during your research. Much appreciated, thanks :-) >> >> In your case you've set the >> Tx_Extbase_Persistence_Storage_BackendInterface.className setting with >> an extension template an write "...feel free to narrow it down to your >> extension solely". How exactly would i be doing that? As i need both the >> REST and DB Backends on the same Page. > > To be honest, I tried really quickly but could not make it work but > according to Bastian, it should be possible. However I fear that nobody > so far tried actually to do that. > > As in my case I could make it "global" in a subtree, that was fine for > my use-case. > > If you come up with a bug report and possibly a patch (if it actually > does not work as advertised), count me in to review it. > > Kind regards > From typo3 at sjbr.ca Mon Feb 20 03:59:15 2012 From: typo3 at sjbr.ca (Stanislas Rolland) Date: Sun, 19 Feb 2012 21:59:15 -0500 Subject: [TYPO3-dev] Re: [TYPO3-v4] This Week's "Friendly Ghost" In-Reply-To: References: Message-ID: Le 2012-02-12 23:57, Stanislas Rolland a ?crit : > Hi, > > I'll be your Core Team friendly ghost for this week, trying to clean up > the issue tracker and keeping an eye on new issues as they enter the > tracker. > > Please do not hesitate to get in touch with me: > > Email: typo3 at sjbr.ca > > The friendly ghost's tasks are described in this Wiki page: > http://forge.typo3.org/projects/typo3v4-core/wiki/FriendlyGhost > > Have a nice week, > Stanislas From typo3 at sjbr.ca Mon Feb 20 04:00:00 2012 From: typo3 at sjbr.ca (Stanislas Rolland) Date: Sun, 19 Feb 2012 22:00:00 -0500 Subject: [TYPO3-dev] Re: [TYPO3-v4] This Week's "Friendly Ghost" In-Reply-To: References: Message-ID: Hi, Here's the weekly friendly ghost summary for last week. A few numbers: ============================ Total: - Open Bugs: 2398 (was: 2393) - Open Features/Tasks: 725 (was: 720) Last week: - 128 issues were touched - bugs: 22 new, 17 resolved - features: 20 new, 14 resolved 126 issues are currently under review. Next week Stefan Galinski will be your friendly ghost, treat him well! Regards, Stanislas [1] http://forge.typo3.org/projects/typo3v4-core/wiki/FriendlyGhost From typo3 at penpal4u.net Mon Feb 20 05:12:33 2012 From: typo3 at penpal4u.net (Christian Lerrahn) Date: Mon, 20 Feb 2012 15:12:33 +1100 Subject: [TYPO3-dev] Password expiry and blacklists References: Message-ID: On Wed, 15 Feb 2012 07:28:58 +0100 Peter Russ wrote: [...] > In an enterprise you use LDAP. There the company's password policy is > defined. I see now need to add this into TYPO3. May be the extension > to connect to the LDAP could be improved to handle the few error > codes getting from LDAP correctly. Actually, I'm not sure that LDAP will always be the authentication system of choice. But even if an organisation employs LDAP, I consider the scenario where the website is integrated into the LDAP authentication scheme rather rare. This is certainly only the case for large organisations but will most likely never apply to anything small or medium size. Nevertheless, these organisations are often large enough already to have strict security policies which might stipulate password expiry. > Further in companies it is a security risk to store passwords in > TYPO3. This is not necessarily true. In fact, in the case which led me to develop something earlier, the client's policy did not allow for sensitive data in the web database but had separate authentication which required password expiry as a requirement for all IT systems in the organisation. If I was in charge, I'd probably also rather keep a web server entirely separate from the corporate network and only ban the use of the same username and password combinations as in the corporate network. To cut a long story short, despite your explanation, I still disagree with there being no need for such a functionality. Cheers, Christian From typo3 at penpal4u.net Mon Feb 20 05:16:46 2012 From: typo3 at penpal4u.net (Christian Lerrahn) Date: Mon, 20 Feb 2012 15:16:46 +1100 Subject: [TYPO3-dev] Password expiry and blacklists References: Message-ID: Hi Georg, On Wed, 15 Feb 2012 08:02:27 +0100 Georg Ringer wrote: > > I've written an extension before for a client and hacked the core > > for that but it was all very messy so I decided against publishing > > it. > > maybe you wanna still share it and post the diffs somewhere? Happy to do that. Hopefully, I'll be able to share the extension (which packages the patches as well) by the end of the week. As Helmut has cleaned up the service chain for 4.7 things might get a it easier if an extension was based on that version. However, I'd love to see something that works with 4.5 as well. (My current patch and extension have been used on 4.4 and 4.5.) > > The > > question I want to ask here is how to approach the problem. As I'm > > not familiar with core development in general, I am worried that I > > might approach this in a way as to never get my patches approved. > > IMO this should be started as an extension as it makes it far easier > to test things, react better on bugs/features and at the end it can be > still talked about having it as sysextension shipped with the core. > > As a member of the security team I would like to have all those > features and would be happy to help you developing the extension! Thanks for the offer. I'll get back to you once I've had some time to look into this again. Hopefully, this will happen in the next couple of weeks. Cheers, Christian From christian.lerrahn at cerebrum.com.au Mon Feb 20 05:27:10 2012 From: christian.lerrahn at cerebrum.com.au (Christian Lerrahn (Cerebrum)) Date: Mon, 20 Feb 2012 15:27:10 +1100 Subject: [TYPO3-dev] Password expiry and blacklists References: Message-ID: Hi Kay, On Wed, 15 Feb 2012 10:03:48 +0100 Kay Strobach wrote: > thanks for taking care - i would like to test your result. > > How this could be achieved: > > 1. React on userpassword changes with a hook: > > $TYPO3_CONF_VARS['SC_OPTIONS']['t3lib/class.t3lib_tcemain.php']['processDatamapClass'][] > > In this hook you can change the processed values (contact me for > details, made something similar for fe_users). > Checking the new password is a bit harder, but there must be a hook > for serverside validation as well. I actually use this hook in my current extension. However, I did not find a way of declaring the input invalid. I worked around this problem, by just expiring an invalid (i.e. blacklisted) password entered in the BE immediately, to make it impossible for a user to change back the password after having been forced to change it on login. > 2. Check in the backend.php, if the password has been expired and > show form: > > 2.1 There are several suitable hooks, which can serve what you need: > > e.g.: $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS'] > ['typo3/backend.php']['constructPostProcess'] > > The hook must than do a http redirect to your password change > form and stop the execution of the script. Not sure about this. I did go on a hunt for adequate hooks before I patched the core. However, there was no hook that allowed me to easily redirect to a password change form AFTER successful authentication and along with forced log out before redirect. The tricky bit here is to make it absolutely impossible to circumvent the password expiry. This was also the problem of a password expiry extension which existed some time ago. It had the user logged in while the password change occurred which meant that the change could be circumvented by just changing the URL in the browser to the backend URL manually. > 2.2 Another approach would be to add an additional BE item and do > the password change with ExtJS and AJAX (like the relogin window in > TYPO3 4.5) > > I would like to see 2.2, as this just stops the interaction for some > seconds, but lets the be load the stores needed for further work. I'd definitely like this as well but would need to do some research for this because I have never worked with ExtJS at this point. Also, I'm unsure if this could easily be used to overlay the log in screen while logged out (even though I suspect it is possible). Cheers, Christian From oliver.salzburg at googlemail.com Mon Feb 20 13:06:29 2012 From: oliver.salzburg at googlemail.com (Oliver Salzburg) Date: Mon, 20 Feb 2012 13:06:29 +0100 Subject: [TYPO3-dev] mkdir and mkdir_deep Message-ID: I wanted to write a small patch for a TYPO3 issue. I need to create a folder hierarchy on the file system to solve that issue. Obviously, I looked to TYPO3 built-in helpers to solve this. I found t3lib_div.mkdir and t3lib_div.mkdir_deep and I don't get how to use either one. What I want is perfectly available to me using the PHP mkdir with recursive set to true. But I assume there is a reason to use t3lib_div.mkdir so that all rights are set as expected etc. So t3lib_div.mkdir doesn't seem to provide recursive folder generation at all. So that is out of the question. t3lib_div.mkdir_deep sounds exactly like what I need. But why do I need to supply 2 directories? And the first directory is the "base" and it *has* to exist? So I need to split up the path that I want, make sure the first part of that split is already existing and then pass both parts to mkdir_deep()? That can't be right. Cheers Oliver From g4-lisz at tonarchiv.ch Mon Feb 20 13:50:39 2012 From: g4-lisz at tonarchiv.ch (g4-lisz at tonarchiv.ch) Date: Mon, 20 Feb 2012 13:50:39 +0100 Subject: [TYPO3-dev] Dispatch Error after adding Boolean Property to Demand Class In-Reply-To: References: Message-ID: On 08.02.2012 18:38, g4-lisz at tonarchiv.ch wrote: > He there > > In my extbase project i'm using a non-persistent object "Demand" for a > search form. Everything worked fine... > > Now i added a new property "isLocalKanton" to this Demand class: > > /* > * Local to Kanton > * > * @var boolean $isLocalKanton > */ > protected $isLocalKanton = false; > > /** > * @param boolean $isLocalKanton > * @return void > */ > public function setIsLocalKanton($isLocalKanton) { > $this->isLocalKanton = (boolean)$isLocalKanton; > } > > /** > * @return boolean isLocalKanton > */ > public function getIsLocalKanton() { > return $this->isLocalKanton; > } > > In the view i added a checkbox to the form: > > action="results" pageUid="26"> > > [...] > > > Before this change, everything worked flawlessly with other boolean > properties. > > Now i get the error: "Could not ultimately dispatch the request after > 101 iterations. Most probably, a @dontvalidate annotation is missing > on re-displaying a form with validation errors." > > Why is this? I can't see any mistake in my code... > > The action for displaying the search form looks like this: > /** > * Displays Fachabteilung Search Form > * > * @param Tx_Hplusinfo_Domain_Model_SearchDemand $demand The optional > default values > * @return void > * @dontvalidate $demand > */ > public function abteilungAction(Tx_Hplusinfo_Domain_Model_SearchDemand > $demand = NULL) { > if ($demand === NULL) { > $demandSession = > unserialize($GLOBALS["TSFE"]->fe_user->getKey("ses", "demand")); > if ( ($demandSession instanceof > Tx_Hplusinfo_Domain_Model_SearchDemand) > && ($demandSession->getPageId() == $GLOBALS["TSFE"]->id) > ) { > $demand = $demandSession; > } > else { > $demand = new Tx_Hplusinfo_Domain_Model_SearchDemand(); > $GLOBALS["TSFE"]->fe_user->setKey("ses", "demand", NULL); > } > } > > $this->view->assign('demand', $demand); > $this->view->assign('abteilungs', > $this->abteilungRepository->findAll()); > } > > If i the form checkbox is commented out, the error disappears. Again, > all other checkboxes work fine! > > I commented out the catch {} in the dispatcher loop > (typo3_src-4.6.1/typo3/sysext/extbase/Classes/MVC/Dispatcher.php:93). > Now it throws a Tx_Extbase_MVC_Exception_StopAction in > /typo3_src-4.6.1/typo3/sysext/extbase/Classes/MVC/Controller/AbstractController.php:277: > > public function forward($actionName, $controllerName = NULL, > $extensionName = NULL, array $arguments = NULL) { > $this->request->setDispatched(FALSE); > $this->request->setControllerActionName($actionName); > if ($controllerName !== NULL) > $this->request->setControllerName($controllerName); > if ($extensionName !== NULL) > $this->request->setControllerExtensionName($extensionName); > if ($arguments !== NULL) > $this->request->setArguments($arguments); > throw new Tx_Extbase_MVC_Exception_StopAction(); > } > > The request is forwarded to another action? Maybe that's a hint for > someone who knows the mechanisms.. > > Any help will be much appreciated! Sorry for bothering you... This issue is still not solved and our extension should be moved to production soon :( I have no idea how to debug this. Maybe someone could give me the name of a person who is in the development of extbase/dispatcher? Cheers, Till From tollepjaer at gmail.com Mon Feb 20 13:53:58 2012 From: tollepjaer at gmail.com (Mattias Nilsson) Date: Mon, 20 Feb 2012 13:53:58 +0100 Subject: [TYPO3-dev] Dispatch Error after adding Boolean Property to Demand Class In-Reply-To: References: Message-ID: Why not just replace boolean with an integer value 0 and 1 instead of false and true? /Mattias On Mon, Feb 20, 2012 at 1:50 PM, wrote: > On 08.02.2012 18:38, g4-lisz at tonarchiv.ch wrote: > >> He there >> >> In my extbase project i'm using a non-persistent object "Demand" for a >> search form. Everything worked fine... >> >> Now i added a new property "isLocalKanton" to this Demand class: >> >> /* >> * Local to Kanton >> * >> * @var boolean $isLocalKanton >> */ >> protected $isLocalKanton = false; >> >> /** >> * @param boolean $isLocalKanton >> * @return void >> */ >> public function setIsLocalKanton($**isLocalKanton) { >> $this->isLocalKanton = (boolean)$isLocalKanton; >> } >> >> /** >> * @return boolean isLocalKanton >> */ >> public function getIsLocalKanton() { >> return $this->isLocalKanton; >> } >> >> In the view i added a checkbox to the form: >> >> > action="results" pageUid="26"> >> >> [...] >> >> >> Before this change, everything worked flawlessly with other boolean >> properties. >> >> Now i get the error: "Could not ultimately dispatch the request after 101 >> iterations. Most probably, a @dontvalidate annotation is missing on >> re-displaying a form with validation errors." >> >> Why is this? I can't see any mistake in my code... >> >> The action for displaying the search form looks like this: >> /** >> * Displays Fachabteilung Search Form >> * >> * @param Tx_Hplusinfo_Domain_Model_**SearchDemand $demand The optional >> default values >> * @return void >> * @dontvalidate $demand >> */ >> public function abteilungAction(Tx_Hplusinfo_**Domain_Model_SearchDemand >> $demand = NULL) { >> if ($demand === NULL) { >> $demandSession = unserialize($GLOBALS["TSFE"]->**fe_user->getKey("ses", >> "demand")); >> if ( ($demandSession instanceof Tx_Hplusinfo_Domain_Model_** >> SearchDemand) >> && ($demandSession->getPageId() == $GLOBALS["TSFE"]->id) >> ) { >> $demand = $demandSession; >> } >> else { >> $demand = new Tx_Hplusinfo_Domain_Model_**SearchDemand(); >> $GLOBALS["TSFE"]->fe_user->**setKey("ses", "demand", NULL); >> } >> } >> >> $this->view->assign('demand', $demand); >> $this->view->assign('**abteilungs', $this->abteilungRepository->** >> findAll()); >> } >> >> If i the form checkbox is commented out, the error disappears. Again, all >> other checkboxes work fine! >> >> I commented out the catch {} in the dispatcher loop >> (typo3_src-4.6.1/typo3/sysext/**extbase/Classes/MVC/**Dispatcher.php:93). >> Now it throws a Tx_Extbase_MVC_Exception_**StopAction in >> /typo3_src-4.6.1/typo3/sysext/**extbase/Classes/MVC/** >> Controller/AbstractController.**php:277: >> >> public function forward($actionName, $controllerName = NULL, >> $extensionName = NULL, array $arguments = NULL) { >> $this->request->setDispatched(**FALSE); >> $this->request->**setControllerActionName($**actionName); >> if ($controllerName !== NULL) $this->request->** >> setControllerName($**controllerName); >> if ($extensionName !== NULL) $this->request->** >> setControllerExtensionName($**extensionName); >> if ($arguments !== NULL) $this->request->setArguments($** >> arguments); >> throw new Tx_Extbase_MVC_Exception_**StopAction(); >> } >> >> The request is forwarded to another action? Maybe that's a hint for >> someone who knows the mechanisms.. >> >> Any help will be much appreciated! >> > Sorry for bothering you... > > This issue is still not solved and our extension should be moved to > production soon :( > > I have no idea how to debug this. > > Maybe someone could give me the name of a person who is in the development > of extbase/dispatcher? > > > Cheers, > Till > ______________________________**_________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-**bin/mailman/listinfo/typo3-dev > From dmitry.dulepov at gmail.com Mon Feb 20 13:53:13 2012 From: dmitry.dulepov at gmail.com (Dmitry Dulepov) Date: Mon, 20 Feb 2012 14:53:13 +0200 Subject: [TYPO3-dev] Authenticating BE User correctly In-Reply-To: References: Message-ID: Hi! Kay Strobach wrote: > Also this would mean, that users of the normal backend can authenticate > like: > > http://user:password at domain/typo3 No, it wouldn't. Do you know how TYPO3 services work? -- Dmitry Dulepov TYPO3 core team member Blog: http://dmitry-dulepov.com/ Twitter: http://twitter.com/dmitryd Simplicity will save the world. From g4-lisz at tonarchiv.ch Mon Feb 20 14:02:35 2012 From: g4-lisz at tonarchiv.ch (g4-lisz at tonarchiv.ch) Date: Mon, 20 Feb 2012 14:02:35 +0100 Subject: [TYPO3-dev] Dispatch Error after adding Boolean Property to Demand Class In-Reply-To: References: Message-ID: On 20.02.2012 13:53, Mattias Nilsson wrote: > Why not just replace boolean with an integer value 0 and 1 instead of false > and true? > > /Mattias > This should help? I have 4 other boolean properties in the same demand object and they are all initialized the same way. Now with 5 boolean properties it doesn't work anymore... Cheers, Till From jigal at xs4all.nl Mon Feb 20 14:08:35 2012 From: jigal at xs4all.nl (Jigal van Hemert) Date: Mon, 20 Feb 2012 14:08:35 +0100 Subject: [TYPO3-dev] mkdir and mkdir_deep In-Reply-To: References: Message-ID: Hi, On 20-2-2012 13:06, Oliver Salzburg wrote: > So t3lib_div.mkdir doesn't seem to provide recursive folder generation > at all. So that is out of the question. t3lib_div.mkdir_deep sounds > exactly like what I need. > > But why do I need to supply 2 directories? And the first directory is > the "base" and it *has* to exist? So I need to split up the path that I > want, make sure the first part of that split is already existing and > then pass both parts to mkdir_deep()? That can't be right. t3lib_div::mkdir_deep() is what you're looking for. The first parameter is the directory path you want to create. The second parameter is optional and kept for backwards compatibility (= it was used in the past but we don't want to break code which still uses it) The difference with PHP mkdir is that the TYPO3 version not only sets the mask to the value in the Install Tool ['BE']['folderCreateMask'], but also makes sure the group is set to the Install Tool setting ['BE']['createGroup']. Just use t3lib_div::mkdir_deep() and forget about the second parameter. -- Kind regards / met vriendelijke groet, Jigal van Hemert. From oliver.salzburg at googlemail.com Mon Feb 20 14:21:44 2012 From: oliver.salzburg at googlemail.com (Oliver Salzburg) Date: Mon, 20 Feb 2012 14:21:44 +0100 Subject: [TYPO3-dev] mkdir and mkdir_deep In-Reply-To: References: Message-ID: On 2012-02-20 14:08, Jigal van Hemert wrote: > The first parameter is the directory path you want to create. > The second parameter is optional and kept for backwards compatibility (= > it was used in the past but we don't want to break code which still uses > it) Are you sure about that? I was reading the source here: http://typo3.org/fileadmin/typo3api-4.0.0/d6/d99/class_8t3lib__div_8php-source.html It seemed to me like $destination has little relevance as long as $deepDir is an absolute path. Which would mean the first parameter is the less relevant one. If $deepDir is empty, it seems like that would cause the whole foreach in mkdir_deep() to be skipped. Cheers Oliver From stefan.galinski at gmail.com Mon Feb 20 14:34:15 2012 From: stefan.galinski at gmail.com (Stefan Galinski) Date: Mon, 20 Feb 2012 14:34:15 +0100 Subject: [TYPO3-dev] This Week's "Friendly Ghost" Message-ID: Hi, I'll be your Core Team friendly ghost for this week, trying to clean up the issue tracker and keeping an eye on new issues as they enter the tracker. Please do not hesitate to get in touch with me: E-Mail: stefan.galinski at gmail.com The friendly ghost's tasks are described in this Wiki page: http://forge.typo3.org/projects/typo3v4-core/wiki/FriendlyGhost -- Stefan Galinski From typo3.lists at philippgampe.info Mon Feb 20 15:27:30 2012 From: typo3.lists at philippgampe.info (Philipp Gampe) Date: Mon, 20 Feb 2012 15:27:30 +0100 Subject: [TYPO3-dev] mkdir and mkdir_deep References: Message-ID: Hi Oliver Salzburg, Oliver Salzburg wrote: > On 2012-02-20 14:08, Jigal van Hemert wrote: >> The first parameter is the directory path you want to create. >> The second parameter is optional and kept for backwards compatibility (= >> it was used in the past but we don't want to break code which still uses >> it) > > Are you sure about that? > I was reading the source here: > http://typo3.org/fileadmin/typo3api-4.0.0/d6/d99/class_8t3lib__div_8php- source.html TYPO3 4.0.0 ??? seriously please use the official documentation: http://api.typo3.org/typo3v4/master/html/classt3lib__div.html#a29fe9295cb3e206faac8916e70309a81 > It seemed to me like $destination has little relevance as long as > $deepDir is an absolute path. Which would mean the first parameter is > the less relevant one. > > If $deepDir is empty, it seems like that would cause the whole foreach > in mkdir_deep() to be skipped. Might be true for older versions: http://api.typo3.org/typo3v4/45/html/classt3lib__div.html#afc20029b8d695e59425bf811f3c5134a All versions on http://api.typo3.org/ Best regards -- Philipp Gampe ? PGP-Key 0AD96065 From jigal at xs4all.nl Mon Feb 20 16:36:02 2012 From: jigal at xs4all.nl (Jigal van Hemert) Date: Mon, 20 Feb 2012 16:36:02 +0100 Subject: [TYPO3-dev] mkdir and mkdir_deep In-Reply-To: References: Message-ID: Hi, On 20-2-2012 14:21, Oliver Salzburg wrote: > On 2012-02-20 14:08, Jigal van Hemert wrote: >> The first parameter is the directory path you want to create. >> The second parameter is optional and kept for backwards compatibility (= >> it was used in the past but we don't want to break code which still uses >> it) > > Are you sure about that? Hmm.. 'old' versions of TYPO3 (before 4.6) needed indeed two parameters: First parameter was the path to an existing directory where you wanted to create a subdirectory (or several levels) The second parameter was the path you wanted to create below the first parameter. For example: inside /var/www/mysite/fileadmin/templates/ you want to create images/portraits/ You can call t3lib_div::mkdir_deep('/var/www/mysite/fileadmin/templates/', 'images/portraits/'); to create these directories. In 4.6 and higher you can combine the two paths. mkdir_deep will then create directories as needed and will make sure the mask and group settings are correct for all parts of the path. Sorry about the confusion. -- Kind regards / met vriendelijke groet, Jigal van Hemert. From oliver.salzburg at googlemail.com Mon Feb 20 16:40:05 2012 From: oliver.salzburg at googlemail.com (Oliver Salzburg) Date: Mon, 20 Feb 2012 16:40:05 +0100 Subject: [TYPO3-dev] mkdir and mkdir_deep In-Reply-To: References: Message-ID: On 2012-02-20 15:27, Philipp Gampe wrote: >> I was reading the source here: >> http://typo3.org/fileadmin/typo3api-4.0.0/d6/d99/class_8t3lib__div_8php- > source.html > > TYPO3 4.0.0 ??? seriously please use the official documentation: > http://api.typo3.org/typo3v4/master/html/classt3lib__div.html#a29fe9295cb3e206faac8916e70309a81 I would have, but that was Googles first hit and a typo3.org URL seemed pretty official to me ;) http://api.typo3.org has never turned up in any of my search results weirdly enough. Well, thanks anyway :) Oliver From fsu-lists at cobweb.ch Mon Feb 20 17:14:19 2012 From: fsu-lists at cobweb.ch (=?UTF-8?B?RnJhbsOnb2lzIFN1dGVy?=) Date: Mon, 20 Feb 2012 17:14:19 +0100 Subject: [TYPO3-dev] mkdir and mkdir_deep In-Reply-To: References: Message-ID: Hi, > http://api.typo3.org has never turned up in any of my search results > weirdly enough. I can see why... It seems like http://api.typo3.org has been "integrated" into the future typo3.org relaunched web site (preview.typo3.org) and the search does not seem like it's (fully) implemented yet. However if you click on one specific API link (4.5 LTS, for example), you get to the "real" api.typo3.org and the search works fine there (at least I could find mkdir_deep ;-) ). Cheers -- Francois Suter Cobweb Development Sarl - http://www.cobweb.ch From ernesto.baschny at typo3.org Mon Feb 20 18:32:46 2012 From: ernesto.baschny at typo3.org (Ernesto Baschny) Date: Mon, 20 Feb 2012 18:32:46 +0100 Subject: [TYPO3-dev] [TYPO3-core] TYPO3 Core Budget from the T3A for 2012 Message-ID: Hi Dear TYPO3 Contributor, every year a certain amount of money is allocated by the TYPO3 Association to the TYPO3v4 and FLOW3/Phoenix Core Development. I am the responsible for the v4 part of the budget starting 2012 (Ingmar Schlecht did it before). Karsten Dambekalns is responsible for the FLOW3/Phoenix part of the budget. To provide a more transparent view for the public how the T3A sponsors our work and by which amounts, we would like to present to the public how we plan to spend the money in 2012. [ Note: This article is also published here for your linking and sharing pleasure: http://bit.ly/t3core-budget-2012 ] Notice that the hourly rate payed by the T3A is now ?55 (was ?50 before) and the daily rate was raised to ?330 (was ?300). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - TYPO3 v4 Core Budget - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - => TYPO3v4 Budget 2012: ?90.000 (roughly) The budget was split up for the application in the following categories: - Travel Expenses: ?20.000 - Release Management: ?6.800 - Core Team Lead: ?39.600 - Co-Core Team Lead: ?15.840 The "rest" (?7.500) is available for our famous "Important Development Pot", which we can decide to use it for stuff that we "need" but nobody is willing to do except for money. Other than that, we've raised the Release Management gratification from ?500 (until 4.7) to ?600 (4.8 and later) per month. More details about the money allocation can be read in this spreadsheet [1]. [1] https://docs.google.com/spreadsheet/ccc?key=0AgW3rWPECPK7dExHUVhIbnFGTDh4Q09EcHNKZS1lZ0E#gid=0 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - TYPO3 v4 and FLOW3/Phoenix Joint Budget - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - We have less Important Development Pot Budget because the T3A decided to allocate a slice of it to a "Joint v4 / Phoenix Budget", managed jointly by Karsten and myself. => Joint TYPO3 v4/v5 Budget 2012: ?36.000 We discussed last week in our R&D meeting about the potential use of this budget, and came up with some points worth considering: - Extbase related "groundwork" (make it stable, make it bug-free, make it reliable, make it *fast*), which can be considered important to avoid frustrations in the path to FLOW3, - forward porting fixes done to Extbase/v4 fixes into FLOW3/Phoenix, if relevant, - backwards porting FLOW3/Phoenix fixes, APIs and features to Extbase/v4, as far as is strategically makes sense, - part of the work on the "new TER" which should be a common basis for FLOW3 Packages *and* TYPO3v4 Extensions. The "new TER" has it's own Budget allocated (Sebastian, Fabien), so this should only cover work necessary to make it a shared resource between the two "worlds, - Content Migration Wizard (Export v4 Content to import it into Phoenix). Has been kick started before (GSoC), and if we find the man-power, it could be finished. Potentially other aspects. Feel free to contact me or Karsten, if you think you (or your team) have some work you want to do which could be covered by this budget. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - FLOW3/Phoenix Budget - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The FLOW3/Phoenix Team budget is (again) managed by Karsten Dambekalns. => FLOW3/Phoenix Budget 2012: ?197.600 The budget is comparable to last year's budget and covers - the planned (paid) work of a number of core team members, - travel expenses for code sprints and meetings The budget application we handed in is available to download (PDF) [2]. Although it does not reflect the exact numbers (the budget was capped and the application did use the hourly rate of 2011) the time planning as well as the feature set mentioned are correct. A look back at the use of the 2011 budget is also available [3] => Phoenix UX Budget 2012: ?24.000 This is a new budget, reserved for UX / UI work. The most pressing blocker for TYPO3 Phoenix right now is the lack of staff on the UX/UI front. We are currently looking into possible solutions and if it makes sense, the money will be invested into staff and travel expenses. [2] http://dl.dropbox.com/u/1536167/Phoenix/budget_2012_application_form_phoenix_flow3_v3.pdf [3] http://dl.dropbox.com/u/1536167/Phoenix/budget_2011_use_phoenix_flow3.pdf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Extbase Budget - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The Extbase Team also got allocated it's own budget, managed by Felix Oertel. => Extbase Budget 2012: ?9.500 According to Felix, it will basically be used to hold three code sprints: March for "finalizing 4.7", before the T3DD12 to "kick-start 4.8" and if possible another one before the 4.8 release. He noted that the budget will probably not be enough for the three sprints. While the extbase team tries to cover the additional costs by sponsoring, we might consider using parts of the Joint Budget to help out on that important front. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Budget Usage - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - In case you have some work that you think fits in one of the mentioned categories and you want it to be a payed job, please do not start working on it until you contact one of the corresponding budget managers, explaining your plan and the estimated amount of money to be spend (travel costs, working hours) so that the budget managers can approve (or deny with a reason) your request. Best Regards, Ernesto -- Ernesto Baschny Core Developer V4 Team Release Manager TYPO3 4.5 TYPO3 .... inspiring people to share! Get involved: typo3.org From typo3.lists at philippgampe.info Mon Feb 20 19:41:55 2012 From: typo3.lists at philippgampe.info (Philipp Gampe) Date: Mon, 20 Feb 2012 19:41:55 +0100 Subject: [TYPO3-dev] mkdir and mkdir_deep References: Message-ID: Hi Fran?ois, Fran?ois Suter wrote: >> http://api.typo3.org has never turned up in any of my search results >> weirdly enough. > > I can see why... It seems like http://api.typo3.org has been > "integrated" into the future typo3.org relaunched web site > (preview.typo3.org) and the search does not seem like it's (fully) > implemented yet. However if you click on one specific API link (4.5 LTS, > for example), you get to the "real" api.typo3.org and the search works > fine there (at least I could find mkdir_deep ;-) ). I think he meant that the google search returns such outdated results. And this is unfortunately the wrong (or outdated) links. "typo3 api" returns the correct result (http://api.typo3.org). But "typo3 mkdir_deep" returns as fourth position the outdated reference on typo3.org/fileadmin/typo3api-4.0.0/. Maybe someone with access to the typo3.org website could remove this folder and replace it with a redirect? Best regards -- Philipp Gampe ? PGP-Key 0AD96065 From oliver.salzburg at googlemail.com Mon Feb 20 20:04:19 2012 From: oliver.salzburg at googlemail.com (Oliver Salzburg) Date: Mon, 20 Feb 2012 20:04:19 +0100 Subject: [TYPO3-dev] mkdir and mkdir_deep In-Reply-To: References: Message-ID: On 2012-02-20 19:41, Philipp Gampe wrote: > I think he meant that the google search returns such outdated results. And > this is unfortunately the wrong (or outdated) links. Exactly. When searching for "t3lib_div.mkdir_deep", I get the documentation site I posted earlier as the top result. api.typo3.org is nowhere in sight. Same goes for bing.com btw. While that is confusing on its own, I'll just keep in mind to use api.typo3.org directly in the future. Thanks again Oliver From peter.russ at 4many.net Mon Feb 20 20:35:33 2012 From: peter.russ at 4many.net (Peter Russ) Date: Mon, 20 Feb 2012 20:35:33 +0100 Subject: [TYPO3-dev] Password expiry and blacklists In-Reply-To: References: Message-ID: --- Original Nachricht --- Absender: Christian Lerrahn Datum: 20.02.2012 05:12: > On Wed, 15 Feb 2012 07:28:58 +0100 > Peter Russ wrote: > > [...] > >> In an enterprise you use LDAP. There the company's password policy is >> defined. I see now need to add this into TYPO3. May be the extension >> to connect to the LDAP could be improved to handle the few error >> codes getting from LDAP correctly. > > Actually, I'm not sure that LDAP will always be the authentication > system of choice. But even if an organisation employs LDAP, I consider > the scenario where the website is integrated into the LDAP > authentication scheme rather rare. This is certainly only the case for > large organisations but will most likely never apply to anything small > or medium size. Nevertheless, these organisations are often large > enough already to have strict security policies which might stipulate > password expiry. > >> Further in companies it is a security risk to store passwords in >> TYPO3. > > This is not necessarily true. In fact, in the case which led me to > develop something earlier, the client's policy did not allow for > sensitive data in the web database but had separate authentication > which required password expiry as a requirement for all IT systems in > the organisation. If I was in charge, I'd probably also rather keep a > web server entirely separate from the corporate network and only > ban the use of the same username and password combinations as in the > corporate network. > > To cut a long story short, despite your explanation, I still disagree > with there being no need for such a functionality. > Sorry I've got you wrong mentioning "corporates environments" with SSO, key cards and AD. If you focusing on SME-market there might be a need. Peter -- Fiat lux! Docendo discimus. _____________________________ uon GbR http://www.uon.li http://www.xing.com/profile/Peter_Russ From Eric.Thibault at dc.ulaval.ca Mon Feb 20 23:47:53 2012 From: Eric.Thibault at dc.ulaval.ca (=?iso-8859-1?Q?=C9ric_Thibault?=) Date: Mon, 20 Feb 2012 17:47:53 -0500 Subject: [TYPO3-dev] eid extension listing Message-ID: Everything is working fine now on my dev system but I am experiencing the same problem as before on my production system (the two environment are virtualy identical)!?!?! My plugin is correctly listed in the Admin tools/configuration/FE>eID_include section but nothing is happening!?!?! The ajax fires and my alert returns success! But no data... I've also added the string 'hello' to the output of the main eid function but still empty! The last time it happened in my dev system everything stated working several days later without modifications... I am curious to know if this is a cashing problem in my Typo3 environment... I've cleared all caches several times (including configuration...) Is there something more I can do? On 12-2-2012 16:44, ?ric Thibault wrote: > Is there a way to list all extensions with eid configuration setup? > I've done eid setup before with no problems but I have an old > extension that I want to "eid enable" but with no success...!? If I > could list all eid extensions I would know if I've done it write on > not. Sure! - ADMIN TOOLS > Configuration, - select "$TYPO3_CONF_VARS (Global Configuration)" in the select box on top, - navigate to: FE > eID_include Now you see the list of extensions in your installation which have registered an eID script. 1. I've changed the ext_localconf.php: > // eID > $GLOBALS['TYPO3_CONF_VARS']['FE']['eID_include'][my_ext'] = 'EXT:my_ext/pi1/class.tx_my_ext_eid.php'; I hope the missing single quote in [my_ext'] was lost during copy/paste? > 2. And in the eid class file (my_ext/pi1/class.tx_my_ext_eid.php): > > require_once(PATH_tslib.'class.tslib_pibase.php'); > class tx_my_ext_eID extends tslib_pibase { Hmm... the point of having an eID script is to have a light weight version of TYPO3. No need to do this. You can use the functions in tslib_eidtools to initialize a database connection, an fe_user, etc. if you need those. > > function main() { > print('Hello'); > } > > } > > $SOBE = t3lib_div::makeInstance('tx_my_ext_eID'); > $SOBE->main(); > ?> That should work. Try it without the tslib_pibase stuff. -- Kind regards / met vriendelijke groet, Jigal van Hemert. ------------------------------ From michel at 4eyes.ch Thu Feb 23 14:35:28 2012 From: michel at 4eyes.ch (Michel Georgy - 4eyes GmbH) Date: Thu, 23 Feb 2012 14:35:28 +0100 Subject: [TYPO3-dev] XML Export with Fluid Message-ID: Hi list, We provide an XML Export with Extbase/Fluid for our customer. Everything works fine, but the Exported XML file contains all the tabs and spaces which are used to format the Fluid template. Is there a (nice) way to get rid of these blanks, tabs etc without having to edit the XML after the generation? Regards Michel From typo3 at strangefruit.nl Thu Feb 23 17:06:18 2012 From: typo3 at strangefruit.nl (Muriel le Pair) Date: Thu, 23 Feb 2012 17:06:18 +0100 Subject: [TYPO3-dev] foreign_table_where select current sys_language_uid Message-ID: Hi, I'm developing an multiple language extension and would like in the BE to select the records in the foreign_table for the current language. So if the record of the current language is English only the english records should visible etc etc. 'form_terms_conditions' => array ( 'exclude' => 0, 'label' => 'LLL:EXT:xx', 'config' => array ( 'type' => 'select', 'foreign_table' => 'tx_xxx', 'foreign_table_where' => 'AND (tx_xxx.sys_language_uid = ###REC_FIELD_sys_language_uid### OR tx_xxx.sys_language_uid = -1) ORDER BY tx_xxx.ref ASC', 'size' => 1, 'maxitems' => 1, 'default' => '' ) ), The query above somehow selects a language but not the correct one. -- kind regards, Muriel le Pair From linux at bigga.de Thu Feb 23 17:20:51 2012 From: linux at bigga.de (Alexander Bigga) Date: Thu, 23 Feb 2012 17:20:51 +0100 Subject: [TYPO3-dev] XML Export with Fluid In-Reply-To: References: Message-ID: Hi Michel, I just asked myself yesterday the same - but I found no answer.In my case it's only a question of "beauty of code". Maybe the typo3v4mvc list [1] is the better place to ask Fluid-questions. Regards, Alexander [1] http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-project-typo3v4mvc Am 23.02.2012 14:35, schrieb Michel Georgy - 4eyes GmbH: > Hi list, > > We provide an XML Export with Extbase/Fluid for our customer. > > Everything works fine, but the Exported XML file contains all the tabs and spaces which > are used to format the Fluid template. > > Is there a (nice) way to get rid of these blanks, tabs etc without having to edit the > XML after the generation? > > Regards > > Michel From typo3 at ringerge.org Thu Feb 23 19:35:49 2012 From: typo3 at ringerge.org (Georg Ringer) Date: Thu, 23 Feb 2012 19:35:49 +0100 Subject: [TYPO3-dev] XML Export with Fluid In-Reply-To: References: Message-ID: Hi, would be interested in that too.. what about a VH which just goes ofer the renderCHildren and split on lines and makes a trim? still stupid ... georg From bastian at typo3.org Thu Feb 23 21:54:12 2012 From: bastian at typo3.org (Bastian Waidelich) Date: Thu, 23 Feb 2012 21:54:12 +0100 Subject: [TYPO3-dev] XML Export with Fluid In-Reply-To: References: Message-ID: Michel Georgy - 4eyes GmbH wrote: Hi Michel, > We provide an XML Export with Extbase/Fluid for our customer. > > Everything works fine, but the Exported XML file contains all the tabs and spaces which > are used to format the Fluid template. Right. It's the same with HTML (and any other format) of course. Probably the easiest solution would be to clean up the output before saving it to the cache / file system (for example with html tidy [1]). If you want to use Fluid for that you should have a look at the so called *interceptors* (see [2]). We use them to apply htmlspecialchars() to dynamic output and in FLOW3 in order to rewrite resource paths [3]. HTH, Bastian [1] http://tidy.sourceforge.net/ [2] http://git.typo3.org/FLOW3/Packages/TYPO3.Fluid.git?a=blob;f=Classes/View/AbstractTemplateView.php;h=05038d69ecbf4736462f75f6ddd51622097a4a19;hb=HEAD#l366 [3] http://git.typo3.org/FLOW3/Packages/TYPO3.Fluid.git?a=blob;f=Classes/Core/Parser/Interceptor/Resource.php;h=df13d51bd019d5de99b7e0c3f4cc4b04ac115114;hb=HEAD From typo3 at ringerge.org Fri Feb 24 06:52:02 2012 From: typo3 at ringerge.org (Georg Ringer) Date: Fri, 24 Feb 2012 06:52:02 +0100 Subject: [TYPO3-dev] XML Export with Fluid In-Reply-To: References: Message-ID: Hi Bastian, Am 23.02.2012 21:54, schrieb Bastian Waidelich: > Probably the easiest solution would be to clean up the output before > saving it to the cache / file system (for example with html tidy [1]). true. is there a way to hook into the render() function for kind of postprocess? > If you want to use Fluid for that you should have a look at the so > called *interceptors* (see [2]). i checked that out but does this really help? as all the tabs and spaces are no objects or something like that? what of those should be used then? ------ const INTERCEPT_OPENING_VIEWHELPER = 1; const INTERCEPT_CLOSING_VIEWHELPER = 2; const INTERCEPT_TEXT = 3; const INTERCEPT_OBJECTACCESSOR = 4; ------- Georg From bastian at typo3.org Fri Feb 24 10:22:18 2012 From: bastian at typo3.org (Bastian Waidelich) Date: Fri, 24 Feb 2012 10:22:18 +0100 Subject: [TYPO3-dev] XML Export with Fluid In-Reply-To: References: Message-ID: Georg Ringer wrote: Hi Georg, >> Probably the easiest solution would be to clean up the output before >> saving it to the cache / file system (for example with html tidy [1]). > > true. is there a way to hook into the render() function for kind of > postprocess? Not yet, but we're planning to add some signals. That would also make it easier to do performance tests. For now I'd try using the "[FE][tidy]" configuration of TYPO3 or use one of the existing cleanup extensions. Obviously this only works in some cases. If you output the rendered result to the browser directly, you can post process is "manually". >> If you want to use Fluid for that you should have a look at the so >> called *interceptors* (see [2]). > > i checked that out but does this really help? as all the tabs and spaces > are no objects or something like that? what of those should be used then? I just gave it a shot and it seems to work: https://gist.github.com/1899672 (of course, this example is very dump and does not check for tags etc). NOTE: Interceptors are not (yet) part of the Public API [1]! Best Bastian [1] http://forge.typo3.org/projects/typo3v4-mvc/wiki/Public_API From michel at 4eyes.ch Fri Feb 24 11:25:35 2012 From: michel at 4eyes.ch (Michel Georgy - 4eyes GmbH) Date: Fri, 24 Feb 2012 11:25:35 +0100 Subject: [TYPO3-dev] XML Export with Fluid In-Reply-To: References: Message-ID: Hi, Thank you for the inputs. It looks like we checkout the tidy option then. michel On Feb 24, 2012, at 10:22 AM, Bastian Waidelich wrote: > Georg Ringer wrote: > > Hi Georg, > >>> Probably the easiest solution would be to clean up the output before >>> saving it to the cache / file system (for example with html tidy [1]). >> >> true. is there a way to hook into the render() function for kind of >> postprocess? > > Not yet, but we're planning to add some signals. That would also make it easier to do performance tests. > For now I'd try using the "[FE][tidy]" configuration of TYPO3 or use one of the existing cleanup extensions. > Obviously this only works in some cases. If you output the rendered result to the browser directly, you can post process is "manually". > >>> If you want to use Fluid for that you should have a look at the so >>> called *interceptors* (see [2]). >> >> i checked that out but does this really help? as all the tabs and spaces >> are no objects or something like that? what of those should be used then? > > I just gave it a shot and it seems to work: https://gist.github.com/1899672 (of course, this example is very dump and does not check for tags etc). > > NOTE: Interceptors are not (yet) part of the Public API [1]! > > Best > Bastian > > > [1] http://forge.typo3.org/projects/typo3v4-mvc/wiki/Public_API > _______________________________________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev From loek at netcoop.nl Fri Feb 24 16:29:51 2012 From: loek at netcoop.nl (Loek Hilgersom) Date: Fri, 24 Feb 2012 16:29:51 +0100 Subject: [TYPO3-dev] Phing or Ant? Message-ID: Hi, Today I was looking into Phing for build and deployment scripts. So far I've been using ant. Phing looks interesting but also very similar and it's going to take a lot of time to figure out pro's and con's of each. Any reasons to use Phing instead of Ant, or is it merely a matter of taste when your environment can run both? I'm happy to hear your experiences! Thanks, Loek From olivier.dobberkau at dkd.de Fri Feb 24 22:09:24 2012 From: olivier.dobberkau at dkd.de (Olivier Dobberkau) Date: Fri, 24 Feb 2012 22:09:24 +0100 Subject: [TYPO3-dev] Phing or Ant? In-Reply-To: References: Message-ID: Am 24.02.12 16:29, schrieb Loek Hilgersom: > I'm happy to hear your experiences! we use capistrano. olivier From loek at netcoop.nl Fri Feb 24 23:28:25 2012 From: loek at netcoop.nl (Loek Hilgersom) Date: Fri, 24 Feb 2012 23:28:25 +0100 Subject: [TYPO3-dev] Phing or Ant? In-Reply-To: References: Message-ID: On 02/24/2012 10:09 PM, Olivier Dobberkau wrote: > Am 24.02.12 16:29, schrieb Loek Hilgersom: > >> I'm happy to hear your experiences! > > we use capistrano. Hi Olivier, Forgot to mention that one, capistrano is third on my shortlist, but it's quite a different animal. I don't know much about it. For what reasons did you choose capistrano, or what shortcomings did you find in other tools that made you look for something else? Thanks, Loek From olivier.dobberkau at dkd.de Sat Feb 25 00:04:27 2012 From: olivier.dobberkau at dkd.de (Olivier Dobberkau) Date: Sat, 25 Feb 2012 00:04:27 +0100 Subject: [TYPO3-dev] Phing or Ant? In-Reply-To: References: Message-ID: Am 24.02.12 23:28, schrieb Loek Hilgersom: > Forgot to mention that one, capistrano is third on my shortlist, but > it's quite a different animal. I don't know much about it. For what > reasons did you choose capistrano, or what shortcomings did you find in > other tools that made you look for something else? as we do also ruby on rails it was a natural idea to use it fot TYPO3 too. We are thinking of releasing our capistrano scripts as Open-source. Hot Stuff! Olivier From typo3.neufeind at speedpartner.de Sun Feb 26 23:58:37 2012 From: typo3.neufeind at speedpartner.de (Stefan Neufeind) Date: Sun, 26 Feb 2012 23:58:37 +0100 Subject: [TYPO3-dev] Review/decision for URL-substitutions needed Message-ID: Hi, could some of you please take a look at https://review.typo3.org/3383 and see if/how we can proceed there? Personally I feel the change would be "okay" to go into earlier releases. But I also understand why Tolleiv says it's a change in behaviour (though it's just "fixing" it to the intended behaviour). Kind regards, Stefan From christian.lerrahn at cerebrum.com.au Mon Feb 27 07:04:57 2012 From: christian.lerrahn at cerebrum.com.au (Christian Lerrahn (Cerebrum)) Date: Mon, 27 Feb 2012 17:04:57 +1100 Subject: [TYPO3-dev] Password expiry and blacklists References: Message-ID: Hi Georg, On Wed, 15 Feb 2012 08:02:27 +0100 Georg Ringer wrote: > Am 15.02.2012 03:01, schrieb Christian Lerrahn (Cerebrum): > > As TYPO3 is referred to as an Enterprise CMS, I really think it > > should have a password expiry (particularly for the backend) and > > password blacklists. This is a very common feature in corporate > > environments but completely absent in TYPO3. > > certainly true. > > > I've written an extension before for a client and hacked the core > > for that but it was all very messy so I decided against publishing > > it. > > maybe you wanna still share it and post the diffs somewhere? I'm sorry I'm running a little bit late with publishing my extension plus the diffs. You can now download them at http://www.cerebrum.com.au/fileadmin/T3X_passwordexpiry-0_0_1-z-201202270249.t3x . I've used them against older versions of T3 4.4 and 4.5.11. Again, the cautionary remark I already made earlier, the diffs are quite messy and focus on getting the job done, no more no less. You can find the diffs in the extension's "res" folder I'm planning to review the cleaned up service chain in 4.7 and see how I could simplify my approach with the cleaner approach present there. I reckon the whole thing with the flag for expired accounts could be avoided if another status code for services was added which flags an authentication as successful but then passes the user on to password change. Services could then also expire passwords for different reasons (e.g. password too weak, etc.). The bigger deal is probably really how to handle the redirect as something like a "limited session" where the user cannot break out but has successfully authenticated. Cheers, Christian From stefan.galinski at gmail.com Mon Feb 27 11:15:58 2012 From: stefan.galinski at gmail.com (Stefan Galinski) Date: Mon, 27 Feb 2012 11:15:58 +0100 Subject: [TYPO3-dev] This Week's "Friendly Ghost" References: Message-ID: Hi, Here's the weekly friendly ghost summary for last week. A few numbers: ============================ Total: - Open Bugs: 2405 (was: 2398) - Open Features/Tasks: 728 (was: 725) Last week: - 131 issues were touched - bugs: 29 new, 20 resolved - features: 11 new, 9 resolved 193 issues are currently under review (review.typo3.org). This week Steffen Gebert will be your friendly ghost, treat him well! -- Stefan Galinski From jigal at xs4all.nl Mon Feb 27 11:35:18 2012 From: jigal at xs4all.nl (Jigal van Hemert) Date: Mon, 27 Feb 2012 11:35:18 +0100 Subject: [TYPO3-dev] [TYPO3-core] This Week's "Friendly Ghost" Message-ID: Hi, I'll be your Core Team friendly ghost for this week, trying to clean up the issue tracker and keeping an eye on new issues as they enter the tracker. Please do not hesitate to get in touch with me: Email: jigal at xs4all.nl Skype: jigal.van.hemert The friendly ghost's tasks are described in this Wiki page: http://forge.typo3.org/projects/typo3v4-core/wiki/FriendlyGhost -- Kind regards / met vriendelijke groet, Jigal van Hemert. From jigal at xs4all.nl Mon Feb 27 11:36:55 2012 From: jigal at xs4all.nl (Jigal van Hemert) Date: Mon, 27 Feb 2012 11:36:55 +0100 Subject: [TYPO3-dev] This Week's "Friendly Ghost" In-Reply-To: References: Message-ID: Hi, On 27-2-2012 11:15, Stefan Galinski wrote: > This week Steffen Gebert will be your friendly ghost, treat him well! Steffen is at T3BOARD12 and doing some server work with his team mates there. I took over his week (it wasn't changed in the schedule). -- Kind regards / met vriendelijke groet, Jigal van Hemert. From shanmugarajan.k at tcs.com Mon Feb 27 16:16:04 2012 From: shanmugarajan.k at tcs.com (Shanmugarajan K) Date: Mon, 27 Feb 2012 20:46:04 +0530 Subject: [TYPO3-dev] Linkvalidator for Flexform value Message-ID: Dear Team, I am checking the linkvalidator system extension in Typo3 4.5. Can you please some one help for how to configure the extension for validating the flexform link values. I.e i am having the flex form for links, but somehow the link Linkvalidator is not identfy the broken links. I want to know will that inbuild linkvalidator on 4.5 will support for flext form values? if so can you tell how to configure the same. My flexform structure is as below and it will be available at tt_content table "tx_templavoila_flex" column. 1 ROOT Select the HTML element on the page which you want to be the overall container element for the template. array attr Related Link 1 link 10 = TEXT 10.typolink.parameter.current = 1 10.typolink.returnLast = url 1 input 15 256 trim typolink,typolink_tag,images,url <_PADDING type="integer">2 popup Link link_popup.gif height=300,width=500,status=0,menubar=0,scrollbars=1 .... Thanks & regards Shan =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you From typo3.lists at philippgampe.info Mon Feb 27 21:38:03 2012 From: typo3.lists at philippgampe.info (Philipp Gampe) Date: Mon, 27 Feb 2012 21:38:03 +0100 Subject: [TYPO3-dev] Linkvalidator for Flexform value References: Message-ID: Hi Shanmugarajan K, Shanmugarajan K wrote: > Dear Team, > > I am checking the linkvalidator system extension in Typo3 4.5. Can you > please some one help for how to configure the extension for validating the > flexform link values. I.e > i am having the flex form for links, but somehow the link Linkvalidator is > not identfy the broken links. I want to know will that inbuild > linkvalidator on 4.5 will support for flext form values? if so can you > tell how to configure the same. > > My flexform structure is as below and it will be available at tt_content > table "tx_templavoila_flex" column. There is currently no support for flexforms. Please file a feature request at [1], but I can not promise you that this gets backported to 4.5. [1] http://forge.typo3.org/projects/extension-linkvalidator/issues/new Best regards -- Philipp Gampe ? PGP-Key 0AD96065 ? TYPO3 UG Bonn/K?ln ? linkvalidator From oliver.hader at typo3.org Tue Feb 28 23:37:30 2012 From: oliver.hader at typo3.org (Oliver Hader) Date: Tue, 28 Feb 2012 23:37:30 +0100 Subject: [TYPO3-dev] [TYPO3-core] Important: New Core Branch for 4.7 Message-ID: Hi everybody, you might have read the status article on the File Abstraction Layer [1]. One of the consequences is to create a new development branch right after the release of 4.7 beta1. So, the new branch is called: *TYPO3_4-7* This allows to continue with new features (i.e. the FAL API) in master, on the other hand bug fixes need to be backported from master to 4.7, 4.6, 4.5 and 4.4 again - so it's a bit more work for the next two months until 4.7.0 final was released. However and since new features are more interesting - I'd kindly ask everybody to concentrate on stabilizing TYPO3 4.7 first - which means, concentrate on bug fixes - instead of thinking too much about new new shiny features. Let's polish the ones we have... Thanks! Cheers, Olly [1] http://news.typo3.org/news/article/development-report-file-abstraction-layer/ -- Oliver Hader TYPO3 v4 Core Team Leader TYPO3 .... inspiring people to share! Get involved: http://typo3.org From tomita.militaru at gmail.com Wed Feb 29 10:40:14 2012 From: tomita.militaru at gmail.com (=?UTF-8?B?VG9tacWjxIMgTUlMSVRBUlU=?=) Date: Wed, 29 Feb 2012 11:40:14 +0200 Subject: [TYPO3-dev] ExtJS Datepicker disabledDays in backend Message-ID: Hello, I'm trying to figure out a method to restrict in the backend for an input field with *eval = date* only allow Wednesdays to be selected in the ExtJS Datepicker. In the ExJS documentation I've found *disabledDays* which allows to restrict week days. (eg. [0, 6] - disable Sunday & Saturday) Is there any way of doing this directly from the TCA (not create an custom eval, could not find anything about this in the TCA documentation) so that the backend user can select from the date picker only Wednesdays? Thanks. -- Engr. Tomi?? MILITARU Certified TYPO3 Integrator Tel. +40741064681 From lists at felixnagel.com Wed Feb 29 10:54:50 2012 From: lists at felixnagel.com (Felix Nagel) Date: Wed, 29 Feb 2012 10:54:50 +0100 Subject: [TYPO3-dev] Scheme enforcement in 4.5.x In-Reply-To: References: Message-ID: Any feedback on this issue? -- Regards Felix Nagel