IRC logs

20150827

Logs from channel #fedext on freenode - our official support channel.

IRC log range: 20150827*

20150827

  • 02:41:11 <mneuhaus> god i hate gridelements, why anyone insists on using this pile of crap is baffling
  • 03:19:47 <Momodedf> Hi every one :)
  • 08:17:03 <Guest|94905> hi to all the world I'm a little blocks , I worked on a rte but when I inserted an image size is 300 max width is can I configure Rte to have a larger width thank you for your help
  • 08:17:28 <Guest|94905> hi to all the world I'm a little blocks , I worked on a rte but when I inserted an picture size is 300 max width is can I configure Rte to have a larger width thank you for your help
  • 08:38:16 <Rabe69> I want to use extension "site" to kickstart a new project. If i try to install it, I get warnings about required extension "fluidcontent" and "fluidpages", which are not available in a version. Can i ignore this warning?
  • 08:38:53 <Rabe69> I want to use extension "site" to kickstart a new project. If i try to install it, I get warnings about required extension "fluidcontent" and "fluidpages", which are not available in a compatible version. Can i ignore this warning?
  • 08:39:37 <Rabe69> The following errors were found while trying to install "site":
  • 08:39:37 <Rabe69> Required extension "fluidcontent":
  • 08:39:37 <Rabe69> The extension fluidcontent is available in version 4.3.1 but is needed in version 4.1.0 - 4.2.99
  • 08:39:37 <Rabe69> Required extension "fluidpages":
  • 08:39:37 <Rabe69> The extension fluidpages is available in version 3.3.1 but is needed in version 3.1.0 - 3.2.99
  • 08:46:49 <Momodedf> I think you should better use builder to start a news project
  • 09:04:46 <Rabe69> @Momededf: but what's the "site" exension about?
  • 09:07:36 <Momodedf> as I see, it is supposed to install dependencies (flux, fluidpages, etc)
  • 09:08:16 <Momodedf> and kickstart many things
  • 09:08:38 <Momodedf> I alse just started a new project today
  • 09:09:20 <Momodedf> and since I've had the same error message I didnt used it
  • 09:10:10 <Momodedf> I just installed vhs flux fluidpages fluidcontent and builder by myself and created my provider with builder
  • 09:15:07 <pedda> hi there
  • 09:15:23 <pedda> anyone experienced with EXT:flll around?
  • 09:20:09 <pedda> re
  • 09:25:16 <xaver> pedda: flll - why?
  • 09:25:37 <pedda> well i can't manage to use it the proper way
  • 09:26:01 <xaver> best way - a small whitelist :)
  • 09:26:11 <pedda> i install it, i create an fce for instance, with no label attributes defined at all, and i expect those labels to be "generated automagically"
  • 09:26:23 <pedda> well i have an extension in my whitelist
  • 09:26:34 <xaver> active checkbox is on?
  • 09:26:38 <pedda> let's say it's xyz_template
  • 09:26:41 <xaver> you need to access it in BE
  • 09:26:44 <pedda> yes it is
  • 09:26:56 <pedda> flll writes content into my lll file
  • 09:27:03 <xaver> yes
  • 09:27:05 <pedda> but i still don'T get when, and why
  • 09:27:12 <pedda> anw why not (sometimes at least)
  • 09:27:14 <pedda> :)
  • 09:27:24 <pedda> i'm just a bit confused
  • 09:27:41 <pedda> the readme says: fll will generate keys, for extensions in the whitelist
  • 09:27:47 <xaver> it writes all missing labels in extension - source is the path
  • 09:27:57 <xaver> yeah
  • 09:28:03 <pedda> it will happen on the fly, as soon as this non existing label should have been accessed for rendering (in backend for instance)
  • 09:28:23 <pedda> example: i have a simple Test.html fce
  • 09:28:30 <pedda> with just a basic flux markup
  • 09:28:38 <xaver> yes
  • 09:28:52 <pedda> i expect keys like flux.test , flux.test.description and so on.. to be generated
  • 09:29:06 <pedda> this happens in actually for some of my fce's but not for all
  • 09:29:10 <pedda> and i don't get why
  • 09:29:24 <pedda> the readme states also: only missing labels will be added to lll file
  • 09:29:30 <xaver> yes it does generate the keys in Backend access
  • 09:29:52 <pedda> so .. if i use lfeditor to define a value for flux.test and hit save
  • 09:30:01 <pedda> this value is written "forever" into my LLL file
  • 09:30:18 <pedda> and shouldn't be readded on next be access of Text fce
  • 09:30:22 <pedda> correct ?
  • 09:30:34 <pedda> well.. sometimes it is added in fact
  • 09:30:41 <pedda> and this is why i'm confused
  • 09:30:54 <pedda> i bet i'm missing something (regarding understanding)
  • 09:31:05 <pedda> what i also got so far
  • 09:31:37 <pedda> if i use v:l(key: 'any.key.defined.manually', default: 'myDefaultValue') no key will be added
  • 09:31:40 <pedda> correct ?
  • 09:31:48 <pedda> because i defined one on my own
  • 09:32:15 <pedda> within flux at least.. it still needs to be added to the LLL file, but manually then, right?
  • 09:32:36 <pedda> you see? i have a few questions regarding the whole magic in the background ;)
  • 09:32:56 <xaver> flux requests the language service for the label
  • 09:33:39 <pedda> i try to follow the "changes" of my lll file via git client, to see what is added and what is removed.. and it appears to me, as if a key is added at one point .. and removed again at some other point, depending on the backend view i access currently
  • 09:33:56 <xaver> language service is signalSlot or similar and if an whitelisted extension access and can't find the label and it is backend it writes the requested key
  • 09:34:10 <pedda> okay
  • 09:34:12 <pedda> but
  • 09:34:30 <pedda> if it is written, it "starts" to exist and willl never ever be readded/removed again
  • 09:34:32 <pedda> right?
  • 09:35:37 <pedda> i access my test fce, flll writes flux.test to my lll file, and after this happened, it will reside there as long as i remove the key manually.. correct ?
  • 09:37:46 <xaver> Language cache and stuff causes sometimes problems and i thiunk also a few bug :P but it should work that way
  • 09:38:21 <xaver> i think i never tested it with not english backend language
  • 09:38:30 <pedda> well .. i would expect it to work this way, the readme states the same facts somehow.. but what i actually see is a bit confusing :)
  • 09:38:48 <pedda> agreed regarding the language cache thingy..
  • 09:38:57 <pedda> this is definetly something i need to keep in mind
  • 09:39:11 <xaver> create a issue with templates attached
  • 09:39:54 <pedda> i would also expect to work with flll runnung in the background for the time of development, i then disable fll, because my LLL file is full of keys, and hand that project over to an editor who takes care of all those keys via LFEditor
  • 09:40:06 <pedda> *running
  • 09:40:39 <zaphod76> Hi, I’ve got a question about fluidpages/flux with TYPO3 7.4. I realised some configuration for the “page configuration” tab in the page properties using flux. Every change is only working after cleaning the caches by the installtool. There is noch other way to get it working. I can’t remember such behaviour in former TYPO3 versions (like 6.2). Any
  • 09:40:39 <zaphod76> known issues about it?
  • 09:41:31 <pedda> zaphod76 maybe this is related to the general configuration of your current 7.4 project ?
  • 09:41:52 <pedda> regarding cache configuration
  • 09:42:15 <zaphod76> Maybe but i didn't configurate something special for caching...
  • 09:43:17 <pedda> didn't configure smth. special = ?
  • 09:43:30 <pedda> did you disable/enable cache for instance?
  • 09:44:21 <zaphod76> I never configurated something about caching in TYPO3. I always used it as it was after installing...
  • 09:44:54 <zaphod76> configure... :-D
  • 09:52:42 <pedda> i use those page configuration properties based on ts properties
  • 09:52:54 <zaphod76> If i change something in my fields in page configuration an open a page that was never opened before, I can see the correct output. Every other page shows the wrong stuff
  • 09:53:12 <pedda> so name="settings.layouts.default.header.enableBreadcrumb" is the name of a flux:field.checkbox
  • 09:53:41 <pedda> this way they're kind of mapped to typoscript properties which you can debug easily
  • 09:53:52 <pedda> in fe, while dealing with your issue
  • 09:54:14 <pedda> i never discovered some strange behaviour in relation to cache and flux at this position
  • 09:54:38 <pedda> what might interfere and look like an issue is the feature of assigning templates for current and child pages
  • 09:54:41 <zaphod76> I did it using TS too but today I decided to become more comfortable for the customer...
  • 09:55:02 <pedda> as well as the parent decied option and then in addition to your flux properties which you maybe expect to become inherited
  • 09:56:22 <pedda> you get me? maybe you deal with an "(non)issue" just due to the matter of fact, that you except page 10 to inherit some setting, which can't be inherited, as it is redefined by page 5 which is the parent page of page 10
  • 09:56:48 <zaphod76> Ok
  • 09:57:02 <pedda> which looks like an issue in the end, but is not
  • 09:57:11 <pedda> this is just an asumption
  • 09:57:43 <pedda> on the other hand: you only see the correct value in FE if the page is not cached is somewhat different
  • 09:59:03 <zaphod76> I see the correct value after cleaning the cache. Then it will be build new an it shows the right value.
  • 09:59:36 <zaphod76> But after every change you have to clean it again
  • 10:01:55 <pedda> maybe this can help you: https://docs.typo3.org/typo3cms/extensions/news/latest/AdministratorManual/BestPractice/ClearCache/Index.html
  • 10:02:14 <pedda> if you put TCEMAIN.clearCacheCmd = pages on your root page
  • 10:02:42 <pedda> the pages cache should be cleared whenever you edit a record (or the page properties maybe?!)
  • 10:02:57 <pedda> but this still looks awkward to me
  • 10:03:36 <zaphod76> I think this will clean the same cache that I can clean from the backend. This does not have any effect. I have to use cache cleaning by installtool
  • 10:04:46 <pedda> hmm .. sorry buddy, but i'm still sticking to 6.2 LTS version and didn't ran into this by now
  • 10:04:46 <zaphod76> Maybe something about extbase? I jut "use" the stuff but I'm not a real developer. Therefore I'm not able to locate such kind of misterious behaviour...
  • 10:05:25 <pedda> were speaking of resulting flexform which is generated by the help of EXT:flux and is cached that hard that you only can clear it from the installtool..
  • 10:05:28 <zaphod76> I hadn't had such probs in 6.2... I'm using 7.4 for the first project now
  • 10:05:53 <pedda> i don't think extbase as a general topic is the issue here
  • 10:06:12 <pedda> maybe 7.4 has some new additional configuration options which can help you
  • 10:06:27 <pedda> what's new 7.0 - 7.4 pdf's could help
  • 10:06:49 <pedda> to see if something new was introduced and is causing you headache now
  • 10:07:12 <zaphod76> I think so too. I have to decide wether to downgrade to 6.2 or wait for a fix. But for a fix it must be a bug and not wrong shit made by myself...
  • 10:08:11 <pedda> well: if you're not in a hurry at all, i would do some more investigation
  • 10:08:22 <pedda> rather than going back to 6.2
  • 10:09:18 <zaphod76> I read about changes in caching for "AbstractConditionViewHelper" and everything that is based on it. Would be nice to unterstand what that all is about :-D
  • 10:09:31 <pedda> hehe
  • 10:09:43 <pedda> this requires even more spare time from you ;)
  • 10:09:53 <zaphod76> I think so...
  • 10:09:59 <pedda> but it'S necessary if you do this for living
  • 10:11:14 <zaphod76> I do it for living but every time we are going to have real development stuff it is the work for a developer...
  • 10:12:18 <pedda> well maybe this issue should be inspected by a developer too..
  • 10:12:32 <zaphod76> Now it is just a problem. But not the first TYPO3 prob in my life. And all the other probs found their solution too.
  • 10:13:32 <zaphod76> In my dreams there was a developer reading the chat knowing about a solution :-)
  • 10:14:02 <pedda> uuuh.. daydreamin' ? you should rest for a while then ;)
  • 10:14:12 <zaphod76> :-D
  • 10:15:13 <zaphod76> I think i will ignore it for a while. Sometimes this works too
  • 11:00:58 <drlimbo> good afternoon
  • 11:01:19 <drlimbo> i have a strange issue with my FCE after upgrading (vhs,flux,fluidcontent,fluidpages)
  • 11:02:12 <drlimbo> Frontend AND backend crashes, if there is ANY FCE Element on a page
  • 11:02:18 <drlimbo> and i get the message Template could not be loaded. I tried "xxxxxx/ext/ogbase/Resources/Private/Templates/Content/Index.html"
  • 11:02:43 <drlimbo> all my FCE's are stored in this /Content Folder and Subfolders
  • 11:03:02 <drlimbo> IF i add an index.html FCE - this will be choosen everywhere in backend and in frontend
  • 11:03:48 <drlimbo> BUT in the database and while editing in the backend - i can choose the Rights FCE Elements, but after chaning the FCE-Type, it switches back to my dummy index.html FCE
  • 11:04:53 <drlimbo> also when adding a new element on a page (without an FCE already) i can see all FCE's (with broken icons - but i didnt set an icon)
  • 11:12:35 <drlimbo> someone an idea?
  • 11:17:01 <drlimbo> mneuhaus maybe? =p
  • 11:32:55 <pedda> drlimbo check namespacing in database of related tt_content records
  • 11:33:16 <pedda> check if your provider extension supports namespacing now, but the records in database don't
  • 11:33:19 <pedda> and vice versa
  • 11:33:56 <pedda> if Index.html "is called" then, because fluidcontent was unable to determine the proper file or action related to the selected fce in backend
  • 11:34:26 <pedda> adjust such a record manually in database to see if it helps
  • 11:36:02 <pedda> if it does: https://gist.github.com/wikipeter/6e67695b143efd77d40a
  • 11:36:41 <pedda> as you might need to adjust all occurences of extension_name: and change them to Vendor.ExtensionName:
  • 11:38:00 <pedda> this snippet is called rename provider extension, as you could also adjuist all my_old_extensionkey: to myNewVendor.MyNewExtensionKey: for both pages and content records
  • 11:38:37 <pedda> btw NamelessCoder you didn't review https://gist.github.com/wikipeter/6e67695b143efd77d40a by now, i added it to the library on fluidtypo3.org
  • 11:39:23 <pedda> drlimbo: always backup your database before you go on with those sql commands!
  • 11:39:30 <pedda> just a reminder ;)