IRC logs

20140626

• 09:42:18 <padd> Hey guys. I just want to try to use <f:translate key="LLL:EXT:..." /> . I have my locallang.xlf in the Language-folder
• 09:42:19 <FT3BOT> ¯\_(ツ)_/¯
• 09:42:36 <padd> but in frontend its empty :/ dont know what i am doing wrong
• 09:47:10 <pedda> padd where did you get f:translate from?
• 09:47:10 <FT3BOT> ¯\_(ツ)_/¯
• 09:47:31 <pedda> i mean.. how do you know f:translate is the right viewhelper ?
• 09:47:32 <FT3BOT> ¯\_(ツ)_/¯
• 09:48:18 <padd> fedext website?:P
• 09:51:09 <pedda> and why don't you just scroll a bit further and see how the key needs to be used?
• 09:51:35 <pedda> or take a look at the official fluid documentation if the fedext one is leaking of proper rendering: http://docs.typo3.org/typo3cms/ExtbaseGuide/Fluid/ViewHelper/Translate.html
• 09:51:53 <pedda> mean
• 09:52:21 <pedda> if your locallang.xlf exists in Resources/Private/Languages/
• 09:53:23 <pedda> and you use in your extension/template some f:translate ViewHelper, it works from scratch by a line like this: <f:translate key="tx_myext_domain_model.title" />
• 09:53:23 <FT3BOT> ¯\_(ツ)_/¯
• 09:54:01 <pedda> does your project rely on a provider extension?
• 09:55:20 <pedda> the official docs don't say LLL:EXT: at any point
• 09:55:45 <pedda> as EXT is unnecessary because if it's your custom extension, then extbase knows where to look for your language file
• 09:55:59 <padd> ok let me check again
• 09:57:47 <padd> the template in which i am workin at is not the provider ext
• 10:00:31 <pedda> why don't you move it to the provider extension ?
• 10:00:56 <mhmli> referring to http://fluidtypo3.org/viewhelpers/fluid/master/Link/ExternalViewHelper.html, is there any way to set link text in the inline usage of f:link.external?
• 10:00:57 <FT3BOT> ¯\_(ツ)_/¯
• 10:01:37 <pedda> mhmli no afaik
• 10:02:08 <mhmli> @pedda so does that mean that there's no usage possibility for it? as the hyperlink is generated with nothing to click on.
• 10:02:08 <pedda> but this vh is capable of doing so: http://fluidtypo3.org/viewhelpers/vhs/master/Link/TypolinkViewHelper.html
• 10:02:33 <pedda> ther eis no usage possibility for it when it comes to inline syntax
• 10:02:38 <mhmli> odd.
• 10:02:42 <pedda> not really
• 10:02:46 <mhmli> why?
• 10:03:01 <pedda> it's known that some vh's are just not able to be used in inline syntax
• 10:03:16 <pedda> ot because someone didn't finish his work
• 10:03:20 <pedda> *not
• 10:03:25 <pedda> it#s because they can't
• 10:03:26 <mhmli> if there's an inline syntax but it's unusable then is there any point in a) having it in the code and b) documenting its usage?
• 10:03:41 <pedda> the inline syntax is mentioned on fedext for any vh
• 10:03:49 <pedda> not in the official documentation
• 10:03:59 <mhmli> http://fluidtypo3.org/viewhelpers/fluid/master/Link/ExternalViewHelper.html
• 10:04:06 <mhmli> is that not the official doc then?
• 10:04:15 <pedda> http://docs.typo3.org/typo3cms/ExtbaseGuide/stable/Fluid/ViewHelper/Link/External.html
• 10:04:22 <pedda> obviously not
• 10:04:48 <pedda> fedext/fluidtypo3 is a set of tools for building templates the fluid way
• 10:04:57 <mhmli> ah i see. i had thought that as it was a 3rd party dev, fluidtypo3.org was the official source
• 10:05:02 <mhmli> godo to know that it's not!
• 10:05:08 <mhmli> *good
• 10:05:22 <pedda> additionally the included the documentation of core fluid features just to enable you a single source of information while dealing with learing fluid
• 10:05:53 <pedda> it's official for all viewhelper documented there but fluid itself
• 10:05:59 <pedda> f: namspace
• 10:06:15 <pedda> f: is typo3 core functionality
• 10:06:37 <pedda> that'S why you don't need to define a {namespace f=... at the top of your files
• 10:07:11 <mhmli> aha!
• 10:07:31 <mhmli> has missed that obvious point. *slaps forehead*
• 10:07:49 <mhmli> but v: is vhs, yes?
• 10:07:54 <pedda> yes
• 10:08:08 <pedda> and this is a product of the fluidtypo3 team
• 10:08:09 <mhmli> tks :)
• 10:08:20 <pedda> as well as flux and all the others on that page are..
• 10:36:09 <bjo3rn> ach, now he's gone :/
• 10:36:49 <bjo3rn> for the record: the docs are rendered automatically from classes docblocks.
• 10:37:16 <bjo3rn> it seems we need a way to avoid rendering of inline usage where it is not possible like in this case.
• 10:37:41 <bjo3rn> you were correct pedda ofc
• 10:38:14 <pedda> ^^
• 10:38:22 <pedda> there was a hint in the past
• 10:38:31 <pedda> on every single vh doc page on fedext
• 10:39:12 <pedda> telling that although the vh is shown in inline syntax, it's not valid for all vh's
• 10:39:25 <pedda> but he got it..
• 10:40:09 <bjo3rn> you can tell from the arguments list also if it supports inline syntax imho
• 10:40:22 <bjo3rn> there's no 'content', 'linktext' or the like
• 10:56:37 <pedda> sometimes there is no content, but still if you use it chained via -> the vh works out
• 10:58:15 <bjo3rn> sure, but you can only chain it with another vh or a variable
• 10:58:26 <pedda> yepp
• 10:58:45 <pedda> my tv arrived.. ready for the match today :D
• 10:58:55 <bjo3rn> aha!
• 10:59:31 <bjo3rn> we'll watch again in the garage with some neighbors
• 10:59:47 <pedda> this was teh one i watched all previous games: http://i.ebayimg.com/t/Sharp-37ET35S-35-6-cm-14-Zoll-Fernseher-plus-IKEA-Observatoer-/00/s/MTEwMVgxMTY5/z/jCoAAOxyOalTXoKs/$_57.JPG
• 10:59:58 <pedda> 14 inch :D
• 11:00:04 <bjo3rn> you mean, you guessed the games ^^
• 11:00:12 <pedda> more or less.. yes
• 11:00:18 <bjo3rn> there was something moving on the screen
• 11:00:22 <bjo3rn> ^^
• 11:00:35 <pedda> thin lines = players, white dot = ball
• 11:00:50 <pedda> some version of pong in hi res
• 11:01:28 <pedda> the only thing i need for today evening is a pittermännchen of schumacher :D
• 11:01:33 <bjo3rn> https://www.dropbox.com/s/ovabgmgod46ds35/2014-06-16%2019.12.51-1.jpg
• 11:01:41 <bjo3rn> our venue ^^
• 11:01:46 <pedda> nice
• 11:02:21 <pedda> the weather is nice too..
• 11:02:29 <pedda> will be a good afternoon -.-
• 11:02:37 <bjo3rn> pittermännchen? ddorf?
• 11:02:45 <pedda> yes
• 11:02:50 <pedda> we talked about it once bjoern
• 11:02:51 <bjo3rn> ach, yes. I remember
• 11:02:57 <pedda> ;)
• 11:03:07 <pedda> i was still unable to get back to you
• 11:03:20 <pedda> regarding a meetup
• 11:03:27 <pedda> i'd love to see ced as well
• 11:03:46 <pedda> and claus..
• 11:03:59 <pedda> have you ever talked about a ft3 group meeting?
• 11:04:19 <pedda> i'd donate food and drinks
• 11:04:29 <pedda> but i also know claus doesn't like to travel
• 11:04:31 <bjo3rn> no, not really. some of us met at t3camps in stuttgart and munich
• 11:04:53 <pedda> you and ced in stutgart as far as i remember.. right?
• 11:04:57 <pedda> +t
• 11:05:16 <bjo3rn> plus danilo and ye olde randomresult
• 11:05:26 <bjo3rn> and xaver
• 11:05:27 <pedda> ye old randomresult .. hehe
• 11:05:37 <pedda> oh .. so nearly the whole team
• 11:05:39 <pedda> more or less
• 11:05:49 <pedda> was probably fun
• 12:18:10 <xaver> cedricziel and i'm in berlin next weekend ;)
• 12:26:44 <bjo3rn> I envy you both
• 12:35:03 <xaver> bjo3rn: maybe essen this year (munich of course :P )
• 12:35:21 <bjo3rn> essen yes, munich no
• 12:40:42 <xaver> bjo3rn: i know - ok essen will sell tickets in 2 waves
• 12:43:33 <pedda> essen munich?
• 12:43:35 <pedda> wtf?
• 12:43:36 <FT3BOT> ¯\_(ツ)_/¯
• 12:43:46 <pedda> bcamps`
• 12:43:47 <pedda> ?
• 12:47:38 <xaver> pedda: yes
• 12:47:56 <xaver> and hopefully regensburg :P
• 12:48:27 <pedda> bcamp = holidays for a developer :D
• 13:03:11 <soee_> wtf
• 13:03:12 <FT3BOT> ¯\_(ツ)_/¯
• 13:05:41 <hans> hi there
• 13:06:04 <beo|2> hello
• 13:06:06 <hans> i want to extend the "news" extention with one field, got the following description: http://t3brightside.com/blog/article/extending-extnews-with-a-fal-compilant-audio-and-customized-youtube-video/
• 13:06:32 <hans> now i wondering about the ext_tables.sql
• 13:07:19 <beo|2> hans: what are you wondering about?
• 13:07:40 <hans> but the "tx_news_domain_model_news" table ist allready exisiting in the db by the news extention.
• 13:08:28 <beo|2> sure. i guess you want to extend it.
• 13:08:39 <hans> yes
• 13:08:57 <hans> so thats the normal way?
• 13:09:13 <hans> there is nothing overwritten or lost?!
• 13:09:28 <hans> when i install my own extention?
• 13:10:02 <beo|2> typo3 makes a diff of the database table and only makes the changes you add in your ext_tables.sql
• 13:11:13 <hans> ok, the "CREATE TABLE" lokks confusing, but i´ll try it! thx for now !!!
• 13:12:19 <beo|2> yes. but you are safe. i think typo3 also never removes table fields on its own. to remove you need to go into the install tool
• 13:13:14 <beo|2> but i guess that is more a question that goes into #typo3. or not?
• 13:14:31 <hans> yes y r right, sry for that :-/
• 13:14:45 <beo|2> np. :)
• 13:15:44 <hans> yes cool it works :-D
• 13:15:49 <hans> Made my day (y)
• 13:18:02 <beo|2> btw. can anyone tell me again what the issue was when the asset from fedext got removed so it threw a 404. i know i had the same issue a long time ago with version fluidpages 2.1.0, fluidcontent 3.1.0, vhs 1.8.4 and i can't remember what i did there
• 13:19:10 <beo|2> or did i just updated from the repository...
• 13:20:05 <beo|2> its odd because when i copy the version from the working hosting to the one with the issue even though the versions are the same it breaks the page and backend
• 13:22:19 <beo|2> i would just update it to the newest version but it would require quite a lot of changes to all the templates. :/
• 13:52:48 <randomresult> hi there
• 14:19:40 <padd> hi guys. I have a problem Could not analyse class:FluidTYPO3\MyExt\Provider\ContentProvider maybe not loaded or no autoloader?
• 14:19:47 <padd> i use all new dev versions
• 14:31:22 <soee_> cache ?
• 14:31:34 <soee_> 90% issues with T3 is cache :D
• 14:35:18 <padd> all cleared :p
• 14:35:30 <padd> t3_temp
• 14:35:34 <padd> and installtool :p
• 14:37:26 <padd> i use fluidcontent_core +f_bootstrap pages too
• 14:37:39 <padd> i wanna use btw :D
• 15:15:18 <pedda> class:FluidTYPO3\MyExt\Provider\ContentProvider <- is this because of some dummy code copy&paste ?
• 15:15:24 <pedda> @padd
• 15:16:00 <pedda> Do you have a file named ContentProvider in typo3conf/ext/my_ext/Classes/Provider/ ?
• 15:23:54 <pedda> how do i implement that collapsible feature which exists for row fce or accordion fce in page module?
• 15:24:08 <pedda> i want to have a tiny +/- button to collapse the preview section of my fce
• 15:24:39 <pedda> is it available for flux:form.content enabled fce's only?
• 15:25:31 <pedda> better say flux:grid enabled..
• 15:35:22 * soee_ bows danilobuerger
• 15:35:30 <danilobuerger> :-=
• 15:35:32 <danilobuerger> :-)
• 15:35:42 <danilobuerger> can you send me a picture of that :-)
• 15:36:26 <soee_> ;D
• 15:44:45 <pedda> @danilobuerger type (bow) in skype
• 15:44:48 <pedda> ^^
• 15:44:56 <pedda> looks pretty similar
• 15:45:04 <danilobuerger> ;-)
• 15:45:36 <pedda> would you mind give me a hint danilobuerger ?
• 15:46:11 <danilobuerger> on what?
• 15:46:12 <danilobuerger> bowing?
• 15:46:16 <pedda> lol
• 15:46:23 <danilobuerger> till the nose hits the ground :-)
• 15:46:25 <pedda> regarding collapse feature in backend for non flux:grid fceÄs
• 15:46:28 <pedda> fce's
• 15:46:31 <danilobuerger> hmm
• 15:46:44 <pedda> can i use some magic vh which has the same effect
• 15:46:58 <danilobuerger> what kind of fce?
• 15:47:05 <pedda> imagine an fce with lots of stuff, which i also want to render in preview
• 15:47:10 <danilobuerger> ah ok
• 15:47:14 <pedda> but if you have lets say 20 of them on a page
• 15:47:14 <danilobuerger> yeah i get it
• 15:47:25 <pedda> the page mode view gets really tall
• 15:47:39 <pedda> i want to collapse them as i can with accordons
• 15:47:44 <pedda> *accordions
• 15:48:53 <danilobuerger> hmm
• 15:49:28 <danilobuerger> can you gist yoru fce?
• 15:51:01 <pedda> Wip: https://gist.github.com/wikipeter/92f1772305f122cc8132
• 15:51:15 <danilobuerger> ah yes i think you can
• 15:51:22 <pedda> how ?
• 15:51:45 <pedda> afaik this is by default enabled in flux:grid affected fce's
• 15:51:56 <danilobuerger> give me a min to gist it ;-)
• 15:52:06 <pedda> sure
• 15:53:55 <danilobuerger> https://gist.github.com/danilobuerger/95811439bfa0990c9735
• 15:53:58 <danilobuerger> try that
• 15:54:05 <danilobuerger> (untested)
• 15:54:16 <pedda> (facepul)
• 15:54:20 <pedda> (facepalm)
• 15:54:30 <pedda> i could have thought of that myself
• 15:54:44 <danilobuerger> where should i send the invoice ;-)
• 15:54:59 <danilobuerger> those things usually cost 1 kasten tegernseer ;-)
• 15:55:42 <xaver> pedda: ship 2 kasten öttinger
• 15:55:52 <danilobuerger> pff
• 15:55:57 <pedda> öttinger .. really?
• 15:56:11 <pedda> i can offer quite delicious beer from düsseldorf
• 15:56:33 <pedda> but afaik danilobuerger is even closer to augustiner brewery which also has delicious HELLES
• 15:56:38 <xaver> 0.20 or 0.33?
• 15:58:15 <danilobuerger> well yes augustiner would work since its the star of all our testshoots fx https://vimeo.com/60506236
• 15:58:44 <pedda> i'ts amaizing how opular it became within a year
• 15:59:07 <pedda> last year there was no helles around my area.. in nower days you can't get it in larger amount
• 15:59:20 <pedda> even if you order it somehow at your local dealer
• 15:59:38 <pedda> they sey augustiner delivers whenever they want.. they don't stick to any apointments
• 16:02:47 <pedda> i love the taste of it
• 16:11:52 <xaver> danilobuerger: we have tegernseer @ work
• 16:13:58 <danilobuerger> us too
• 16:14:44 <xaver> is it in Bavaria allowed to open or run a company without beer in the fridge?
• 16:41:56 <pedda> danilobuerger it looks the same, but it's not collapsing
• 16:42:05 <danilobuerger> hmm
• 16:42:08 <pedda> do you think all those gen-XY id's are required ?
• 16:42:14 <danilobuerger> anyyhtign on the javascript console?
• 16:43:12 <pedda> only this one: Uncaught Element.alignToXY with an element that doesn't exist
• 16:43:49 <pedda> but as i never dealt with be layouts and be js functionality, i'm not that into it
• 16:45:06 <pedda> i will try to edit the html in chrome inspector in a working example of a grid based fce to determine what is missing
• 16:45:25 <pedda> i hope i can track it down
• 16:45:38 <danilobuerger> hmm i just tried it and for me it works
• 16:46:01 <danilobuerger> maybe you forgot to copy something
• 16:53:26 <randomresult> is @cedricziel around?
• 16:53:58 <randomresult> or can anyone help me with a commit message? i want to change a message made trying to use git rebase -i HEAD~1
• 17:00:01 <oliver_1234> hi all. next week i'm going to a meeting where i have to argue for fluidpages. Do you know some reference websites which use fluidpages? Especially swiss websites..
• 17:29:29 <soee_> randomresult: something with amend maybe ?
• 17:30:58 <randomresult> i rebased and recommitet forcepushed the whole shit!
• 17:31:15 <randomresult> dont give a shit about others.
• 17:36:48 <pedda> how come danilobuerger
• 17:37:04 <pedda> if i copy paste the gist, it doesn't work for me
• 17:37:20 <pedda> but maybe because teh mentioned js error interferres with it
• 17:37:28 <pedda> and breaks js functionality at all..
• 17:45:19 <beo|2> �
• 17:46:59 <danilobuerger> pedda could be, i just used what i gisted for you in another content element, and it just works fine
• 18:02:39 <xaver> randomresult ?
• 18:03:05 <xaver> rebase is a really powerful feature and cause a lot of damage
• 18:48:09 <pedda> danilobuerger may this be dependent to some certain flux version ?
• 18:51:39 <pedda> hmm.. this code in fact is working in another project of mine
• 19:19:40 <soee_> xaver: your extension to optimize images works with T3 6.2 ?
• 20:22:00 <xaver> soee_: no
• 20:22:11 <xaver> and i stopped maintenance
• 20:22:18 <xaver> or maybe
• 21:43:52 <pedda> danilobuerger got it working finally
• 21:44:00 <pedda> the js code was missing
• 21:44:00 <danilobuerger> cool
• 21:44:08 <danilobuerger> why was it missing?
• 21:44:19 <pedda> it was just missing
• 21:44:20 <pedda> dunno
• 21:44:25 <pedda> not added by default ?!
• 21:45:01 <pedda> i noticed other fc bs elements were expandable.. but they also contained script tags right after the collapsible container in be
• 21:45:38 <pedda> this is t3 6.2.3
• 21:46:01 <pedda> i also added lots of id's just to make sure my code is the same as the autogenerated
• 21:49:01 <pedda> if i add code this code in the Preview section, the collapse works: https://gist.github.com/wikipeter/da894f58d3075c4bc61d
• 21:49:09 <pedda> -code
• 21:52:42 <pedda> maybe the js code inclusion changed since a few commits in the typo3.cms
• 22:36:25 <xaver> ExtJs - puke