11:06:01 <Guest|73570> i got the TYPO3 Version 6.2.5
11:06:39 <martinhummer> according to this issue: https://github.com/FluidTYPO3/fluidpages/issues/212 i try to hide the column "Fluid Content Area" in the language view.
11:07:22 <martinhummer> but i'm stuck with getting the javascript part into the page module...
11:07:41 <martinhummer> is it possible to insert javascript into the backend with my provider extension?
11:09:52 <soee> xaver: i should add the icons today, they are ready
11:35:34 <drlimbo> What does the Message mean? "Flux View FluidTYPO3\Flux\View\ExposedTemplateView is able to read stored configuration from source code with hash value ..."
11:35:54 <drlimbo> and ".. to read stored configuration .."
11:36:01 <Akii> just a quick question, when inside page/content template you might already have the pid available
11:36:21 <Akii> {_all -> f:debug()} will show that
11:54:58 <drlimbo> What does the Message mean? "Flux View FluidTYPO3\Flux\View\ExposedTemplateView is able to read stored configuration from source code with hash value ..."
11:59:59 <bjo3rn> drlimbo it basically means that your template is error free.
12:00:20 <bjo3rn> to avoid that message set the debug level in flux to '2'
12:00:30 <bjo3rn> you will only be noticed about errors then
12:15:02 <rosieres> It seems that I cannot check if a flux:grid.column has content. Is that true? A condition on the name does not work. In layout on section name doesn't work either ... any hints?
12:36:06 <rosieres> Other way asked: How can I check if a column on page has content?
13:41:24 <Guest|73570> i updated flux and fluid on the newest versions, but i got that error: "The action name must be a valid string, array given (Array)."
14:34:19 <batjony> but I am trying to render images from a File Collection record
14:35:01 <batjony> for example, in your List view - you can add File Collections
14:35:30 <batjony> lets say you add a File Collection record with X images, and this File Collection record is with id 17
14:35:59 <batjony> then I am trying to get all the images for this file collection record with id 17 inside a plugin's template
14:37:31 <Gast> hi guys , i updated the flux und fluidextension and i get that error in the frontend : The action name must be a valid string, array given (Array).
15:03:57 <rosieres> Gast: and you should read the different version changes. Some vh might have changed
15:06:03 <beo6> Can i somehow have all flux:flexform.object not unfolded by default? So by default i only see the name/description and not all fields of the object?
15:08:18 <Momodedf> cause i dont want to make for just to know the lenght of my rootline
15:08:41 <beo6> whats the difference of v:iterator to the default iterator?
15:09:02 <batjony> btw I found the solution when you are trying to render file collection records, just for your information: <v:resource.record.fal table="sys_file_collection" field="files" uid="[sys file collection record uid]" as="images">
15:10:00 <Momodedf> the default iterator is set in a f:for when the v:iterator can call function
15:10:29 <Gast> @akii i run the update scripts ,but i still get the exception
15:38:25 <rosieres> jmverges: what did you do. What did you expect. What did you get? :-)
15:39:21 <rosieres> Gast: did you read this? -> https://fluidtypo3.org/blog/news/flux-71-changes.html
15:46:02 <rosieres> jmverges: https://fluidtypo3.org/community/irc-logs.html?tx_fluidtypo3org_content[date]=20141029&cHash=82b3974dc2d446ca4a44210b06ed5906#17:52:00 -> 17:52:00 -> looks like your answer -> It's often helpful to query the irc logs -> https://fluidtypo3.org/search.html?q=typo3pageModule.js
16:03:02 <Gast> @xaver can you help me with my problem? I updated flux 7.0 to 7.1 and get the error "The action name must be a valid string, array given (Array)" in the frontend
16:04:14 <rosieres> @Gast -> determine where it occours ... "The action name must be a valid string, array given (Array)." ... it must not neccessarily be flux or fluidcontent. It's also possible that this occours in a different extensions. Deinstall every extension that is not needed and clear all caches every time in installtool
16:07:35 <Gast> but that error appeared only when i updated flux and the first lines show that the AbstractFluxController.php throw this exception
16:10:33 <rosieres> install builder extension and run the error checking. Also enable debug mode in flux
16:11:13 <beo6> Can i somehow have all flux:flexform.object not unfolded by default? So by default i only see the name/description and not all fields of the object?
16:12:55 <rosieres> Gast: do you run a provider extension?
16:42:34 <jloew> Does anyone happen to know, why typo3 6.2.6 and flux 7.1 don't show my grid layout in the backend? I've updated the namespace to match the new one, Frontend works like a charm, but I can't seem to get it to display the backend correctly!
16:43:45 <jloew> I'm talking about grid in the page Layout, not Content
16:45:44 <Akii> jloew: select fluidtemplate as the backendlayout
16:48:34 <NamelessCoder> jloew it's a good idea to keep an eye on the blog, we always write about changes like that
16:49:25 <jloew> I know =) this is just the first time I'm implementing on 6.2.6 and flux 7.1 and I think I got caught up a little too much in the namespace changes that I must have missed that...
16:52:00 <rosieres> NamelessCoder: perhaps put this into the Channel head -> https://fluidtypo3.org/search.html?q=your+searchwords
16:52:30 <NamelessCoder> hopefully people already know how awesome the search is
16:52:55 <rosieres> I did forget it . . . that's why I mention
16:55:09 <jloew> I did use it, but the search engine is only as smart as the person using it, it seems...
18:26:27 <bjo3rn> maybe. what is the actual question?
18:27:07 <jmverges> first of all I wrote: {namespace m8th=Tx_M8thstructures_ViewHelpers}
18:27:36 <xaver> use namespaces /Vendor/Plugin/Viewhelpers and
18:27:37 <jmverges> then I create a class class InArrayViewHelper extends \FluidTYPO3\Vhs\ViewHelpers\Asset\AbstractAssetViewHelper with namespace "namespace MANDARINA\M8thstructures\ViewHelpers;"
18:46:11 <jousch> hi, (topic: <v:asset.style />) is it possible to include a css with an absolute custom domain url? I've a typo3 instance with many subdomain.domain.at websites they share many assets. Any suggestions?
18:47:51 <bjo3rn> jousch is plugin.tx_vhs.settings.prependPath = http://static.mydomain.com/ what you are looking for?
18:50:31 <jousch> think of a photographer website with a main page for general stuff. then there are "sub websites" for peoplephotography, wedding, still, ...
18:51:19 <jousch> I think this features resolves my problem
19:15:35 <jousch> bjo3rn is it also possible to deactivate for certain assets?
20:42:59 <TaucherMK> Hi, I have a really simple content element, providing two columns. It worked a long time and seems to be broke with an update, I don’t know which though. The code can be found here: http://pastebin.com/9eP1C0zU
20:43:49 <TaucherMK> The content elements in existing elements in the columns are not displayed in backend and if I add new elements, they appear in both columns
20:44:55 <NamelessCoder> TaucherMK you need to read the migration notes of the documentation, specifically how flux:form.content now works and doesn't. https://fluidtypo3.org/documentation/templating-manual/appendix/migration/to-flux-71.html
20:56:22 <TaucherMK> Thank you NamelessCoder, that did it. Is there still a way to get the columns aligned next to each other in the backend? The style option is still present on column, but it doesn’t work for me?!?
20:57:12 <NamelessCoder> depends on what you mean by aligned next to each other
20:57:28 <NamelessCoder> two columns inside the same row will do that as default 50% 50% split
21:00:02 <xaver> next feature is finished - return the ip from VM
21:01:57 <TaucherMK> NamelessCoder: In my case each column gets its own row in the backend view (only content elements though, fluidpage columns split equally)
21:05:28 <s-andersen> After upgrade to 6.2 from 6.0, my flexible content elements displays: LLL:EXT:flux/Resources/Private/Language/locallang.xlf:flux.my-widget.columns.column in the backend. Can't find out why?
21:06:07 <TaucherMK> NamelessCoder: Just an issue of display I guess, it’s placed in tds and one of the columns just takes too much space
21:14:44 <NamelessCoder> s-andersen looks like one or more templates are being rendered with the "flux" extension context rather than fluidcontent. Did you also upgrade all the fluidtypo3 extensions when you upgraded the core?
21:19:49 <soee> btw fluidcontent and fluidpages are almost compatible with 7.0-dev, there is only one array function to replace in both extensions to make the work
21:21:49 <s-andersen> NamelessCoder: Yes I upgraded flux, fluidcontent, fluidpages and vhs to new versions
21:22:51 <NamelessCoder> s-andersen do you use any other extensions which contain Provider classes and if so, are those also updated and/or have you ensured the Provider uses your extension key, not "flux"?
21:23:59 <s-andersen> NamelessCoder: I'm not sure how to check that, but I'm 80% certain that I'm just using the default FluidTYPO3 setup
21:24:56 <soee> xaver: my colegue forget to add 5 icons, i will upload them this week i think. The one that are ready https://github.com/bootstraptheme-for-typo3/fluidbootstraptheme/pull/233
21:25:12 <soee> but the build fails, but thats not my fault i think
21:26:59 <s-andersen> NamelessCoder: Looks like I'm using the old tx_fed typoscript setup in my extension, maybe that is the problem?
21:27:21 <NamelessCoder> yep - that will force the "flux" extension key on every element registered that way
21:28:16 <NamelessCoder> you may be able to simply switch to a Core::registerProviderExtensionKey approach and delete the typoscript, but that requires you use a provider extension - fileadmin files not supported
21:36:40 <s-andersen> NamelessCoder: Now I have changed the typoscript to the new version, but my FCE's will not register in the backend. They are rendered nicely in the frontend though
21:43:30 <NamelessCoder> clear system cache specifically
21:46:30 <s-andersen> NamelessCoder:Have cleared cache through install tool and in backend, no luck. Creating a dummy extension with "builder" gives me the example FCE, so somewhere there must be something I haven't changed correctly yet.
21:57:07 <s-andersen> Forgot to change ext_tables.php.... that helped a lot :)
22:21:44 <soma> unfortunately i'm having some other problems too. labels disappear after clearing caches, reappear after flushing all caches in install tool. also setting "debug mode" to 1 in flux config in extensionmanager does not show debug messages anymore