From me at henjohoeksma.nl Fri Feb 1 05:54:03 2013 From: me at henjohoeksma.nl (Henjo Hoeksma | Stylence) Date: Fri, 1 Feb 2013 05:54:03 +0100 Subject: [TYPO3-dev] FAL in an Extbase 6.0 extension... but how?! In-Reply-To: References: Message-ID: Hi both, thanks for sharing your insights. I need to be working on this asap, so I might give some insights on my approach when I get there ;-) Kind regards, Henjo Problems are small because we learned how to deal with them. Problems are big because we need to learn how to deal with them. On Thu, Jan 31, 2013 at 8:39 PM, Andreas Kiessling wrote: > Hi, > > i used a different approach to render images/files (for read-only access): > > > > > lib.singleImage = FILES > lib.singleImage{ > references { > table = your_table > uid.field = uid > fieldName = your_field > } > > renderObj = COA > renderObj { > 10 = IMAGE > 10 { > file.import.data = file:current:publicUrl > file.maxW = 281 > altText.data = file:current:alternative > titleText.data = file:current:title > } > } > } > > > The only real "problems" i encountered were: > > - if you need to support multilanguage, add something like this to your > model, because .uid always is always set to the one from default language: > > /** > * Returns the real uid for the record to use with FAL TS > * > * @return \integer > */ > public function getRealUid() { > return ($this->_localizedUid ? $this->_localizedUid : $this->uid); > } > and pass uid: model.realUid from the ViewHelper > > - I tried to pass a whole "news" model to the cObject ViewHelper and got > stuck with some weird DateTime conversion/mapping errors, so i went for > the uid due to lack of time to investigate further. > > - probably not working with workspaces (luckily i did not need that > right now) > > > Have a look at tt_content.uploads.20 for a lot of examples (or the TS > documentation > > http://docs.typo3.org/typo3cms/TyposcriptReference/ContentObjects/Files/Index.html > ) and ContentObjectRenderer->getFileDataKey for possible fields to use > (or just use the columns like in the db, e.g. if you extend > sys_file_reference) > > HTH, > Andreas > _______________________________________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev > From adrien.crivelli at gmail.com Sat Feb 2 07:01:35 2013 From: adrien.crivelli at gmail.com (Adrien Crivelli) Date: Sat, 2 Feb 2013 15:01:35 +0900 Subject: [TYPO3-dev] PHP Framework Interop Group and coding standards In-Reply-To: References: Message-ID: Thanks for the pointers. I couldn't find anything especially interesting though, but that's ok :P I agree with you for space VS tabs. Nowadays I use tabs, but I am willing to change (again) for the sake of following standards. However you have a very good point with invalidating existing patches. Luckily this is not an issue for my own projects, but I understand it might be slightly more complex for TYPO3. Cheers, Adrien On 30 January 2013 03:30, Philipp Gampe wrote: > Hi Adrien, > > Adrien Crivelli wrote: > > > Was it ever considered for TYPO3 6.0 to both request membership and apply > > their standards ? If so, what happened ? Is there any publicly available > > discussion about that topic, on mailing list or anywhere else ? > > If anything is public, then on the typo3.teams.core list. > > However we discussed that in the past and we will follow the PSR where it > makes sense. > For example PSR-2 requires to use spaces instead of tabs like TYPO3 CMS > does. I never found a good argument for spaces and I guess we will not > change the TYPO3 source, because this would make all pending patches to > raise conflicts. > > Maybe you find some information in the code sniffer team: > http://forge.typo3.org/projects/team-php_codesniffer > > We discussed some of this at the code sprint in Linz: > http://typo3.org/news/article/typo3-qa-code-sprint-linz-2012/ > > Best regards > -- > Philipp Gampe ? PGP-Key 0AD96065 ? TYPO3 UG Bonn/K?ln > Documentation ? linkvalidator > TYPO3 .... inspiring people to share! > > _______________________________________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev > From adrien.crivelli at gmail.com Sat Feb 2 07:23:12 2013 From: adrien.crivelli at gmail.com (Adrien Crivelli) Date: Sat, 2 Feb 2013 15:23:12 +0900 Subject: [TYPO3-dev] [TYPO3-ect] Announcing TER cleanup process In-Reply-To: References: Message-ID: Hello, Was it ever considered to change the publishing workflow of extension ? Using svn/git tags seem to be much simpler for developers. And, most importantly, it would avoid non-synchronized versionning between actual code and what is in TER. De-synchronization can easily happen if developer do not commit after TER upload (and the automatic version incrementation that happens during that process). A repository-based TER, would ensure that source code (and its very interesting history) is publicly available. And thus make it easier to manage third-party extension via svn/git. Also, it may (or not ?) simplify TYPO3 server infrastructure if it only needs to pull from its own repositories instead of accepting upload from anywhere. This could also make it easier to link TER extensions to their forge project and/or repositories. Making the whole system much more transparent for power-users. To sum up, what I hope for is something similar to what was done recently for jQuery Pugins: http://plugins.jquery.com/docs/publish/ Cheers, Adrien On 30 January 2013 08:32, Henjo Hoeksma | Stylence wrote: > Seriously - I am thrilled to read this! Great and bold steps! > > Kind regards, > > Henjo > > Problems are small because we learned how to deal with them. > Problems are big because we need to learn how to deal with them. > > > On Tue, Jan 29, 2013 at 10:42 PM, Jigal van Hemert < > jigal.van.hemert at typo3.org> wrote: > > > TER "cleanup" > > ============= > > > > Everybody recognizes this situation: you're looking for an extension with > > a certain functionality and after you've installed it all kinds of errors > > appear about missing functions or even worse, you only see a blank page. > > Further investigation shows that the extension isn't compatible with your > > TYPO3 version. > > > > For a long time extensions can set the TYPO3 version(s) they are > > compatible with. Unfortunately not many extension authors use that > setting. > > You could take a look at the date of publication, but even that won't be > a > > sure sign. > > > > The plans > > --------- > > To reduce the chances for such problems some things will change: > > > > 1. the dependency setting in an extension for a TYPO3 version (or a range > > of versions) will become mandatory; this means that extensions without a > > dependency for one of the currently supported core versions will be > > rejected during the upload. > > > > 2. extensions without a TYPO3 dependency setting or with a dependency for > > none of the current TYPO3 versions will be marked as "outdated". > > > > 3. "outdated" extensions will not show up at first in the TER search > > results; you can activate a switch to also show "outdated" extensions. > > > > 4. "outdated" extensions will be clearly marked in the Extension Manager. > > > > The schedule > > ------------ > > - Announcements in as many places as possible (end of January) > > > > - Mails to extension authors to notify them of the changes (February) > > > > - Patches for TYPO3 Extension Manager to display "outdated" extensions > > differently (beginning of February) > > > > - Rejecting extensions without valid dependency during upload (August > 1st, > > 2013) > > > > - Marking extensions without (valid) dependency in TER (beginning of > > August 2013) > > > > - Hiding "outdated" extensions in TER search (beginning of August 2013) > > > > Definition of an "outdated" extension > > ------------------------------**------- > > An extension is called "outdated" if it has set a dependency for TYPO3, > > but none of the versions it depends on is actively maintained. For > example: > > it has a dependency for TYPO3 4.0-4.3; all these versions are > 'end-of-life' > > and this extension is clearly not designed to work with any current TYPO3 > > installation. > > > > Because a lot of extensions don't have a dependency set, we have to > expand > > the definition a bit in the beginning: extensions which were uploaded > > before the release of the oldest, currently maintained TYPO3 version are > > also "outdated". If an extension was uploaded before the release of TYPO3 > > 4.5 it was obviously not tested with that version. > > > > > > And in the (near) future... > > > > Shortly we will have a 'gap' in the range of supported versions: 4.5 > > (LTS), 4.7, 6.0. This will mean that the check will be a bit more > > complicated, but the basic rule will remain the same: > > check if there is a match between the range of TYPO3 versions set in the > > dependency property and the currently maintained versions. > > > > Implications for integrators > > ---------------------------- > > If you search for extensions in TER after August 1st, 2013 these > > "outdated" extensions will not show up immediately. Only if you activate > > the option to include "outdated" extensions they will be included in the > > results. It is still possible to download these extensions, but you need > > extra effort. > > > > If you search in the Extension Manager in the list of extensions in TER > > the "outdated" extensions will not show up. > > > > If you try to install an "outdated" extension (uploading it in the EM) > the > > behavior will depend on whether the TYPO3 dependency has been set or not > in > > the extension. This is the current situation already. > > > > If an extension you currently use is marked as "outdated" there is really > > no problem. It works for you, but it might not work in newer TYPO3 > > versions. You could ask the extension author to update the extension. > > > > Please note that also not-"outdated" extensions might fail with a new > > TYPO3 core version. If the extension is compatible with TYPO3 4.5 it is > not > > "outdated", but it may be incompatible with TYPO3 4.7 you want to upgrade > > to. Checks to see if your installation is upgrade-ready might be a nice > > feature for a new tool. > > > > Implications for extension authors > > ------------------------------**---- > > If you try to upload an extension without a dependency for TYPO3 or with > a > > dependency which is outside the range of currently supported TYPO3 > versions > > your upload will be rejected and an error message will be shown. Simply > add > > to ext_emconf.php a dependency for the version(s) you tested the > extension > > with: > > > > 'constraints' => array( > > 'depends' => array( > > 'typo3' => '4.5.0-4.7.99', > > ), > > ), > > > > You can set the minimum for a version of TYPO3 which is not supported > > anymore, but then the maximum must be within the supported range. You > > cannot set a maximum outside the range of supported versions. > > > > > > What happens with "outdated" extensions and their keys? > > > > Really, nothing much. They will remain in TER, but not as visible as they > > were before. The extension keys will still remain with their owners. > > > > If you upload a new version of an "outdated" extension it will appear > > again in the search results, because the dependency is set for one or > more > > of the currently maintained TYPO3 versions. > > > > Security issues and "outdated" extensions > > ------------------------------**----------- > > The security team will give more attention to extensions which are > > actively maintained. If a security issue is reported for an "outdated" > > extension the normal procedure will be followed. > > > > Future developments > > ------------------- > > The information about the TYPO3 versions an extension will work with can > > be used for other features of the TER and the Extension Manager. > > > > In the future it will be possible to search for compatibility with a > > specific TYPO3 version. > > > > It would also be possible to show in the EM the list of extensions in the > > TER which are compatible with the installed TYPO3 version. > > > > A check to see if all installed extensions are compatible with a new > TYPO3 > > version before you perform the upgrade would also be possible. > > > > More information > > ---------------- > > The Extension Coordination Team [1] handles this operation. See [2] for > > the wiki information. There is a mailing list / newsgroup > > "typo3.teams.extension-**coordination" to ask questions and discuss the > > procedures. > > > > [1] http://forge.typo3.org/**projects/team-ect< > http://forge.typo3.org/projects/team-ect> > > [2] http://forge.typo3.org/**projects/team-ect/wiki/TER_**Clean-up< > http://forge.typo3.org/projects/team-ect/wiki/TER_Clean-up> > > > > -- > > Jigal van Hemert > > TYPO3 CMS Core Team member > > Extension Coordination Team Leader > > > > TYPO3 .... inspiring people to share! > > Get involved: typo3.org > > ______________________________**_________________ > > TYPO3-dev mailing list > > TYPO3-dev at lists.typo3.org > > http://lists.typo3.org/cgi-**bin/mailman/listinfo/typo3-dev< > 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 rowild at gmx.net Sat Feb 2 12:37:24 2013 From: rowild at gmx.net (Robert Wildling) Date: Sat, 02 Feb 2013 12:37:24 +0100 Subject: [TYPO3-dev] Old ###Template### function in extbase TCA? Message-ID: Hi, A question for the developers of Extbase and fluid: when generating an m:n relation in an extbase plugin, there is still a marker in the tca that has the old template format: ###CURRENT_PID### I would like to know why this is the way it is? Why no fluid? Why duplication of functionality? And - since it fits the topic: is there any chance to define something else than ###CURRENT_PID###? Sth like ###STORAGE_PID### which is declared in some TypoScript (UserTS? PageTS?) and therefore enabling a "static" sysfolder, which would be really helpful with IRRE? (I am on TYPO3 4.6) Thanks! Cheers, Robert From philipp.gampe at typo3.org Sat Feb 2 15:09:39 2013 From: philipp.gampe at typo3.org (Philipp Gampe) Date: Sat, 02 Feb 2013 15:09:39 +0100 Subject: [TYPO3-dev] Old ###Template### function in extbase TCA? References: Message-ID: Hi Robert, Robert Wildling wrote: > A question for the developers of Extbase and fluid: when generating an > m:n relation in an extbase plugin, there is still a marker in the tca > that has the old template format: ###CURRENT_PID### This is not the old format as there is no other format for TCA. And this has nothing to do with frontend markers. > I would like to know why this is the way it is? Why no fluid? Why > duplication of functionality? It is not a duplication, but a simple marker ... other projects use other formats, this is just to distinguish the marker from the other parts of the string. > And - since it fits the topic: is there any chance to define something > else than ###CURRENT_PID###? Sth like ###STORAGE_PID### which is > declared in some TypoScript (UserTS? PageTS?) and therefore enabling a > "static" sysfolder, which would be really helpful with IRRE? Please check the TCA documentation: http://docs.typo3.org/typo3cms/TCAReference/Reference/Columns/Select/Index.html Scroll down to foreign_table_where. Best regards -- Philipp Gampe ? PGP-Key 0AD96065 ? TYPO3 UG Bonn/K?ln Documentation ? linkvalidator TYPO3 .... inspiring people to share! From typo3ml at schams.net Sun Feb 3 03:01:16 2013 From: typo3ml at schams.net (Michael) Date: Sun, 03 Feb 2013 13:01:16 +1100 Subject: [TYPO3-dev] Statistics: TYPO3 extensions without a TYPO3 dependency setting (Feb/2013) Message-ID: Hi TYPO3 extension developers! As officially announced [1] in January 2013, a TER cleanup process is currently in progress. In the near future, TYPO3 extensions without a TYPO3 dependency setting (or with a dependency for none of the current TYPO3 versions) will be marked as "outdated". Therefore, extension developers are urged to update their extensions and define a dependency to the TYPO3 versions they tested their code with. The statistics below show the numbers of TYPO3 extensions in the TER and their current TYPO3 dependency settings. Only the last version of extensions has been taken into account for these figures. *02 February 2013* Total number of TYPO3 extensions in the TER: 5835 TYPO3 extensions without a TYPO3 dependency: 4657 (79.8% of all extensions) TYPO3 extensions, last updated 2012/2013: 1050 TYPO3 extensions, last updated 2012/2013 and without a (valid) TYPO3 dependency: 919 TYPO3 extensions, last updated 2012/2013 and with a min or max dependency to TYPO3 version 4.x or 6.x: 124 Further background information, a schedule and the implications of the "TER cleanup" initiative and TYPO3 extensions without a valid dependency settings are explained in [1] and discussed in the TYPO3 Extension Coordination Team mailing list [2] as well as in the Wiki [3]. Cheers Michael [1] http://typo3.org/news/article/announcing-ter-cleanup-process/ [2] http://lists.typo3.org/pipermail/typo3-team-extension-coordination/ [3] http://forge.typo3.org/projects/team-ect/wiki/TER_Clean-up From jigal.van.hemert at typo3.org Sun Feb 3 09:47:15 2013 From: jigal.van.hemert at typo3.org (Jigal van Hemert) Date: Sun, 03 Feb 2013 09:47:15 +0100 Subject: [TYPO3-dev] [TYPO3-ect] Announcing TER cleanup process In-Reply-To: References: Message-ID: Hi, On 2-2-2013 7:23, Adrien Crivelli wrote: > Was it ever considered to change the publishing workflow of extension ? > Using svn/git tags seem to be much simpler for developers. This is a different topic. The consequences are that it would become mandatory for extension developers to use the typo3.org infrastructure for version management. Some extension authors want or need to use their own systems (for example because new versions go to sponsors first and with some delay to TER, or because they want to use github, or because the company wants to use their own svn/git server, ...). Forcing to use forge seemed to be too restrictive. -- Jigal van Hemert TYPO3 Core Team member TYPO3 .... inspiring people to share! Get involved: typo3.org From tolleiv.nietsch at typo3.org Sun Feb 3 12:20:05 2013 From: tolleiv.nietsch at typo3.org (Tolleiv Nietsch) Date: Sun, 03 Feb 2013 12:20:05 +0100 Subject: [TYPO3-dev] [TYPO3-ect] Announcing TER cleanup process In-Reply-To: References: Message-ID: Hi, Adrien Crivelli schrieb: > > Was it ever considered to change the publishing workflow of extension ? > Using svn/git tags seem to be much simpler for developers. most complicated part related to the TER stuff is not the feature-wishes but the man-power behind that tool. The T3O team is happy to have at least one motivated enthusiast (Thomas) who's able to make some improvements in the tool. Pushing out large features like the one you described would require a real team behind it (which we don't have at the moment). If you've ambitions to help with the TER feel free to get in contact with Thomas L?ffler, Ben v. Ende or me. Cheers, Tolleiv -- Tolleiv Nietsch TYPO3 Core Developer TYPO3 .... inspiring people to share! Get involved: typo3.org From philipp.gampe at typo3.org Sun Feb 3 15:11:17 2013 From: philipp.gampe at typo3.org (Philipp Gampe) Date: Sun, 03 Feb 2013 15:11:17 +0100 Subject: [TYPO3-dev] [TYPO3-ect] Announcing TER cleanup process References: Message-ID: Hi Jigal, Jigal van Hemert wrote: > Forcing to use forge seemed to be too restrictive. No need to restrict git usage to forge. You just need the URL to the repo and then you can do a "git ls-remote -t" to get all tags. Use it like so: git ls-remote -t http://git.typo3.org/TYPO3v4/Core.git The more interesting question would be how to package the version? Do a checkout and delete the .git and then use this as package? Or refactor the TER to use URLs too (like composer); we should use composer then. Best regards -- Philipp Gampe ? PGP-Key 0AD96065 ? TYPO3 UG Bonn/K?ln Documentation ? linkvalidator TYPO3 .... inspiring people to share! From tolleiv.nietsch at typo3.org Sun Feb 3 15:16:05 2013 From: tolleiv.nietsch at typo3.org (Tolleiv Nietsch) Date: Sun, 03 Feb 2013 15:16:05 +0100 Subject: [TYPO3-dev] [TYPO3-ect] Announcing TER cleanup process In-Reply-To: References: Message-ID: Hi, we'll have a "Extension" related Code sprint under the umbrella of the 6.1 release. This sprint will hopefully answer these questions ... feel free to join the sprint or the TER team ;) Cheers. Philipp Gampe schrieb: > Hi Jigal, > > Jigal van Hemert wrote: > >> Forcing to use forge seemed to be too restrictive. > > No need to restrict git usage to forge. You just need the URL to the repo > and then you can do a "git ls-remote -t" to get all tags. > > Use it like so: > git ls-remote -t http://git.typo3.org/TYPO3v4/Core.git > > The more interesting question would be how to package the version? > Do a checkout and delete the .git and then use this as package? > Or refactor the TER to use URLs too (like composer); we should use composer > then. > > Best regards -- Tolleiv Nietsch TYPO3 Core Developer TYPO3 .... inspiring people to share! Get involved: typo3.org From philipp.gampe at typo3.org Sun Feb 3 16:10:54 2013 From: philipp.gampe at typo3.org (Philipp Gampe) Date: Sun, 03 Feb 2013 16:10:54 +0100 Subject: [TYPO3-dev] [TYPO3-ect] Announcing TER cleanup process References: Message-ID: Hi Tolleiv, Tolleiv Nietsch wrote: > we'll have a "Extension" related Code sprint under the umbrella of the > 6.1 release. This sprint will hopefully answer these questions ... feel > free to join the sprint or the TER team ;) I would gladly join the sprint. I plan to put some love into the EM the coming weeks, because there are many small glitches, but the bigger task should be discussed beforehand. Is it already planned? p.s.: Ben contacted me in January if I want to Host a sprint for EM, but I have no location, nor did I had the time (and planning ahead) back then. So count me in for TER/EM if it somehow fits into my schedule. Best regards -- Philipp Gampe ? PGP-Key 0AD96065 ? TYPO3 UG Bonn/K?ln Documentation ? linkvalidator TYPO3 .... inspiring people to share! From rik at metmeer.nl Mon Feb 4 10:16:38 2013 From: rik at metmeer.nl (Rik Willems) Date: Mon, 04 Feb 2013 10:16:38 +0100 Subject: [TYPO3-dev] Locallang labels with a dot Message-ID: Dear all, For a project I came across an extension that used dots (.) in the locallang labels. This meant I could not override the values through Typoscript setup. I assume this is because of the Typoscript to array parsing that is done. I think there are many more extension that have this problem besides this one extension so I thought it'd be worth a post here. How do we best handle this? I think there are generally two options: 1) Don't just dots in the locallang labels. 2) Don't parse the _LOCAL_LANG.xx part of Typoscript setup to an array but just as is. (1) will change nothing in the short run. (2) will change how Typoscript is being parse for ages. What do you think? Cheers Rik From jigal.van.hemert at typo3.org Mon Feb 4 10:41:29 2013 From: jigal.van.hemert at typo3.org (Jigal van Hemert) Date: Mon, 04 Feb 2013 10:41:29 +0100 Subject: [TYPO3-dev] Locallang labels with a dot In-Reply-To: References: Message-ID: Hi, On 4-2-2013 10:16, Rik Willems wrote: > For a project I came across an extension that used dots (.) in the > locallang labels. This meant I could not override the values through > Typoscript setup. I assume this is because of the Typoscript to array > parsing that is done. Yes. locallang labels shouldn't contain dots. If you need to override them you can use the locallangXMLOverride feature describe in [1] . [1] http://xavier.perseguers.ch/en/tutorials/typo3/articles/managing-localization-files.html#c962 -- Jigal van Hemert TYPO3 Core Team member TYPO3 .... inspiring people to share! Get involved: typo3.org From lolli at schwarzbu.ch Tue Feb 5 01:14:18 2013 From: lolli at schwarzbu.ch (Christian Kuhn) Date: Tue, 05 Feb 2013 01:14:18 +0100 Subject: [TYPO3-dev] [TYPO3-english] ImageMagick 6.8.0-10 2012-12-16 Q16 + TYPO3 V6.X too dark images In-Reply-To: References: Message-ID: Hey, cross posting to dev-list, please follow-up there. On 02/05/2013 12:08 AM, Philipp Gampe wrote: >> Is anybody aware of the fact that using the bleeding edge version of >> ImageMagick 6.8.0-10 (build date: 2012-12-16) with TYPO3 V6.X results >> generates too dark images? > > IM changed their API again ... :( > > There is a patch pending for this: > https://review.typo3.org/#/c/17474/ Yes. I've talked with Anja about this issue, and until now I didn't vote on it for the following reasons: * I don't like that some additional setting needs to be done to get it right again. imho, the code should handle it internally (read: take correct path by checking im version). But, if its done internally and released as bugfix, this means that all images will change during upgrading (they are technically more correct than before, but they *do* change). This might not be exactly cool for some people, especially if released as bugfix for 4.5. * We might release the patch for 6.1 only (and *maybe* 6.0), but then there will be no good choice for instances of 4.7 and below ... * If there is an additional config setting, there should be logic to at least choose some sane default during install process. I'm personally unsure on how to proceed in this case ... the current patch itself is obvious and works, but ... is it the best way to handle this API change of im? Regards Christian From tolleiv.nietsch at typo3.org Tue Feb 5 06:44:40 2013 From: tolleiv.nietsch at typo3.org (Tolleiv Nietsch) Date: Tue, 05 Feb 2013 06:44:40 +0100 Subject: [TYPO3-dev] [TYPO3-ect] Announcing TER cleanup process In-Reply-To: References: Message-ID: Hi, that's good to hear. The only "fixed" plan atm. is to make it in the AOE office somewhere in March / April. (As you see in the 6.1 meeting minutes: http://forge.typo3.org/projects/typo3v4-core/wiki/Release_Team_Meeting_2013-01-28 ) Once we discuss more details, I'll try make sure that your name is added to the list of participants. Cheers, Tolleiv Philipp Gampe schrieb: > Hi Tolleiv, > > Tolleiv Nietsch wrote: > >> we'll have a "Extension" related Code sprint under the umbrella of the >> 6.1 release. This sprint will hopefully answer these questions ... feel >> free to join the sprint or the TER team ;) > > I would gladly join the sprint. I plan to put some love into the EM the > coming weeks, because there are many small glitches, but the bigger task > should be discussed beforehand. > > Is it already planned? > > p.s.: Ben contacted me in January if I want to Host a sprint for EM, but I > have no location, nor did I had the time (and planning ahead) back then. > So count me in for TER/EM if it somehow fits into my schedule. > > Best regards -- Tolleiv Nietsch TYPO3 Core Developer TYPO3 .... inspiring people to share! Get involved: typo3.org From adrien.crivelli at gmail.com Tue Feb 5 10:19:00 2013 From: adrien.crivelli at gmail.com (Adrien Crivelli) Date: Tue, 5 Feb 2013 18:19:00 +0900 Subject: [TYPO3-dev] [TYPO3-ect] Announcing TER cleanup process In-Reply-To: References: Message-ID: Hi, I'm with you on that. Even without remote listing, git is flexible enough for developers to have a private git server (github or whatever) and only push from time to time to git.typo3.org to actually publish a version. This alternative keep it (maybe) slightly easier for TYPO3 team and flexible enough for developers. Of course, it completely ignore SVN support. But, as I stated a few times on this mailing list, I have a feeling that SVN should be dropped entirely as soon as possible. And that nobody today would start a significant enough extension without git knowledge. It does indeed increase (slightly) the barrier for newcomers. But I really don't see it as a problem, on the contrary this ensure a minimum of technical knowledge before publishing extension and so, hopefully raise the public extensions quality. If jQuery did it, I don't see why TYPO3 couldn't. Anyway, I think there are several ways to improve the current workflow. But first of all, we should decide if we want to improve it. I could help with that, if we are moving toward a git-based solution (or composer ?) Cheers, PS: this is not the first time I have "organisational/philosophical" discussion about TYPO3 ecosystem. But I feel unheard/misunderstood/ignored. And I wonder if there is a way to suggest new "feature/orientation" (in a very broad way) and to vote them. Or to somehow find out what the community think and who will finally decide what. Maybe some sort of polls ? or voted roadmap ? Basically, what is decision-making process within TYPO3 ? On 3 February 2013 23:11, Philipp Gampe wrote: > Hi Jigal, > > Jigal van Hemert wrote: > > > Forcing to use forge seemed to be too restrictive. > > No need to restrict git usage to forge. You just need the URL to the repo > and then you can do a "git ls-remote -t" to get all tags. > > Use it like so: > git ls-remote -t http://git.typo3.org/TYPO3v4/Core.git > > The more interesting question would be how to package the version? > Do a checkout and delete the .git and then use this as package? > Or refactor the TER to use URLs too (like composer); we should use composer > then. > > Best regards > -- > Philipp Gampe ? PGP-Key 0AD96065 ? TYPO3 UG Bonn/K?ln > Documentation ? linkvalidator > TYPO3 .... inspiring people to share! > > _______________________________________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev > From typo3 at kay-strobach.de Tue Feb 5 12:00:50 2013 From: typo3 at kay-strobach.de (Kay Strobach) Date: Tue, 05 Feb 2013 12:00:50 +0100 Subject: [TYPO3-dev] [TYPO3-ect] Announcing TER cleanup process In-Reply-To: References: Message-ID: Perhaps we can join forces with the jQuery team and use their genius work for the jquery plugins - i'd like to see this solved :D Am 03.02.13 12:20, schrieb Tolleiv Nietsch: > Hi, > > Adrien Crivelli schrieb: >> >> Was it ever considered to change the publishing workflow of extension ? >> Using svn/git tags seem to be much simpler for developers. > > most complicated part related to the TER stuff is not the feature-wishes > but the man-power behind that tool. The T3O team is happy to have at > least one motivated enthusiast (Thomas) who's able to make some > improvements in the tool. Pushing out large features like the one you > described would require a real team behind it (which we don't have at > the moment). > > If you've ambitions to help with the TER feel free to get in contact > with Thomas L?ffler, Ben v. Ende or me. > > Cheers, > Tolleiv > -- http://www.kay-strobach.de - Open Source Rocks TYPO3 .... inspiring people to share! Get involved: http://typo3.org Answer was useful - feel free to donate: - https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=KPM9NAV73VDF2 - https://flattr.com/profile/kaystrobach From philipp.gampe at typo3.org Tue Feb 5 13:05:13 2013 From: philipp.gampe at typo3.org (Philipp Gampe) Date: Tue, 05 Feb 2013 13:05:13 +0100 Subject: [TYPO3-dev] [TYPO3-ect] Announcing TER cleanup process References: Message-ID: Hi Adrien Crivelli, Adrien Crivelli wrote: > PS: this is not the first time I have > "organisational/philosophical" discussion about TYPO3 ecosystem. But I > feel unheard/misunderstood/ignored. And I wonder if there is a way to > suggest new "feature/orientation" (in a very broad way) and to vote them. > Or to somehow find out what the community think and who will finally > decide what. Maybe some sort of polls ? or voted roadmap ? Basically, what > is decision-making process within TYPO3 ? Discussing pros und cons in public (or sometimes in smaller cycles) and then to go ahead ;) ("Code rulez"). A solved problem counts more then a theoretical solution. Cheers -- Philipp Gampe ? PGP-Key 0AD96065 ? TYPO3 UG Bonn/K?ln Documentation ? linkvalidator TYPO3 .... inspiring people to share! From rik at actiview.nl Tue Feb 5 21:31:59 2013 From: rik at actiview.nl (Rik Willems) Date: Tue, 05 Feb 2013 21:31:59 +0100 Subject: [TYPO3-dev] Locallang labels with a dot In-Reply-To: References: Message-ID: Hi Jigal, This is a very good resource. Thanks for this link! Cheers, Rik Op 4-2-2013 10:41, Jigal van Hemert schreef: > Hi, > > On 4-2-2013 10:16, Rik Willems wrote: >> For a project I came across an extension that used dots (.) in the >> locallang labels. This meant I could not override the values through >> Typoscript setup. I assume this is because of the Typoscript to array >> parsing that is done. > > Yes. locallang labels shouldn't contain dots. > > If you need to override them you can use the locallangXMLOverride > feature describe in [1] . > > [1] > http://xavier.perseguers.ch/en/tutorials/typo3/articles/managing-localization-files.html#c962 > > From helmut.hummel at typo3.org Wed Feb 6 18:21:22 2013 From: helmut.hummel at typo3.org (Helmut Hummel) Date: Wed, 06 Feb 2013 18:21:22 +0100 Subject: [TYPO3-dev] FAL in an Extbase 6.0 extension... but how?! In-Reply-To: References: Message-ID: Hi, On 31.01.13 18:37, Anders Gissel wrote: > thanks to some helpful tips from a fellow TYPO3-freak, I was able to get > things up and running. Great you managed to get it going. Who was the "TYPO3-freak"? :) > Mind you, these are extremely dirty hacks (albeit > inside your own extension only), It is not that bad, if you skip the select query and use an API method for that as I will show below. > and once Extbase starts properly > supporting FAL (which, currently, it doesn't), you will have to change a > lot of things, at the very least in your frontend rendering. We will be working on that during the Extbase code sprint this weekend. > You'd be > wise to plan accordingly. But without further ado, here's how to use FAL > to attach a single image to a domain model object, and then retrieve the > raw data in frontend. You could use the object instead. Works fine with all the getters that do not have parameters (like getProperty). > Here's where things get tricky. Your regular domain model should > probably look something like this: > /** > * Returns the file USING HAXX0RED METHODS! PLEASE DON'T TRY THIS > AT HOME, KIDS! :) > * > * @return array $file > */ > public function getFile() { > > // Get the UID from the current image object. > $objectUid = $this->getUid(); > > // Use the UID to search sys_file_reference > $row = $GLOBALS['TYPO3_DB']->exec_SELECTgetSingleRow('uid', > 'sys_file_reference', "uid_foreign={$objectUid} AND fieldname = 'file' > AND tablenames = 'tx_myext_domain_model_image' AND deleted=0 AND hidden=0"); > if (is_array($row)) { > $fileObject = > $this->typo3FALRepository->findFileReferenceByUid($row['uid']); change this to to: $fileObject = $this->typo3FALRepository->findByRelation('', 'file', $this->getUid()); And it will be much cleaner and not so likely to break as it is a pulic API. 'file' here again is the field name defined in TCA. > $fileObjectData = $fileObject->toArray(); You can do that, but using the object directly should be fine, too. 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 invadercyg at gmail.com Wed Feb 6 20:45:12 2013 From: invadercyg at gmail.com (Anders Gissel) Date: Wed, 06 Feb 2013 20:45:12 +0100 Subject: [TYPO3-dev] FAL in an Extbase 6.0 extension... but how?! In-Reply-To: References: Message-ID: Hello Helmut, On 06-02-2013 18:21, Helmut Hummel wrote: >> thanks to some helpful tips from a fellow TYPO3-freak, I was able to get >> things up and running. > > Great you managed to get it going. Who was the "TYPO3-freak"? :) Karsten Madsen from DKM, Aarhus, Denmark. His insights into the problem got me on track to getting the TCA-update to work. My usual source of TYPO3-oracle'isms is Claus Due, but on this particular point he had no inputs. >> and once Extbase starts properly >> supporting FAL (which, currently, it doesn't), you will have to change a >> lot of things, at the very least in your frontend rendering. > > We will be working on that during the Extbase code sprint this weekend. Awesome! >> // Use the UID to search sys_file_reference >> $row = $GLOBALS['TYPO3_DB']->exec_SELECTgetSingleRow('uid', >> 'sys_file_reference', "uid_foreign={$objectUid} AND fieldname = 'file' >> AND tablenames = 'tx_myext_domain_model_image' AND deleted=0 AND >> hidden=0"); >> if (is_array($row)) { >> $fileObject = >> $this->typo3FALRepository->findFileReferenceByUid($row['uid']); > > change this to to: > > $fileObject = $this->typo3FALRepository->findByRelation(' name>', 'file', $this->getUid()); > > And it will be much cleaner and not so likely to break as it is a > pulic API. > > 'file' here again is the field name defined in TCA. Oh, nice. I'm pretty new to the game of extbase, so things like these are always a revelation to me. :-) Thanks for your pointers ? although I must confess I ended up tearing FAL out of my extension and falling back to ye olde way of doing things (namely, using /uploads/tx_whatever). It's not nearly as elegant, but it works just fine, and I can now easily handle multipart-uploads and similar through the frontend, which my users will need. :-) Best regards, Anders From invadercyg at gmail.com Wed Feb 6 21:00:00 2013 From: invadercyg at gmail.com (Anders Gissel) Date: Wed, 06 Feb 2013 21:00:00 +0100 Subject: [TYPO3-dev] Extbase 6.0 and AJAX-driven widgets Message-ID: Hey guys, I'm working on an extension in Extbase 6.0, and I've come across a peculiar problem that I can't seem to fix: whenever I use a widget in my frontend, and use it to run an AJAX-widget-request, all I get is this: *#1284793775: No widget context was found for the Ajax Widget Identifier "(long identifier goes here)". This only happens if AJAX URIs are called without including the widget on a page.* Some background info: * The entire extension was built on 6.0.1, and everything is using namespaces * The primary controller that instantiates the widget is uncached * The widget viewhelper itself has set $ajaxWidget = TRUE; * The widget controller can run its indexAction() just fine. * indexAction() then uses {f:widget.uri(ajax: 1, action: 'update')} to generate the URL for the AJAX-request * The resulting URL uses the proper page type, and has all the proper arguments. However, the request fails with the message seen above. * updateAction() has @ajax in its annotation * No closures, object storages or similar are sent along in the AJAX-request... it's just basic integers and strings all the way I have compared my code to a set of widgets written by the Almighty (that would be @Namelesscoder) that I know works on 4.7, and the only difference I can see between his code and mine is, that I'm using namespacing and running my code on 6.0.1. Any ideas? Thoughts? I feel I'm going mad here. Best regards, Anders From g4-lisz at tonarchiv.ch Thu Feb 7 11:29:50 2013 From: g4-lisz at tonarchiv.ch (g4-lisz at tonarchiv.ch) Date: Thu, 07 Feb 2013 11:29:50 +0100 Subject: [TYPO3-dev] Crawler doesn't trigger Indexing anymore Message-ID: Hi there There's a big problem on the T3 website of one of our clients: indexed_search stopped working! Crawler is filling up the queue like normal. But when the queue is processed, nothing happens. I.e. the queue entries have a result_data and process_id_completed filled in, but there is no update to the index tables at all. I tried several things: - Purging all the index tables - Re-installing indexed_search - Runnig crawler_im from CLI with -o exec None of them did solve the problem. Because all the search results are outdated, i should find a solution asap... Any help would be much appreciated! Cheers, Till From adrien.crivelli at gmail.com Fri Feb 8 04:22:54 2013 From: adrien.crivelli at gmail.com (Adrien Crivelli) Date: Fri, 8 Feb 2013 12:22:54 +0900 Subject: [TYPO3-dev] [TYPO3-ect] Announcing TER cleanup process In-Reply-To: References: Message-ID: The problem is I am not very close to TYPO3 ecosystem by any means. And, even though I have a clear vision of what I would like to change (drop svn entirely, more git/github based things), I don't feel it would be right if I force my ideas on hundreds of people who are (much) "older" than me in this community. I feel it would not be fair to apply my radical changes without a clear approval by the community. And I fail to understand how to get this approval. For instance I didn't hear about TER cleanup process until a few days ago. I have no idea who and how it was discussed. And it may be too late to change the plan now. Or is it ? Here is what I would love to have: - existing svn is readonly from today - all extensions are hosted on github, or TYPO3 git servers for a few very important one (much *less maintenance* for TYPO3 git/svn servers) - publishing extension on TER, require: - installing webhookon github - matching repository name and extension key - using semver tags for each release - downloads for any version can be served directly from github as zip file (again much *less work* for TYPO3 servers) This allow for a much more *natural workflow for developer*, and easier collaboration via github's pull request (as long as gerrit is not required, which probably is a vast majority of case for extensions). It also allow to *simplify Extension Manager* extension (dropping all code related to uploading). The only downside that I see is a total break for SVN users. But I feel it's a good time for a big change (with TYPO3 6.0 and TER cleanup). On 5 February 2013 21:05, Philipp Gampe wrote: > Hi Adrien Crivelli, > > Adrien Crivelli wrote: > > > PS: this is not the first time I have > > "organisational/philosophical" discussion about TYPO3 ecosystem. But I > > feel unheard/misunderstood/ignored. And I wonder if there is a way to > > suggest new "feature/orientation" (in a very broad way) and to vote them. > > Or to somehow find out what the community think and who will finally > > decide what. Maybe some sort of polls ? or voted roadmap ? Basically, > what > > is decision-making process within TYPO3 ? > > Discussing pros und cons in public (or sometimes in smaller cycles) and > then > to go ahead ;) ("Code rulez"). A solved problem counts more then a > theoretical solution. > > Cheers > -- > Philipp Gampe ? PGP-Key 0AD96065 ? TYPO3 UG Bonn/K?ln > Documentation ? linkvalidator > TYPO3 .... inspiring people to share! > > _______________________________________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev > From adrien.crivelli at gmail.com Fri Feb 8 04:28:40 2013 From: adrien.crivelli at gmail.com (Adrien Crivelli) Date: Fri, 8 Feb 2013 12:28:40 +0900 Subject: [TYPO3-dev] [TYPO3-ect] Announcing TER cleanup process In-Reply-To: References: Message-ID: Oh, I forgot, since I am about to launch a revolution, also strictly apply PHP Framework Interop Group standards (PSR-0, PSR-1, PSR-2) in as much things as possible, starting with Core :-D From philipp.gampe at typo3.org Fri Feb 8 04:58:58 2013 From: philipp.gampe at typo3.org (Philipp Gampe) Date: Fri, 08 Feb 2013 04:58:58 +0100 Subject: [TYPO3-dev] [TYPO3-ect] Announcing TER cleanup process References: Message-ID: Hi Adrien, Adrien Crivelli wrote: > Oh, I forgot, since I am about to launch a revolution, also strictly apply > PHP Framework Interop Group standards > (PSR-0, PSR-1, PSR-2) in as much things as possible, starting with Core > :-D We already try to follow those standards where it makes sense. However, we will not strictly follow those standards as some are unpractical (e.g. spaces instead of tabs). Some of the rules in the "standard" seems to come from votes instead of rational, technical thinking reasoning. IMHO those standards are more important for libraries. After all, standards are about interfaces and not so much about code formatting. I consider formatting standards more being a suggestion. Best regards -- Philipp Gampe ? PGP-Key 0AD96065 ? TYPO3 UG Bonn/K?ln Documentation ? linkvalidator TYPO3 .... inspiring people to share! From philipp.gampe at typo3.org Fri Feb 8 05:12:08 2013 From: philipp.gampe at typo3.org (Philipp Gampe) Date: Fri, 08 Feb 2013 05:12:08 +0100 Subject: [TYPO3-dev] [TYPO3-ect] Announcing TER cleanup process References: Message-ID: Hi Adrien, Adrien Crivelli wrote: > The problem is I am not very close to TYPO3 ecosystem by any means. And, > even though I have a clear vision of what I would like to change (drop svn > entirely, more git/github based things), I don't feel it would be right if > I force my ideas on hundreds of people who are (much) "older" than me in > this community. There are many ideas, but most lack manpower. So if you have an idea, then write it down (a bit like an RFC) wait for some feedback and then go ahead and start coding (e.g. show a proof of concept). If your idea is stupid or does not fit TYPO3 at all, you most likely will get that feedback before you started to put too much effort into it. Just report early and often (communication is a key!). > I feel it would not be fair to apply my radical changes without a clear > approval by the community. And I fail to understand how to get this > approval. For instance I didn't hear about TER cleanup process until a few > days ago. I have no idea who and how it was discussed. And it may be too > late to change the plan now. Or is it ? It has been in the air for very long, but not much was done, because nobody was able or willing to change the TER code. Please also remember that the TER needs to stay backward compatible to older TYPO3 versions for at least two years (more likely you want 5 years). > Here is what I would love to have: > > - existing svn is readonly from today Not really needed. > - all extensions are hosted on github, or TYPO3 git servers for a few > very important one (much less maintenance for TYPO3 git/svn servers) > - publishing extension on TER, require: > - installing > webhookon github > - matching repository name and extension key > - using semver tags for each release That might be a need idea. However, in the meantime we could just provide an admin interface that allows to enter an URL and to select a tag to publish a new version. But it looks like such a hook endpoint would not need that many resources. > - downloads for any version can be served directly from github as zip > file (again much less work for TYPO3 servers) Maybe it would be a lot easier to just use composer for this? > This allow for a much more *natural workflow for developer*, and easier > collaboration via github's pull request (as long as gerrit is not > required, which probably is a vast majority of case for extensions). It > also allow to simplify Extension Manager extension (dropping all code > related to uploading). The code related to uploading has already been dropped in 6.0. > The only downside that I see is a total break for SVN users. But I feel > it's a good time for a big change (with TYPO3 6.0 and TER cleanup). I do not think that we need to break SVN here. We could use a deprecation phase (and I think this is already planned) and move to Git. I do not know if the automated git setup for forge is already integrated and fully functional. With the mentioned Admin Interface to the TER, it should not be too hard to support both custom Git locations as well as custom SVN locations. Versions can then be publish by authors individually. Last but not least, we could also support .zip uploads. Maybe we should first move TER to an own server to shift the load away from typo3.org? And remember, all plans will fail if nobody does the work! Best regards -- Philipp Gampe ? PGP-Key 0AD96065 ? TYPO3 UG Bonn/K?ln Documentation ? linkvalidator TYPO3 .... inspiring people to share! From benni at typo3.org Sat Feb 9 04:27:54 2013 From: benni at typo3.org (Benjamin Mack) Date: Sat, 09 Feb 2013 04:27:54 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager Message-ID: Hey everybody, as most of you (hopefully :)) played around with the new extension manager in 6.0, you might have noticed that it has a different feel to it: It is more focused on actually downloading and installing extensions instead of doing everything else that has been in that place for the last years: * Uploading extensions * Updating language files * Developer information about an extension * Cleanup ext_emconf.php * Creating a new extension (kickstarter) * List of updated extensions So, as we want to improve this area for 6.1, I am eager to get your input on what should definitively get back in there (and why) and what should be placed somewhere else. I would also like to have your feedback on the UI parts, the things you like and the things you don't like. Please keep in mind that we really want to make this thing better than before. Answers like "Make it like it was in 4.0" won't get. This is our chance to make this tool easier and more useful than ever - as we have a great new and clean code base now. Thanks for your feedback! Benni. From philipp.gampe at typo3.org Sat Feb 9 10:15:26 2013 From: philipp.gampe at typo3.org (Philipp Gampe) Date: Sat, 09 Feb 2013 10:15:26 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager References: Message-ID: Hi Benjamin Mack, Benjamin Mack wrote: > It is more focused on actually downloading and installing extensions > instead of doing everything else that has been in that place for the > last years: I would like to keep it this way. > * Uploading extensions Should be moved to a dev tools extension (extdevel?). > * Updating language files Is an own module > * Developer information about an extension Which one? > * Cleanup ext_emconf.php Imho not needed, can be done via extdevel. > * Creating a new extension (kickstarter) Definitly not part of extension management > * List of updated extensions Still there > So, as we want to improve this area for 6.1, I am eager to get your > input on what should definitively get back in there (and why) and what > should be placed somewhere else. I would also like to have your feedback > on the UI parts, the things you like and the things you don't like. I would like to see support (at least by not deleting it) for Git and SVN repositories. Currently, your repository/checkout will be deleted if you update a symlinked extension. There should be a warning, if extensions are symlinked. I might be easiest if we integrate composer support into the EM and let composer handle the Git/SVN/external URL fetching of extensions. Also composer would help a lot with dependency management. Best regards -- Philipp Gampe ? PGP-Key 0AD96065 ? TYPO3 UG Bonn/K?ln Documentation ? linkvalidator TYPO3 .... inspiring people to share! From henrik at ziegenhain.me Sat Feb 9 11:04:33 2013 From: henrik at ziegenhain.me (Henrik Ziegenhain) Date: Sat, 09 Feb 2013 11:04:33 +0100 Subject: [TYPO3-dev] =?utf-8?q?_function_retrieveMediaUrl?= Message-ID: Hi all, in an own extension I need a video from Youtube. Youtube gives us 3 different links (youtu.be/, youtube.com/v/, youtube.com/watch). TYPO3 CE Media offers a great way to handle all kinds of different link schema and video platforms. If I am right, everything is handled in retrieveMediaUrl() - Why is this a protected function? Is there a way to use this function in my extension? At the moment i just copied this function into my own ext, but this is not very nice I think. Kind regards Henrik From typo3 at thomasnu.ch Sat Feb 9 12:48:32 2013 From: typo3 at thomasnu.ch (Thomas Nussbaumer) Date: Sat, 09 Feb 2013 12:48:32 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager In-Reply-To: References: Message-ID: Hi Philipp >> * Uploading extensions > > Should be moved to a dev tools extension (extdevel?). Do you mean extdeval? I find no feature request in http://forge.typo3.org/projects/extension-extdeveval/issues. Best regards Am 09.02.2013 10:15, schrieb Philipp Gampe: > Hi Benjamin Mack, > > Benjamin Mack wrote: > >> It is more focused on actually downloading and installing extensions >> instead of doing everything else that has been in that place for the >> last years: > > I would like to keep it this way. > >> * Uploading extensions > > Should be moved to a dev tools extension (extdevel?). > >> * Updating language files > > Is an own module > >> * Developer information about an extension > Which one? > >> * Cleanup ext_emconf.php > Imho not needed, can be done via extdevel. > >> * Creating a new extension (kickstarter) > Definitly not part of extension management > >> * List of updated extensions > > Still there > >> So, as we want to improve this area for 6.1, I am eager to get your >> input on what should definitively get back in there (and why) and what >> should be placed somewhere else. I would also like to have your feedback >> on the UI parts, the things you like and the things you don't like. > > I would like to see support (at least by not deleting it) for Git and SVN > repositories. Currently, your repository/checkout will be deleted if you > update a symlinked extension. > There should be a warning, if extensions are symlinked. > > I might be easiest if we integrate composer support into the EM and let > composer handle the Git/SVN/external URL fetching of extensions. Also > composer would help a lot with dependency management. > > Best regards > From invadercyg at gmail.com Sat Feb 9 14:09:26 2013 From: invadercyg at gmail.com (Anders Gissel) Date: Sat, 09 Feb 2013 14:09:26 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager In-Reply-To: References: Message-ID: Hey all, On 09-02-2013 10:15, Philipp Gampe wrote: >> >* Uploading extensions > Should be moved to a dev tools extension (extdevel?). > Oh, please, no. Uploading extensions directly to the system is paramount to usability. Unless you mean from the local installation to TER - but being able to upload a ZIP-file directly to the server is one thing I would hate to live without. /A. From tobias.liebig at typo3.org Sat Feb 9 17:07:30 2013 From: tobias.liebig at typo3.org (Tobias Liebig) Date: Sat, 9 Feb 2013 17:07:30 +0100 Subject: [TYPO3-dev] Ideas for Google Summer of Code Message-ID: Hej, we hope Google will announce the Google Summer of Code [1] for this year again and we expect them to do it soon. GSoC is a program by Google to fund OpenSource projects (like TYPO3) by enabling student developers to contribute to OpenSource projects over a three month period ("flip bits, not burgers"). We're planing to apply this year again. Last year we got rejected, most likely because we couldn't provide an outstanding list of ideas on which students can work on. However, we like to improve in this regard for this years application. This is why I ask you to collect and suggest ideas for possible GSoC-Projects. We created a wiki page [2] and ask *you* to fill this with your ideas using the provided template. It's about projects for all our products: TYPO3 CMS, TYPO3 Flow, TYPO3 Neos, Extbase, Fluid, TYPO3.Surf, . Feel free to add new ideas to the wiki page, as well as improving the already existing ones. For deeper discussions about an idea I suggest to use the typo3.gsoc maillinglist [3]. GSoC is the "Summer of Code". So a "documentation task" won't really fit. Remind that possible students might not have any deep knowledge in TYPO3 yet. Also a project should be achievable for one student within the three month coding period. So completely rewriting the TYPO3 backend might not be the best choice for a GSoC project. Your critical business depends on this new feature being available by the end of this summer? Humm.. better do it yourself or pay someone for it. But this idea, you already have in mind for months or even years, you can't find time to implement it and you know people will be like "wow, this is cool". Someone really should do it somewhen? Yes, that might be a cool GSoC project! Or this great concept, which came up lately while discussing in the mailinglist/twitter/bugtracker or on the T3Something event. That might be one, too! Please spread the word and forward this mail to your colleagues, which do not follow this list, but might have some ideas. If you have any question, do not hesitate to ask me (or Christian M?ller). You can send us a mail [4][5], poke me on twitter [6] and most likely you will find someone in our IRC channel [7]. Also we are reading the typo3.gsoc maillinglist, too. We are really looking forward to your suggestions. kind regards tobias [1] https://developers.google.com/open-source/soc/ [2] http://wiki.typo3.org/Gsoc2013/Ideas (you need a typo3.org account to edit this page) [3] http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-gsoc or http://forum.typo3.org/index.php/f/59/ [4] christian.mueller at typo3.org [5] tobias.liebig at typo3.org [6] https://twitter.com/typo3_gsoc [7] irc://irc.freenode.net/#typo3-gsoc -- Tobias Liebig TYPO3 Core Team member TYPO3 .... inspiring people to share! Get involved: typo3.org http://bit.ly/supportTYPO3 From fsu-lists at cobweb.ch Sat Feb 9 17:40:13 2013 From: fsu-lists at cobweb.ch (=?UTF-8?B?RnJhbsOnb2lzIFN1dGVy?=) Date: Sat, 09 Feb 2013 17:40:13 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager In-Reply-To: References: Message-ID: Hi Anders, > Oh, please, no. Uploading extensions directly to the system is paramount > to usability. Unless you mean from the local installation to TER - but > being able to upload a ZIP-file directly to the server is one thing I > would hate to live without. It's about uploading to TER. The "local upload" possibility is still there (see the little icon at the top left of the docheader bar). Cheers -- Francois Suter Cobweb Development Sarl - http://www.cobweb.ch From fsu-lists at cobweb.ch Sat Feb 9 17:48:49 2013 From: fsu-lists at cobweb.ch (=?ISO-8859-1?Q?Fran=E7ois_Suter?=) Date: Sat, 09 Feb 2013 17:48:49 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager In-Reply-To: References: Message-ID: Hi Benni, > as most of you (hopefully :)) played around with the new extension > manager in 6.0, you might have noticed that it has a different feel to > it: It is more focused on actually downloading and installing extensions > instead of doing everything else that has been in that place for the > last years: At first I was rather upset by the new EM, but I'm now used to it and quite enjoy it. > * Uploading extensions > * Cleanup ext_emconf.php Moving this to extdeveval has been discussed already before, but nobody is taking care of it yet. I'm fine with the idea but it should be tackled soon IMO, so that you don't need to launch another version of TYPO3 just to upload your extension. > * Updating language files Is in a separate module now and seems fine. > * Developer information about an extension With older EMs we could see such information about installed extensions. I never found this really useful. However with the new EM installing extensions silently, I would support having some kind of preview: some screen/dialog window could tell you about database modifications and warn you about configuration options, for example. I find it too silent in its current state (I would even backport that to 6.0). > * Creating a new extension (kickstarter) Extension "kickstarter" should be modified to be a stand-alone module. The new extension builder is already that way. Ideally any effort should really rather be targeted at the extension builder to add what might be missing there, rather than continue maintaining the old kickstarter, which will require always more care in the future (like adding generation for namespaced plugins, for example, which would be quite an effort). > * List of updated extensions You can already see what extensions can be updated. Do you mean something else? Cheers -- Francois Suter Cobweb Development Sarl - http://www.cobweb.ch From m.bless at gmx.de Sat Feb 9 20:51:48 2013 From: m.bless at gmx.de (Martin Bless) Date: Sat, 09 Feb 2013 20:51:48 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager References: Message-ID: Hi Benjamin, great you're asking. Two things: 1. How do you run the UPDATE! function of an extension? 2. Make it more visible how to update the list of extensions. See this screenshots about what I mean: http://www.evernote.com/shard/s288/sh/fd424639-bcf5-4578-a4f1-683eb00ef214/f38b2f24f8c4b69e87d52b471f6fd492 Thanks, and: See you in Stuttgart! Martin -- Certified TYPO3 Integrator | TYPO3 Documentation Team Member http://mbless.de From philipp.gampe at typo3.org Sat Feb 9 21:01:10 2013 From: philipp.gampe at typo3.org (Philipp Gampe) Date: Sat, 09 Feb 2013 21:01:10 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager References: Message-ID: Hi Martin Bless, Martin Bless wrote: > 1. How do you run the UPDATE! function of an extension? The feature was missing, but at least 6.1-dev has it now. I do not know if it has been backported. If an extension offers update, then you will see an icon. Best regards -- Philipp Gampe ? PGP-Key 0AD96065 ? TYPO3 UG Bonn/K?ln Documentation ? linkvalidator TYPO3 .... inspiring people to share! From fsu-lists at cobweb.ch Sat Feb 9 21:17:16 2013 From: fsu-lists at cobweb.ch (=?UTF-8?B?RnJhbsOnb2lzIFN1dGVy?=) Date: Sat, 09 Feb 2013 21:17:16 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager In-Reply-To: References: Message-ID: Hi, >> 1. How do you run the UPDATE! function of an extension? > > The feature was missing, but at least 6.1-dev has it now. I do not know if > it has been backported. It has been backported, but just missed the 6.0.1 release. It will be in 6.0.2. Cheers -- Francois Suter Cobweb Development Sarl - http://www.cobweb.ch From typo3ml at schams.net Sun Feb 10 03:27:30 2013 From: typo3ml at schams.net (Michael) Date: Sun, 10 Feb 2013 13:27:30 +1100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager In-Reply-To: References: Message-ID: On 09/02/13 14:27, Benjamin Mack wrote: [...] > So, as we want to improve this area for 6.1, I am eager to get your > input on what should definitively get back in there (and why) and what > should be placed somewhere else. In my opinion, the question should *not* be: "What would you like to see/have in the EM?" ("you" in the context of: we, the nerds who read this dev-mailinglist). I would look at the roles who use the EM, which are: integrators, developers and administrators - and then think about their tasks. Integrators are the main target group and they should be able to: search/find extensions and easily "see" extension updates, choose if they have or should install an ext or ext update, install and remove extensions, configure installed ext, etc. They do *not* upload extensions to the TER for example. This is a developer's task and "upload to TER" is a feature I would not expect to see in a LIVE environment (if you strictly separate your instances between "dev", "test" and "live" or a similar staging concept). Therefore, out-of-scope of the EM from my perspective. However, very important, and the other responses in this thread already pointed this out: in urgent need (e.g. as a feature of extdeval or so) :-) Editing files, view file list (of extensions), updating ext_emconf, etc. is a developer/admin task, too. However, sometimes it is useful for an integrator to see which files are available and to review them (e.g. templates or default TypoScript) but if the documentation has a certain level of quality, this should not be required. Speaking of "documentation": I would love to give integrators direct access to extension manuals... *inside* their TYPO3 instance and for the correct extension version (the currently installed version). No need to search on docs.typo3.org or TER, no need to download OpenOffice or PDF files, etc. but show the manual as HTML in TYPO3 with a click of a button. With reST we made a big step forward and have a great foundation in place for such a feature :-) My opinion in short words: keep the EM as slim and streamlined as possible, focus on integrators and their tasks - and keep everything out of the EM, that should not be available in a "live" instance of TYPO3. All developer/admin-related stuff should be provided by other extensions (not mandatory to install, not installed/activated by default). Integrators should have all tools/information by hand to make well-informed decisions about an extension (install/remove/update/configure and how to configure -> quick and easy access to the manual). Oh, one last thing: retrieving the extension list from TER. Maybe I should double check what is possible and how the EM currently behaves, but I was (negatively) surprised when the EM downloaded the extension list automatically when you access the EM the first time (I would prefer to control the download) and secondly, I always dreamed of a different extensionlist download concept. For example, instead of downloading, extracting and parsing a 10MB extensionlist.xml.gz file, maybe it's achievable to split this into 4 or 6 smaller parts (maybe configurable) and download them in a row. This would prevent timeouts as well as server loads over long time. On the other hand, with modern server hardware today, this becomes less an issue and also, making this dream come true requires some significant changes on the TER side as well :-) Cheers Michael From jan.kornblum at gmx.de Sun Feb 10 13:00:43 2013 From: jan.kornblum at gmx.de (Jan Kornblum) Date: Sun, 10 Feb 2013 13:00:43 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager References: Message-ID: Hi Benjamin, i would suggest the following features (useful for both administrator, integrator and developer): * being "less silent" on extension updates (showing db operations, etc.. require an aditional "confirm" step in this case, ...) * displaying author in listview (to be able to choose exts by a known or "trusted" author) * having something like a detail view to show additional ext-infos (extension files, conflicts, suggests, requires, author, ...). The features above are focused to "downloading and installing" and wouldn't blow up EM, i think... Regards, Jan From typo3 at thomasnu.ch Sun Feb 10 14:57:43 2013 From: typo3 at thomasnu.ch (Thomas Nussbaumer) Date: Sun, 10 Feb 2013 14:57:43 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager In-Reply-To: References: Message-ID: Hi Fran?ois > Moving this to extdeveval has been discussed already before, but nobody > is taking care of it yet. I'm fine with the idea but it should be > tackled soon IMO, so that you don't need to launch another version of > TYPO3 just to upload your extension. I'm dealing with Extbase and Fluid. Possess little knowledge about the core. But I think that it should not be hard to port the TER upload to extdeveval for 6.0. Cheers Am 09.02.2013 17:48, schrieb Fran?ois Suter: > Hi Benni, > >> as most of you (hopefully :)) played around with the new extension >> manager in 6.0, you might have noticed that it has a different feel to >> it: It is more focused on actually downloading and installing extensions >> instead of doing everything else that has been in that place for the >> last years: > > At first I was rather upset by the new EM, but I'm now used to it and > quite enjoy it. > >> * Uploading extensions >> * Cleanup ext_emconf.php > > Moving this to extdeveval has been discussed already before, but nobody > is taking care of it yet. I'm fine with the idea but it should be > tackled soon IMO, so that you don't need to launch another version of > TYPO3 just to upload your extension. > >> * Updating language files > > Is in a separate module now and seems fine. > >> * Developer information about an extension > > With older EMs we could see such information about installed extensions. > I never found this really useful. However with the new EM installing > extensions silently, I would support having some kind of preview: some > screen/dialog window could tell you about database modifications and > warn you about configuration options, for example. I find it too silent > in its current state (I would even backport that to 6.0). > >> * Creating a new extension (kickstarter) > > Extension "kickstarter" should be modified to be a stand-alone module. > The new extension builder is already that way. Ideally any effort should > really rather be targeted at the extension builder to add what might be > missing there, rather than continue maintaining the old kickstarter, > which will require always more care in the future (like adding > generation for namespaced plugins, for example, which would be quite an > effort). > >> * List of updated extensions > > You can already see what extensions can be updated. Do you mean > something else? > > Cheers > From philipp.gampe at typo3.org Sun Feb 10 16:14:15 2013 From: philipp.gampe at typo3.org (Philipp Gampe) Date: Sun, 10 Feb 2013 16:14:15 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager References: Message-ID: Hi Thomas Nussbaumer, Thomas Nussbaumer wrote: > I'm dealing with Extbase and Fluid. Possess little knowledge about the > core. But I think that it should not be hard to port the TER upload to > extdeveval for 6.0. The code should be pretty much standalone, check: https://github.com/etobi/Typo3ExtensionUtils Best regards -- Philipp Gampe ? PGP-Key 0AD96065 ? TYPO3 UG Bonn/K?ln Documentation ? linkvalidator TYPO3 .... inspiring people to share! From jigal.van.hemert at typo3.org Sun Feb 10 16:29:11 2013 From: jigal.van.hemert at typo3.org (Jigal van Hemert) Date: Sun, 10 Feb 2013 16:29:11 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager In-Reply-To: References: Message-ID: Hi, On 9-2-2013 4:27, Benjamin Mack wrote: > * Uploading extensions Extdeveval > * Updating language files Lang module in 6.0 > * Developer information about an extension There is one feature here that is useful to integrators: files which seem modified. The use case: a future client asks for a quote for an upgrade of an old TYPO3 site. Knowing if an extension might be modified (needs further investigation on the actual changes; could be temporary debug code which is already removed in the past) is vital information for such a quote. > * Cleanup ext_emconf.php Extdeveval > * Creating a new extension (kickstarter) Extdeveval > * List of updated extensions If you keep the TER list up-to-date (scheduler task) the EM 6.0 already shows which extensions have a new version. * Documentation of extension, online and offline (offline for installations without online connection (intranets) or limited connection) * paginator in local ext list (for a jQuery expert) * better local upload form (usability) * improved usability for search options -- Jigal van Hemert TYPO3 Core Team member TYPO3 .... inspiring people to share! Get involved: typo3.org From loek at netcoop.nl Sun Feb 10 17:12:17 2013 From: loek at netcoop.nl (Loek Hilgersom) Date: Sun, 10 Feb 2013 17:12:17 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager In-Reply-To: References: Message-ID: Hi Benni and others, I fully agree with most of the stripping-down of the Extension Manager, but there is one feature I really miss, which has been gone since 4.5 AFAIK. In 4.5, when checking for extension updates, you got a very useful list containing all updatable extensions including the upload-comments from the extension author for each version higher than what you have now. See screenshot: http://img.im/i/dic3m6 I never understood why this had been dropped, because it gives a perfect list on which you can decide which extensions urgently need an update because of a security issue, or which ones require more work because they include breaking changes. Or has it just been hidden in a far away corner that I haven't discovered? Cheers, Loek From most.wanted at gmx.at Sun Feb 10 17:59:45 2013 From: most.wanted at gmx.at (Roland) Date: Sun, 10 Feb 2013 17:59:45 +0100 Subject: [TYPO3-dev] =?utf-8?q?_Re=3A_RealURL=3A_bypass_and_lookupTable=2C?= =?utf-8?q?_missing_feature=3F?= References: Message-ID: Hi everybody, is there still no (better) possibility to work around this? kind regards roland From scecere at krur.com Sun Feb 10 18:23:39 2013 From: scecere at krur.com (Stefano Cecere) Date: Sun, 10 Feb 2013 18:23:39 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager In-Reply-To: References: Message-ID: Hi Benni i started using 6.0 and i have just two really nosing problem with EM: 1) the "overwrite" checkbox when uploading an ext: whoever doesn't check it? (in 10 years i have always needed to overwirte any ext i upload.. and i don't see any benefits in not overwriting) so, let's make it checked by default 2) .git/.svn folders are now exported in the .zip file, and uploaded. the download button should prevent any .invisible folder to get zipped in! thank you and see ya for 6.1! stefano On 09/02/13 04:27, Benjamin Mack wrote: > Hey everybody, > > as most of you (hopefully :)) played around with the new extension > manager in 6.0, you might have noticed that it has a different feel to > it: It is more focused on actually downloading and installing extensions > instead of doing everything else that has been in that place for the > last years: > > * Uploading extensions > * Updating language files > * Developer information about an extension > * Cleanup ext_emconf.php > * Creating a new extension (kickstarter) > * List of updated extensions > > So, as we want to improve this area for 6.1, I am eager to get your > input on what should definitively get back in there (and why) and what > should be placed somewhere else. I would also like to have your feedback > on the UI parts, the things you like and the things you don't like. > > Please keep in mind that we really want to make this thing better than > before. Answers like "Make it like it was in 4.0" won't get. This is our > chance to make this tool easier and more useful than ever - as we have a > great new and clean code base now. > > Thanks for your feedback! > Benni. > -- -- --- ----- ------- Stefano Cecere KRUR studio - http://krur.com From lolli at schwarzbu.ch Sun Feb 10 22:51:23 2013 From: lolli at schwarzbu.ch (Christian Kuhn) Date: Sun, 10 Feb 2013 22:51:23 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager In-Reply-To: References: Message-ID: Hey, On 02/09/2013 04:27 AM, Benjamin Mack wrote: > So, as we want to improve this area for 6.1, I am eager to get your > input on what should definitively get back in there (and why) and what > should be placed somewhere else. I would also like to have your feedback > on the UI parts, the things you like and the things you don't like. Reading the current feedback, most important things were raised already. First, it seems that people in general agree on the current solution that the new em is stripped down to the important 'integrator' extension handling stuff, which is installing, de-installing, updating, fetching and configuring extensions, plus directly related things. This was our intention and it is great to see this is accepted in the wild. One important missing feature was the 'update script' handling. This is now done and will be delivered with 6.0.2. Other things like 'edit extension files' is not part of extension management itself and can be done way better by other extensions like t3quixplorer if that is *really* needed by people. The TER upload is also missing, the implementation of this feature in extdeveval is not done, and I personally do not know anyone actually working on that at the moment. If anyone would like to step in, feel free to contact us, I'm sure we will find someone from or near the core team to support any efforts. Maybe we should raise an own thread to ask for help to get this done. Other than that, there are still some issues with the new em, most of them also raised: * It is good that the em does a lot of things automatically (like fetching dependencies on its own when installing extensions from TER), but it misses visual feedback sometimes to say for example "hey, I'm working for you now, please wait". This should be improved. * At several points some more information should be given, like the one or the other flash message, maybe an information of an extensions version changelog before upgrading, maybe some information on dependencies or conflicts when installing from TER. Those things should only be given if it is important in the current instance. For example it *is* important that some extension can not be installed because of some conflict to another installed extension, but there is no additional information in just showing all possible conflicts. * Codewise the em is still not as straight as it should be, from an architectural point of view the utility classes for example contain too much magic and cross-connections which makes some parts harder to follow and understand than it should be. The situation is still way better than before, but some refactoring can be done. * Another feature of the old em was left out for the new one by intention: Show required database updates when installing something. Reason: This is clearly *not* a detail integrators should take care of, it should be done under the hood. If we are serious, nobody ever had a chance of not accepting the list of db changes anyway. * Usability and styling should get more love. The search for extensions in TER is not as cool as it should be, a better feedback on important issues with current installed extensions (eg. pending security updates) would be nice. We should work together with the usability team to improve that in a way that it is in line with other backend usability concepts. Regards Christian From mark at nasaustralia.com.au Mon Feb 11 03:18:06 2013 From: mark at nasaustralia.com.au (Mark Roemermann) Date: Mon, 11 Feb 2013 12:18:06 +1000 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager In-Reply-To: References: Message-ID: On 11/02/2013 2:12 AM, Loek Hilgersom wrote: > > In 4.5, when checking for extension updates, you got a very useful list > containing all updatable extensions including the upload-comments from > the extension author for each version higher than what you have now. > > See screenshot: http://img.im/i/dic3m6 > > I never understood why this had been dropped, because it gives a perfect > list on which you can decide which extensions urgently need an update > because of a security issue, or which ones require more work because > they include breaking changes. Or has it just been hidden in a far away > corner that I haven't discovered? > > Cheers, > Loek > I agree Loek, this was a useful integrator feature to have, although this had gone by the time of the 4.5 EM? I think this was the old 3.8~4.4 EM that had this 'check updated extensions' list? I do miss it however, as having one place that gave just that little bit more context for a given update was very useful. Saved having to check the TER website for each extension one at a time to review changes between verisons, particularly if you skipped one or two. A second feature I miss from the 4.5 era EM is the ability to add columns to the remote extension list. You could click on the little triangle and select additional columns (such as author) and filter on these columns. I agree that by default, a simpler interface is less confusing but it could be a useful power user feature when searching for a particular authors extensions, particularly when you may be after a suite of extensions by a particular author (like Claus' FED exts, or the sportsbet exts, or the several DAM exts). For a large database like TER efficient discoverability is just as much a part of integrator usability as well as the simplified UI/UX. Cheers. Mark R. From adrien.crivelli at gmail.com Mon Feb 11 03:44:07 2013 From: adrien.crivelli at gmail.com (Adrien Crivelli) Date: Mon, 11 Feb 2013 11:44:07 +0900 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager In-Reply-To: References: Message-ID: Hello, There currently is a discussion going onabout the upload to TER process (more details here). The aim would be to replace the current workflow with a git-based workflow, very similar to what was recently done for jQuery plugins. So publishing an extension would be as simple as a git tag pushing. This would avoid to re-code the upload to TER part in another extension, and progressively deprecate the existing API on TER servers. And, obviously, I hope that every developer will agree with me that the workflow is much more developer-friendly. To me, it sounds "compatible" with new EM's philosophy and seems to be a good time to implement it (or rather not re-implement it as an extension ;-) ). What do you think ? Cheers, Adrien On 11 February 2013 06:51, Christian Kuhn wrote: > Hey, > > > On 02/09/2013 04:27 AM, Benjamin Mack wrote: > >> So, as we want to improve this area for 6.1, I am eager to get your >> input on what should definitively get back in there (and why) and what >> should be placed somewhere else. I would also like to have your feedback >> on the UI parts, the things you like and the things you don't like. >> > > Reading the current feedback, most important things were raised already. > > First, it seems that people in general agree on the current solution that > the new em is stripped down to the important 'integrator' extension > handling stuff, which is installing, de-installing, updating, fetching and > configuring extensions, plus directly related things. This was our > intention and it is great to see this is accepted in the wild. > > One important missing feature was the 'update script' handling. This is > now done and will be delivered with 6.0.2. > > Other things like 'edit extension files' is not part of extension > management itself and can be done way better by other extensions like > t3quixplorer if that is *really* needed by people. > > The TER upload is also missing, the implementation of this feature in > extdeveval is not done, and I personally do not know anyone actually > working on that at the moment. If anyone would like to step in, feel free > to contact us, I'm sure we will find someone from or near the core team to > support any efforts. Maybe we should raise an own thread to ask for help to > get this done. > > > Other than that, there are still some issues with the new em, most of them > also raised: > > * It is good that the em does a lot of things automatically (like fetching > dependencies on its own when installing extensions from TER), but it misses > visual feedback sometimes to say for example "hey, I'm working for you now, > please wait". This should be improved. > > * At several points some more information should be given, like the one or > the other flash message, maybe an information of an extensions version > changelog before upgrading, maybe some information on dependencies or > conflicts when installing from TER. Those things should only be given if it > is important in the current instance. For example it *is* important that > some extension can not be installed because of some conflict to another > installed extension, but there is no additional information in just showing > all possible conflicts. > > * Codewise the em is still not as straight as it should be, from an > architectural point of view the utility classes for example contain too > much magic and cross-connections which makes some parts harder to follow > and understand than it should be. The situation is still way better than > before, but some refactoring can be done. > > * Another feature of the old em was left out for the new one by intention: > Show required database updates when installing something. Reason: This is > clearly *not* a detail integrators should take care of, it should be done > under the hood. If we are serious, nobody ever had a chance of not > accepting the list of db changes anyway. > > * Usability and styling should get more love. The search for extensions in > TER is not as cool as it should be, a better feedback on important issues > with current installed extensions (eg. pending security updates) would be > nice. We should work together with the usability team to improve that in a > way that it is in line with other backend usability concepts. > > > Regards > Christian > > ______________________________**_________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-**bin/mailman/listinfo/typo3-dev > From jan.kornblum at gmx.de Mon Feb 11 09:32:57 2013 From: jan.kornblum at gmx.de (Jan Kornblum) Date: Mon, 11 Feb 2013 09:32:57 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager References: Message-ID: Hi Christian, > * Another feature of the old em was left out for the new one by intention: > Show required database updates when installing something. Reason: This is > clearly *not* a detail integrators should take care of, it should be done > under the hood. If we are serious, nobody ever had a chance of not accepting > the list of db changes anyway. Why that? In previous versions there was a button like "make updates" or "perform updates" (for ext installations and ext updates). At this point you were able to "accept the list of db changes" or you could stop the whole process (by not clicking the button and maybe remove the ext after this or something else). i definitely want to see what happens to the db *before* i install or update any extension. each integrator must know about this, too! this is not only informative, this also could prevent any trouble in certain cases... Regards, Jan From manuel.kammermann at unibas.ch Mon Feb 11 13:09:41 2013 From: manuel.kammermann at unibas.ch (Manuel Kammermann) Date: Mon, 11 Feb 2013 12:09:41 +0000 Subject: [TYPO3-dev] makeInstance caches multiple entries Message-ID: Hi List, I try to achieve the following: from my extension, i want two different outputs of the same different extension. I use t3lib_div::makeInstance() and change the conf for the second init()-call (TYPO3 is 4.5.5): code: require_once(PATH_typo3conf.'ext/foreignextkey/pi1/class.tx_foreignextkey_pi1.php'); $publ = t3lib_div::makeInstance('tx_foreignextkey_pi1'); $publ->pi_checkCHash = TRUE; $publ->pi_USER_INT_obj = TRUE; $publ->cObj = $this->cObj; $conf = $GLOBALS['TSFE']->tmpl->setup['plugin.']['tx_foreignextkey_pi1.']; if($pubView == 'two'){ $conf['category_sub'] = $bookCats; } $publ->init('',$conf); $publ->piVars['showAll'] = 1; $mArr['###marker###'] = $publ->listAll(); if($pubView == 'two'){ $conf['category_sub'] = $otherCats; $publ->init('',$conf); $publ->piVars['showAll'] = 1; $mArr['###publications###'] .= $publ->listAll(); } unset($conf); Not sure how to clear the cache between the two calls (you see some tried effort in the code). Any hints? Thanks for your help, and have a good day. ------------ MANUEL KAMMERMANN, M. Sc. Web Developer Research IT Technology Platform Biozentrum der Universit?t Basel The Center of Molecular Life Sciences Klingelbergstrasse 50, CH-4056 Basel +41 (0)61 267 21 83 From tobias.liebig at typo3.org Tue Feb 12 08:58:17 2013 From: tobias.liebig at typo3.org (Tobias Liebig) Date: Tue, 12 Feb 2013 08:58:17 +0100 Subject: [TYPO3-dev] Ideas for Google Summer of Code In-Reply-To: References: Message-ID: Hej, In the meanwhile Google announced the GSoC 2013 [1]. So now, we really need your ideas added here: http://wiki.typo3.org/Gsoc2013/Ideas. Get in touch with me, if you have any questions. [1] http://google-opensource.blogspot.de/2013/02/flip-bits-not-burgers-google-summer-of.html looking forward to the summer! tobias Am 09.02.2013 um 17:07 schrieb Tobias Liebig : > Hej, > > we hope Google will announce the Google Summer of Code [1] for this year again and we expect them to do it soon. GSoC is a program by Google to fund OpenSource projects (like TYPO3) by enabling student developers to contribute to OpenSource projects over a three month period ("flip bits, not burgers"). > > We're planing to apply this year again. Last year we got rejected, most likely because we couldn't provide an outstanding list of ideas on which students can work on. > However, we like to improve in this regard for this years application. > > This is why I ask you to collect and suggest ideas for possible GSoC-Projects. > We created a wiki page [2] and ask *you* to fill this with your ideas using the provided template. > > It's about projects for all our products: TYPO3 CMS, TYPO3 Flow, TYPO3 Neos, Extbase, Fluid, TYPO3.Surf, . > > Feel free to add new ideas to the wiki page, as well as improving the already existing ones. For deeper discussions about an idea I suggest to use the typo3.gsoc maillinglist [3]. > > GSoC is the "Summer of Code". So a "documentation task" won't really fit. > Remind that possible students might not have any deep knowledge in TYPO3 yet. > Also a project should be achievable for one student within the three month coding period. So completely rewriting the TYPO3 backend might not be the best choice for a GSoC project. > Your critical business depends on this new feature being available by the end of this summer? Humm.. better do it yourself or pay someone for it. > But this idea, you already have in mind for months or even years, you can't find time to implement it and you know people will be like "wow, this is cool". Someone really should do it somewhen? Yes, that might be a cool GSoC project! > Or this great concept, which came up lately while discussing in the mailinglist/twitter/bugtracker or on the T3Something event. That might be one, too! > > Please spread the word and forward this mail to your colleagues, which do not follow this list, but might have some ideas. > > If you have any question, do not hesitate to ask me (or Christian M?ller). > You can send us a mail [4][5], poke me on twitter [6] and most likely you will find someone in our IRC channel [7]. Also we are reading the typo3.gsoc maillinglist, too. > > We are really looking forward to your suggestions. > > kind regards > tobias > > > [1] https://developers.google.com/open-source/soc/ > [2] http://wiki.typo3.org/Gsoc2013/Ideas (you need a typo3.org account to edit this page) > [3] http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-gsoc or http://forum.typo3.org/index.php/f/59/ > [4] christian.mueller at typo3.org > [5] tobias.liebig at typo3.org > [6] https://twitter.com/typo3_gsoc > [7] irc://irc.freenode.net/#typo3-gsoc > > -- > Tobias Liebig > TYPO3 Core Team member > > TYPO3 .... inspiring people to share! > Get involved: typo3.org > > http://bit.ly/supportTYPO3 > > _______________________________________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev -- Tobias Liebig TYPO3 Core Team member TYPO3 .... inspiring people to share! Get involved: typo3.org http://bit.ly/supportTYPO3 From t3ng at bernd-wilke.net Tue Feb 12 09:52:12 2013 From: t3ng at bernd-wilke.net (bernd wilke) Date: Tue, 12 Feb 2013 09:52:12 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager In-Reply-To: References: Message-ID: Am 09.02.2013 04:27, schrieb Benjamin Mack: > Hey everybody, > > as most of you (hopefully :)) played around with the new extension > manager in 6.0, you might have noticed that it has a different feel to > it: It is more focused on actually downloading and installing extensions > instead of doing everything else that has been in that place for the > last years: > > * Updating language files as this got an own module it is fine for me to stop support in EM > * Uploading extensions > * Developer information about an extension > * Cleanup ext_emconf.php > * Creating a new extension (kickstarter) as these are actions which belongs to developing it could be exported to developing moduls. we have kickstarter, extension builder, extdeveval, maybe we can create an own module group where extension like these can be integrated. > * List of updated extensions this is a big lack for me: in the old EM you could get a list of all updateable extensions INCLUDING all upload-comments (including intermediate versions [1]), so you had all information in one view which extension are updateable the easy way and which need further assistence or reconfiguration. and so it belongs into the developer-module: at the moment of update it was a very helpful information that an extension had modified files (and which files got modified)!! I would be happy if these information would be re-implemented. [1] as unsecure versions were removed from TER, their comments were missing and you can't say whether an update to a new secure version would include changed behaviour This view was a good base for documentation which updates an installation got. maybe we also can get an own log (history) about extension updates AND the possibility to revert single updates in an easy way. maybe a backup of old installed versions, as the TER does not hold localy modified extensions ;-). > So, as we want to improve this area for 6.1, I am eager to get your > input on what should definitively get back in there (and why) and what > should be placed somewhere else. I would also like to have your feedback > on the UI parts, the things you like and the things you don't like. the other thing I miss: I want to know which changes are done if an extension is installed. so please make the 'silent' installation configurable. read as: please give me an option to configure that depending extensions are installed only with my explicit permission, and the same for changes to the database. > Please keep in mind that we really want to make this thing better than > before. Answers like "Make it like it was in 4.0" won't get. This is our > chance to make this tool easier and more useful than ever - as we have a > great new and clean code base now. as others said: as more and more extensions are available only in GIT it would be nice to import extensions not only from TER but also from GIT and other sources. (Why should I store a copy of an extension on my computer, only to upload it to the webserver?) and is t3x still the best format for extensions? bernd -- http://www.pi-phi.de/cheatsheet.html From olivier.dobberkau at dkd.de Tue Feb 12 10:14:36 2013 From: olivier.dobberkau at dkd.de (Olivier Dobberkau) Date: Tue, 12 Feb 2013 10:14:36 +0100 Subject: [TYPO3-dev] Ideas for Google Summer of Code In-Reply-To: References: Message-ID: Am 09.02.13 17:07, schrieb Tobias Liebig: > This is why I ask you to collect and suggest ideas for possible GSoC-Projects. > We created a wiki page [2] and ask *you* to fill this with your ideas using the provided template. if you need more inspiration for ideas: http://wiki.typo3.org/T3A-budget-ideas-2013 olivier From philipp.gampe at typo3.org Tue Feb 12 11:19:46 2013 From: philipp.gampe at typo3.org (Philipp Gampe) Date: Tue, 12 Feb 2013 11:19:46 +0100 Subject: [TYPO3-dev] Ideas for Google Summer of Code References: Message-ID: Hi Tobias, Tobias Liebig wrote: > We are really looking forward to your suggestions. Just an idea: Let a student work on a next-gen TER which combines Flow and CMS extensions/packages? Maybe based on composer package repository, but with integration into existing T3o infrastructure. I am just not sure if the workload can be handled within a three month period. Best regards -- Philipp Gampe ? PGP-Key 0AD96065 ? TYPO3 UG Bonn/K?ln Documentation ? linkvalidator TYPO3 .... inspiring people to share! From philipp.gampe at typo3.org Tue Feb 12 11:23:42 2013 From: philipp.gampe at typo3.org (Philipp Gampe) Date: Tue, 12 Feb 2013 11:23:42 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager References: Message-ID: Hi bernd, bernd wilke wrote: > and is t3x still the best format for extensions? No, it will be zip as soon as the TER fully supports zip. I hope for native git support too, but maybe that should be combined with composer support for dependency handling? Best regards -- Philipp Gampe ? PGP-Key 0AD96065 ? TYPO3 UG Bonn/K?ln Documentation ? linkvalidator TYPO3 .... inspiring people to share! From jan.kornblum at gmx.de Tue Feb 12 12:35:11 2013 From: jan.kornblum at gmx.de (Jan Kornblum) Date: Tue, 12 Feb 2013 12:35:11 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager References: Message-ID: Hi again, > * being "less silent" on extension updates (showing db operations, etc.. > require an aditional "confirm" step in this case, ...) > * displaying author in listview (to be able to choose exts by a known or > "trusted" author) > * having something like a detail view to show additional ext-infos (extension > files, conflicts, suggests, requires, author, ...). I've fogotten something: Where can i find information about if an extension is installed as "system" or "local". This information is also missing in current EM, or don't i just see it? Should be added again! Regards, Jan From jeroen at serpieters.be Tue Feb 12 13:49:22 2013 From: jeroen at serpieters.be (Jeroen Serpieters) Date: Tue, 12 Feb 2013 18:19:22 +0530 Subject: [TYPO3-dev] CMIS support Message-ID: Hi, Is there any support planned for CMIS in TYPO3? If not has this been thought of and then why not? I feel like this would be a great addition. And while it seems like a major task it might be something I am willing to work on since I see direct benefit for customers. But of course before starting such a venture I am wondering whether it has crossed some minds before or not. I did see an old (client) extension: http://typo3.org/extension-manuals/cmis/0.0.2/view/ From olivier.dobberkau at dkd.de Tue Feb 12 15:41:01 2013 From: olivier.dobberkau at dkd.de (Olivier Dobberkau) Date: Tue, 12 Feb 2013 15:41:01 +0100 Subject: [TYPO3-dev] CMIS support In-Reply-To: References: Message-ID: Am 12.02.13 13:49, schrieb Jeroen Serpieters: > Hi, > > Is there any support planned for CMIS in TYPO3? If not has this been > thought of and then why not? > I feel like this would be a great addition. And while it seems like a > major task it might be something I am willing to work on since I see > direct benefit for customers. But of course before starting such a > venture I am wondering whether it has crossed some minds before or not. > > I did see an old (client) extension: > http://typo3.org/extension-manuals/cmis/0.0.2/view/ Hi, please contact me in PM. We at dkd plan to work on this. best greetings, Olivier From tomasnorre at gmail.com Tue Feb 12 17:31:25 2013 From: tomasnorre at gmail.com (Tomas Norre Mikkelsen) Date: Tue, 12 Feb 2013 17:31:25 +0100 Subject: [TYPO3-dev] sr_feuser_register - info mail on submit. In-Reply-To: References: Message-ID: On 01/31/2013 01:58 PM, Tomas Norre Mikkelsen wrote: > Is this possible? I Have looked into the constants.ts and manuals, but > didn't find anything. If it is not implemented I?ll be glad to do so and > submitting a patch to the repository. I fixed this with the registrationProcess_afterSaveCreate() function in $GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['sr_feuser_register']['tx_srfeuserregister_pi1']['registrationProcess'][] - hook. See more her: ext/sr_feuser_register/hooks/class.tx_srfeuserregister_hooksHandler.php -- Best Regards Tomas Norre Mikkelsen TYPO3 Profile: http://forge.typo3.org/users/4289 TYPO3 Developer @ netimage.dk Follow me at twitter.com/tomasnorre From tobias.liebig at typo3.org Tue Feb 12 17:48:22 2013 From: tobias.liebig at typo3.org (Tobias Liebig) Date: Tue, 12 Feb 2013 17:48:22 +0100 Subject: [TYPO3-dev] Ideas for Google Summer of Code In-Reply-To: References: Message-ID: Hej Philipp, Am 12.02.2013 um 11:19 schrieb Philipp Gampe : > Just an idea: > > Let a student work on a next-gen TER which combines Flow and CMS > extensions/packages? > Maybe based on composer package repository, but with integration into > existing T3o infrastructure. > I am just not sure if the workload can be handled within a three month > period. Maybe its possible to spilt this into smaller steps and thus separated projects/ideas. For example (spontaneous, without any deeper conceptional thinking of it; you might be deeper into this stuff): * extend the EM to be able to fetch from git repository and/or using composer (beside of the current TER way to fetch/download extensions) * the package repository itself (i guess this will be something like packagist?) * maybe an "git/github to TER" service (webhook on github triggers upload to TER or triggers TER to "pull" the extension itself?) did you already talked to one of the Flow guys what their concept is? I think julle did the composer stuff for Flow, right? Beside of that: I really like the idea. Please follow it and try to make it "doable" :-) kind regards Tobias -- Tobias Liebig TYPO3 Core Team member TYPO3 .... inspiring people to share! Get involved: typo3.org http://bit.ly/supportTYPO3 From tobias.liebig at typo3.org Tue Feb 12 18:01:59 2013 From: tobias.liebig at typo3.org (Tobias Liebig) Date: Tue, 12 Feb 2013 18:01:59 +0100 Subject: [TYPO3-dev] Ideas for Google Summer of Code In-Reply-To: References: Message-ID: Thanks for the hint, Olivier. I'll check that. Am 12.02.2013 um 10:14 schrieb Olivier Dobberkau : > Am 09.02.13 17:07, schrieb Tobias Liebig: > >> This is why I ask you to collect and suggest ideas for possible GSoC-Projects. >> We created a wiki page [2] and ask *you* to fill this with your ideas using the provided template. > > if you need more inspiration for ideas: > > http://wiki.typo3.org/T3A-budget-ideas-2013 > > olivier > _______________________________________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev -- Tobias Liebig TYPO3 Core Team member TYPO3 .... inspiring people to share! Get involved: typo3.org http://bit.ly/supportTYPO3 From philipp.gampe at typo3.org Tue Feb 12 18:05:54 2013 From: philipp.gampe at typo3.org (Philipp Gampe) Date: Tue, 12 Feb 2013 18:05:54 +0100 Subject: [TYPO3-dev] Ideas for Google Summer of Code References: Message-ID: Hi Tobias, Tobias Liebig wrote: > Maybe its possible to spilt this into smaller steps and thus separated > projects/ideas. > > For example (spontaneous, without any deeper conceptional thinking of it; > you might be deeper into this stuff): > * extend the EM to be able to fetch > from git repository and/or using composer (beside of the current TER way > to fetch/download extensions) This can be done rather fast AFAICS, IMHO this is not a "full" project. > * the package repository itself (i guess > this will be something like packagist?) This depends heavily how much of the packagist/jQuery repository code is reused. That can vary between a day and a few weeks. This depends also on how much further work you want to put into it (e.g. various admin panels). > * maybe an "git/github to TER" > service (webhook on github triggers upload to TER or triggers TER to > "pull" the extension itself?) This depends if you want to tune the existing TER or if you want to replace it altogether. Best regards -- Philipp Gampe ? PGP-Key 0AD96065 ? TYPO3 UG Bonn/K?ln Documentation ? linkvalidator TYPO3 .... inspiring people to share! From info at cybercraft.de Wed Feb 13 01:19:35 2013 From: info at cybercraft.de (JoH asenau) Date: Wed, 13 Feb 2013 01:19:35 +0100 Subject: [TYPO3-dev] TypoScript TSFE data array and Fluidtemplate In-Reply-To: References: Message-ID: Am 19.12.2011 16:26, schrieb Steffen M?ller: > Hi. > > On 14.12.2011 12:52 Helmut Hummel wrote: >> >> But you could create a small extension implementing this hook: >> >> $TYPO3_CONF_VARS['SC_OPTIONS']['tslib/class.tslib_content.php']['getData'] >> >> >> so that the following could work: >> >> fe_user = TEXT >> fe_user.data = globalArray:TSFE|fe_user|user >> > > I played around with this a while. > > Unfortunately your suggestion won't work. The value from fe_user is > parsed with stdWrap which always returns string. So with your example I > get $value='Array'; This is due to the fact that variables in FLUIDTEMPLATE are passed through cObjGetSingle, which is silently converting arrays into the string "Array" due to the usage of $content .= blah Since any line dealing with $content inside cObjGetSingle is doing it like that, you will always get a string. On the other hand stdWrap alone would happily provide you with the desired array, so IMHO the variables section of FLUIDTEMPLATE is buggy, since it can not deal with stdWrap without assigning a full cObject. Usually both should be working: variables { myvariable = WHATEVER myvariable.field = arrayfield myvariable2.field = arrayfield } But with the current implementation the first one will give you "Array" and the second one will be ignored, which makes it impossible to hand over datasets to make use of the really sophisticated FLUID functionality. I can provide a fix for that, if necessary. What do you think? Cheers Joey -- Wenn man keine Ahnung hat: Einfach mal Fresse halten! (If you have no clues: simply shut your gob sometimes!) Dieter Nuhr, German comedian Xing: http://contact.cybercraft.de Twitter: http://twitter.com/bunnyfield TYPO3 cookbook (2nd edition): http://www.typo3experts.com From Mohammed.Rebai at cspq.gouv.qc.ca Wed Feb 13 16:07:24 2013 From: Mohammed.Rebai at cspq.gouv.qc.ca (Mohammed.Rebai at cspq.gouv.qc.ca) Date: Wed, 13 Feb 2013 15:07:24 +0000 Subject: [TYPO3-dev] limit login attempts to the backend Message-ID: Hi, I'm trying to develop some modifications to TYPO3 to limit the number of login attempts. For example, when i define a limit of 5 attempts, after 5 failure to login to the backend, the account will be suspended during an hour. Is it possible to develop the functionality in TYPO3 ? is there a hook I can use ? or a service ? Thank you ________________________________ Ce message est confidentiel et est ? l'usage exclusif du destinataire identifi? ci-dessus. Toute autre personne est, par les pr?sentes, avis?e qu'il lui est strictement interdit de le diffuser, de le distribuer, d'en d?voiler le contenu ou de le reproduire. Si vous avez re?u cette communication par erreur, veuillez en informer l'exp?diteur par courrier ?lectronique imm?diatement et d?truire l'original de ce message ainsi que toute copie. ________________________________ From tobias.liebig at typo3.org Wed Feb 13 16:11:51 2013 From: tobias.liebig at typo3.org (Tobias Liebig) Date: Wed, 13 Feb 2013 16:11:51 +0100 Subject: [TYPO3-dev] Ideas for Google Summer of Code In-Reply-To: References: Message-ID: Hej Philipp, as Robert wrote in the core list today [1] Rens is going to work on the new PackageBuilder. I think this also affects your idea about using composer for the next-fen TER. Maybe you both could get in touch and talk about if both are going into the same direction and if it could make sense to propose a sub-project (like the EM-thing?) as a GSoC project. However, i think GSoC might also be a good opportunity to let "outsiders" (students, which might not know the TYPO3 world yet, but might also be a 'potential new contributer') work on certain parts of a project, which then might help us to get a different point of view to a solution. regards tobias [1] http://forum.typo3.org/index.php/t/194349/ Am 12.02.2013 um 18:05 schrieb Philipp Gampe : > Hi Tobias, > > Tobias Liebig wrote: > >> Maybe its possible to spilt this into smaller steps and thus separated >> projects/ideas. >> >> For example (spontaneous, without any deeper conceptional thinking of it; >> you might be deeper into this stuff): >> * extend the EM to be able to fetch >> from git repository and/or using composer (beside of the current TER way >> to fetch/download extensions) > > This can be done rather fast AFAICS, IMHO this is not a "full" project. > >> * the package repository itself (i guess >> this will be something like packagist?) > > This depends heavily how much of the packagist/jQuery repository code is > reused. That can vary between a day and a few weeks. > This depends also on how much further work you want to put into it (e.g. > various admin panels). > >> * maybe an "git/github to TER" >> service (webhook on github triggers upload to TER or triggers TER to >> "pull" the extension itself?) > > This depends if you want to tune the existing TER or if you want to replace > it altogether. > > Best regards > -- > Philipp Gampe ? PGP-Key 0AD96065 ? TYPO3 UG Bonn/K?ln > Documentation ? linkvalidator > TYPO3 .... inspiring people to share! > > _______________________________________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev -- Tobias Liebig TYPO3 Core Team member TYPO3 .... inspiring people to share! Get involved: typo3.org http://bit.ly/supportTYPO3 From tobias.liebig at typo3.org Wed Feb 13 16:34:45 2013 From: tobias.liebig at typo3.org (Tobias Liebig) Date: Wed, 13 Feb 2013 16:34:45 +0100 Subject: [TYPO3-dev] Ideas for Google Summer of Code In-Reply-To: References: Message-ID: Hej, Am 12.02.2013 um 18:05 schrieb Philipp Gampe : > >> Maybe its possible to spilt this into smaller steps and thus separated >> projects/ideas. >> >> For example (spontaneous, without any deeper conceptional thinking of it; >> you might be deeper into this stuff): >> * extend the EM to be able to fetch >> from git repository and/or using composer (beside of the current TER way >> to fetch/download extensions) > > This can be done rather fast AFAICS, IMHO this is not a "full" project. > >> * the package repository itself (i guess >> this will be something like packagist?) > > This depends heavily how much of the packagist/jQuery repository code is > reused. That can vary between a day and a few weeks. A student could (when the possible mentor suggests that and think it would make sense) also combine multiple ideas for his project proposal. In that sense it might make sense to have more, but smaller "Ideas", which could be combined, if it makes sense and if the student has enough experience with e.g. TYPO3. Some of the ideas/projects might be implemented fast, if done by one of us. But that's not what the GSoC is about. I think it's also about giving the student the chance to get involved into our community. > This depends also on how much further work you want to put into it (e.g. > various admin panels). The "idea" could have a flexible "goal", it's could be an "inspiration" for the student, so he could suggest a concrete project based on his own concept. > >> * maybe an "git/github to TER" >> service (webhook on github triggers upload to TER or triggers TER to >> "pull" the extension itself?) > > This depends if you want to tune the existing TER or if you want to replace > it altogether. In my personal opinion: It's easier to get something done/ready, if you don't have many dependencies on other (projects/people) and if you do small steps, one by one. regards tobias -- Tobias Liebig TYPO3 Core Team member TYPO3 .... inspiring people to share! Get involved: typo3.org http://bit.ly/supportTYPO3 From jan.kornblum at gmx.de Wed Feb 13 23:25:42 2013 From: jan.kornblum at gmx.de (Jan Kornblum) Date: Wed, 13 Feb 2013 23:25:42 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager References: Message-ID: This should get back again (Listview / Get Extensions): + Last Updated + Author + System / local From typo3 at kay-strobach.de Thu Feb 14 08:49:25 2013 From: typo3 at kay-strobach.de (Kay Strobach) Date: Thu, 14 Feb 2013 08:49:25 +0100 Subject: [TYPO3-dev] limit login attempts to the backend In-Reply-To: References: Message-ID: Hello Mohammed, yes there is a hook, in the function which authenticates the user. Sadly i can't remember how the function was exactly named :( I think it was directly after interating over the auth services :) Regards Kay Am 13.02.13 16:07, schrieb Mohammed.Rebai at cspq.gouv.qc.ca: > Hi, > > I'm trying to develop some modifications to TYPO3 to limit the number of login attempts. For example, when i define a limit of 5 attempts, after 5 failure to login to the backend, the account will be suspended during an hour. > > Is it possible to develop the functionality in TYPO3 ? is there a hook I can use ? or a service ? > > Thank you > > ________________________________ > Ce message est confidentiel et est ? l'usage exclusif du destinataire identifi? ci-dessus. Toute autre personne est, par les pr?sentes, avis?e qu'il lui est strictement interdit de le diffuser, de le distribuer, d'en d?voiler le contenu ou de le reproduire. Si vous avez re?u cette communication par erreur, veuillez en informer l'exp?diteur par courrier ?lectronique imm?diatement et d?truire l'original de ce message ainsi que toute copie. > ________________________________ > -- http://www.kay-strobach.de - Open Source Rocks TYPO3 .... inspiring people to share! Get involved: http://typo3.org Answer was useful - feel free to donate: - https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=KPM9NAV73VDF2 - https://flattr.com/profile/kaystrobach From tomasnorre at gmail.com Thu Feb 14 14:04:02 2013 From: tomasnorre at gmail.com (Tomas Norre Mikkelsen) Date: Thu, 14 Feb 2013 14:04:02 +0100 Subject: [TYPO3-dev] Leaver 'article' out of URL - RealURL / tt_news Message-ID: Hi, I have problem with RealURL and tt_news, I want to leave out 'article' of the url like this: http://domain.ni/press/singleview/article/new-website-born/ should be: http://domain.ni/press/singleview/new-website-born/ According to following links: 1) http://stackoverflow.com/questions/9617293/tt-news-and-realurl-shorten-url-of-news-article 2) http://wiki.typo3.org/Realurl/manual#Example:_.22fixedPostVars.22 This could be fixed with fixedPostVars, but mine is not working. I have following configuration: 53 = singleview(pid) 'fixedPostVars' => array( '53' => array( array( 'GETvar' => 'tx_ttnews[tt_news]', 'lookUpTable' => array( 'table' => 'tt_news', 'id_field' => 'uid', 'alias_field' => 'title', 'addWhereClause' => ' AND NOT deleted', 'useUniqueCache' => 1, 'useUniqueCache_conf' => array( 'strtolower' => 1, 'spaceCharacter' => '-', ), ), ), ), ), Any hints on what could be missing? When using config as above link looks like this. http://domain.ni/press/singleview/?tx_ttnews%5Btt_news%5D=99&cHash=43cfb05bc08707a86bb7582fc3c17d29 So the link is not rewritten. :/ -- Best Regards Tomas Norre Mikkelsen TYPO3 Profile: http://forge.typo3.org/users/4289 TYPO3 Developer @ netimage.dk Follow me at twitter.com/tomasnorre From invadercyg at gmail.com Thu Feb 14 14:07:58 2013 From: invadercyg at gmail.com (Anders Gissel) Date: Thu, 14 Feb 2013 14:07:58 +0100 Subject: [TYPO3-dev] =?iso-8859-1?q?Extbase=3A_Setting_relational_field_to?= =?iso-8859-1?q?_empty_using_frontend=B4?= Message-ID: Hey y'all, I'm building an Extbase-extension (6.0.1), and my model has a field that relates to another table using a simple dropdown. The user can then select a single value, and all is fine. However: once the user has selected (and saved) a value, he can't empty the field again... I've added an empty value to both the frontend selector and the TCA, but apparently setting an empty value is the same as selecting nothing at all. Therefore, the only way to empty the field is to do it through the backend. Selecting a different value works just fine, but obviously that's not what I'm after. My question then is: how do I empty the field from the frontend? Once the data reaches the controller's updateAction() it has already been processed, so how do I go about it? Can anyone recommend any material on the subject? Best regards, Anders From dmitry.dulepov at gmail.com Thu Feb 14 15:35:36 2013 From: dmitry.dulepov at gmail.com (Dmitry Dulepov) Date: Thu, 14 Feb 2013 16:35:36 +0200 Subject: [TYPO3-dev] Leaver 'article' out of URL - RealURL / tt_news In-Reply-To: References: Message-ID: Hi! Tomas Norre Mikkelsen wrote: > Any hints on what could be missing? When using config as above link > looks like this. > > http://domain.ni/press/singleview/?tx_ttnews%5Btt_news%5D=99&cHash=43cfb05bc08707a86bb7582fc3c17d29 > > > So the link is not rewritten. :/ Configuration looks ok to me. Do you have multiple domains? May be, it is placed in the wrong domain? -- Dmitry Dulepov TYPO3 CMS core & security teams member Simplicity Crocodiles will save the world. From tomasnorre at gmail.com Thu Feb 14 15:57:06 2013 From: tomasnorre at gmail.com (Tomas Norre Mikkelsen) Date: Thu, 14 Feb 2013 15:57:06 +0100 Subject: [TYPO3-dev] Leaver 'article' out of URL - RealURL / tt_news In-Reply-To: References: Message-ID: On 02/14/2013 03:35 PM, Dmitry Dulepov wrote: > Hi! > Configuration looks ok to me. Do you have multiple domains? May be, it > is placed in the wrong domain? It is multi-domain site. And I've got following config: $GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['realurl'] = array( 'domain1.tld' => 'domain.tld', 'domain2.tld' => 'domain.tld', 'domain.tld' => arrray( 'init' => array(...), 'pagePath' => array(...), 'fileName' => array(...), 'preVars' => array(...), 'fixedPostVars' => array('as shown in previous'), ), ); -- Best Regards Tomas Norre Mikkelsen TYPO3 Profile: http://forge.typo3.org/users/4289 TYPO3 Developer @ netimage.dk Follow me at twitter.com/tomasnorre From lsascha at gmail.com Thu Feb 14 16:58:15 2013 From: lsascha at gmail.com (Sascha) Date: Thu, 14 Feb 2013 16:58:15 +0100 Subject: [TYPO3-dev] =?utf-8?q?_sorting_IRRE_in_FlexForm?= Message-ID: Hello Everyone. I hope someone can help me with my (small?) problem. i currently have a Extbase model that can added multiple times into a FlexForm. I do this with the following FlexForm part. inline tx_extension_domain_model_images sorting 9999 1 1 1 1 0 1 1 1 1 1 1 both So far everything works without any problem. But the sorting i make in the FlexForm is not saved in the database. Maybe it ignores the definiton of I noticed that it saves the sorting in an XML inside the tt_content database-table. It looks like this: 20,21 And inside the are the two IDs of the Objects i added. And when i change the sorting it changes in the XML too. But not in the "sorting" field in the database. That way i can not read the sorting when i use Extbase. How can i solve this? Many thanks in advance. From oliver.hader at typo3.org Thu Feb 14 17:08:31 2013 From: oliver.hader at typo3.org (Oliver Hader) Date: Thu, 14 Feb 2013 17:08:31 +0100 Subject: [TYPO3-dev] [TYPO3-core] Announcing TYPO3 CMS 4.5.23, 4.6.16, 4.7.8 and 6.0.2 Message-ID: Dear TYPO3 World, The TYPO3 Community has just released TYPO3 CMS versions 4.5.23, 4.6.16, 4.7.8 and 6.0.2, which are now ready for you to download. These versions are maintenance releases and contain bug fixes only. The packages can be downloaded here: http://typo3.org/download/packages/ For details about the release, please see: http://typo3.org/news/article/typo3-cms-4523-4616-478-and-602-released/ MD5 checksums: 32878935d2857f7d7ac11579b765c281 blankpackage-4.5.23.tar.gz 4bf734861eb5adbc31f899e80a7d4944 blankpackage-4.5.23.zip b4c5d4c887e0ec98f08da997757bb413 dummy-4.5.23.tar.gz b2bed05dae92936dfd6a3bcd902de4f9 dummy-4.5.23.zip b6dcaf762224570f6b84b60aa43764be introductionpackage-4.5.23.tar.gz fb9f1f74be276937fdc64a59f9a10a5c introductionpackage-4.5.23.zip 545e4cdf772d04f411992621edc95307 typo3_src+dummy-4.5.23.zip 6a59f05839815109dec21a6e769ca54e typo3_src-4.5.23.tar.gz 3fd6bde829d1901fe2e42f78bdac5a7a typo3_src-4.5.23.zip 326585989d19d1b9de4227f43bc0a51d blankpackage-4.6.16.tar.gz 661cf65d2cbbe34ef6ba9af48ff4b48b blankpackage-4.6.16.zip 18396f351176d9615e124f1d91d87e64 dummy-4.6.16.tar.gz c387a89b123aef2432e588b5bf56a7eb dummy-4.6.16.zip c3585ab038a7866732bcef7685fe6889 typo3_src+dummy-4.6.16.zip a9bba952f62eb82312d0513468babffe typo3_src-4.6.16.tar.gz acbcd05ff13cedef3a4c502cd05369ec typo3_src-4.6.16.zip b69ed8fcf0edfde506cdd5d088d39229 blankpackage-4.7.8.tar.gz 0423a55dbe7eafda6e0793430706bf7e blankpackage-4.7.8.zip 856f46dc450034af186497d6114191ab dummy-4.7.8.tar.gz 07560e5cd89f6057e6978a44aa0fea65 dummy-4.7.8.zip ff12e5b7298780af0f6cddd1e5d5cefc typo3_src+dummy-4.7.8.zip 100adacf39f58c1cfd3c34137a5cbfd1 typo3_src-4.7.8.tar.gz a94773fa83fd10b4c6ae215cef56aef5 typo3_src-4.7.8.zip e61f9433278266d4d5bc2d52efda06f9 blankpackage-6.0.2.tar.gz 3408123f29c7d550ccc4ad52f980f098 blankpackage-6.0.2.zip ddafc3525ba3f890e364100b841cfcd3 dummy-6.0.2.tar.gz 53b4b1bbbd899f7ea44388fb34b0b511 dummy-6.0.2.zip ff37e3d1a84e5d3009b33ad30af2e2f4 governmentpackage-6.0.2.tar.gz b6839fcb87a655399c1a4c9c7e88a51a governmentpackage-6.0.2.zip aa38852b5b7f3ae3c9ef72b2d05b7c4d introductionpackage-6.0.2.tar.gz 1410321d1b76c936c97d46ff236387b3 introductionpackage-6.0.2.zip 848cf9a8b2ea05f3e1ace971d5bed388 typo3_src+dummy-6.0.2.zip ba0102330a08f9dcd330efca97234280 typo3_src-6.0.2.tar.gz 75ab14b99495848b4a7610dcd9db5c35 typo3_src-6.0.2.zip Best regards, Oliver -- Oliver Hader TYPO3 CMS Core Team Leader TYPO3 .... inspiring people to share! Get involved: http://typo3.org From tomasnorre at gmail.com Thu Feb 14 21:06:54 2013 From: tomasnorre at gmail.com (Tomas Norre Mikkelsen) Date: Thu, 14 Feb 2013 21:06:54 +0100 Subject: [TYPO3-dev] Multiple instance of a field in backend. Message-ID: Hi, I'm about to create an new extension which extends tt_news, yes I know its not extbase etc., but need it. =/ Like the extension "jg_youtubeinnews" which gives the marker ###YOUTUBEVIDEO### and create an extra db-field in tt_news with HTML for replacement of the marker. I want to extend this function such I can have multiple markers. A little like how the Powermail creates multiple fields and fields set. I'm thinking something like this: MARKER1: ###YOUTUBE_VIDEO### HTML1:

YouTube Video-HTML

MARKER2: ###FLICKR_GALLERY### HTML2:

Flickr Gallery-HTML

MARKER3: ###VIMEO_VIDEO### HTML3:

Vimeo Video-HTML

MARKER4: ###EXTRA_MARKER### HTML4:

Extra Marker-HTML

I want to create multiple markers, not necessarily the same amount of marker at each news, it can variate. So I consider something like: ext_tables.sql /* Create an extra field with comma seperated list of relations-uids with ref to embedded_content-table. CREATE TABLE tt_news ( tx_embedded_content text NOT NULL ); CREATE TABLE embedded_content ( ... uid int embedded_content_html text NOT NULL tt_news_uid int ... ); Any suggestions, hints on how to create this? Honestly I don't know what to look for so perhaps a small hint could be enough. Hope someone could point me into the right direction. -- Best Regards Tomas Norre Mikkelsen TYPO3 Profile: http://forge.typo3.org/users/4289 TYPO3 Developer @ netimage.dk Follow me at twitter.com/tomasnorre From kraftb at kraftb.at Thu Feb 14 21:30:39 2013 From: kraftb at kraftb.at (Bernhard Kraft) Date: Thu, 14 Feb 2013 20:30:39 +0000 (UTC) Subject: [TYPO3-dev] Multiple instance of a field in backend. References: Message-ID: Hello ! Am Thu, 14 Feb 2013 21:06:54 +0100 schrieb Tomas Norre Mikkelsen: > I want to extend this function such I can have multiple markers. A > little like how the Powermail creates multiple fields and fields set. Powermail uses IRRE (Inline relational record editing): http://docs.typo3.org/typo3cms/TCAReference/Reference/Columns/Inline/ Index.html Or search for "TYPO3 IRRE" on the web. Another approach would be to use "Flexforms": http://docs.typo3.org/typo3cms/TCAReference/Reference/Columns/Flex/ Index.html The UI differences are minimal. The architectural differences are: * Flex uses one DB field storing field-values in XML * IRRE uses real tables feel free to decide, greetings, Bernhard From Trotzek at citeq.de Fri Feb 15 08:00:07 2013 From: Trotzek at citeq.de (Uwe Trotzek) Date: Fri, 15 Feb 2013 08:00:07 +0100 Subject: [TYPO3-dev] Antw: sorting IRRE in FlexForm In-Reply-To: References: Message-ID: Hi Sascha, i don't think you can use the foreign_sortby option for your frontend controller. It is used to sort the available items section in the backend-flexform. If you want to provide an additional field to the user to manually change the sorting direction, you have to add something like this: select ascending ascending descending descending 1 you can use the selected value easily in your controller by using $this->settings['flexform']['mysorting'] kind regards Uwe >>> Sascha 14.02.2013 16:58 >>> Hello Everyone. I hope someone can help me with my (small?) problem. i currently have a Extbase model that can added multiple times into a FlexForm. I do this with the following FlexForm part. inline tx_extension_domain_model_images sorting 9999 1 1 1 1 0 1 1 1 1 1 1 both So far everything works without any problem. But the sorting i make in the FlexForm is not saved in the database. Maybe it ignores the definiton of I noticed that it saves the sorting in an XML inside the tt_content database-table. It looks like this: 20,21 And inside the are the two IDs of the Objects i added. And when i change the sorting it changes in the XML too. But not in the "sorting" field in the database. That way i can not read the sorting when i use Extbase. How can i solve this? Many thanks in advance. _______________________________________________ TYPO3-dev mailing list TYPO3-dev at lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev From t3ng at bernd-wilke.net Fri Feb 15 08:08:03 2013 From: t3ng at bernd-wilke.net (bernd wilke) Date: Fri, 15 Feb 2013 08:08:03 +0100 Subject: [TYPO3-dev] sorting IRRE in FlexForm In-Reply-To: References: Message-ID: Am 14.02.2013 16:58, schrieb Sascha: > Hello Everyone. > > I hope someone can help me with my (small?) problem. > > i currently have a Extbase model that can added multiple times into a > FlexForm. > > So far everything works without any problem. > But the sorting i make in the FlexForm is not saved in the database. > Maybe it ignores the definiton of > > I noticed that it saves the sorting in an XML inside the tt_content > database-table. > It looks like this: > > > > > > > > 20,21 > > > > > > > > And inside the are the two IDs of the Objects i > added. And when i change the sorting it changes in the XML too. But not > in the "sorting" field in the database. you may use this kind of ordering in your query: $orderBy = 'field(uid,' . $orderedUidList . ')'; > That way i can not read the sorting when i use Extbase. I think this information should be also available in extbase. bernd -- http://www.pi-phi.de/cheatsheet.html From tomasnorre at gmail.com Fri Feb 15 08:10:55 2013 From: tomasnorre at gmail.com (Tomas Norre Mikkelsen) Date: Fri, 15 Feb 2013 08:10:55 +0100 Subject: [TYPO3-dev] Multiple instance of a field in backend. In-Reply-To: References: Message-ID: Hi, On 02/14/2013 09:30 PM, Bernhard Kraft wrote: >> I want to extend this function such I can have multiple markers. A >> little like how the Powermail creates multiple fields and fields set. > > Powermail uses IRRE (Inline relational record editing): > http://docs.typo3.org/typo3cms/TCAReference/Reference/Columns/Inline/ > Index.html > > Or search for "TYPO3 IRRE" on the web. > > Another approach would be to use "Flexforms": > http://docs.typo3.org/typo3cms/TCAReference/Reference/Columns/Flex/ > Index.html > > The UI differences are minimal. The architectural differences are: > * Flex uses one DB field storing field-values in XML > * IRRE uses real tables That was exactly that kind of hints I was looking for =) Thank you very much. -- Best Regards Tomas Norre Mikkelsen TYPO3 Profile: http://forge.typo3.org/users/4289 TYPO3 Developer @ netimage.dk Follow me at twitter.com/tomasnorre From info at cretection.eu Fri Feb 15 08:15:27 2013 From: info at cretection.eu (Starck Jonathan) Date: Fri, 15 Feb 2013 08:15:27 +0100 Subject: [TYPO3-dev] RealUrl Message-ID: Hi, is it possible to set the variable 'rootpage_id' in my RealUrl configuration dynamically? I found an interesting approach: $RootPID = array( 'www . domainname . de' => '2', 'www . domainname . de' => '22', 'www . domainname . de' => '45' ); 'rootpage_id' => $RootPID[$_SERVER['HTTP_HOST']] But this is not really dynamic. Regards Jonathan From lsascha at gmail.com Fri Feb 15 10:06:38 2013 From: lsascha at gmail.com (Sascha) Date: Fri, 15 Feb 2013 10:06:38 +0100 Subject: [TYPO3-dev] =?utf-8?q?_Re=3A_sorting_IRRE_in_FlexForm?= References: Message-ID: Hello and thank you for all your ideas. The problem here is that the backend-user could add the images in a custom order inside the FlexForm and there is no other field that could be used for sorting. The Uid order would also not represent the actual order of the elements. And even if i use some custom field where i could only think of a integer where the backend-user needs to enter an integer to set the position of every element in the list that would be really annoying and the order in frontend and backend would always be different except when using the list-view. @bernd If i understand your posting correctly you suggest that i use the uid-list of the xml inside the element in tt_content to correctly sort the extbase query? How should i get the uid-list from that xml inside the database when extbase does not currently provide that information? I hope there is a solution for this or will get added in a future typo3 release. Thanks again with best regards Sascha From tomasnorre at gmail.com Fri Feb 15 15:23:06 2013 From: tomasnorre at gmail.com (Tomas Norre Mikkelsen) Date: Fri, 15 Feb 2013 15:23:06 +0100 Subject: [TYPO3-dev] New extension - Review needed Message-ID: Hi, Just created a new TYPO3 extension extending tt_news with extra markers. Need a review. Security comments etc is very velcome! http://forge.typo3.org/projects/extension-news_embedded_content -- Best Regards Tomas Norre Mikkelsen TYPO3 Profile: http://forge.typo3.org/users/4289 TYPO3 Developer @ netimage.dk Follow me at twitter.com/tomasnorre From scecere at krur.com Fri Feb 15 19:19:29 2013 From: scecere at krur.com (Stefano Cecere) Date: Fri, 15 Feb 2013 19:19:29 +0100 Subject: [TYPO3-dev] =?iso-8859-1?q?_Re=3A__Extbase=3A_Setting_relational_?= =?iso-8859-1?q?field_to_empty_using_frontend=B4?= In-Reply-To: References: Message-ID: Hi Anders i have the same problem i explained it (with a solution i found) here http://forum.typo3.org/index.php/t/194225/ note : the typo3v4mvc newsgroup is the right place for Extbase/Fluid topics ciao On 14/02/13 14:07, Anders Gissel wrote: > Hey y'all, > > I'm building an Extbase-extension (6.0.1), and my model has a field that > relates to another table using a simple dropdown. The user can then > select a single value, and all is fine. > > However: once the user has selected (and saved) a value, he can't empty > the field again... I've added an empty value to both the frontend > selector and the TCA, but apparently setting an empty value is the same > as selecting nothing at all. Therefore, the only way to empty the field > is to do it through the backend. Selecting a different value works just > fine, but obviously that's not what I'm after. > > My question then is: how do I empty the field from the frontend? Once > the data reaches the controller's updateAction() it has already been > processed, so how do I go about it? Can anyone recommend any material on > the subject? > > > Best regards, > Anders -- -- --- ----- ------- Stefano Cecere KRUR studio - http://krur.com From mail at ringerge.org Sat Feb 16 07:51:39 2013 From: mail at ringerge.org (Georg Ringer) Date: Sat, 16 Feb 2013 07:51:39 +0100 Subject: [TYPO3-dev] New extension - Review needed In-Reply-To: References: Message-ID: Hi, important information: If there are security issues, never contact the author of the extension but always and only the TYPO3 Security team. see http://typo3.org/teams/security thanks Georg Ringer Leader TYPO3 Security Team From tomita.militaru at gmail.com Sat Feb 16 09:19:32 2013 From: tomita.militaru at gmail.com (=?UTF-8?B?VG9tacWjxIMgTUlMSVRBUlU=?=) Date: Sat, 16 Feb 2013 10:19:32 +0200 Subject: [TYPO3-dev] Extbase extension performance Message-ID: Hello, I am building an extbase extension that imports from a CSV file > 100.000 records, reading line by line and adding object by object to the repository. But that never finishes as it takes way too long, 30 k records in 20 minutes and still running. Is it a better way to do it or should I just switch to the classic exec_INSERTquery functions as it worked much better this way than using extbase. Thanks! From franssaris at gmail.com Sat Feb 16 09:47:52 2013 From: franssaris at gmail.com (Frans Saris) Date: Sat, 16 Feb 2013 09:47:52 +0100 Subject: [TYPO3-dev] Extbase extension performance In-Reply-To: References: Message-ID: Hi Tomi??, Have you debugged to see where most of the delay occurs? A plain insertinto will definitely be faster because you don't have the object overhead. Gr. Frans Op 16 feb. 2013 09:20 schreef "Tomi?? MILITARU" het volgende: > Hello, > > I am building an extbase extension that imports from a CSV file > 100.000 > records, reading line by line and adding object by object to the > repository. But that never finishes as it takes way too long, 30 k records > in 20 minutes and still running. > Is it a better way to do it or should I just switch to the classic > exec_INSERTquery functions as it worked much better this way than using > extbase. > > Thanks! > _______________________________________________ > 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 Sat Feb 16 09:51:55 2013 From: tomita.militaru at gmail.com (=?UTF-8?B?VG9tacWjxIMgTUlMSVRBUlU=?=) Date: Sat, 16 Feb 2013 10:51:55 +0200 Subject: [TYPO3-dev] Extbase extension performance In-Reply-To: References: Message-ID: On Sat, Feb 16, 2013 at 10:47 AM, Frans Saris wrote: > Hi Tomi??, > Hi Frans > > Have you debugged to see where most of the delay occurs? > The problem is at persistAll(), so when storing the objects in the database. > A plain insertinto will definitely be faster because you don't have the > object overhead. > True, but I thought I would be safe with under 100 k objects, it's a pitty to return to insertinto's > > Gr. Frans > Op 16 feb. 2013 09:20 schreef "Tomi?? MILITARU" < > tomita.militaru at gmail.com> > het volgende: > > > Hello, > > > > I am building an extbase extension that imports from a CSV file > 100.000 > > records, reading line by line and adding object by object to the > > repository. But that never finishes as it takes way too long, 30 k > records > > in 20 minutes and still running. > > Is it a better way to do it or should I just switch to the classic > > exec_INSERTquery functions as it worked much better this way than using > > extbase. > > > > Thanks! > > _______________________________________________ > > 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 tomasnorre at gmail.com Sat Feb 16 10:37:36 2013 From: tomasnorre at gmail.com (Tomas Norre Mikkelsen) Date: Sat, 16 Feb 2013 10:37:36 +0100 Subject: [TYPO3-dev] New extension - Review needed In-Reply-To: References: Message-ID: On 02/16/2013 07:51 AM, Georg Ringer wrote: > important information: If there are security issues, never contact the > author of the extension but always and only the TYPO3 Security team. > see http://typo3.org/teams/security I understand, its my first public extension, so where not into the procedure, sorry. I'll contact the security team my self, with the questions i'm having regarding my extension. -- Best Regards Tomas Norre Mikkelsen TYPO3 Profile: http://forge.typo3.org/users/4289 TYPO3 Developer @ netimage.dk Follow me at twitter.com/tomasnorre From me at henjohoeksma.nl Sat Feb 16 11:21:13 2013 From: me at henjohoeksma.nl (Henjo Hoeksma | Stylence) Date: Sat, 16 Feb 2013 11:21:13 +0100 Subject: [TYPO3-dev] =?iso-8859-1?q?Extbase=3A_Setting_relational_field_to?= =?iso-8859-1?q?_empty_using_frontend=B4?= In-Reply-To: References: Message-ID: Like I said in my response to Stefano, it would be better to check in your setter method of your model to check wether something is NULL or not. If it is some fancy checking you need to do, you could write a Domain Utility of Custom Domain Object Validator to do so. Take a look at the validator classes to see what it possible there. When putting this stuff in your controller you are placing domain logic in your application, instead of keeping it in the domain. Doing this you will find yourself repeating code to achieve the same things over and over and you are on a fast track of getting into trouble ;-) Kind regards, Henjo Problems are small because we learned how to deal with them. Problems are big because we need to learn how to deal with them. On Fri, Feb 15, 2013 at 7:19 PM, Stefano Cecere wrote: > Hi Anders > > i have the same problem > i explained it (with a solution i found) here > http://forum.typo3.org/index.**php/t/194225/ > > note : the typo3v4mvc newsgroup is the right place for Extbase/Fluid topics > > ciao > > > > On 14/02/13 14:07, Anders Gissel wrote: > >> Hey y'all, >> >> I'm building an Extbase-extension (6.0.1), and my model has a field that >> relates to another table using a simple dropdown. The user can then >> select a single value, and all is fine. >> >> However: once the user has selected (and saved) a value, he can't empty >> the field again... I've added an empty value to both the frontend >> selector and the TCA, but apparently setting an empty value is the same >> as selecting nothing at all. Therefore, the only way to empty the field >> is to do it through the backend. Selecting a different value works just >> fine, but obviously that's not what I'm after. >> >> My question then is: how do I empty the field from the frontend? Once >> the data reaches the controller's updateAction() it has already been >> processed, so how do I go about it? Can anyone recommend any material on >> the subject? >> >> >> Best regards, >> Anders >> > > > -- > > -- --- ----- ------- > > Stefano Cecere > KRUR studio - http://krur.com > > ______________________________**_________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-**bin/mailman/listinfo/typo3-dev > From luberti at archicoop.it Sun Feb 17 02:33:40 2013 From: luberti at archicoop.it (Ivano Luberti) Date: Sun, 17 Feb 2013 02:33:40 +0100 Subject: [TYPO3-dev] showing error message in the backend Message-ID: Hello, just finished to write a backend extension everything works as expected except of showing result messages in the backend. I have seen from documentation the I have to write something like this for showing flash messages $debugMessage='message text'; $message = t3lib_div::makeInstance('t3lib_FlashMessage', $debugMessage, 'Errore nella notifca della pubblicazione', t3lib_FlashMessage::ERROR); t3lib_FlashMessageQueue::addMessage($message); if i debug the code it seems everything is executed correctly and from documentation seems that nothing has to be done client side. TIA for any suggestion From daniel.siepmann at typo3.org Sun Feb 17 05:20:11 2013 From: daniel.siepmann at typo3.org (Daniel Siepmann) Date: Sun, 17 Feb 2013 05:20:11 +0100 Subject: [TYPO3-dev] showing error message in the backend In-Reply-To: References: Message-ID: Are you using extbase and fluid? Then you can use the ViewHelper do show the FlashMessage. Anyway you have to show the messages. With the above code you just add them. You don't show them. You have to display the messages in the Template. Take a look at the ViewHelper inside typo3/sysext/fluid/Classes/ViewHelper ... -- Daniel Siepmann TYPO3 Editorial Team Co-Leader TYPO3 .... inspiring people to share! Get involved: typo3.org On Sun, Feb 17, 2013 at 2:33 AM, Ivano Luberti wrote: > Hello, just finished to write a backend extension everything works as > expected except of showing result messages in the backend. > I have seen from documentation the I have to write something like this > for showing flash messages > > $debugMessage='message text'; > $message = t3lib_div::makeInstance('t3lib_FlashMessage', > $debugMessage, 'Errore nella notifca della pubblicazione', > t3lib_FlashMessage::ERROR); > > t3lib_FlashMessageQueue::addMessage($message); > > > if i debug the code it seems everything is executed correctly and from > documentation seems that nothing has to be done client side. > > TIA for any suggestion > _______________________________________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev From luberti at archicoop.it Sun Feb 17 09:57:44 2013 From: luberti at archicoop.it (Ivano Luberti) Date: Sun, 17 Feb 2013 09:57:44 +0100 Subject: [TYPO3-dev] showing error message in the backend In-Reply-To: References: Message-ID: Hello Daniel, thanks for you answer. I think my question is not clear enough: Il 17/02/2013 05:20, Daniel Siepmann ha scritto: > Are you using extbase and fluid? > Then you can use the ViewHelper do show the FlashMessage. No I'm not using extabse and fluid. And I'm using TYPO3 4.6.15 > Anyway you have to show the messages. With the above code you just add > them. You don't show them. From this link http://docs.typo3.org/typo3cms/CoreApiReference/ApiOverview/FlashMessages/Index.html I had understood that queing a message is a way to delegate the show action to the backend UI. Since I'm writing an extension that hooks the hide/unhide operation on a record I need a way to show messages without implementig my own backend interface, because the action can be performed in different locations and/or different modules, maybe third party extension backend modules. -- ================================================== 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 xavier at typo3.org Sun Feb 17 10:46:34 2013 From: xavier at typo3.org (Xavier Perseguers) Date: Sun, 17 Feb 2013 10:46:34 +0100 Subject: [TYPO3-dev] RealUrl In-Reply-To: References: Message-ID: Hi, > is it possible to set the variable 'rootpage_id' in my RealUrl configuration dynamically? > > I found an interesting approach: > > $RootPID = array( 'www . domainname . de' => '2', 'www . domainname . de' => '22', 'www . domainname . de' => '45' ); > 'rootpage_id' => $RootPID[$_SERVER['HTTP_HOST']] > > But this is not really dynamic. What do you find not "dynamic" in this approach? The fact that the list of domains is "hardcoded" in the configuration file? Then read an external text file, retrieve this list from somewhere else, ... but keep in mind that you certainly should have some sort of "caching" to prevent you from loosing time there. HTH -- Xavier Perseguers Release Manager TYPO3 4.6 TYPO3 .... inspiring people to share! Get involved: http://typo3.org From xavier at typo3.org Sun Feb 17 10:56:59 2013 From: xavier at typo3.org (Xavier Perseguers) Date: Sun, 17 Feb 2013 10:56:59 +0100 Subject: [TYPO3-dev] Locallang labels with a dot In-Reply-To: References: Message-ID: Hi, > On 4-2-2013 10:16, Rik Willems wrote: >> For a project I came across an extension that used dots (.) in the >> locallang labels. This meant I could not override the values through >> Typoscript setup. I assume this is because of the Typoscript to array >> parsing that is done. > > Yes. locallang labels shouldn't contain dots. This is typically a problem with the Extbase extension kickstarter that generates such files. People tend to rely on defaults and learn it this way. -- Xavier Perseguers Release Manager TYPO3 4.6 TYPO3 .... inspiring people to share! Get involved: http://typo3.org From fsu-lists at cobweb.ch Sun Feb 17 11:15:04 2013 From: fsu-lists at cobweb.ch (=?ISO-8859-1?Q?Fran=E7ois_Suter?=) Date: Sun, 17 Feb 2013 11:15:04 +0100 Subject: [TYPO3-dev] Locallang labels with a dot In-Reply-To: References: Message-ID: Hi Xavier, > This is typically a problem with the Extbase extension kickstarter that > generates such files. People tend to rely on defaults and learn it this way. It's even worse than this, the Core is full of them (look at sysext lang, for example, in file locallang_core.xlf). I know I use dots almost everywhere :-( Cheers -- Francois Suter Cobweb Development Sarl - http://www.cobweb.ch From xavier at typo3.org Sun Feb 17 11:50:03 2013 From: xavier at typo3.org (Xavier Perseguers) Date: Sun, 17 Feb 2013 11:50:03 +0100 Subject: [TYPO3-dev] Locallang labels with a dot In-Reply-To: References: Message-ID: Hi Francois, >> This is typically a problem with the Extbase extension kickstarter that >> generates such files. People tend to rely on defaults and learn it >> this way. > > It's even worse than this, the Core is full of them (look at sysext > lang, for example, in file locallang_core.xlf). I know I use dots almost > everywhere :-( Well, you're not alone... and actually dots in those keys are quite "pretty", perhaps some "compatibility layer" for TS under _LOCAL_LANG could be thought of instead of willing to remove dots from those files. The former should be possible whereas the latter is simply infeasible. Cheers -- Xavier Perseguers Release Manager TYPO3 4.6 TYPO3 .... inspiring people to share! Get involved: http://typo3.org From fsu-lists at cobweb.ch Sun Feb 17 12:11:34 2013 From: fsu-lists at cobweb.ch (=?ISO-8859-1?Q?Fran=E7ois_Suter?=) Date: Sun, 17 Feb 2013 12:11:34 +0100 Subject: [TYPO3-dev] Locallang labels with a dot In-Reply-To: References: Message-ID: Hi, > Well, you're not alone... and actually dots in those keys are quite > "pretty", perhaps some "compatibility layer" for TS under _LOCAL_LANG > could be thought of instead of willing to remove dots from those files. > The former should be possible whereas the latter is simply infeasible. That's a good idea. Removing all dots from existing labels is actually impossible, as it would invalidate all existing translations. Cheers -- Francois Suter Cobweb Development Sarl - http://www.cobweb.ch From daniel.siepmann at typo3.org Sun Feb 17 16:10:27 2013 From: daniel.siepmann at typo3.org (Daniel Siepmann) Date: Sun, 17 Feb 2013 16:10:27 +0100 Subject: [TYPO3-dev] showing error message in the backend In-Reply-To: References: Message-ID: Thanks, I thought you're writing your own backend module I've no experience using FlashMessages in Hooks. But reading the documentation it looks like the backend module you're writing the hook for doesn't render the FlashMassges. Did you add a Message and switch to a Module that will render them? E.g. The Template > TypoScript Object Browser. Perhaps they are shown there. Then you know that adding FlashMessages still works, you just have to show them. Then you just have to show them. Perhaps the paragraph from the documentation will help: > By default flash messages are shown atop the content of a module. However, if needed, you can change where the messages are shown by manipulating a module's template and inserting the ###FLASHMESSAGES### marker. Messages will then replace that marker instead of appearing at the top of the module. > > It is also possible to render a single message directly, instead of adding it to the queue. This makes it possible to display flash messages absolutely anywhere. Here's how this is achieved: >> $message->render(); I would play around a bit or ask in the irc channel: http://typo3.org/support/irc-chat/ Another place to ask would be the core mailinglist. I think the core developers can help, because they have to do the same thing. -- Daniel Siepmann TYPO3 Editorial Team Co-Leader TYPO3 .... inspiring people to share! Get involved: typo3.org On Sun, Feb 17, 2013 at 9:57 AM, Ivano Luberti wrote: > Hello Daniel, thanks for you answer. > I think my question is not clear enough: > > Il 17/02/2013 05:20, Daniel Siepmann ha scritto: > >> Are you using extbase and fluid? >> Then you can use the ViewHelper do show the FlashMessage. > > > No I'm not using extabse and fluid. > And I'm using TYPO3 4.6.15 > > >> Anyway you have to show the messages. With the above code you just add >> them. You don't show them. > > From this link > > http://docs.typo3.org/typo3cms/CoreApiReference/ApiOverview/FlashMessages/Index.html > > I had understood that queing a message is a way to delegate the show action > to the backend UI. > > Since I'm writing an extension that hooks the hide/unhide operation on a > record I need a way to show messages without implementig my own backend > interface, because the action can be performed in different locations and/or > different modules, maybe third party extension backend modules. > > > > -- > ================================================== > 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 > ================================================== > > > _______________________________________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev From luberti at archicoop.it Sun Feb 17 18:22:22 2013 From: luberti at archicoop.it (Ivano Luberti) Date: Sun, 17 Feb 2013 18:22:22 +0100 Subject: [TYPO3-dev] showing error message in the backend In-Reply-To: References: Message-ID: I followed your suggestion and played with the feature. It turned out that there is no way for the message to live outside the instance of t3lib_FlashMessage created in my code. The only to use it is to set the message as a session one (one of the option for the make instance). BTW: the session value is cleared when the reponse page is rendered, so there is no risk that an old messages shows up during the following navigation. I think that the term session is somwhat misused in this case. Thanks for your help. -- ================================================== 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 typo3 at kay-strobach.de Mon Feb 18 13:26:16 2013 From: typo3 at kay-strobach.de (Kay Strobach) Date: Mon, 18 Feb 2013 13:26:16 +0100 Subject: [TYPO3-dev] [TYPO3-core] Skinning / Theming / ... / small 5 question survey Message-ID: [Crosspost with TYPO3.teams.core, surveylink is newsgroup dependend] Hello Guys, as stated already sometime before, I'm working on an easy frontend skin / theme solution. The idea originally came up with TVFramework by Ron Hall, but as there are some problems of acceptance of a TV based skin directory i analyzed other options. I got so far, that i have a working prototype, which is able to inject: - TSConfig - TYPOScript + Constants to a page and the corresponding page with a hook and sadly one xclass. For the future there are some plans: - register skins by simply obeying an convention of directory structure -> allready reached - Fedext compatibility -> allready mostly reached - Backwards compatibility to TVF and Migration assistent - Standardized FCEs (2-4 Columns, see TVF for details) - A skin directory, either on my site, or on TYPO3.org - A skin preview extension -> should work already, as this is compatible to TVF with same hook - A Skin wizard, where you can map html elements with some dynamic stuff like menus -> can be achieved on top of fedext As this is a rather big block of features and i want to keep the skin seletor extension is small as possible this stuff will be seperated in other extensions, which depend on the skin selector. Regarding the name there are some alternative and i gently want to ask you, what i should take ;). Please take the short 5 question survey to help me with development ;) http://de.surveymonkey.com/s/NPJHYZ8 Thanks Kay -- http://www.kay-strobach.de - Open Source Rocks TYPO3 .... inspiring people to share! Get involved: http://typo3.org Answer was useful - feel free to donate: - https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=KPM9NAV73VDF2 - https://flattr.com/profile/kaystrobach From invadercyg at gmail.com Mon Feb 18 21:09:10 2013 From: invadercyg at gmail.com (Anders Gissel) Date: Mon, 18 Feb 2013 21:09:10 +0100 Subject: [TYPO3-dev] =?iso-8859-1?q?Extbase=3A_Setting_relational_field_to?= =?iso-8859-1?q?_empty_using_frontend=B4?= In-Reply-To: References: Message-ID: Hello Henjo, the problem here is that the setter never gets called - if it did, it would empty the field just fine (like the hack'y example by Stefano does). I'll have a look at the validators, but honestly I can't see how a validator would help here. The whole point is that the field should allow empty values (and does, if edited through the backend), but that the model setter /isn't/ actually called. And if the setter isn't called, I can't keep my model logic inside the domain AND fix the problem. Not this way, at least. :-) Best regards, Anders On 16-02-2013 11:21, Henjo Hoeksma | Stylence wrote: > Like I said in my response to Stefano, it would be better to check in your > setter method of your model to check wether something is NULL or not. > If it is some fancy checking you need to do, you could write a Domain > Utility of Custom Domain Object Validator to do so. > > Take a look at the validator classes to see what it possible there. > > When putting this stuff in your controller you are placing domain logic in > your application, instead of keeping it in the domain. > Doing this you will find yourself repeating code to achieve the same things > over and over and you are on a fast track of getting into trouble ;-) > > Kind regards, > > Henjo > > Problems are small because we learned how to deal with them. > Problems are big because we need to learn how to deal with them. > > > On Fri, Feb 15, 2013 at 7:19 PM, Stefano Cecere wrote: > >> Hi Anders >> >> i have the same problem >> i explained it (with a solution i found) here >> http://forum.typo3.org/index.**php/t/194225/ >> >> note : the typo3v4mvc newsgroup is the right place for Extbase/Fluid topics >> >> ciao >> >> >> >> On 14/02/13 14:07, Anders Gissel wrote: >> >>> Hey y'all, >>> >>> I'm building an Extbase-extension (6.0.1), and my model has a field that >>> relates to another table using a simple dropdown. The user can then >>> select a single value, and all is fine. >>> >>> However: once the user has selected (and saved) a value, he can't empty >>> the field again... I've added an empty value to both the frontend >>> selector and the TCA, but apparently setting an empty value is the same >>> as selecting nothing at all. Therefore, the only way to empty the field >>> is to do it through the backend. Selecting a different value works just >>> fine, but obviously that's not what I'm after. >>> >>> My question then is: how do I empty the field from the frontend? Once >>> the data reaches the controller's updateAction() it has already been >>> processed, so how do I go about it? Can anyone recommend any material on >>> the subject? >>> >>> >>> Best regards, >>> Anders >>> >> >> -- >> >> -- --- ----- ------- >> >> Stefano Cecere >> KRUR studio - http://krur.com >> >> ______________________________**_________________ >> 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 invadercyg at gmail.com Mon Feb 18 21:12:08 2013 From: invadercyg at gmail.com (Anders Gissel) Date: Mon, 18 Feb 2013 21:12:08 +0100 Subject: [TYPO3-dev] =?iso-8859-1?q?Extbase=3A_Setting_relational_field_to?= =?iso-8859-1?q?_empty_using_frontend=B4?= In-Reply-To: References: Message-ID: Hello Stefano, your solution looks a bit hack'y, but it also looks like it would work. At least the logic is easily determined, so thanks for that! I'll try crossposting my question in the other newsgroup and see if I'll have more luck there. :-) Best regards, Anders On 15-02-2013 19:19, Stefano Cecere wrote: > Hi Anders > > i have the same problem > i explained it (with a solution i found) here > http://forum.typo3.org/index.php/t/194225/ > > note : the typo3v4mvc newsgroup is the right place for Extbase/Fluid > topics > > ciao > > > On 14/02/13 14:07, Anders Gissel wrote: >> Hey y'all, >> >> I'm building an Extbase-extension (6.0.1), and my model has a field that >> relates to another table using a simple dropdown. The user can then >> select a single value, and all is fine. >> >> However: once the user has selected (and saved) a value, he can't empty >> the field again... I've added an empty value to both the frontend >> selector and the TCA, but apparently setting an empty value is the same >> as selecting nothing at all. Therefore, the only way to empty the field >> is to do it through the backend. Selecting a different value works just >> fine, but obviously that's not what I'm after. >> >> My question then is: how do I empty the field from the frontend? Once >> the data reaches the controller's updateAction() it has already been >> processed, so how do I go about it? Can anyone recommend any material on >> the subject? >> >> >> Best regards, >> Anders > > From rik at actiview.nl Mon Feb 18 22:13:58 2013 From: rik at actiview.nl (Rik Willems) Date: Mon, 18 Feb 2013 22:13:58 +0100 Subject: [TYPO3-dev] Locallang labels with a dot In-Reply-To: References: Message-ID: That was my suggestion yes. It should be safe as the _LOCAL_LANG section, when parsed, won't (or shouldn't) be used as an array. Flattening the _LOCAL_LANG section to the first level of label + value would 'fix' many extension that you can't change language fields of. Cheers! Op 17-2-2013 11:50, Xavier Perseguers schreef: > Hi Francois, > >>> This is typically a problem with the Extbase extension kickstarter that >>> generates such files. People tend to rely on defaults and learn it >>> this way. >> >> It's even worse than this, the Core is full of them (look at sysext >> lang, for example, in file locallang_core.xlf). I know I use dots almost >> everywhere :-( > > Well, you're not alone... and actually dots in those keys are quite > "pretty", perhaps some "compatibility layer" for TS under _LOCAL_LANG > could be thought of instead of willing to remove dots from those files. > The former should be possible whereas the latter is simply infeasible. > > Cheers > From xavier at typo3.org Tue Feb 19 08:46:51 2013 From: xavier at typo3.org (Xavier Perseguers) Date: Tue, 19 Feb 2013 08:46:51 +0100 Subject: [TYPO3-dev] Locallang labels with a dot In-Reply-To: References: Message-ID: Hello, > That was my suggestion yes. It should be safe as the _LOCAL_LANG > section, when parsed, won't (or shouldn't) be used as an array. > > Flattening the _LOCAL_LANG section to the first level of label + value > would 'fix' many extension that you can't change language fields of. Just did a quick test on a 4.6 install: plugin.tx_myplugin._LOCAL_LANG.default.tx_myplugin_domain_model_object.some_property = custom label and I got "custom label" instead of the original label. So it seems to work (Extbase extension here). After a quick search in the source code, I found this for pibase: class.tslib_pibase.php:977: // Remove the dot after the language key foreach ($languageArray as $labelKey => $labelValue) { and in ChangeLog of Extbase: [+BUGFIX] Extbase (Utility): Make _LOCAL_LANG override work with dots. Thanks to Thomas Maroschik. Resolves #12121 https://forge.typo3.org/issues/12121 So in fact it seems to work at first sight :) What does not work is overriding another language than "default". Cheers -- Xavier Perseguers Release Manager TYPO3 4.6 TYPO3 .... inspiring people to share! Get involved: http://typo3.org From scecere at krur.com Tue Feb 19 09:28:04 2013 From: scecere at krur.com (Stefano Cecere) Date: Tue, 19 Feb 2013 09:28:04 +0100 Subject: [TYPO3-dev] =?iso-8859-1?q?_Re=3A__Extbase=3A_Setting_relational_?= =?iso-8859-1?q?field_to_empty_using_frontend=B4?= In-Reply-To: References: Message-ID: On 18/02/13 21:12, Anders Gissel wrote: > Hello Stefano, > > your solution looks a bit hack'y, but it also looks like it would work. > At least the logic is easily determined, so thanks for that! I'll try > crossposting my question in the other newsgroup and see if I'll have > more luck there. :-) Hi Anders i didn't find any better "hack" :) i'm still under 4.7 .. i know lot's of improvements are being made into Extbase 6.1 ... anyway i find it so strange that such a important basic function needs such discussions! i'll try opening an issue on Extbase Forge. ciaooo -- -- --- ----- ------- Stefano Cecere KRUR studio - http://krur.com From thomas at visualworx.de Wed Feb 20 12:56:00 2013 From: thomas at visualworx.de (Thomas Mammitzsch) Date: Wed, 20 Feb 2013 12:56:00 +0100 Subject: [TYPO3-dev] default value in rtehtmlarea Message-ID: hi list, according to the $tca reference, it should be possible to set a default value for text fields. I have a text field as an rte in a flexform. text 30 5 required foo - bar richtext[textstyle]:rte_transform[flag=rte_enabled|mode=css] It doesn't work. Any ideas? regards, Thomas From thomas at visualworx.de Wed Feb 20 14:34:20 2013 From: thomas at visualworx.de (Thomas Mammitzsch) Date: Wed, 20 Feb 2013 14:34:20 +0100 Subject: [TYPO3-dev] default value in rtehtmlarea In-Reply-To: References: Message-ID: sorry, it works. Seems like i forgot to clear the cache. regards, Thomas On 20.02.2013 12:56, Thomas Mammitzsch wrote: > hi list, > > according to the $tca reference, it should be possible to set a default > value for text fields. I have a text field as an rte in a flexform. > > > > > > > > text > 30 > 5 > required > foo - bar > > richtext[textstyle]:rte_transform[flag=rte_enabled|mode=css] > > > > > It doesn't work. Any ideas? > > regards, Thomas From stefan.franke at gmx.co.uk Wed Feb 20 17:32:11 2013 From: stefan.franke at gmx.co.uk (Stefan Franke) Date: Wed, 20 Feb 2013 17:32:11 +0100 Subject: [TYPO3-dev] Localizing content element with FAL images (flexform) Message-ID: Hello, I'm experiencing problems when localizing a content element that contains FAL images via flexform in TYPO3 6.0.2. Example: The original content element contains 2 FAL images. After localization the localized element contains 3 FAL images. The third FAL image is a duplication of one of the others and is greyed out. Moreover there are little speech bubbles on some of the IRRE elements that are not greyed out, that say "Record was removed in original language". The greyed out entry also has a little speech bubble icon that says "Record can be localized". Is this a bug or am I doing something wrong? Below please find the flexform code I'm using. Thanks for your help! Best, Stefan inline --palette--;LLL:EXT:lang/locallang_tca.xlf:sys_file_reference.imageoverlayPalette;imageoverlayPalette,--palette--;;filePalette sys_file_reference uid_foreign sorting_foreign tablenames image uid_local uid_local 10 file jpg,png uid_local 90 65 Add new Image TRUE TRUE TRUE TRUE FALSE TRUE TRUE TRUE TRUE TRUE TRUE both select TRUE From luberti at archicoop.it Wed Feb 20 17:57:17 2013 From: luberti at archicoop.it (Ivano Luberti) Date: Wed, 20 Feb 2013 17:57:17 +0100 Subject: [TYPO3-dev] about using ['columns'][field name]['config'] / TYPE: "user" Message-ID: Hi, I'm trying to use the possibility to customize a field in the backend using the 'user' type field of the TCA as specified in the ['columns'][field name]['config'] / TYPE: "user" of TCA manual. I have wrote a funcion and specified it in the TCA. What I'm trying to achieve is quite simple: based on a certain condition I want to display either a textarea or an input field.. So I have written this function: $tceforms = t3lib_div::makeInstance('t3lib_TCEforms'); $tceforms->initDefaultBEMode(); .. $tceforms->disableWizards = 1; //removed code to get the $condition value if($condition){ return $tceforms->getSingleField_typeText($PA['table'], $PA['field'], $PA['row'], &$PA); }else{ return $tceforms->getSingleField_typeInput($PA['table'], $PA['field'], $PA['row'], &$PA); } It doesn't work: the field is diplayed and it is the right type but there is no value in it. To understand if tranlsating parameters I get in my function for adapting them to the TCEForms methods was causing something wrong I modified the getSingleField_SW in TCEForms method as follows: case 'user': $item = $this->getSingleField_typeUser($table, $field, $row, $PA); $item = $this->getSingleField_typeInput($table, $field, $row, $PA); Now the $item value after each method execution seems to be identical (except for the uniqueid generated for the HTML control). But If I execute only my method the value is not showed in the control, while if I execute $this->getSingleField_typeInput($table, $field, $row, $PA); after my method or instead of my method everything works correclty. I really cannot understand what I'm doing wrong. I hope someone can point me in the right direction: thanks for your attention. -- ================================================== 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 fabien.udriot at ecodev.ch Fri Feb 22 13:30:23 2013 From: fabien.udriot at ecodev.ch (Fabien Udriot) Date: Fri, 22 Feb 2013 13:30:23 +0100 Subject: [TYPO3-dev] TYPO3 infrastructure - video Message-ID: Hi, To let you know there is a 15 minutes video on-line from the FOSDEM 2013 where Steffen Gebert [1], member of the server team, is pulling the curtain of the TYPO3 infrastructure. I found it interesting enough to post it here. The link: http://video.fosdem.org/2013/lightningtalks/The_development_infrastructure_of_the_TYPO3_project.webm All the best Fabien [1] https://twitter.com/StGebert From luberti at archicoop.it Sun Feb 24 18:30:27 2013 From: luberti at archicoop.it (Ivano Luberti) Date: Sun, 24 Feb 2013 18:30:27 +0100 Subject: [TYPO3-dev] solved: about using ['columns'][field name]['config'] / TYPE: "user" Message-ID: Hi, clearly the problem was in a not proper instantiation of the TCEForms object. It seemed to me really cumbersome that a developer would be forced to know every detail and so I digged more in the code, only to realize that the $fobj passed by TYPO3 to my custom funcition is a reference to the TCEforms currently executing. Using that instead of my own instance solved the problem. Hope this can help other developers ------------------------ Hi, I'm trying to use the possibility to customize a field in the backend using the 'user' type field of the TCA as specified in the ['columns'][field name]['config'] / TYPE: "user" of TCA manual. I have wrote a funcion and specified it in the TCA. What I'm trying to achieve is quite simple: based on a certain condition I want to display either a textarea or an input field.. So I have written this function: $tceforms = t3lib_div::makeInstance('t3lib_TCEforms'); $tceforms->initDefaultBEMode(); .. $tceforms->disableWizards = 1; //removed code to get the $condition value if($condition){ return $tceforms->getSingleField_typeText($PA['table'], $PA['field'], $PA['row'], &$PA); }else{ return $tceforms->getSingleField_typeInput($PA['table'], $PA['field'], $PA['row'], &$PA); } It doesn't work: the field is diplayed and it is the right type but there is no value in it. To understand if tranlsating parameters I get in my function for adapting them to the TCEForms methods was causing something wrong I modified the getSingleField_SW in TCEForms method as follows: case 'user': $item = $this->getSingleField_typeUser($table, $field, $row, $PA); $item = $this->getSingleField_typeInput($table, $field, $row, $PA); Now the $item value after each method execution seems to be identical (except for the uniqueid generated for the HTML control). But If I execute only my method the value is not showed in the control, while if I execute $this->getSingleField_typeInput($table, $field, $row, $PA); after my method or instead of my method everything works correclty. I really cannot understand what I'm doing wrong. I hope someone can point me in the right direction: thanks for your attention. -- ================================================== 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 rik at metmeer.nl Mon Feb 25 11:04:55 2013 From: rik at metmeer.nl (Rik Willems) Date: Mon, 25 Feb 2013 11:04:55 +0100 Subject: [TYPO3-dev] Locallang labels with a dot In-Reply-To: References: Message-ID: Hi! Op 19-02-13 08:46, Xavier Perseguers schreef:> > https://forge.typo3.org/issues/12121 > > So in fact it seems to work at first sight :) > > What does not work is overriding another language than "default". And that is exactly what I was trying to do. I think it would be valuable to enable this for all other languages as well. What do you think? Cheer! From xavier at typo3.org Mon Feb 25 11:19:22 2013 From: xavier at typo3.org (Xavier Perseguers) Date: Mon, 25 Feb 2013 11:19:22 +0100 Subject: [TYPO3-dev] Locallang labels with a dot In-Reply-To: References: Message-ID: Hi, > And that is exactly what I was trying to do. I think it would be > valuable to enable this for all other languages as well. What do you think? Exactly, I see no reason why this shouldn't work. -- Xavier Perseguers Release Manager TYPO3 4.6 TYPO3 .... inspiring people to share! Get involved: http://typo3.org From cl at viazenetti.de Mon Feb 25 20:32:40 2013 From: cl at viazenetti.de (Christian Ludwig) Date: Mon, 25 Feb 2013 20:32:40 +0100 Subject: [TYPO3-dev] RealUrl #13475: userFunc an Bypass or: Add possibility to userFuncs to bypass the param as known from valueMap Message-ID: Hi Dmitry, it would be nice if you could document the fact that a userFunc is not executed when 'noMatch' is set to 'bypass' (or 'null'?). I think page 13 would be the best place to change the first sentence to: User function to do id<=>alias mapping. Only used if "lookUpTable" or "noMatch" are not set. It took me hours until I found this post and finally got my userFunc to run. Thanks for your great work Christian From cl at viazenetti.de Mon Feb 25 20:42:36 2013 From: cl at viazenetti.de (Christian Ludwig) Date: Mon, 25 Feb 2013 20:42:36 +0100 Subject: [TYPO3-dev] RealUrl #13475: userFunc an Bypass or: Add possibility to userFuncs to bypass the param as known from valueMap Message-ID: Hi, > Solution: > change line 1344 to: > $params = array('pObj' => &$this, 'value' => $value, 'decodeAlias' => > TRUE, 'pathParts' => &$pathParts, 'origValue' => $origValue); has this feature been implemented in RealURL? I am hitting exactly the same problem here and don't know how to get things running. This configuration did what I want to do but I need to use a userFunc because the values to map must be fetched by a webservice. 'preVars' => array ( array ( 'GETvar' => 'tx_myext[id]', 'valueMap' => array ( 'robert' => 1, 'christina' => 2, 'peter' => 3, ), 'noMatch' => 'bypass', ), ), So I changed it to this: ------ 'preVars' => array ( array ( 'GETvar' => 'tx_myext[id]', 'userFunc' => 'EXT:myext/real_url.php:&tx_myext ->main, 'noMatch' => 'bypass', ), ), ------ public function main($params, $ref) { $valueMap = array ( 'robert' => 1, 'christina' => 2, 'peter' => 3, ); if ($params['decodeAlias']) { if (isset($valueMap[$params['value']])) { return $valueMap[$params['value']]; } } else { $alias = array_search($params['value'], $valueMap); if ($alias !== false) { return $alias; } } return null; } ------ Now the problem is that I always get the 'emptySegmentValue' = 'nothing' as the first path segment when there is no hit (http://me.com/nothing/page instead of http://me.com/page). When I do not set 'emptySegmentValue', I end up in seeing the startpage (links are rendered as wished to http://me.com/page but pare output is like http://me.com/) until I add the desired page alias as the second segment (http://me.com/page/page). What is the right way to let my userFunc exactly do the same as 'noMatch' => 'bypass' does? Using array_unshift($params['pathParts'],$params['origValue']); before my return null; statement did not change anything. Thanks. Regards Christian From dmitry.dulepov at gmail.com Tue Feb 26 09:48:57 2013 From: dmitry.dulepov at gmail.com (Dmitry Dulepov) Date: Tue, 26 Feb 2013 12:48:57 +0400 Subject: [TYPO3-dev] RealUrl #13475: userFunc an Bypass or: Add possibility to userFuncs to bypass the param as known from valueMap In-Reply-To: References: Message-ID: Hi! Christian Ludwig wrote: > it would be nice if you could document the fact that a userFunc is not > executed when 'noMatch' is set to 'bypass' (or 'null'?). Did that. -- Dmitry Dulepov TYPO3 CMS core & security teams member Love gorillas. From dmitry.dulepov at gmail.com Tue Feb 26 09:51:06 2013 From: dmitry.dulepov at gmail.com (Dmitry Dulepov) Date: Tue, 26 Feb 2013 12:51:06 +0400 Subject: [TYPO3-dev] RealUrl #13475: userFunc an Bypass or: Add possibility to userFuncs to bypass the param as known from valueMap In-Reply-To: References: Message-ID: Hi! Christian Ludwig wrote: >> > Solution: >> > change line 1344 to: >> > $params = array('pObj' => &$this, 'value' => $value, 'decodeAlias' => >> > TRUE, 'pathParts' => &$pathParts, 'origValue' => $origValue); > > has this feature been implemented in RealURL? That piece of code looks like you show in the current development version. -- Dmitry Dulepov TYPO3 CMS core & security teams member Love gorillas. From cl at viazenetti.de Tue Feb 26 10:00:39 2013 From: cl at viazenetti.de (Christian Ludwig) Date: Tue, 26 Feb 2013 10:00:39 +0100 Subject: [TYPO3-dev] RealUrl #13475: userFunc an Bypass or: Add possibility to userFuncs to bypass the param as known from valueMap In-Reply-To: References: Message-ID: Hi Dmitry, > Did that. Thanks, hope this will help others when using userFunc for the first time. Christian From cl at viazenetti.de Tue Feb 26 10:04:35 2013 From: cl at viazenetti.de (Christian Ludwig) Date: Tue, 26 Feb 2013 10:04:35 +0100 Subject: [TYPO3-dev] RealUrl #13475: userFunc an Bypass or: Add possibility to userFuncs to bypass the param as known from valueMap In-Reply-To: References: Message-ID: Hi Dmitry, do you have any hints or an example on how or what to unset in user functions in order to get rid of the empty path segment? This would enhance the documentation, too. > That piece of code looks like you show in the current development version. So it is not possible to bypass empty segments in v1.12.3? Christian From dmitry.dulepov at gmail.com Tue Feb 26 12:02:04 2013 From: dmitry.dulepov at gmail.com (Dmitry Dulepov) Date: Tue, 26 Feb 2013 15:02:04 +0400 Subject: [TYPO3-dev] RealUrl #13475: userFunc an Bypass or: Add possibility to userFuncs to bypass the param as known from valueMap In-Reply-To: References: Message-ID: Hi! Christian Ludwig wrote: > do you have any hints or an example on how or what to unset in user > functions in order to get rid of the empty path segment? > This would enhance the documentation, too. If you have an empty path segment, than it is needed. If you unset it, RealURL will not be able to decode the URL. You can only split your postVarSets to more sets. > So it is not possible to bypass empty segments in v1.12.3? No and it will never be possible. It is a technical limitation related to decoding and current architecture. This may change in RealURL 2.0. -- Dmitry Dulepov TYPO3 CMS core & security teams member Love gorillas. From cl at viazenetti.de Tue Feb 26 12:24:56 2013 From: cl at viazenetti.de (Christian Ludwig) Date: Tue, 26 Feb 2013 12:24:56 +0100 Subject: [TYPO3-dev] RealUrl #13475: userFunc an Bypass or: Add possibility to userFuncs to bypass the param as known from valueMap In-Reply-To: References: Message-ID: Hi Dmitry, thank you for your reply, but maybe we misunderstood each other. What I mean is that when using a valueMap, everything works as expected and I can "bypass" an empty segment (see example below). 'preVars' => array ( array ( 'GETvar' => 'tx_myext[id]', 'valueMap' => array ( 'robert' => 1, 'christina' => 2, 'peter' => 3, ), 'noMatch' => 'bypass', ), ), > No and it will never be possible. It is a technical limitation related to decoding and current architecture. > This may change in RealURL 2.0. Do you mean it will never be possible with userFunc or in general? Christian From luberti at archicoop.it Tue Feb 26 14:56:08 2013 From: luberti at archicoop.it (Ivano Luberti) Date: Tue, 26 Feb 2013 14:56:08 +0100 Subject: [TYPO3-dev] add TSCofnig from file Message-ID: Hello, I'm developing an extension on a TYPO3 4.6.16 instance. In my extension ext_tables.php I have: t3lib_extMgm::addPageTSConfig(''); in my dev environemt works correclty, but when I deploy on the production server the TSConfig is not loaded. I checked using the configuration module and the file is loaded in the TYPO3_CONF_VARS['BE']['defaultPageTSConfig'] There are other extensions on the same server that use the same way to add TSConfig and they seem to work correctly. Any ideas? From typo3 at kay-strobach.de Tue Feb 26 17:04:24 2013 From: typo3 at kay-strobach.de (Kay Strobach) Date: Tue, 26 Feb 2013 17:04:24 +0100 Subject: [TYPO3-dev] add TSCofnig from file In-Reply-To: References: Message-ID: Have you cleared the cache? Am 26.02.13 14:56, schrieb Ivano Luberti: > Hello, I'm developing an extension on a TYPO3 4.6.16 instance. > In my extension ext_tables.php I have: > > t3lib_extMgm::addPageTSConfig(' source="FILE:EXT:my_ext/static/pageTSconfig.txt">'); > > in my dev environemt works correclty, but when I deploy on the > production server the TSConfig is not loaded. > > I checked using the configuration module and the file is loaded in the > TYPO3_CONF_VARS['BE']['defaultPageTSConfig'] > > There are other extensions on the same server that use the same way to > add TSConfig and they seem to work correctly. > > Any ideas? > > > -- http://www.kay-strobach.de - Open Source Rocks TYPO3 .... inspiring people to share! Get involved: http://typo3.org Answer was useful - feel free to donate: - https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=KPM9NAV73VDF2 - https://flattr.com/profile/kaystrobach From luberti at archicoop.it Tue Feb 26 18:47:28 2013 From: luberti at archicoop.it (Ivano Luberti) Date: Tue, 26 Feb 2013 18:47:28 +0100 Subject: [TYPO3-dev] add TSCofnig from file In-Reply-To: References: Message-ID: :-) Yes. Using the clear all caches command in the backend. Il 26/02/2013 17:04, Kay Strobach ha scritto: > Have you cleared the cache? > > Am 26.02.13 14:56, schrieb Ivano Luberti: >> Hello, I'm developing an extension on a TYPO3 4.6.16 instance. >> In my extension ext_tables.php I have: >> >> t3lib_extMgm::addPageTSConfig('> source="FILE:EXT:my_ext/static/pageTSconfig.txt">'); >> >> in my dev environemt works correclty, but when I deploy on the >> production server the TSConfig is not loaded. >> >> I checked using the configuration module and the file is loaded in the >> TYPO3_CONF_VARS['BE']['defaultPageTSConfig'] >> >> There are other extensions on the same server that use the same way to >> add TSConfig and they seem to work correctly. >> >> Any ideas? >> >> >> > -- ================================================== 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 typo3 at kay-strobach.de Wed Feb 27 07:12:26 2013 From: typo3 at kay-strobach.de (Kay Strobach) Date: Wed, 27 Feb 2013 07:12:26 +0100 Subject: [TYPO3-dev] add TSCofnig from file In-Reply-To: References: Message-ID: Mhmm, i always use: t3lib_extMgm::addPageTSConfig(''); So it should be basically the same. Have you switched from a caseIgnorand OS (e.g. Windows) to a case-sensitive one (e.g. Linux)? Does the file exist? Is the extension loaded? Are the cache directories writeable? Any warnings in DB compare? Any warnings in Installtool? Regards Kay Am 26.02.13 18:47, schrieb Ivano Luberti: > :-) > > Yes. > Using the clear all caches command in the backend. > > > Il 26/02/2013 17:04, Kay Strobach ha scritto: >> Have you cleared the cache? >> >> Am 26.02.13 14:56, schrieb Ivano Luberti: >>> Hello, I'm developing an extension on a TYPO3 4.6.16 instance. >>> In my extension ext_tables.php I have: >>> >>> t3lib_extMgm::addPageTSConfig('>> source="FILE:EXT:my_ext/static/pageTSconfig.txt">'); >>> >>> in my dev environemt works correclty, but when I deploy on the >>> production server the TSConfig is not loaded. >>> >>> I checked using the configuration module and the file is loaded in the >>> TYPO3_CONF_VARS['BE']['defaultPageTSConfig'] >>> >>> There are other extensions on the same server that use the same way to >>> add TSConfig and they seem to work correctly. >>> >>> Any ideas? >>> >>> >>> >> > -- http://www.kay-strobach.de - Open Source Rocks TYPO3 .... inspiring people to share! Get involved: http://typo3.org Answer was useful - feel free to donate: - https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=KPM9NAV73VDF2 - https://flattr.com/profile/kaystrobach From luberti at archicoop.it Wed Feb 27 09:21:33 2013 From: luberti at archicoop.it (Ivano Luberti) Date: Wed, 27 Feb 2013 09:21:33 +0100 Subject: [TYPO3-dev] add TSCofnig from file In-Reply-To: References: Message-ID: Il 27/02/2013 07:12, Kay Strobach ha scritto: > Mhmm, i always use: > > t3lib_extMgm::addPageTSConfig(' source="FILE:EXT:basictemplate/Configuration/Skin/tsconfig.ts">'); correct > So it should be basically the same. > Have you switched from a caseIgnorand OS (e.g. Windows) to a > case-sensitive one (e.g. Linux)? yes, what could be the problem: are you suggesting to use only lower cases in the filename? > Does the file exist? Yes :-) > Is the extension loaded? yes > Are the cache directories writeable? I'm not sure because I have not access to the file system. One thing I forgot to mention is that to install the extension my customer had to place the extension files in the right place because my ext is not going to be published. What I can say is that clearing cache using the backend interface has effect. > Any warnings in DB compare Do you mean DB Check? > Any warnings in Installtool? I don't have complete control on the server, I have to ask to customer to give me the password. Thanks for now. -- ================================================== 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 shanmugarajan.k at tcs.com Wed Feb 27 15:35:37 2013 From: shanmugarajan.k at tcs.com (shanmugarajan.k at tcs.com) Date: Wed, 27 Feb 2013 20:05:37 +0530 Subject: [TYPO3-dev] add TSCofnig from file In-Reply-To: References: Message-ID: Hi Lvano, As per your statement, " I'm not sure because I have not access to the file system. One thing I forgot to mention is that to install the extension my customer had to place the extension files in the right place because my ext is not going to be published. What I can say is that clearing cache using the backend interface has effect." it seems you have not installed the extension using extension manager. Just upload the folder on /ext in the filesystem rite? If that is the case, Typo3 might not understant such extension in installed. I.e that extension key will not be available on typo3conf/localconf.php on $TYPO3_CONF_VARS['EXT']['extList'] or $TYPO3_CONF_VARS['EXT']['extList_FE'] value. Please check that will help? Thanks & regards Shan From: Ivano Luberti To: typo3-dev at lists.typo3.org Date: 02/27/2013 01:51 PM Subject: Re: [TYPO3-dev] add TSCofnig from file Sent by: typo3-dev-bounces at lists.typo3.org Il 27/02/2013 07:12, Kay Strobach ha scritto: > Mhmm, i always use: > > t3lib_extMgm::addPageTSConfig(' source="FILE:EXT:basictemplate/Configuration/Skin/tsconfig.ts">'); correct > So it should be basically the same. > Have you switched from a caseIgnorand OS (e.g. Windows) to a > case-sensitive one (e.g. Linux)? yes, what could be the problem: are you suggesting to use only lower cases in the filename? > Does the file exist? Yes :-) > Is the extension loaded? yes > Are the cache directories writeable? I'm not sure because I have not access to the file system. One thing I forgot to mention is that to install the extension my customer had to place the extension files in the right place because my ext is not going to be published. What I can say is that clearing cache using the backend interface has effect. > Any warnings in DB compare Do you mean DB Check? > Any warnings in Installtool? I don't have complete control on the server, I have to ask to customer to give me the password. Thanks for now. -- ================================================== 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 ================================================== _______________________________________________ TYPO3-dev mailing list TYPO3-dev at lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev =====-----=====-----===== 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 luberti at archicoop.it Wed Feb 27 16:56:42 2013 From: luberti at archicoop.it (Ivano Luberti) Date: Wed, 27 Feb 2013 16:56:42 +0100 Subject: [TYPO3-dev] solved: add TSCofnig from file In-Reply-To: References: Message-ID: Shan thanks for your suggestion: the extension was deployed copying the files but then was installed using the extension manager. Anyway: it was a problem in the file name: as Kay was suggesting the name of the file contained some uppercase letters the were not in the call. Sorry If I have bugged the list with a very stupid question. Il 27/02/2013 15:35, shanmugarajan.k at tcs.com ha scritto: > Hi Lvano, > > As per your statement, > " > I'm not sure because I have not access to the file system. > One thing I forgot to mention is that to install the extension my > customer had to place the extension files in the right place because my > ext is not going to be published. > What I can say is that clearing cache using the backend interface has > effect." > > it seems you have not installed the extension using extension manager. > Just upload the folder on /ext in the filesystem rite? > > If that is the case, Typo3 might not understant such extension in > installed. I.e that extension key will not be available on > typo3conf/localconf.php on $TYPO3_CONF_VARS['EXT']['extList'] or > $TYPO3_CONF_VARS['EXT']['extList_FE'] value. > > Please check that will help? > > > Thanks & regards > Shan > > > > > From: > Ivano Luberti > To: > typo3-dev at lists.typo3.org > Date: > 02/27/2013 01:51 PM > Subject: > Re: [TYPO3-dev] add TSCofnig from file > Sent by: > typo3-dev-bounces at lists.typo3.org > > > > > Il 27/02/2013 07:12, Kay Strobach ha scritto: >> Mhmm, i always use: >> >> t3lib_extMgm::addPageTSConfig('> source="FILE:EXT:basictemplate/Configuration/Skin/tsconfig.ts">'); > correct > >> So it should be basically the same. >> Have you switched from a caseIgnorand OS (e.g. Windows) to a >> case-sensitive one (e.g. Linux)? > yes, what could be the problem: are you suggesting to use only lower > cases in the filename? > >> Does the file exist? > Yes :-) > >> Is the extension loaded? > yes > >> Are the cache directories writeable? > I'm not sure because I have not access to the file system. > One thing I forgot to mention is that to install the extension my > customer had to place the extension files in the right place because my > ext is not going to be published. > What I can say is that clearing cache using the backend interface has > effect. > >> Any warnings in DB compare > Do you mean DB Check? > >> Any warnings in Installtool? > I don't have complete control on the server, I have to ask to customer > to give me the password. > > Thanks for now. > -- ================================================== 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 vorbeck at TYPO3Tutor.de Wed Feb 27 17:19:05 2013 From: vorbeck at TYPO3Tutor.de (Sacha Vorbeck) Date: Wed, 27 Feb 2013 17:19:05 +0100 Subject: [TYPO3-dev] Replacement for t3lib_extMgm to add fields to TCA Message-ID: Hi, I use the following lines to add a field to the tt_content TCA: t3lib_div::loadTCA('tt_content'); t3lib_extMgm::addTCAcolumns('tt_content',$additionalContentFields,1); t3lib_extMgm::addToAllTCAtypes('tt_content','tx_masterconfig_sliderimage;;;;1-1-1','menu', 'after:menu_type'); now I read somewhere that t3lib_extMgm is deprecated and will be dropped in 7.0. Can someone tell me what I should use instead? -- thank you - all the best, Sacha From info at cybercraft.de Wed Feb 27 17:51:11 2013 From: info at cybercraft.de (JoH asenau) Date: Wed, 27 Feb 2013 17:51:11 +0100 Subject: [TYPO3-dev] Replacement for t3lib_extMgm to add fields to TCA In-Reply-To: References: Message-ID: Am 27.02.2013 17:19, schrieb Sacha Vorbeck: > Hi, > > I use the following lines to add a field to the tt_content TCA: > > t3lib_div::loadTCA('tt_content'); > t3lib_extMgm::addTCAcolumns('tt_content',$additionalContentFields,1); > t3lib_extMgm::addToAllTCAtypes('tt_content','tx_masterconfig_sliderimage;;;;1-1-1','menu', > 'after:menu_type'); > > now I read somewhere that t3lib_extMgm is deprecated and will be dropped > in 7.0. Can someone tell me what I should use instead? Shouldn't this be part of the deprecation log message? Usually methods will be deprecated when there is a replacement available, so the message should tell you what to use. In case there is no replacement available yet, it would be quite useless to deprecate a method without knowing how to proceed. Just my 2 cents Joey -- Wenn man keine Ahnung hat: Einfach mal Fresse halten! (If you have no clues: simply shut your gob sometimes!) Dieter Nuhr, German comedian Xing: http://contact.cybercraft.de Twitter: http://twitter.com/bunnyfield TYPO3 cookbook (2nd edition): http://www.typo3experts.com From typo3 at kay-strobach.de Wed Feb 27 18:10:13 2013 From: typo3 at kay-strobach.de (Kay Strobach) Date: Wed, 27 Feb 2013 18:10:13 +0100 Subject: [TYPO3-dev] solved: add TSCofnig from file In-Reply-To: References: Message-ID: Hi, no problem, sometimes we have tomatoes on our eyes - this is normal :D Regards Kay Am 27.02.13 16:56, schrieb Ivano Luberti: > Shan thanks for your suggestion: the extension was deployed copying the > files but then was installed using the extension manager. > > Anyway: it was a problem in the file name: as Kay was suggesting the > name of the file contained some uppercase letters the were not in the call. > Sorry If I have bugged the list with a very stupid question. > > > Il 27/02/2013 15:35, shanmugarajan.k at tcs.com ha scritto: >> Hi Lvano, >> >> As per your statement, >> " >> I'm not sure because I have not access to the file system. >> One thing I forgot to mention is that to install the extension my >> customer had to place the extension files in the right place because my >> ext is not going to be published. >> What I can say is that clearing cache using the backend interface has >> effect." >> >> it seems you have not installed the extension using extension manager. >> Just upload the folder on /ext in the filesystem rite? >> >> If that is the case, Typo3 might not understant such extension in >> installed. I.e that extension key will not be available on >> typo3conf/localconf.php on $TYPO3_CONF_VARS['EXT']['extList'] or >> $TYPO3_CONF_VARS['EXT']['extList_FE'] value. >> >> Please check that will help? >> >> >> Thanks & regards >> Shan >> >> >> >> >> From: >> Ivano Luberti >> To: >> typo3-dev at lists.typo3.org >> Date: >> 02/27/2013 01:51 PM >> Subject: >> Re: [TYPO3-dev] add TSCofnig from file >> Sent by: >> typo3-dev-bounces at lists.typo3.org >> >> >> >> >> Il 27/02/2013 07:12, Kay Strobach ha scritto: >>> Mhmm, i always use: >>> >>> t3lib_extMgm::addPageTSConfig('>> source="FILE:EXT:basictemplate/Configuration/Skin/tsconfig.ts">'); >> correct >> >>> So it should be basically the same. >>> Have you switched from a caseIgnorand OS (e.g. Windows) to a >>> case-sensitive one (e.g. Linux)? >> yes, what could be the problem: are you suggesting to use only lower >> cases in the filename? >> >>> Does the file exist? >> Yes :-) >> >>> Is the extension loaded? >> yes >> >>> Are the cache directories writeable? >> I'm not sure because I have not access to the file system. >> One thing I forgot to mention is that to install the extension my >> customer had to place the extension files in the right place because my >> ext is not going to be published. >> What I can say is that clearing cache using the backend interface has >> effect. >> >>> Any warnings in DB compare >> Do you mean DB Check? >> >>> Any warnings in Installtool? >> I don't have complete control on the server, I have to ask to customer >> to give me the password. >> >> Thanks for now. >> > -- http://www.kay-strobach.de - Open Source Rocks TYPO3 .... inspiring people to share! Get involved: http://typo3.org Answer was useful - feel free to donate: - https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=KPM9NAV73VDF2 - https://flattr.com/profile/kaystrobach From lorenz-typo3 at visol.ch Wed Feb 27 18:10:18 2013 From: lorenz-typo3 at visol.ch (Lorenz Ulrich) Date: Wed, 27 Feb 2013 18:10:18 +0100 Subject: [TYPO3-dev] Replacement for t3lib_extMgm to add fields to TCA In-Reply-To: References: Message-ID: Hi Sacha The methods inside this class are not deprecated, but calling them without using the new namespaced class: \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addTCAcolumns(...... Best regards, Lorenz Am 27.02.2013 17:19, schrieb Sacha Vorbeck: > Hi, > > I use the following lines to add a field to the tt_content TCA: > > t3lib_div::loadTCA('tt_content'); > t3lib_extMgm::addTCAcolumns('tt_content',$additionalContentFields,1); > t3lib_extMgm::addToAllTCAtypes('tt_content','tx_masterconfig_sliderimage;;;;1-1-1','menu', > 'after:menu_type'); > > now I read somewhere that t3lib_extMgm is deprecated and will be dropped > in 7.0. Can someone tell me what I should use instead? > From philipp.gampe at typo3.org Thu Feb 28 00:23:13 2013 From: philipp.gampe at typo3.org (Philipp Gampe) Date: Thu, 28 Feb 2013 00:23:13 +0100 Subject: [TYPO3-dev] solved: add TSCofnig from file References: Message-ID: Hi Ivano, Ivano Luberti wrote: > name of the file contained some uppercase letters the were not in the > call A typical problem of Windows users (?!?) ;) We Unix users usually forget that there are people out there that use case insensitive filesystems. Happened to me before ... you test something, it works and once you copy it, it stops working ? you get a headache trying to figure out what you might have missed, and it turns out it is something so simple. It might be a good habit to work case sensitive on case insensitive systems too. Cheers -- Philipp Gampe ? PGP-Key 0AD96065 ? TYPO3 UG Bonn/K?ln Documentation ? linkvalidator TYPO3 .... inspiring people to share! From philipp.gampe at typo3.org Thu Feb 28 00:24:57 2013 From: philipp.gampe at typo3.org (Philipp Gampe) Date: Thu, 28 Feb 2013 00:24:57 +0100 Subject: [TYPO3-dev] Replacement for t3lib_extMgm to add fields to TCA References: Message-ID: Hi JoH asenau, JoH asenau wrote: > Shouldn't this be part of the deprecation log message? > Usually methods will be deprecated when there is a replacement > available, so the message should tell you what to use. It is written in the old file for sure. Best regards -- Philipp Gampe ? PGP-Key 0AD96065 ? TYPO3 UG Bonn/K?ln Documentation ? linkvalidator TYPO3 .... inspiring people to share! From vorbeck at TYPO3Tutor.de Thu Feb 28 01:42:19 2013 From: vorbeck at TYPO3Tutor.de (Sacha Vorbeck) Date: Thu, 28 Feb 2013 01:42:19 +0100 Subject: [TYPO3-dev] Replacement for t3lib_extMgm to add fields to TCA In-Reply-To: References: Message-ID: Hello, >> Shouldn't this be part of the deprecation log message?>> Usually methods will be deprecated when there is a replacement >> available, so the message should tell you what to use. > > It is written in the old file for sure. oops, must have overlooked that. And thanks for the hint to the new namespaced class :-). -- all the best, Sacha From dmitry.dulepov at gmail.com Thu Feb 28 06:36:29 2013 From: dmitry.dulepov at gmail.com (Dmitry Dulepov) Date: Thu, 28 Feb 2013 09:36:29 +0400 Subject: [TYPO3-dev] solved: add TSCofnig from file In-Reply-To: References: Message-ID: Hi! Philipp Gampe wrote: > A typical problem of Windows users (?!?) On OS X too. I recently had a project with 'Classes' and 'classes' directory in an extension. OS X file system is not case sensitive by default, so SVN complained that the directory already exists and refused to check it out. Funny that most utilities, which were created on Linux, do not care about the case when the file system is case insensitive. On the other hand, why should they? :) -- Dmitry Dulepov TYPO3 CMS core & security teams member Love gorillas. From jigal.van.hemert at typo3.org Thu Feb 28 09:23:26 2013 From: jigal.van.hemert at typo3.org (Jigal van Hemert) Date: Thu, 28 Feb 2013 09:23:26 +0100 Subject: [TYPO3-dev] solved: add TSCofnig from file In-Reply-To: References: Message-ID: Hi, On 28-2-2013 0:23, Philipp Gampe wrote: > We Unix users usually forget that there are people out there that use case > insensitive filesystems. .. and forget about proper handling of directory separators in different cases, and forget about proper line ending handling, and forget about PHP functions that are not supported on all OSs or work differently, and... SCNR :-) -- Jigal van Hemert TYPO3 Core Team member TYPO3 .... inspiring people to share! Get involved: typo3.org From jigal.van.hemert at typo3.org Thu Feb 28 09:51:50 2013 From: jigal.van.hemert at typo3.org (Jigal van Hemert) Date: Thu, 28 Feb 2013 09:51:50 +0100 Subject: [TYPO3-dev] Replacement for t3lib_extMgm to add fields to TCA In-Reply-To: References: Message-ID: Hi, On 28-2-2013 1:42, Sacha Vorbeck wrote: > oops, must have overlooked that. And thanks for the hint to the new > namespaced class :-). The namespace operation included: - keep the old file with a require_once for the new file (to support code that does an include of the old file instead of relying on the autoloader) - some text hints for the new location - typo3/sysext/core/Migrations/Code/LegacyClassesForIde.php for IDE to help them find the new class in case the code uses the old class - class aliases for all the old class names to map them to the new class names - compatibility class for PHP < 5.3.7 which can rewrite some cases of type hints, etc. Seems plenty of help :-) -- Jigal van Hemert TYPO3 Core Team member TYPO3 .... inspiring people to share! Get involved: typo3.org From t3ng at bernd-wilke.net Thu Feb 28 10:32:50 2013 From: t3ng at bernd-wilke.net (bernd wilke) Date: Thu, 28 Feb 2013 10:32:50 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager In-Reply-To: References: Message-ID: Am 09.02.2013 04:27, schrieb Benjamin Mack: > Hey everybody, > > as most of you (hopefully :)) played around with the new extension > manager in 6.0, you might have noticed that it has a different feel to > it: It is more focused on actually downloading and installing extensions > instead of doing everything else that has been in that place for the > last years: > > * Uploading extensions > * Updating language files > * Developer information about an extension > * Cleanup ext_emconf.php > * Creating a new extension (kickstarter) > * List of updated extensions > > So, as we want to improve this area for 6.1, I am eager to get your > input on what should definitively get back in there (and why) and what > should be placed somewhere else. I would also like to have your feedback > on the UI parts, the things you like and the things you don't like. > I got a further feedback which asks for the possibility to add notes to an (installed) extension. In this way you can store remarks to an extension for other integrators like: can not be updates because of ... has been modified in file ... for ... watch for special configuration ... bernd -- http://www.pi-phi.de/cheatsheet.html From fsu-lists at cobweb.ch Thu Feb 28 16:25:13 2013 From: fsu-lists at cobweb.ch (=?ISO-8859-1?Q?Fran=E7ois_Suter?=) Date: Thu, 28 Feb 2013 16:25:13 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager In-Reply-To: References: Message-ID: Hi bernd, > I got a further feedback which asks for the possibility to add notes to > an (installed) extension. In this way you can store remarks to an > extension for other integrators like: > can not be updates because of ... > has been modified in file ... for ... > watch for special configuration ... An excellent idea! We generally do that with some specially-named file and set the extension's status to "excludeFromUpdates", but it would be very convenient to have this. Although not trivial, as there's currently no database relation to installed extensions. It would be a whole new mechanism. Cheers -- Francois Suter Cobweb Development Sarl - http://www.cobweb.ch From t3ng at bernd-wilke.net Thu Feb 28 17:21:44 2013 From: t3ng at bernd-wilke.net (bernd wilke) Date: Thu, 28 Feb 2013 17:21:44 +0100 Subject: [TYPO3-dev] Your Input On: 6.x Extension Manager In-Reply-To: References: Message-ID: Am 28.02.2013 16:25, schrieb Fran?ois Suter: > Hi bernd, > >> I got a further feedback which asks for the possibility to add notes to >> an (installed) extension. In this way you can store remarks to an >> extension for other integrators like: >> can not be updates because of ... >> has been modified in file ... for ... >> watch for special configuration ... > > An excellent idea! We generally do that with some specially-named file > and set the extension's status to "excludeFromUpdates", but it would be > very convenient to have this. Although not trivial, as there's currently > no database relation to installed extensions. It would be a whole new > mechanism. > I think a special file in the extension-directory would be enough. there are a lot of 'magic' files. this file would get a special treatment from EM & Co. (no overwrite on update, no upload to TER, shown in lists, with possibility to edit) bernd -- http://www.pi-phi.de/cheatsheet.html