From helmut.hummel at typo3.org Mon Dec 2 13:34:39 2013 From: helmut.hummel at typo3.org (Helmut Hummel) Date: Mon, 02 Dec 2013 13:34:39 +0100 Subject: [TYPO3-dev] PHPUnit cache? In-Reply-To: References: Message-ID: Hi Fran?ois, On 27.11.13 17:22, Fran?ois Suter wrote: >> /Users/fsuter/Sites/foo/typo3conf/ext/foo/Tests/Calculation/CalculationTest.php >> >> (not in Tests/Unit/ like AnnualizedPerformanceTest.php) > > That did it. > > I was also kind of surprised to put the tests in the "Unit" subfolder, This is a convention to better separate unit test cases from functional test cases. Unit tests should reside in Tests/Unit/... and functional tests in Tests/Functional/... > but I actually followed the structure created by the Extension Builder > for default test classes for domain models. This is fine, if the tests then are unit tests (testing only small code units of a class). > But it had really weird effects all around. On top of the problem > discussed here, I found out that if I added "Unit/" in the namespace, i.e. > > namespace Cobweb\Foo\Tests\Unit\Calculation; > > PphStorm would not resolve the name of the base class. PhpStorm sometimes chokes when renaming namespaces. If everything is correct and PhpStorm does not resolve classes correctly, closing and reopening PhpStorm always worked for me. > Maybe part of the mess is due to the namespace declared in the domain > model test classes, which is just > > namespace Cobweb\Foo\Tests; Yes, this it not optimal and Steffen already fixed it. > Again, this seems to be the default output by the Extension Builder. I > don't know if it's a good idea, nor how namespaces and file paths are > actually resolved in such cases. The sure is that they don't match, but > that does not seem to bother phpunit. > > Anyway moving the test classes around worked, thanks for the suggestion. > There's still some black magic going on, but I'm going to ignore it for > now, as it is not critical. Not too much magic in place. It boils down to only one rule: ===== If your class namespace and name matches the file location and name, this class will be autoloaded when needed without any additional configuration (since 6.0) ===== This implies: If your class namespace and name does not match the file location, you either need to require the class file manually or configure it in the class loader registry (ext_autoload.php), before you can use it. How to match namespace and file location (for Extensions)? 1. The *first segment* of the namespace is *always* a (free to choose) vendor name written in *UpperCamelCase*. Besides these two mandatory things, the vendor name is completely arbitrary and will be ignored during class loading. 2. The *second segment* must be the extension key, while underscores must be translated to camel casing (Extkey "foo_bar_baz" must be "FooBarBaz" as second namespace segment) 3. The following segments of the namespace must match exactly the directory structure of the class file, while it has to be distinguished between test classes and application classes 3a) Application Classes reside in a (top level) "Classes" folder and the "Classes" folder will *not* be part of the namespace e.g. A class with the namespace "\Vendor\FooBarBaz\Bla" must reside in the directory: foo_bar_baz/Classes/Bla/ (and vice versa) 3b) Test Classes reside in a (top level) "Tests" folder and the "Tets" folder *must* be part of the namespace e.g. A test class in the directory: foo_bar_baz/Tests/Unit/Bla/ must have the namespace "\Vendor\FooBarBaz\Tests\Unit\Bla" (and vice versa) 4. The file name must match exactly the class name (including casing) with an appended ".php" file extension e.g. a fully qualified class name "\Vendor\FooBarBaz\Bla\Blupp" must have a class file at exactly this location: "foo_bar_baz/Classes/Bla/Blupp.php" Maybe this more detailed info can be added to the docs here: http://docs.typo3.org/typo3cms/CoreApiReference/ApiOverview/Namespaces/Index.html#namespaces-extensions This information combined with the fact that the phpunit library includes test case files manually explains why test case classes could have inconsistent (or no) namespace, but if the tests themselves instantiate classes, these classes *must* match the convention described above to be found without a manual include in the test case. Hope this explains the behaviour you experienced a bit more detailed. Kind regards, Helmut -- Helmut Hummel Release Manager TYPO3 6.0 TYPO3 Core Developer, TYPO3 Security Team Member TYPO3 .... inspiring people to share! Get involved: typo3.org From mirko.steiner at me.com Mon Dec 2 14:57:02 2013 From: mirko.steiner at me.com (Mirko Steiner) Date: Mon, 02 Dec 2013 14:57:02 +0100 Subject: [TYPO3-dev] =?utf-8?q?_Which_Version_to_choose_starting_developin?= =?utf-8?q?g_plugins=3F?= Message-ID: Hi, i'm completly fresh to typo3 development but i'm an experienced PHP Developer. I downloaded the latest version of Typo3 (6.1.6) but the documentation an extensions are not working with this version perfectly. We planning to relaunch our website and currently typo3 seems to be the best candidate. I want to develop a few plugins for the company i'm working. So the question for me is, which version to choose. From blueduck at gmx.net Mon Dec 2 15:44:48 2013 From: blueduck at gmx.net (Stefano Kowalke) Date: Mon, 02 Dec 2013 15:44:48 +0100 Subject: [TYPO3-dev] Which Version to choose starting developing plugins? In-Reply-To: References: Message-ID: Hey Mirko, > I downloaded the latest version of Typo3 (6.1.6) but the documentation > an extensions are not working with this version perfectly. I don't understand this part. Which documentation of which extension is not working? I am using 6.1.6 for developing new extensions. If you planning to setup a complete new TYPO3 installation it makes sense to use the latest stable version. Stefano From fsu-lists at cobweb.ch Mon Dec 2 16:41:00 2013 From: fsu-lists at cobweb.ch (=?UTF-8?B?RnJhbsOnb2lzIFN1dGVy?=) Date: Mon, 02 Dec 2013 16:41:00 +0100 Subject: [TYPO3-dev] PHPUnit cache? In-Reply-To: References: Message-ID: Hi Helmut, Thanks for all those detailed explanations. > Maybe this more detailed info can be added to the docs here: > > http://docs.typo3.org/typo3cms/CoreApiReference/ApiOverview/Namespaces/Index.html#namespaces-extensions You're right. I have created an issue about it: http://forge.typo3.org/issues/54141 > Hope this explains the behaviour you experienced a bit more detailed. It does, thanks. Actually I still wonder why it worked for some classes and not for others, but I now know the correct structure with certainty and all my tests run fine. Cheers -- Francois Suter Work: Cobweb Development Sarl - http://www.cobweb.ch TYPO3: Help the project! - http://typo3.org/contribute/ Appreciate my work? Support me - http://www.monpetitcoin.com/en/francois/support-me/ From t3ng at bernd-wilke.net Mon Dec 2 17:19:11 2013 From: t3ng at bernd-wilke.net (bernd wilke) Date: Mon, 02 Dec 2013 17:19:11 +0100 Subject: [TYPO3-dev] Which Version to choose starting developing plugins? In-Reply-To: References: Message-ID: Am 02.12.13 14:57, schrieb Mirko Steiner: > Hi, > > i'm completly fresh to typo3 development but i'm an experienced PHP > Developer. > > I downloaded the latest version of Typo3 (6.1.6) but the documentation > an extensions are not working with this version perfectly. propably you got a version mix from documentations and sources beeing new with TYPO3 you may not know the great change TYPO3 is doing at the moment. until last year the running versions were 4.5, 4.6, 4.7 . where 4.5 is a LTS then a big version break came with 6.0, followed by version 6.1 with minor changes. in the near future (march 2014) is 6.2 with further changes as it will be the next LTS wich will replace 4.5 with 6.0 were introduced namespaces and a big restructuring of the code appeared, which breaks a lot of extensions. so having old documentation and / or old extensions will stop your installation and stop you from developing. beginning with 4.3 there existed 'extbase' as new framework/library for a MVC-based development and so existed some docuementation how to build extensions. But 'extbase' changed for each version. sometimes less, sometimes more, resulting in 'extbase 6.1' which is not the same as 6.0 or any earlier 'extbase'. and until now no book or document exist which will guide you with this version of extbase. The only available docuemantation is the source (or the api-description at api.typo3.org) and so you can still build up pibase extensions (old style since ever) you have to respect the new namespace pathes to the functions to let your extension run smoothly. and you don't have the Kickstarter which was a good startup example for pibased extensions. the ExtensionBuilder will give you a wireframe for extbase-extensions, but still misses a lot of features of teh old kickstarter. so it is not easy to start with TYPO3 extension development at the moment. But you may ask the community for specific problems and get good help (or you consult the newsgroup/forum) > We planning to relaunch our website and currently typo3 seems to be the > best candidate. I want to develop a few plugins for the company i'm > working. > > So the question for me is, which version to choose. 6.1 will be the best solution at the moment, you may use a 6.2beta, but as you are new to TYPO3 this might be more problematic. bernd -- http://www.pi-phi.de/cheatsheet.html From mirko.steiner at me.com Tue Dec 3 10:36:17 2013 From: mirko.steiner at me.com (Mirko Steiner) Date: Tue, 03 Dec 2013 10:36:17 +0100 Subject: [TYPO3-dev] =?utf-8?q?Which_Version_to_choose_starting_developing?= =?utf-8?q?_plugins=3F?= References: Message-ID: Quote: Stefano Kowalke wrote on Mon, 02 December 2013 15:44 ---------------------------------------------------- > Hey Mirko, > > > I downloaded the latest version of Typo3 (6.1.6) but the documentation > > an extensions are not working with this version perfectly. > > I don't understand this part. Which documentation of which extension is > not working? I'm using the documentation which is available under the typo3 document library (can't use the link here, because i have < 3 posts) Most of the docs are fine, but there are several differences between 6.1.6 and the version where the documentation belongs to. For example the Typoscript in 45 Minutes has some differences and the Extension for the Templating Tutorial can't be installed (does not work for 6.1.6) > I am using 6.1.6 for developing new extensions. If you planning to setup > a complete new TYPO3 installation it makes sense to use the latest > stable version. I agree, also i don't want to learn things related to versions which are outdated soon. From helmut.hummel at typo3.org Tue Dec 3 11:18:24 2013 From: helmut.hummel at typo3.org (Helmut Hummel) Date: Tue, 03 Dec 2013 11:18:24 +0100 Subject: [TYPO3-dev] PHPUnit cache? In-Reply-To: References: Message-ID: Hi Fran?ois, On 02.12.13 16:41, Fran?ois Suter wrote: > You're right. I have created an issue about it: > http://forge.typo3.org/issues/54141 Thanks. > Actually I still wonder why it worked for some classes > and not for others, The classes which worked (being the test case classes), were included by phpunit. At least that is what I assume. > but I now know the correct structure with certainty > and all my tests run fine. Great! Kind regards, Helmut -- Helmut Hummel Release Manager TYPO3 6.0 TYPO3 Core Developer, TYPO3 Security Team Member TYPO3 .... inspiring people to share! Get involved: typo3.org From alancampion at tiscali.co.uk Tue Dec 3 15:39:18 2013 From: alancampion at tiscali.co.uk (Alan Campion) Date: Tue, 03 Dec 2013 14:39:18 +0000 Subject: [TYPO3-dev] Fwd: Fwd: Re: [Ticket#2013113074000082] Observations from a Typo3 newbie In-Reply-To: <529DA275.6030207@tiscali.co.uk> References: <529DA275.6030207@tiscali.co.uk> Message-ID: Hello Everyone, The following was originally submitted to info at typo3.org with the following response from Peter Kraume. I am therefore forwarding the message to the two mailing lists Peter has suggested. Look forward to hearing from you. Regards Alan -------- Original Message -------- Subject: Re: [Ticket#2013113074000082] Observations from a Typo3 newbie Date: Mon, 2 Dec 2013 08:12:39 +0100 From: Peter Kraume via TYPO3 Association Organisation: TYPO3 Association To: alancampion at tiscali.co.uk CC: paul at bac111.co.uk Dear Alan Campion, Thank you for your mail, your kind words and your effort to write us in detail! As you might already know, TYPO3 is open source software. Thus everybody is encouraged to improve the software. To get your points to a broader audience, I'd suggest that you post your mail to our mailinglists. The english and the dev list should be suitable: http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev Thx again for your effort! Best regards, Peter Kraume -- TYPO3 Association, Sihlbruggstrasse 105, CH-6340 Baar, Switzerland http://association.typo3.org 11/30/2013 15:25 - Alan Campion wrote: Observations from a Typo3 newbie Firstly I will offer my apologies in advance, as this is probably not right entry point for what follows, as I'm still getting my head around the documentation. If you point me in the right direction for future reference, that would be appreciated. I have two machines, an (older) laptop and (newer) desktop running openSuSE 12.3 and the reason I'm telling you this will become apparent shortly. I successfully installed the typo3 introduction package (6.1.1) on my laptop a couple of months again without any apparent problems, and had a brief play around before making a start on the template tutorial. For this I attempted to install Typo3 (6.1.5) on my desktop. No apparent problems until I tried to add a task to the scheduler, when I discovered the SQL was broken. After a bit of digging I discovered the typo3 core bug #41596, and found that between the (rpm) package mariaDB 5.5.33-1.16.1.i586 (laptop) and mariaDB 5.5.33-7.2.i586, the usual openSuSE updates had added the following line to my /etc/my.cnf file. sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES Setting this to sql_mode = "" in line with laptop version, fixed that problem and I was then able to proceed with the template tutorial. That is, until that broke, which I presumed was my fault. The problem this time prevented me logging in as an admin user. No worries I thought, I'll simply do a fresh install of typo3; and in doing so update from version 6.1.5 to 6.1.6. Still broke, as was a reinstall of 6.1.5 and also 6.1.1. At this point I realised I hadn't broken typo3, something else had. So more digging revealed core bug #53682 which lead me to the difference in versions of PHP between my laptop (PHP version 5.3.17) and desktop (PHP 5.5.6). Looking at the typo3 download page requirements carefully this time, I see a range of versions for PHP and mySQL specified, rather than simply minimum versions. So I was my fault after all, for allowing the PHP version on my desktop to go beyond this range, which gets me to the point of this memo. Firstly I suggest the upper limit on the version of mySQL, from my very limited experience, probably needs to be tied down more precisely than 5.5.x, to avoid the first problem I encountered. Likewise, the range of versions for both PHP and MySQL, needs to be emphasised, something just short of big red letters that scream at you ;-) with the caveat, (warning) that versions beyond these upper limits, are untested (by the typo3 team) and therefore may not work. I.e the usual assumption that updates beyond these maximum values, "will only make things better" is not necessarily true. For Typo3/OpenSuSE users this is likely to become more problematic with the recent release of openSuSE 13.1. It would be helpful if, for example, the release notes in the download packages included a list or link, to known problems between these upper limits and current versions, however I appreciate the practical difficulties in maybe doing this. My reason for looking at Typo3, and persevering thus far, is because I'm a member of a small Linux user group (LUG), that is evaluating the implications of moving our existing CMS website to another platform. While this is a snapshot in time, I think the latter point is still worth stressing, if others are not to be put off, by making the same (newbie) mistakes as I did. I hope these observations are of some small help. Despite my initial teething problems, I've been impressed so far by the attention to detail, and quality of the documentation provided. My regards to Typo3 team Alan email: alancampion at tiscali.co.uk From philipp.gampe at typo3.org Tue Dec 3 22:39:08 2013 From: philipp.gampe at typo3.org (Philipp Gampe) Date: Tue, 03 Dec 2013 22:39:08 +0100 Subject: [TYPO3-dev] Fwd: Fwd: Re: [Ticket#2013113074000082] Observations from a Typo3 newbie References: <529DA275.6030207@tiscali.co.uk> Message-ID: Hi Alan, Alan Campion wrote: > also 6.1.1. At this point I realised I hadn't broken typo3, something > else had. So more digging revealed core bug #53682 which lead me to the > difference in versions of PHP between my laptop (PHP version 5.3.17) and > desktop (PHP 5.5.6). > > Looking at the typo3 download page requirements carefully this time, I > see a range of versions for PHP and mySQL specified, rather than simply > minimum versions. So I was my fault after all, for allowing the PHP > version on my desktop to go beyond this range, which gets me to the > point of this memo. I use PHP 5.5.6 on Fedora 64bit just fine. I did not hear about any problems about too new PHP versions so far. Best regards -- Philipp Gampe ? PGP-Key 0AD96065 ? TYPO3 UG Bonn/K?ln Documentation ? Active contributor TYPO3 CMS TYPO3 .... inspiring people to share! From linux at bigga.de Wed Dec 4 09:02:40 2013 From: linux at bigga.de (Alexander Bigga) Date: Wed, 04 Dec 2013 09:02:40 +0100 Subject: [TYPO3-dev] Fwd: Fwd: Re: [Ticket#2013113074000082] Observations from a Typo3 newbie In-Reply-To: References: <529DA275.6030207@tiscali.co.uk> Message-ID: Hi Philipp, with PHP 5.5.6 there is currently an open TYPO3-bug (4.5.x - 6.2.x) which breaks the backend. You really have no problems with PHP 5.5.6 on Fedora? That would really suprise me... http://forge.typo3.org/issues/53682 Best regards, Alexander Am 03.12.2013 22:39, schrieb Philipp Gampe: > Hi Alan, > > Alan Campion wrote: > >> also 6.1.1. At this point I realised I hadn't broken typo3, something >> else had. So more digging revealed core bug #53682 which lead me to the >> difference in versions of PHP between my laptop (PHP version 5.3.17) and >> desktop (PHP 5.5.6). >> >> Looking at the typo3 download page requirements carefully this time, I >> see a range of versions for PHP and mySQL specified, rather than simply >> minimum versions. So I was my fault after all, for allowing the PHP >> version on my desktop to go beyond this range, which gets me to the >> point of this memo. > > I use PHP 5.5.6 on Fedora 64bit just fine. I did not hear about any problems > about too new PHP versions so far. > > Best regards > From sara_bets at hotmail.com Wed Dec 4 11:47:47 2013 From: sara_bets at hotmail.com (Mike Kane) Date: Wed, 04 Dec 2013 11:47:47 +0100 Subject: [TYPO3-dev] =?utf-8?q?_=5BTypo3-dev=5D_Paypal_Payments?= Message-ID: Greetings friends ! I'm developing a website for a client where the registered users must pay by paypal a anual fee to stay "active" members of this bikers club, and this fee is very simple, a value for average bikers and other value for senior bikers. I guess in what concerns to the complexity it won't be much of a problem, because the possible values are only 2, so i guess it doesnt need to be as much elaborated like an online store or something about that... So, to deal with memberships i need to move the users from usergroups by a certain period of time, and when that period ends the user must be put in another usergroup until the next payment. Concerning all this needs, none of the current extensions give answers to them, so i guess i need to create an own extension do deal with paypal payments and auto usergroups changes after the payment...Can anyone point me in the right direction ? Kimd regards From gianluca.strafella at webformat.com Wed Dec 4 14:14:15 2013 From: gianluca.strafella at webformat.com (Gianluca Strafella) Date: Wed, 04 Dec 2013 14:14:15 +0100 Subject: [TYPO3-dev] Which Version to choose starting developing plugins? In-Reply-To: References: Message-ID: Hi Mirko, Il 02/12/2013 17:19, bernd wilke ha scritto: > Am 02.12.13 14:57, schrieb Mirko Steiner: >> Hi, >> >> i'm completly fresh to typo3 development but i'm an experienced PHP >> Developer. >> >> I downloaded the latest version of Typo3 (6.1.6) but the documentation >> an extensions are not working with this version perfectly. > > propably you got a version mix from documentations and sources > > beeing new with TYPO3 you may not know the great change TYPO3 is doing > at the moment. > until last year the running versions were 4.5, 4.6, 4.7 . where 4.5 is a > LTS > then a big version break came with 6.0, followed by version 6.1 with > minor changes. in the near future (march 2014) is 6.2 with further > changes as it will be the next LTS wich will replace 4.5 > > with 6.0 were introduced namespaces and a big restructuring of the code > appeared, which breaks a lot of extensions. > > so having old documentation and / or old extensions will stop your > installation and stop you from developing. > > beginning with 4.3 there existed 'extbase' as new framework/library for > a MVC-based development and so existed some docuementation how to build > extensions. But 'extbase' changed for each version. sometimes less, > sometimes more, resulting in 'extbase 6.1' which is not the same as 6.0 > or any earlier 'extbase'. > and until now no book or document exist which will guide you with this > version of extbase. > The only available docuemantation is the source (or the api-description > at api.typo3.org) You can start by http://docs.typo3.org/typo3cms/ExtbaseFluidBook/ to know exbase. This book is written starting by extbase to TYPO3 4.5 LTS, but it can be useful also for TYPO3 6.x that use namespaces. > > and so you can still build up pibase extensions (old style since ever) > you have to respect the new namespace pathes to the functions to let > your extension run smoothly. and you don't have the Kickstarter which > was a good startup example for pibased extensions. > > the ExtensionBuilder will give you a wireframe for extbase-extensions, > but still misses a lot of features of teh old kickstarter. > > so it is not easy to start with TYPO3 extension development at the > moment. But you may ask the community for specific problems and get good > help (or you consult the newsgroup/forum) > > >> We planning to relaunch our website and currently typo3 seems to be the >> best candidate. I want to develop a few plugins for the company i'm >> working. >> >> So the question for me is, which version to choose. > > 6.1 will be the best solution at the moment, > you may use a 6.2beta, but as you are new to TYPO3 this might be more > problematic. > > bernd Other useful links can be: http://forge.typo3.org/projects/typo3v4-mvc/wiki/Cookbook http://forge.typo3.org/projects/typo3v4-mvc/wiki/FAQ but I raccomand you, start by ExtbaseFluidBook. Regards, Gianluca Gianluca Strafella Software Developer gianluca.strafella at webformat.com Tel. +39-0427-926.389 WEBFORMAT srl ? www.webformat.com Via Mecenate, 76 - 20138 MILANO Corte Europa, 12 - 33097 SPILIMBERGO (PN) From luberti at archicoop.it Wed Dec 4 14:34:09 2013 From: luberti at archicoop.it (Ivano Luberti) Date: Wed, 04 Dec 2013 14:34:09 +0100 Subject: [TYPO3-dev] [Typo3-dev] Paypal Payments In-Reply-To: References: Message-ID: I have developed pi_base extension sometime ago that does just that. Is not published but I can share it with you if you like Il 04/12/2013 11:47, Mike Kane ha scritto: > Greetings friends ! > > I'm developing a website for a client where the registered users must > pay by paypal a anual fee to stay "active" members of this bikers > club, and this fee is very simple, a value for average bikers and > other value for senior bikers. > > I guess in what concerns to the complexity it won't be much of a > problem, because the possible values are only 2, so i guess it doesnt > need to be as much elaborated like an online store or something about > that... > So, to deal with memberships i need to move the users from usergroups > by a certain period of time, and when that period ends the user must > be put in another usergroup until the next payment. > > Concerning all this needs, none of the current extensions give answers > to them, so i guess i need to create an own extension do deal with > paypal payments and auto usergroups changes after the payment...Can > anyone point me in the right direction ? > > Kimd regards > _______________________________________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev > -- ================================================== dott. Ivano Mario Luberti Archimede Informatica societa' cooperativa a r. l. Sede Operativa Via Gereschi 36 - 56126- Pisa tel.: +39-050- 580959 tel/fax: +39-050-9711344 web: www.archicoop.it ================================================== From t3ng at bernd-wilke.net Wed Dec 4 14:44:17 2013 From: t3ng at bernd-wilke.net (bernd wilke) Date: Wed, 04 Dec 2013 14:44:17 +0100 Subject: [TYPO3-dev] [Typo3-dev] Paypal Payments In-Reply-To: References: Message-ID: Am 04.12.13 11:47, schrieb Mike Kane: > Greetings friends ! > > I'm developing a website for a client where the registered users must > pay by paypal a anual fee to stay "active" members of this bikers club, > and this fee is very simple, a value for average bikers and other value > for senior bikers. > > I guess in what concerns to the complexity it won't be much of a > problem, because the possible values are only 2, so i guess it doesnt > need to be as much elaborated like an online store or something about > that... > So, to deal with memberships i need to move the users from usergroups by > a certain period of time, and when that period ends the user must be put > in another usergroup until the next payment. > > Concerning all this needs, none of the current extensions give answers > to them, so i guess i need to create an own extension do deal with > paypal payments and auto usergroups changes after the payment...Can > anyone point me in the right direction ? > > Kimd regards there are at least two extensions in TER with this functionality. as been discussed in other newsgroups in the last weeks: timed_ugs itypo_expiring_fe_groups bernd -- http://www.pi-phi.de/cheatsheet.html From alkativo at gmx.de Wed Dec 4 15:21:02 2013 From: alkativo at gmx.de (alkativo) Date: Wed, 04 Dec 2013 15:21:02 +0100 Subject: [TYPO3-dev] =?utf-8?q?_Include_a_hook_in_extension?= Message-ID: Hi, i have a hook under typo3conf/ext/myhook/Classes/Hooks/MyhookAction.php and want to include a static public method from there to my other extension. I tried makeInstance is not working. Include_once relative and absolute not working. What can I do? See you Al From xavier at typo3.org Wed Dec 4 15:26:16 2013 From: xavier at typo3.org (Xavier Perseguers) Date: Wed, 04 Dec 2013 15:26:16 +0100 Subject: [TYPO3-dev] Include a hook in extension In-Reply-To: References: Message-ID: Hi, > i have a hook under > typo3conf/ext/myhook/Classes/Hooks/MyhookAction.php > > and want to include a static public method from there to my other > extension. I tried makeInstance is not working. Include_once relative > and absolute not working. > > What can I do? Show some code of what you did and try to do, it's not clear by reading. Kind regards -- Xavier Perseguers Release Manager TYPO3 4.6 TYPO3 .... inspiring people to share! Get involved: http://typo3.org From alkativo at gmx.de Wed Dec 4 15:34:26 2013 From: alkativo at gmx.de (alkativo) Date: Wed, 04 Dec 2013 15:34:26 +0100 Subject: [TYPO3-dev] =?utf-8?q?Include_a_hook_in_extension?= References: Message-ID: public function getPageItems($pid = 0){ $includestuff = \TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance('tx_realurl'); $return = array(); $aPids = $this->getPagetreeIds($pid); foreach ($aPids as $iPid) { $return[$iPid] = Tx_MyOtherClass_Hooks_MyAction::getPagePathesForPid($iPid); } $here = ''; } So in my Extension i try in one method to get a method from a other class. The includestuff with the sample extension is working but i can not get the public static method from the hook. I tried something like this include_once '/path/on/server/www/typo3conf/ext/MyOtherClass/Classes/Hooks/MyAction.php'; also relative pathes. In the hook i also got $genPath = tx_pagepath_api::getPagePath(intval($pid), $urlParameters); and do not need any include. Is it clearer now. Thanks so far ;) See you Al From alkativo at gmx.de Wed Dec 4 17:38:50 2013 From: alkativo at gmx.de (alkativo) Date: Wed, 04 Dec 2013 17:38:50 +0100 Subject: [TYPO3-dev] =?utf-8?q?Include_a_hook_in_extension?= References: Message-ID: So include works and class_exist return true but errorlog say PHP Fatal error class not found...this is really spooky From xavier at typo3.org Wed Dec 4 17:43:16 2013 From: xavier at typo3.org (Xavier Perseguers) Date: Wed, 04 Dec 2013 17:43:16 +0100 Subject: [TYPO3-dev] Include a hook in extension In-Reply-To: References: Message-ID: Hi, alkativo wrote: > public function getPageItems($pid = 0){ > $includestuff = > \TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance('tx_realurl'); $includestuff is never used, so I really don't get why you need this. > > $return = array(); > $aPids = $this->getPagetreeIds($pid); > > foreach ($aPids as $iPid) { > $return[$iPid] = > Tx_MyOtherClass_Hooks_MyAction::getPagePathesForPid($iPid); > } > $here = ''; > } > > So in my Extension i try in one method to get a method from a other > class. The includestuff with the sample extension is working but i can What is working? You don't use it! > not get the public static method from the hook. I tried something like this Your sample shows a non-namespaced class Tx_MyOtherClass_Hooks_MyAction whereas you use \TYPO3\CMS\Core\Utility\GeneralUtility. This suggests that you are using TYPO3 6.x. If you are using namespace in the code enclosing your code snippet here, you certainly have something like that: namespace \Whatever\Something; class YourExample { // your code snippet } so that when you write Tx_MyOtherClass_Hooks_MyAction, PHP (this has nothing to do with TYPO3) is looking for the fully qualified class name \Whatever\Something\Tx_MyOtherClass_Hooks_MyAction but your Tx_My... is from another extension (and it is not using namespaces) so that you should ask the correct class to be used: \Tx_MyOtherClass_Hooks_MyAction::getPagePathesForPid($iPid); (with a leading backslash). Kind regards -- Xavier Perseguers Release Manager TYPO3 4.6 TYPO3 .... inspiring people to share! Get involved: http://typo3.org From stefan.franke at gmx.co.uk Wed Dec 4 18:14:39 2013 From: stefan.franke at gmx.co.uk (Stefan Franke) Date: Wed, 4 Dec 2013 18:14:39 +0100 (CET) Subject: [TYPO3-dev] remove Parsetime-comment via TypoScript Message-ID: Hello, the Install Tool ("All configuration") tells me that it is possible to remove frontend debug output like the Parsetime-comment via Typoscript: -----install tool-----start--- [FE][debug] Boolean: If set, some debug HTML-comments may be output somewhere. Can also be set by TypoScript. -----install tool-----stop---- I couldn't find anything on how to do that with TypoScript in Google. Does anyone know how to do that? (I'm using TYPO3 4.5) Thanks & kind regards, Stefan From eichelt at web.de Wed Dec 4 18:28:24 2013 From: eichelt at web.de (Stefan Reichelt) Date: Wed, 04 Dec 2013 18:28:24 +0100 Subject: [TYPO3-dev] remove Parsetime-comment via TypoScript In-Reply-To: References: Message-ID: Hello Stefan, On 04.12.2013 18:14, Stefan Franke wrote: > I couldn't find anything on how to do that with TypoScript in Google. Does anyone know how to do that? (I'm using TYPO3 4.5) I believe it was 'config.debug'. Kind regards Stefan From alancampion at tiscali.co.uk Wed Dec 4 19:08:29 2013 From: alancampion at tiscali.co.uk (Alan Campion) Date: Wed, 04 Dec 2013 18:08:29 +0000 Subject: [TYPO3-dev] Fwd: Fwd: Re: [Ticket#2013113074000082] Observations from a Typo3 newbie In-Reply-To: References: <529DA275.6030207@tiscali.co.uk> Message-ID: Hi Philipp and Alexander, To the information posted by Alexander (included in bug #53682) I can add the following summary based on a screen shot I took at the time, if this is of further help to anyone. (I assume image attachments would be frowned on?). If I've understood the information in the bug history correctly, there is an issue with (legacy?) Typo3 code, which Chris Zepernick covers, as well as second issue with PHP itself, that Stefan Neufeind refers to. This latter reference I don't pretend to understand, nor the differences between 32/64 bit, both are outside my comfort zone. I'm guessing the Typo3 source code is the same(?), so any differences in compiled objects would be down to the respective compilers. That may explain why Philipp is apparently leading a charmed life, if my guesswork is correct. Regards Alan Summary of screenshot ------------------------------------ #1195126772:$toolbaritem "shortcuts" must implement interface TYPO3\Backend\Toolbar\ToolbarItemHookInterface UnexpectedValueException thrown in file typo3_src-6.1.5/typo3/sysext/backend/Classes/Controller/BackendController.php in line 148 3 TYPO3\CMS|Backend\Controller\BackendController::initializeCoreToolbarItems() typo3_src-6.1.5/typo3/sysext/backend/Classes/Controller/BackendController.php: /In listing, line 00126 is highlighted// / 2 TYPO3\CMS|Backend\Controller\BackendController::__construct() typo3_src-6.1.5/typo3/sysext/core/Classes/Utility/GeneralUtility.php: /line 04111 is highlighted// / 1 TYPO3\Core\Utility\GeneralUtility::makeInstance("TYPO3\CMS\Backend\Controller\BackendController") typo3_src-6.1.5/typo3/backend.php /line 00036 is highlighted// /------------------------------------------------- On 04/12/13 08:02, Alexander Bigga wrote: > Hi Philipp, > > with PHP 5.5.6 there is currently an open TYPO3-bug (4.5.x - 6.2.x) > which breaks the backend. > > You really have no problems with PHP 5.5.6 on Fedora? That would really > suprise me... > > http://forge.typo3.org/issues/53682 > > Best regards, > > Alexander > > Am 03.12.2013 22:39, schrieb Philipp Gampe: >> Hi Alan, >> >> Alan Campion wrote: >> >>> also 6.1.1. At this point I realised I hadn't broken typo3, something >>> else had. So more digging revealed core bug #53682 which lead me to the >>> difference in versions of PHP between my laptop (PHP version 5.3.17) and >>> desktop (PHP 5.5.6). >>> >>> Looking at the typo3 download page requirements carefully this time, I >>> see a range of versions for PHP and mySQL specified, rather than simply >>> minimum versions. So I was my fault after all, for allowing the PHP >>> version on my desktop to go beyond this range, which gets me to the >>> point of this memo. >> I use PHP 5.5.6 on Fedora 64bit just fine. I did not hear about any problems >> about too new PHP versions so far. >> >> Best regards >> > _______________________________________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev From administrator at credes.cz Thu Dec 5 12:00:07 2013 From: administrator at credes.cz (Martin Dostál) Date: Thu, 05 Dec 2013 12:00:07 +0100 Subject: [TYPO3-dev] =?utf-8?q?_Hook_to_filter_content_before_rendering=3F?= =?utf-8?b?Pz8=?= Message-ID: Hi all, could anyone help me? I need to filter content from tt_content by some criteria, before rendering in my extension. Probably by hook. Is there such a hook in typo3 6.1.6? And how can I use it? Thank you .... From m.bless at gmx.de Sat Dec 7 11:47:56 2013 From: m.bless at gmx.de (Martin Bless) Date: Sat, 07 Dec 2013 11:47:56 +0100 Subject: [TYPO3-dev] Tool that checks for CGL compliance? (php) Message-ID: Hi friends, I would like to run a tool that checks some PHP files a have here for TYPO3 Coding Guidelines compliance. Is such a tool available? Have a nice weekend ... Martin -- Certified TYPO3 Integrator | TYPO3 Documentation Team Member http://mbless.de From philipp.gampe at typo3.org Sat Dec 7 12:47:37 2013 From: philipp.gampe at typo3.org (Philipp Gampe) Date: Sat, 07 Dec 2013 12:47:37 +0100 Subject: [TYPO3-dev] Tool that checks for CGL compliance? (php) References: Message-ID: Hi Martin Bless, Martin Bless wrote: > Is such a tool available? http://metrics.typo3.org/ Other than that, you can use the code sniffs: http://pear.typo3.org/ Best regards -- Philipp Gampe ? PGP-Key 0AD96065 ? TYPO3 UG Bonn/K?ln Documentation ? Active contributor TYPO3 CMS TYPO3 .... inspiring people to share! From sara_bets at hotmail.com Mon Dec 9 14:19:11 2013 From: sara_bets at hotmail.com (Mike Kane) Date: Mon, 09 Dec 2013 14:19:11 +0100 Subject: [TYPO3-dev] =?utf-8?q?_Re=3A_=5BTypo3-dev=5D_Paypal_Payments?= References: Message-ID: Thank you both for your answers. However, i've not made my self clear like it was supossed to, it's entirelly my fault. I forgot to mention some details in what i need and why the extensions that Bernd mentioned does not satisfy my needs. I need that when the user logs in and makes the Paypal payment, the timed membership is defined AUTOMATICALLY, without any kind of action of the administrators. I guess that somehow this is possible, because i imagine that for example an organization that receives 1000 paypal payments every month, the administrator of the websites cannot do manually all the 1000 timed memberships, so that's why timed_ugs and itypo_expiring_fe_groups can't serve all my needs, they all need be defined manually. Or if they can, please tell me how. I think now i made more clear what i intend to do. Kind regards From t3ng at bernd-wilke.net Tue Dec 10 08:02:14 2013 From: t3ng at bernd-wilke.net (bernd wilke) Date: Tue, 10 Dec 2013 08:02:14 +0100 Subject: [TYPO3-dev] [Typo3-dev] Paypal Payments In-Reply-To: References: Message-ID: Am 09.12.13 14:19, schrieb Mike Kane: > Thank you both for your answers. > > However, i've not made my self clear like it was supossed to, it's > entirelly my fault. > > I forgot to mention some details in what i need and why the extensions > that Bernd mentioned does not satisfy my needs. > > I need that when the user logs in and makes the Paypal payment, the > timed membership is defined AUTOMATICALLY, without any kind of action of > the administrators. > I guess that somehow this is possible, because i imagine that for > example an organization that receives 1000 paypal payments every month, > the administrator of the websites cannot do manually all the 1000 timed > memberships, so that's why timed_ugs and itypo_expiring_fe_groups can't > serve all my needs, they all need be defined manually. > > Or if they can, please tell me how. > > I think now i made more clear what i intend to do. I think I got it before. Until now there is no public extension which will fulfil your needs in one. but you can enhance these existing extensions with a new extension to fulfil it. These old extensions are working to limit your premium memberships in time. and there is no difference whether you set the limit by hand or by any extension, which has to be written. bernd -- http://www.pi-phi.de/cheatsheet.html From luberti at archicoop.it Mon Dec 9 22:30:06 2013 From: luberti at archicoop.it (Ivano Luberti) Date: Mon, 09 Dec 2013 22:30:06 +0100 Subject: [TYPO3-dev] [Typo3-dev] Paypal Payments In-Reply-To: References: Message-ID: My extension does exactly that. When a payment is acknowledged by PAYPAL via IPN, it changes the fe_groups field of the fe_user record of the user that has made the payment. Actually my extensions is meant to manage payments for subscribers of courses managed by the seminar extension by Oliver Klee. I have extended it so that for each course the administrator defines a group to which the user is subscribed. When the payment arrives my extension look up in the course configuration, finds the id of the group and add it to the fe_groups field of the user The code it's really simple. If you like, you can look at my code and reuse the meaningful parts for your code. I hope this helps Il 09/12/2013 14:19, Mike Kane ha scritto: > Thank you both for your answers. > > However, i've not made my self clear like it was supossed to, it's > entirelly my fault. > > I forgot to mention some details in what i need and why the extensions > that Bernd mentioned does not satisfy my needs. > > I need that when the user logs in and makes the Paypal payment, the > timed membership is defined AUTOMATICALLY, without any kind of action > of the administrators. > I guess that somehow this is possible, because i imagine that for > example an organization that receives 1000 paypal payments every > month, the administrator of the websites cannot do manually all the > 1000 timed memberships, so that's why timed_ugs and > itypo_expiring_fe_groups can't serve all my needs, they all need be > defined manually. > > Or if they can, please tell me how. > > I think now i made more clear what i intend to do. > > Kind regards > _______________________________________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev > -- ================================================== dott. Ivano Mario Luberti Archimede Informatica societa' cooperativa a r. l. Sede Operativa Via Gereschi 36 - 56126- Pisa tel.: +39-050- 580959 tel/fax: +39-050-9711344 web: www.archicoop.it ================================================== From philippwrann at gmx.at Tue Dec 10 10:42:16 2013 From: philippwrann at gmx.at (Philipp) Date: Tue, 10 Dec 2013 10:42:16 +0100 Subject: [TYPO3-dev] =?utf-8?q?_Trigger_action_after_cache_is_cleared?= Message-ID: Hey! How can i register a hook to TYPO3 to trigger some action when someone cleared the cache? I want to update some caches directly in stead of updated them on demand when something is requested threough the FE. kind regards. From oliver.hader at typo3.org Tue Dec 10 11:53:50 2013 From: oliver.hader at typo3.org (Oliver Hader) Date: Tue, 10 Dec 2013 11:53:50 +0100 Subject: [TYPO3-dev] [TYPO3-core] Announcing TYPO3 CMS 4.5.32, 4.7.17, 6.0.12 and 6.1.7 Message-ID: Dear TYPO3 World, the TYPO3 Community has just released TYPO3 CMS versions 4.5.32, 4.7.17, 6.0.12 and 6.1.7 which are now ready for you to download. All versions are maintenance releases and contain bug and security fixes. *IMPORTANT* These versions include important security fixes to the TYPO3 CMS Core. A security announcement has just been released: http://typo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2013-004/ The packages can be downloaded here: http://typo3.org/download/ For details about the releases, please see: http://typo3.org/news/article/typo3-cms-4532-4717-6012-and-617-released/ MD5 checksums: f61c3e9a973d23e4a487c28d28ece5fa blankpackage-4.5.32.tar.gz 13bbfc7e80597097bedbfa90cdacca02 blankpackage-4.5.32.zip e04ee38c259b5319743a7986d708c958 dummy-4.5.32.tar.gz 2f64427e5683108a57f10b2396c0b0c9 dummy-4.5.32.zip 3ea6ddaf138087e993e59c60f9a29ff4 introductionpackage-4.5.32.tar.gz b59b0a040729e77df1354cd4783302ff introductionpackage-4.5.32.zip 49d79e50ec3d8fe7ab0b5505283af4eb typo3_src+dummy-4.5.32.zip a7dc7474dd60b210b97c60a3f07141fe typo3_src-4.5.32.tar.gz ccd38a5bbccc295749de2ede52e1ff1a typo3_src-4.5.32.zip eded3a2610931e74de5f5f15ebd9a347 blankpackage-4.7.17.tar.gz 881aaeb8115420a470f206232816185c blankpackage-4.7.17.zip f3366b856cc4a38937dd6efdc79e0bbb dummy-4.7.17.tar.gz 00c8a329bc75ab471c4d36a1b5e4066d dummy-4.7.17.zip 7ac3586f432f2d85b6dc6e4b8106a70e typo3_src+dummy-4.7.17.zip 4c3085e7f9b5e576ebdec9b7833b2af2 typo3_src-4.7.17.tar.gz fc9a7d1c75f5bf54703b8c1a31ebd334 typo3_src-4.7.17.zip 07c789c3986778fc5a6d10d71c2ee093 blankpackage-6.0.12.tar.gz 9f581f1531fbd53c2ff5ac01af607f92 blankpackage-6.0.12.zip da0b1a03940f0f968cab4d63a0cdfae6 dummy-6.0.12.tar.gz aea7b13c14b0a172b8fc699748f5d8e4 dummy-6.0.12.zip 19d97301de624a5996eae506aeb995d8 typo3_src+dummy-6.0.12.zip 8238e4af63bfbca34d43193065604d34 typo3_src-6.0.12.tar.gz 25ba5afe61b5d426a1895fb298536b7a typo3_src-6.0.12.zip a03c09e9bf8850d98d7db2c030469feb blankpackage-6.1.7.tar.gz b8070f90c3b7cbbb2d3cfadd0134bace blankpackage-6.1.7.zip 5bd2054a24b4b83595f5b4d9008d42d8 dummy-6.1.7.tar.gz 5c1dbe7e967ba1ea81c5d4b9a098e421 dummy-6.1.7.zip 4783b306f0188ba3cd9c0dcd7dcc274a governmentpackage-6.1.7.tar.gz f1d607795075772ac52a24b12231b056 governmentpackage-6.1.7.zip fd422bb1eb592ac03073ba371022c61c introductionpackage-6.1.7.tar.gz 83ecb19d4fdc08e1bdafb167ffbe8cb0 introductionpackage-6.1.7.zip 16a952424b355a3efbcdac5b836eca86 typo3_src+dummy-6.1.7.zip 66130b21ce61ef2ff5eafdd28b4ba6e1 typo3_src-6.1.7.tar.gz e7e65287615e6d7254e5442f653b6f49 typo3_src-6.1.7.zip Best regards Oliver -- Oliver Hader TYPO3 CMS Core Team Leader TYPO3 .... inspiring people to share! Get involved: http://typo3.org From sara_bets at hotmail.com Tue Dec 10 12:05:01 2013 From: sara_bets at hotmail.com (Mike Kane) Date: Tue, 10 Dec 2013 12:05:01 +0100 Subject: [TYPO3-dev] =?utf-8?q?=5BTypo3-dev=5D_Paypal_Payments?= References: Message-ID: Yes Bernd exactly, that's why i came here to get some proper instructions and directions, i never created an extension before, so i asked here for some guidance. Thank you very much Ivano, seeing your code would be a massive help to my work, how do you suggest to do that ? Kind regards From christian at futterlieb.ch Wed Dec 11 14:34:16 2013 From: christian at futterlieb.ch (Christian Futterlieb) Date: Wed, 11 Dec 2013 14:34:16 +0100 Subject: [TYPO3-dev] Trigger action after cache is cleared In-Reply-To: References: Message-ID: Hi Philipp You can use this hook: $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['t3lib/class.t3lib_tcemain.php']['clearCachePostProc'] But keep in mind, that this hook is called via backend. Thus the frontend stuff (eg. TSFE, typoscript setup, etc) will not be present. Regards, Christian On 10.12.13 10:42, Philipp wrote: > Hey! > > How can i register a hook to TYPO3 to trigger some action when someone > cleared the cache? > I want to update some caches directly in stead of updated them on demand > when something is requested threough the FE. > > kind regards. From sara_bets at hotmail.com Fri Dec 13 00:50:58 2013 From: sara_bets at hotmail.com (Mike Kane) Date: Fri, 13 Dec 2013 00:50:58 +0100 Subject: [TYPO3-dev] =?utf-8?q?=5BTypo3-dev=5D_Paypal_Payments?= References: Message-ID: Please Ivano, don't forget me :-) Kind regards From luberti at archicoop.it Fri Dec 13 08:59:10 2013 From: luberti at archicoop.it (Ivano Luberti) Date: Fri, 13 Dec 2013 08:59:10 +0100 Subject: [TYPO3-dev] [Typo3-dev] Paypal Payments In-Reply-To: References: Message-ID: My fault! I will email you during the week end....sorry for the delay!!!! Il 13/12/2013 00:50, Mike Kane ha scritto: > Please Ivano, don't forget me :-) > Kind regards _______________________________________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev > -- ================================================== dott. Ivano Mario Luberti Archimede Informatica societa' cooperativa a r. l. Sede Operativa Via Gereschi 36 - 56126- Pisa tel.: +39-050- 580959 tel/fax: +39-050-9711344 web: www.archicoop.it ================================================== From t3ng at bernd-wilke.net Fri Dec 13 09:33:43 2013 From: t3ng at bernd-wilke.net (bernd wilke) Date: Fri, 13 Dec 2013 09:33:43 +0100 Subject: [TYPO3-dev] [Typo3-dev] Paypal Payments In-Reply-To: References: Message-ID: Am 13.12.13 08:59, schrieb Ivano Luberti: > My fault! > I will email you during the week end....sorry for the delay!!!! > maybe you (both) can publish your extension(s) in TER? it seems to be a missing extension in the world of TYPO3. bernd -- http://www.pi-phi.de/cheatsheet.html From sara_bets at hotmail.com Sun Dec 15 13:57:16 2013 From: sara_bets at hotmail.com (Mike Kane) Date: Sun, 15 Dec 2013 13:57:16 +0100 Subject: [TYPO3-dev] =?utf-8?q?=5BTypo3-dev=5D_Paypal_Payments?= References: Message-ID: Thank you Ivano, i'm waiting for your contact :-) From luberti at archicoop.it Sun Dec 15 16:06:55 2013 From: luberti at archicoop.it (Ivano Luberti) Date: Sun, 15 Dec 2013 16:06:55 +0100 Subject: [TYPO3-dev] [Typo3-dev] Paypal Payments In-Reply-To: References: Message-ID: As I wrote before 1) I don't have to maintain the extensions (there is one for paypal and another one to manage groups). Recently and comprehensibly TER policies for publishing have been restricted for quality insurance. 2) one of the extensions is heavily linked to seminars( for example it accesses the seminars tables to know the group to be subscribed: I have extended seminars as well to manage a new field for defining a group for each course. So I don't think would be responsible to add an extension. Il 13/12/2013 09:33, bernd wilke ha scritto: > Am 13.12.13 08:59, schrieb Ivano Luberti: >> My fault! >> I will email you during the week end....sorry for the delay!!!! >> > > maybe you (both) can publish your extension(s) in TER? > > it seems to be a missing extension in the world of TYPO3. > > bernd -- ================================================== dott. Ivano Mario Luberti Archimede Informatica societa' cooperativa a r. l. Sede Operativa Via Gereschi 36 - 56126- Pisa tel.: +39-050- 580959 tel/fax: +39-050-9711344 web: www.archicoop.it ================================================== From t3ng at bernd-wilke.net Mon Dec 16 08:54:38 2013 From: t3ng at bernd-wilke.net (bernd wilke) Date: Mon, 16 Dec 2013 08:54:38 +0100 Subject: [TYPO3-dev] [Typo3-dev] Paypal Payments In-Reply-To: References: Message-ID: Am 15.12.13 16:06, schrieb Ivano Luberti: > As I wrote before > > 1) I don't have to maintain the extensions (there is one for paypal and > another one to manage groups). Recently and comprehensibly TER policies > for publishing have been restricted for quality insurance. > > 2) one of the extensions is heavily linked to seminars( for example it > accesses the seminars tables to know the group to be subscribed: I have > extended seminars as well to manage a new field for defining a group for > each course. > > So I don't think would be responsible to add an extension. Oh. it seems I missed the change to the motto of TYPO3: TYPO3 - Inspiring people NOT to share :( > > > > > Il 13/12/2013 09:33, bernd wilke ha scritto: >> Am 13.12.13 08:59, schrieb Ivano Luberti: >>> My fault! >>> I will email you during the week end....sorry for the delay!!!! >>> >> >> maybe you (both) can publish your extension(s) in TER? >> >> it seems to be a missing extension in the world of TYPO3. >> >> bernd > -- http://www.pi-phi.de/cheatsheet.html From xavier at typo3.org Mon Dec 16 09:02:06 2013 From: xavier at typo3.org (Xavier Perseguers) Date: Mon, 16 Dec 2013 09:02:06 +0100 Subject: [TYPO3-dev] [Typo3-dev] Paypal Payments In-Reply-To: References: Message-ID: Hi, >> 1) I don't have to maintain the extensions (there is one for paypal and >> another one to manage groups). Recently and comprehensibly TER policies >> for publishing have been restricted for quality insurance. >> >> 2) one of the extensions is heavily linked to seminars( for example it >> accesses the seminars tables to know the group to be subscribed: I have >> extended seminars as well to manage a new field for defining a group for >> each course. >> >> So I don't think would be responsible to add an extension. > > Oh. it seems I missed the change to the motto of TYPO3: > > TYPO3 - Inspiring people NOT to share > > :( There's a difference between "not sharing" and "not publishing something that is not meant as being reused as-this". It would be good to publish the work, together with quick note on how to extend EXT:seminars to some public repository such as github, this way, others may benefit from the work as "somewhere to start". But I fully understand Ivano not willing to add "highly customized personal extension" to TER because there is no point into feeding TER with useless extensions (in the sense of "cannot be reused as-this"). Kind regards -- Xavier Perseguers Release Manager TYPO3 4.6 TYPO3 .... inspiring people to share! Get involved: http://typo3.org From luberti at archicoop.it Mon Dec 16 11:17:46 2013 From: luberti at archicoop.it (Ivano Luberti) Date: Mon, 16 Dec 2013 11:17:46 +0100 Subject: [TYPO3-dev] [Typo3-dev] Paypal Payments In-Reply-To: References: Message-ID: Thank you Xavier, you get my point, that nonetheless was inspired from some I will consider publishing the extension on a service like the one you mention. Il 16/12/2013 09:02, Xavier Perseguers ha scritto: > Hi, > >>> 1) I don't have to maintain the extensions (there is one for paypal and >>> another one to manage groups). Recently and comprehensibly TER policies >>> for publishing have been restricted for quality insurance. >>> >>> 2) one of the extensions is heavily linked to seminars( for example it >>> accesses the seminars tables to know the group to be subscribed: I have >>> extended seminars as well to manage a new field for defining a group for >>> each course. >>> >>> So I don't think would be responsible to add an extension. >> Oh. it seems I missed the change to the motto of TYPO3: >> >> TYPO3 - Inspiring people NOT to share >> >> :( > There's a difference between "not sharing" and "not publishing something > that is not meant as being reused as-this". > > It would be good to publish the work, together with quick note on how to > extend EXT:seminars to some public repository such as github, this way, > others may benefit from the work as "somewhere to start". > > But I fully understand Ivano not willing to add "highly customized > personal extension" to TER because there is no point into feeding TER > with useless extensions (in the sense of "cannot be reused as-this"). > > Kind regards > -- ================================================== dott. Ivano Mario Luberti Archimede Informatica societa' cooperativa a r. l. Sede Operativa Via Gereschi 36 - 56126- Pisa tel.: +39-050- 580959 tel/fax: +39-050-9711344 web: www.archicoop.it ================================================== From kraft at webconsulting.at Mon Dec 16 17:12:21 2013 From: kraft at webconsulting.at (Bernhard Kraft) Date: Mon, 16 Dec 2013 17:12:21 +0100 Subject: [TYPO3-dev] Unit tests Message-ID: Hello, When writing unit tests for the core or extensions I came across the following problem: How should I handle obvious errors/problems with current source. When a method is returning some result which does not conform to the methods description and/or intention. How should this get handled in a unit test? Is it possible to mark this as some kind of "todo". I mean it IS no error as it is currently in the source and working. But for some special input it will generate an error or at least not behave correctly. So the unit test should recognize this and generate some kind of warning or "todo" message. Whenever the method gets refactored such issues should get handled. An example: The method "extractHyperLinks" of direct_mail: When passing a link like: -------------------------- -------------------------- to the method it will return an array with quotes => '' Altough the "href" attribute obviously has quotes around it so quotes => '"' should get returned. This is related to the internal coding of "extractHyperLinks". So how should this get handled in an unit test? Of course a bug report should get created for every such issue but the unit test should still run through. greetings, Bernhard From typo3 at t3node.com Mon Dec 16 18:10:07 2013 From: typo3 at t3node.com (=?UTF-8?B?U3RlZmZlbiBNw7xsbGVy?=) Date: Mon, 16 Dec 2013 18:10:07 +0100 Subject: [TYPO3-dev] Unit tests In-Reply-To: References: Message-ID: Hi. If a unit test fails under a certain condition, I would not let it pass, as long as the condition is valid. Skipped tests have a bad smell and should be avoided. IMHO a failed test is equivalent to "@todo". If you find a condition which lets a function fail and it is not covered by the unit tests, then write a test for it. Or - if it makes sense, add the suspect to the dataprovider. Append this test to the bug report. -- cheers, Steffen Active Contributor TYPO3 CMS TYPO3 Blog: http://www.t3node.com/ Twitter: @t3node - http://twitter.com/t3node From kraft at webconsulting.at Mon Dec 16 19:36:00 2013 From: kraft at webconsulting.at (Bernhard Kraft) Date: Mon, 16 Dec 2013 19:36:00 +0100 Subject: [TYPO3-dev] Extension migration Message-ID: Hello again, Is there any suggested way for upgrade-procedures to make an extension 6.x compatible? Altough it is trivial to simply remove all require_once() statements I wonder if it makes sense to write a basic unit test for every file which checks if the class file can get included ... If not: Must be some problem like syntax error (which require_once(PATH_t3lib...) causes in 6.2. greetings, Bernhard From jigal.van.hemert at typo3.org Mon Dec 16 21:42:07 2013 From: jigal.van.hemert at typo3.org (Jigal van Hemert) Date: Mon, 16 Dec 2013 21:42:07 +0100 Subject: [TYPO3-dev] Extension migration In-Reply-To: References: Message-ID: Hi, On 16-12-2013 19:36, Bernhard Kraft wrote: > Is there any suggested way for upgrade-procedures to make an extension > 6.x compatible? > > Altough it is trivial to simply remove all require_once() statements I > wonder if it makes sense to write a basic unit test for every file which > checks if the class file can get included ... All supported versions of TYPO3 CMS support the use of the autoloader feature. For your own classes use the ext_autoload.php and simply do not use and include/require(_once) for core classes. For 6.x you can/should use the namespaced names of core classes. If you have XCLASSes use the new method. -- Jigal van Hemert TYPO3 CMS Active Contributor TYPO3 .... inspiring people to share! Get involved: typo3.org From dennis.luemkemann at gmx.de Wed Dec 18 10:34:12 2013 From: dennis.luemkemann at gmx.de (Dennis Luemkemann) Date: Wed, 18 Dec 2013 10:34:12 +0100 Subject: [TYPO3-dev] File reference using Extbase/Fluid/FAL and backwards compatibility In-Reply-To: References: Message-ID: Hello Frans & all, now I'm creating a version of my extension for 4.5, basically backporting it. Turns out that the old Fluid doesn't support treatIdAsReference in the f:image tag, which breaks my templates. What would be the right syntax for older Fluid to get the image to render? Just using gives me the file name, but without the path. How can I get the path? Thanks Dennis Am 12.11.2013 um 23:05 schrieb Dennis Luemkemann : > Frans, > >> public function getImage1() { >> return $this->image1; >> } >> Should be enough. > > that's what I thought, but then I copy&pasted the code from the wiki article. > >> And then in fluid >> >> > > adding treatIdAsReference="1" solved the problem. Somehow I must have overlooked that. > >> Maybe you can use this working example as reference. Are multiple >> references instead of one. >> https://github.com/fsaris/newsfal > > I'll have a look. > > Thank you for your help! > Dennis > > _______________________________________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev From pgallagher at electricretina.com Wed Dec 18 20:40:25 2013 From: pgallagher at electricretina.com (Peter Gallagher) Date: Wed, 18 Dec 2013 14:40:25 -0500 Subject: [TYPO3-dev] PHPUnit in TYPO3 v6.1 In-Reply-To: References: Message-ID: On 16/10/2013 3:06 PM, Peter Gallagher wrote: > On 16/10/2013 2:34 PM, Philipp Gampe wrote: >> Hi Peter, >> >> Peter Gallagher wrote: >> >>> Anyone actually running PHPUnit in V6.1 of TYPO3? >> >> The version from TER or from git? >> >> Best regards >> > I'm running TYPO3 6.1.5 and I just got the version from GIT. It shows > the same sad-face icon and nothing loads. > > I've left the extension settings at default. Turns out that PHPUnit doesn't like Backend compression. Once I turned that off it worked just fine. From steffen at gaming-inc.de Thu Dec 19 15:09:59 2013 From: steffen at gaming-inc.de (Steffen Wickham) Date: Thu, 19 Dec 2013 15:09:59 +0100 Subject: [TYPO3-dev] Extbase disrespect hidden and deleted status Message-ID: Hi guys, I'm working on a TYPO3 CMS Extension based on Extbase. I'd wrote an eID Script which initialize the TS parser itself and creates a repository object for my aggregate root. But it seems that the "hidden" and "deleted" status doesn't get respected during query, even when I set the defaultQuerySettings ("setIgnoreEnableFields(false)" and "setIncludeDeleted(false)") to the correct values. So I get the whole bunch of data including deleted and hidden one. Is there any option I missed to set? Best regards, Steffen From philippwrann at gmx.at Fri Dec 20 11:07:57 2013 From: philippwrann at gmx.at (Philipp) Date: Fri, 20 Dec 2013 11:07:57 +0100 Subject: [TYPO3-dev] =?utf-8?q?Extbase_disrespect_hidden_and_deleted_statu?= =?utf-8?q?s?= References: Message-ID: if you use an eID script a whole bunch of config will be missing, maybe extbase does not know what field flags your record as deleted. You will need to bootstrap a full frontend i think. From ernesto.baschny at typo3.org Fri Dec 20 18:35:24 2013 From: ernesto.baschny at typo3.org (Ernesto Baschny) Date: Fri, 20 Dec 2013 18:35:24 +0100 Subject: [TYPO3-dev] [TYPO3-core] Announcing TYPO3 CMS 6.2 LTS beta3 Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear TYPO3 enthusiasts, We released TYPO3 6.2 beta3 yesterday. For details about the release, please read: https://typo3.org/news/article/typo3-cms-62-lts-beta3-released/ The packages can be downloaded here: http://typo3.org/download/ The MD5 Sums: c8b7ff8cf9e51fe46e0867ebc750ae15 typo3_src-6.2.0beta3.tar.gz 092df23deca99b58657cce7ddb0ad062 typo3_src-6.2.0beta3.zip Kind Regards, Ernesto - -- Ernesto Baschny TYPO3 CMS Core Developer Release Manager TYPO3 4.5 & 6.2 LTS TYPO3 .... inspiring people to share! Get involved: typo3.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlK0f9wACgkQHHDui5FfZDjaLACg8jNRfl0hrv/osMEZpu6IoSMI 4hsAnRxJ8qUQ+HVvOpZdU61GWwwJGmrE =JlFD -----END PGP SIGNATURE----- From andreas.kiessling at web.de Sun Dec 22 11:18:24 2013 From: andreas.kiessling at web.de (Andreas Kiessling) Date: Sun, 22 Dec 2013 11:18:24 +0100 Subject: [TYPO3-dev] Configure ordering of displayed extension tables in list module in 6.x Message-ID: Hi, with the "old way" of registering extension tables in ext_tables.php, you were able to influence the order in which they appeared in the list module. Since all TCA setup now goes to "Extension"/Configuration/TCA/"tablename".php, the order is just alphabetic. I'd like to move the most used tables to the top of the list. With translated labels for the tables, the alphabetic ordering isn't visible to a lot of backend users anyway. Splitting the tables over several sysfolders also isn't a solution, it just complicates the setup (which records should be shown for relations, storage pages for extbase etc.) Is there any way to reorder the tables? Regards, Andreas From wenzel at webfox03.de Sun Dec 22 18:55:44 2013 From: wenzel at webfox03.de (Dirk Wenzel) Date: Sun, 22 Dec 2013 18:55:44 +0100 Subject: [TYPO3-dev] Extbase disrespect hidden and deleted status In-Reply-To: References: Message-ID: Hi, today I asked quite the same question on the typo3v4mvc mailing list. @Philipp: I think the main goal of the eID script is to avoid loading the frontend. I guess the 'enable fields settings' are not being respected when not in frontend context. There should be a way to detect this and adjust the query. I just couldn't figure out how. Cheers Dirk Am 20.12.13 11:07, schrieb Philipp: > if you use an eID script a whole bunch of config will be missing, maybe > extbase does not know what field flags your record as deleted. > You will need to bootstrap a full frontend i think. From typo3 at mbh-web.de Mon Dec 23 14:16:45 2013 From: typo3 at mbh-web.de (Marc Bastian Heinrichs) Date: Mon, 23 Dec 2013 14:16:45 +0100 Subject: [TYPO3-dev] Extbase disrespect hidden and deleted status In-Reply-To: References: Message-ID: Hey, jep, eID scripts are for avoiding loading the frontend. But you are doing frontend requests, so you need a frontend environment to make TYPO3 and Extbase/Fluid work correct. I would suggest to use a own page type to call the ajax actions of your extbase plugins instead of building a frontend environment on your own in the eID script. Best Marc Bastian Am 22.12.2013 18:55, schrieb Dirk Wenzel: > Hi, > today I asked quite the same question on the typo3v4mvc mailing list. > > @Philipp: I think the main goal of the eID script is to avoid loading > the frontend. > > I guess the 'enable fields settings' are not being respected when not in > frontend context. There should be a way to detect this and adjust the > query. I just couldn't figure out how. > > Cheers Dirk > > Am 20.12.13 11:07, schrieb Philipp: >> if you use an eID script a whole bunch of config will be missing, maybe >> extbase does not know what field flags your record as deleted. >> You will need to bootstrap a full frontend i think. From steffen.gebert at typo3.org Mon Dec 30 13:39:14 2013 From: steffen.gebert at typo3.org (Steffen Gebert) Date: Mon, 30 Dec 2013 13:39:14 +0100 Subject: [TYPO3-dev] Including email addresses of reviewers in commits Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, like since the beginning of our Gerrit history, we have a patch [1] in our custom Gerrit build included that removes the email address of the reviewers from the commits made by Gerrit (see e.g. in [2] the Reviewed-By lines). To my knowledge this was added (removed) because some people complained that their email addresses are published in the commit messages. However, starting with Gerrit 2.8 (released ~2 months ago), we wouldn't need custom Gerrit builds anymore, if we could also get rid of this customization. Thus I suggest do also drop this patch and just include the mail addresses (like it is also done for the Author/Committer attributes). Is there a majority that is NOT happy with including them? Thanks for your feedback! Kind regards Steffen P.S: I have no ETA for a Gerrit 2.8 upgrade, but want to have this issue negotiated in advance. Gerrit 2.8 brings one major change with what I'm personally not so happy with (the new Change Screen UI, which is however optional). As they also switched the build system (from Maven to Buck), this could be a good opportunity, if we don't need to use the new build system at all. - -- [1] https://github.com/TYPO3-infrastructure/gerrit/commit/6f1df910e6ff169fc29642d19785683b3b866a3c [2] https://git.typo3.org/Packages/TYPO3.CMS.git/commit/f8fdcea7949a5c71f6078f7dda76f08881f56c01 Steffen Gebert TYPO3 Server Administration Team Member TYPO3 .... inspiring people to share! Get involved: http://typo3.org My wish list: https://www.amazon.de/registry/wishlist/922E3JYSQ7CV/ref=cm_wl_sb_v?sort=priority -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSwWlyAAoJEIskG/rSlyw4qNIIAMXNFRQnT7S/P1UNWGWlx9Sm fx1w7FhUiH3zY42DoBnD2pJJDSkh58kezM/Lkaac+UUd5pRi+uqwc5InQIOws372 VgAqm1b3/3zlQGvKZbhW5Gdxs+/HyDl9/8i7gmNfJ9VIE0bh+yA3p6TstZnDbgr2 b4UHkOgB2oR5Mzw8ESYgsrIHoFjt+JzMiBZi4QQx5dxQJx6oO7uEXroTMphw7yZl GdmZajUrF88OHcQQltmoRD6AQ/H2lQfOEBM7d/AR1+8ap/U1iJnT4xPKYhhm6rUf h+UlUAC841uZDU2zWJXtKXnaLMs62kYE6ALhN+AZTdvNG9bZEAaaxTo2Oii7tu4= =haJ7 -----END PGP SIGNATURE----- From ernesto.baschny at typo3.org Mon Dec 30 17:33:39 2013 From: ernesto.baschny at typo3.org (Ernesto Baschny) Date: Mon, 30 Dec 2013 17:33:39 +0100 Subject: [TYPO3-dev] Including email addresses of reviewers in commits In-Reply-To: References: Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Steffen, Steffen Gebert schrieb am 30.12.2013 13:39: > like since the beginning of our Gerrit history, we have a patch [1] > in our custom Gerrit build included that removes the email address > of the reviewers from the commits made by Gerrit (see e.g. in [2] > the Reviewed-By lines). > > To my knowledge this was added (removed) because some people > complained that their email addresses are published in the commit > messages. > > However, starting with Gerrit 2.8 (released ~2 months ago), we > wouldn't need custom Gerrit builds anymore, if we could also get > rid of this customization. > > Thus I suggest do also drop this patch and just include the mail > addresses (like it is also done for the Author/Committer > attributes). > > Is there a majority that is NOT happy with including them? I personally have no problem with it, since my email is visible in so many places already. But I see a difference to the commiter/author: The author/commiter are the ones that we might need to contact in case of some trouble (i.e. licensing, copyright, patent, etc...), while we will never need to contact the Reviewers and Testers. So there is no gain in having this information disclosed in the commit message. But, since this eases future deployment and "streamlines" our infrastructure by using the original Gerrit Code, I would endorse changing that. To make that clear to everyone using our infrastructure, we should add a disclaimer somewhere when registering on typo3.org (or when using Gerrit?). Currently, when you "sign in" at typo3.org it will only display the register form in the popup, without any further information. After clicking around, you can find this page: http://typo3.org/my-account/sign-up/ This text is too short, old and misleading ("Email addresses are always spam-protected, so don't worry about spam too much"). The email addresses are already shown at forge.typo3.org without any "spam protection". So I would suggest the editorial team to rephrase this a bit and maybe streamline this registration process a bit (with more explanations). > P.S: I have no ETA for a Gerrit 2.8 upgrade, but want to have this > issue negotiated in advance. Gerrit 2.8 brings one major change > with what I'm personally not so happy with (the new Change Screen > UI, which is however optional). As they also switched the build > system (from Maven to Buck), this could be a good opportunity, if > we don't need to use the new build system at all. Makes sense, and I am glad the server team is doing such an amazing job in keeping the services runing and up-to-date as much as it is possible with the limited resources. Thanks! Cheers, Ernesto - -- Ernesto Baschny TYPO3 CMS Core Developer Release Manager TYPO3 4.5 & 6.2 LTS TYPO3 .... inspiring people to share! Get involved: typo3.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: GnuPT 2.6.2.1 by EQUIPMENTE.DE Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLBoGMACgkQHHDui5FfZDigjwCdFEJTfEeQMLCps02U8k4OPHn0 OSoAn0fg+FhIbhfK7w+Cr+b8x/GM8Pku =VWB1 -----END PGP SIGNATURE----- From helmut.hummel at typo3.org Mon Dec 30 19:15:16 2013 From: helmut.hummel at typo3.org (Helmut Hummel) Date: Mon, 30 Dec 2013 19:15:16 +0100 Subject: [TYPO3-dev] Including email addresses of reviewers in commits In-Reply-To: References: Message-ID: Hi! I'm very much for removing this (last) customisation as it does not really improve anything. On 30.12.13 17:33, Ernesto Baschny wrote: > I personally have no problem with it, since my email is visible in so > many places already. Same here! > But I see a difference to the commiter/author: The author/commiter are > the ones that we might need to contact in case of some trouble (i.e. > licensing, copyright, patent, etc...), while we will never need to > contact the Reviewers and Testers. So there is no gain in having this > information disclosed in the commit message. The email address is pretty much discosed once participating on Gerrit (like it is when participating on a mailing list or newsgroup). Picking the example commit[1] You can find the review URL in the commit message[2] [1]https://git.typo3.org/Packages/TYPO3.CMS.git/commit/f8fdcea7949a5c71f6078f7dda76f08881f56c01 [2]https://review.typo3.org/25636 There you can click on *any* reviewer in the list to see the email address. So "hiding" the email address from the commit message, at best obfuscates the fact that the email address is disclosed on Gerrit. > To make that clear to everyone using our infrastructure, we should add > a disclaimer somewhere when registering on typo3.org (or when using > Gerrit?). It might not be as apparent like when participating on a mailing list, but it is quite logical that your email address is disclosed when using a tool which is based on git (which needs an email address as committer identifier). > Currently, when you "sign in" at typo3.org it will only display the > register form in the popup, without any further information. After > clicking around, you can find this page: > > http://typo3.org/my-account/sign-up/ > > This text is too short, old and misleading ("Email addresses are > always spam-protected, so don't worry about spam too much"). But of course adding hints about that fact in a prominent place like this will not harm. Kind regards, Helmut -- Helmut Hummel Release Manager TYPO3 6.0 TYPO3 Core Developer, TYPO3 Security Team Member TYPO3 .... inspiring people to share! Get involved: typo3.org