From oliver.hader at typo3.org Tue Jan 3 13:21:51 2017 From: oliver.hader at typo3.org (Oliver Hader) Date: Tue, 3 Jan 2017 13:21:51 +0100 Subject: [TYPO3-dev] [TYPO3-core] Announcing TYPO3 CMS 6.2.30 LTS, 7.6.15 LTS and 8.5.1 Message-ID: Dear TYPO3 World, the TYPO3 Community has just released TYPO3 CMS versions 6.2.30 LTS, 7.6.15 LTS and 8.5.1 which are now ready for you to download. All versions are maintenance releases and contain bug fixes and security fixes. *IMPORTANT* These versions include important security fixes to the TYPO3 CMS Core. The according security bulletins with details have just been released: https://typo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2017-001/ The packages can be downloaded here: https://typo3.org/download/ For details about the releases, please see: https://typo3.org/news/article/typo3-cms-6230-7615-and-851-released/ MD5 checksums: 76e7d9fc55e876ca50b3da523f213f5f typo3_src-6.2.30.tar.gz 581a39cbc58f28705c744dd713607901 typo3_src-6.2.30.zip 2126e2291948674e6290269d62d372f4 typo3_src-7.6.15.tar.gz 4f44064625feb682da3078c1c161d301 typo3_src-7.6.15.zip 81688be430a6d1157a8dac23908479fc typo3_src-8.5.1.tar.gz 6d575cebf43dfa381ce91fcf55674980 typo3_src-8.5.1.zip SHA256 checksums: 278feef7a972084dfc352eda46e7d4771f460213714b90314802295894ba30b4 typo3_src-6.2.30.tar.gz 7698ee6d342e29edb3824d7be576b555d09ba1e4bdfc2ae8c9071efb462a8823 typo3_src-6.2.30.zip e263bf3f20dbd50b5f790d25995f02785a35681d1c18406f571d10df5f75a9c9 typo3_src-7.6.15.tar.gz a1bc9b4359f53a67c088519baa945a3da2a6a00efd2e886a75efa5c9ba39c8d1 typo3_src-7.6.15.zip 0684e266c3711616efe260ec1381af30dfec3a4db0d0647313f1040ff48eb5fd typo3_src-8.5.1.tar.gz d60bb677bfd4d353b91d6a8f2474337ba4a3deefbb9b49b278c3f71c5424a849 typo3_src-8.5.1.zip Further details on the signing and hashing process of TYPO3 releases: https://typo3.org/download/signed-packages/ Best regards Oliver -- Oliver Hader TYPO3 .... inspiring people to share! Get involved: http://typo3.org From 00marduk at gmail.com Wed Jan 4 11:21:01 2017 From: 00marduk at gmail.com (mardz iop) Date: Wed, 04 Jan 2017 11:21:01 +0100 Subject: [TYPO3-dev] =?utf-8?q?_dropdown_login_box_in_menu?= Message-ID: I would like to create a dropdown login box in the menu. When users hover over "login" in the menu, it shows the login or register form. I found an example here: planet-sports.com/en/ I am quite new to TYPO3 so I don't know where I should start. Is there a way to do this with Typoscript only or should I modify the navbar with html and javascript? What is the best way to do this ? I am using a custom theme (not done by myself) The Menu is called in a "header.html" file like this: From info at bugblatterbeast.de Fri Jan 13 17:21:02 2017 From: info at bugblatterbeast.de (bugblatterbeast) Date: Fri, 13 Jan 2017 17:21:02 +0100 Subject: [TYPO3-dev] =?utf-8?q?_f=3Aimage_onClick_enlargement?= Message-ID: Hi, I've created an extension that uses a fal image-collection. It works quite well, but I also want onClick enlargement. I've expecten f:image to support this feature but I didn't find any documentation on it particular, so I've decided to solve the problem in the simplest way by wrapping a link-tag around the image. Now I wonder: how do I get the path of a file-reference? {image} returns: Extbase Variable Dump TYPO3\CMS\Extbase\Domain\Model\FileReferenceprototypepersistent entity (uid=108, pid=167) uidLocal => 418 (integer) originalResource => NULL uid => 108 (integer) _localizedUid => 108 (integer)modified _languageUid => 0 (integer)modified _versionedUid => 108 (integer)modified pid => 167 (integer) Kind regards, Nils From franssaris at gmail.com Fri Jan 13 17:32:38 2017 From: franssaris at gmail.com (Frans Saris) Date: Fri, 13 Jan 2017 16:32:38 +0000 Subject: [TYPO3-dev] f:image onClick enlargement In-Reply-To: References: Message-ID: Hi, You can use for this. Or if you want to make sure the large version isn't to large. Groet Frans Op vr 13 jan. 2017 17:25 schreef bugblatterbeast : > Hi, > > > > I've created an extension that uses a fal image-collection. It works quite > well, but I also want onClick enlargement. > > > > height="" treatIdAsReference="1" /> > > > > I've expecten f:image to support this feature but I didn't find any > documentation on it particular, so I've decided to solve the problem in the > simplest way by wrapping a link-tag around the image. > > alt="" width="270" height="" treatIdAsReference="1" /> > > Now I wonder: how do I get the path of a file-reference? > > {image} returns: > > Extbase Variable Dump > > TYPO3\CMS\Extbase\Domain\Model\FileReferenceprototypepersistent entity > (uid=108, pid=167) > uidLocal => 418 (integer) > originalResource => NULL > uid => 108 (integer) > _localizedUid => 108 (integer)modified > _languageUid => 0 (integer)modified > _versionedUid => 108 (integer)modified > pid => 167 (integer) > > > > Kind regards, Nils > _______________________________________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev > From info at bugblatterbeast.de Fri Jan 13 17:47:55 2017 From: info at bugblatterbeast.de (bugblatterbeast) Date: Fri, 13 Jan 2017 17:47:55 +0100 Subject: [TYPO3-dev] =?utf-8?q?f=3Aimage_onClick_enlargement?= References: Message-ID: Hi, thank you very much your reply but I think it doesn't work with FileRelation images (maybe I've done it wrong). ... just resolves to ... and {image.publicUrl} returns: Extbase Variable Dump NULL Thanks though, it was worth a try. Any corrections or other solutions? Kind regards, Nils From franssaris at gmail.com Fri Jan 13 17:57:58 2017 From: franssaris at gmail.com (Frans Saris) Date: Fri, 13 Jan 2017 16:57:58 +0000 Subject: [TYPO3-dev] f:image onClick enlargement In-Reply-To: References: Message-ID: Hi, Try {image.originalResource.publicUrl} Groet Frans Op vr 13 jan. 2017 17:50 schreef bugblatterbeast : > Hi, > > thank you very much your reply but I think it doesn't work with > FileRelation images (maybe I've done it wrong). > > ... just resolves to href="" target="_blank">... > > and {image.publicUrl} returns: > > Extbase Variable Dump > > NULL > > Thanks though, it was worth a try. Any corrections or other solutions? > > Kind regards, Nils > _______________________________________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev > From info at bugblatterbeast.de Fri Jan 13 18:06:55 2017 From: info at bugblatterbeast.de (bugblatterbeast) Date: Fri, 13 Jan 2017 18:06:55 +0100 Subject: [TYPO3-dev] =?utf-8?q?f=3Aimage_onClick_enlargement?= References: Message-ID: Well Frans I didn't expect your suggestion to work. As you see in the variable dumb in my first post: image.originalResource => NULL But IT DOES!!! You've solved it. {image.originalResource.publicUrl} returns the full path. Thank you very much and have a nice weekend. Kind regard, sch?ne Gr??e, Nils From franssaris at gmail.com Fri Jan 13 21:07:51 2017 From: franssaris at gmail.com (Frans Saris) Date: Fri, 13 Jan 2017 20:07:51 +0000 Subject: [TYPO3-dev] f:image onClick enlargement In-Reply-To: References: Message-ID: The value is empty in the dump because the property is lazy loaded. If you call the debug after {image.originalRecource.publicUrl} you will that the value is set. Groet Frans Op vr 13 jan. 2017 18:10 schreef bugblatterbeast : > Well Frans I didn't expect your suggestion to work. As you see in the > variable dumb in my first post: image.originalResource => NULL > > But IT DOES!!! You've solved it. {image.originalResource.publicUrl} > returns the full path. > > Thank you very much and have a nice weekend. > > Kind regard, sch?ne Gr??e, Nils > _______________________________________________ > TYPO3-dev mailing list > TYPO3-dev at lists.typo3.org > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev From stas at codelobster.com Tue Jan 17 09:12:02 2017 From: stas at codelobster.com (Stas Ustimenko) Date: Tue, 17 Jan 2017 09:12:02 +0100 Subject: [TYPO3-dev] =?utf-8?q?_Re=3A_Re=3A_Favorite_PHP_editor/IDE=3F?= References: Message-ID: Free version of Codelobster works best for me. From Info at ReinhardtMedien.de Thu Jan 26 11:02:09 2017 From: Info at ReinhardtMedien.de (Reinhardt Medien) Date: Thu, 26 Jan 2017 11:02:09 +0100 Subject: [TYPO3-dev] =?utf-8?q?wizard=5Felement=5Fbrowser_and_hide_option_?= =?utf-8?q?file=2C_mail_and_folder?= References: Message-ID: Hello, some month ago, but i think first i would type array ever in small cases then 'module' => array( 'name' => 'wizard_link', ), ), works for me my whole code is: [code] 'link' => array( 'exclude' => 1, 'label' => 'LLL:EXT:rmbase/Resources/Private/Language/locallang_db.xlf:tx_rmbase_domain_model_rmlink.link', 'config' => array( 'type' => 'input', 'size' => 30, 'eval' => 'trim', 'required' => 1, 'wizards' => array( 'link' => array( 'type' => 'popup', 'title' => 'LLL:EXT:frontend/Resources/Private/Language/locallang_ttc.xlf:header_link_formlabel', 'icon' => 'actions-wizard-link', 'module' => array( 'name' => 'wizard_link', ), 'JSopenParams' => 'width=800,height=600,status=0,menubar=0,scrollbars=1', 'params' => [ 'blindLinkOptions' => 'folder', 'blindLinkFields' => 'class, target, title, params', ], ) ), 'softref' => 'typolink' ), ), [/code] -- Beste Gr??e Monti Reinhardt Medien www.ReinhardtMedien.de Info (at) ReinhardtMedien.de From center13 at gmx.de Fri Jan 27 03:16:53 2017 From: center13 at gmx.de (Falk Duwe) Date: Fri, 27 Jan 2017 03:16:53 +0100 Subject: [TYPO3-dev] =?utf-8?q?_Tried_to_get_a_variable_=22sections=22_whi?= =?utf-8?q?ch_is_not_stored_in_the_context!?= Message-ID: Hi I setting up a new typo3 fluid template and with the following code it worked pretty well before, but this time I get this Error message in the frontend where the content should be: "Tried to get a variable "sections" which is not stored in the context!" Here the code for my main template:
And this is my code for the template with the section content: {content} I work with
tags in my content. Could this be a problem? My TS looks like this: page.10 = FLUIDTEMPLATE page.10 { format = html file = fileadmin/templates/layouts/main.html partialRootPath = fileadmin/templates/partials/ layoutRootPath = fileadmin/templates/layouts/ variables { content < styles.content.get content.select.where = colPos = 0 } } page.10.file.stdWrap.cObject = CASE page.10.file.stdWrap.cObject { key.data = levelfield:-1, backend_layout_next_level, slide key.override.field = backend_layout default = TEXT default.value = fileadmin/templates/layouts/main.html 2 = TEXT 2.value = fileadmin/templates/home.html } Maybe someone can help me... Thanks, Falk