fluidtypo3 / fluidpages Goto Github PK

By default we can't do nothing and get only error message in Page Configuration tab if page layouts (for page and subpages) aren't set in Page Layouts tab. Maybe it is possible to just hide Page Configuration tab if layouts aren't set or there is no any configuration defined for page ?

Hi Claus,
In the Configuration Setting of a page template I define:

<flux:flexform.grid.column colPos="5" colspan="1" name="Inhalt Rechts"/>

Basically everything works besides the minor flaw that the name does not show up in the Column select box:
[invalid value ("5")]

I rememember that I had this issue with prior versions. I got rid of this when I installed the extension "gridelements". This does not work in the current setup.

My setup:
TYPO3 (v 6.0.0)
Flux (v 5.0.1)
Fluidcontent (v 2.1.0)
fluidpages (v 1.1.0)

preparing a site to upgrade from 4.5.23 to 6.0.4 and changing from jetts templates to fluidpages. With the existing database and files (fluidpages 1.3.0) after an upgrade I receive an error when switching to the list module:

Uncaught TYPO3 Exception
#1294585070: No module "" could be found. (More information)

UnexpectedValueException thrown in file
/home/<user>/t3src/typo3_src-6.0.4/typo3/mod.php in line 55.

This error will occur if I click on a page doktype in the pagetree in the list module. If I click on a sysfolder or shortcut however, the list module does load.

If I uninstall fluidpages, the list module works again. The error from core is not particularly useful, I'm an integrator not a programmer so unsure of how to properly debug this, but so far I have tried:

• in devlog when accessing the list module all I get is the UnexpectedValueException nothing else.
• turning on flux debug mode (but have no templates set up yet so no info from that)
• clearing cache and temp files (including the flux/fluidpages manifest files in typo3temp) - no effect
• switching source to TYPO3 versions 6.0.1 -> 6.0.4 with fluidpages 1.3.0 and below gives the list module error with the existing database
• TYPO3 version 6.0.0 and the upgraded database does work with fluidpages and the list module - something changed after that version?
• A new empty install of 6.0.4 and fluidpages 1.3.0 does work

Is there anything else I could do to narrow down the conflict between core/fluidpages more?

I noticed Fluid variables {page}, {user}, {cookies}, {session} defined in Tx_Fluidpages_Controller_AbstractPageController are not available anymore in a Fluid template. As a result, If I put <f:debug>{page}</f:debug> in a template, the output of the debug would be "NULL".

I also tried adding my custom assignation for the sake of testing by adding $view->assign('foo', 'bar'); in Tx_Fluidpages_Controller_AbstractPageController. Outcome is also NULL consequently to the rest.

Environment: TYPO3 6.1.1
FluidTYPO3: master

I wonder if that is an isolate case...

Added folder doktype to basic.doktypes but it doesn't work.
Also adding '254' to $doktypes in ext_tables.php does not work.
Didn't try it with 6.0.

First, thanks for your very inspiring work.

I have spotted a rendering issue related to page layouts. Default page layout provided by EXT:fuildpages_bootstrap makes the value fluidpages->Render saved in the DB, column tx_fed_page_controller_action to be precise. The second example will save fluidpages->WithSidebar as value.

However, only the first page layout is rendered on the FE. I guess this is due to the last commit which removes the call of method setTemplatePathAndFilename. Check out: NamelessCoder@9315159

With the last commit, you will also notice line 111 has become useless (which is not the aim I would say) https://github.com/NamelessCoder/fluidpages/blob/master/Classes/Controller/PageController.php#L111

Re-introducing the method call solved the problem:

diff --git a/Classes/Controller/PageController.php b/Classes/Controller/PageController.php
index 98e9878..b5a4070 100644
--- a/Classes/Controller/PageController.php
+++ b/Classes/Controller/PageController.php
@@ -111,6 +111,10 @@ class Tx_Fluidpages_Controller_PageController extends Tx_Extbase_MVC_Controller_
                list ($extensionName, $action) = explode('->', $configuration['tx_fed_page_controller_action']);
                $paths = $pageConfigurationProvider->getTemplatePaths($row);
                $flexformData = $pageConfigurationProvider->getFlexFormValues($row);
+
+               $templatePathAndFilename = $provider->getTemplatePathAndFilename($row);
+               $view->setTemplatePathAndFilename($templatePathAndFilename);
+
                $view->setLayoutRootPath($paths['layoutRootPath']);
                $view->setPartialRootPath($paths['partialRootPath']);
                $view->setTemplateRootPath($paths['templateRootPath']);

Can you fix the issue?

Hi,

let's say I overwrite the rootPaths in TS like this:

plugin.tx_fluidpagesbootstrap.view {
    templateRootPath = fileadmin/standard/templates/pages/Templates/
    partialRootPath = fileadmin/standard/templates/pages/Partials/
    layoutRootPath = fileadmin/standard/templates/pages/Layouts/
}

Now if I want to add a new page-layout called "mylaout"

• adding "mylayoutAction()" into the PageController.php
• creating an appropriate Mylayout.html in the Template- and Layouts-folder under "fileadmin"

results into an Error

"Sorry, the requested view was not found."
The technical reason is: No template was found. View could not be resolved for action "errorPage" in class "Tx_FluidpagesBootstrap_Controller_PageController".

To avoid the error i have to add the same html-files into /typo3conf/ext/fluidpages_bootstrap/Ressources/Private/Templates/Page

All templates have this code:

<div xmlns="http://www.w3.org/1999/xhtml" lang="en"
     xmlns:v="http://fedext.net/ns/vhs/ViewHelpers"
     xmlns:f="http://typo3.org/ns/fluid/ViewHelpers">

W3C validator shows an error on this HTML code.
xmlns code is not allowed in a div tag.

Hi Claus,

as soon as I install fluidpages 1.3.0 on a TYPO3 6.x , Page Module doesnt show any columns and going to page properties throws error "Unable to get a valid page template configuration from page UID 1".

Static typoscript templates are included for flux and fluidpages.
Flux works without fluidpages though, vhs is also instelld

Wouldn't be a problem if Tx_Flux_Service_FluxService::getViewConfigurationForExtensionName() wouldn't return the paths without trailing slashes and generally that case should be handled

if you're using language file references (format LLL: ...) for column names, they get not resolved via overwritten "colPosListItemProcFunc" within "BackendLayoutView" class

You can find informations about templavoila_framework at this site: http://templavoila.busynoggin.com/
Here you can see how to use the skin selector: http://templavoila.busynoggin.com/workflow/integrate-design-into-typo3/create-a-new-skin/

For me the templavoila_framework made my life easier. I would be happy to use something like this with fluidpages also.

Hello,
would it be possible to add multilanguage support to fluidpages and maybe to the other extensions?

Thanks in advance

Stephan

I just installed a brand new server with TYPO3 6.0.0 (and PHP 5.3.10) on it.
I installed the following extensions:

• fed
• fluidcontent
• fluidcontent_bootstrap
• fluidpages
• fluidpages_bootstrap
• flux
• vhs

I included the static TS required to use the page templates and selected the template for the single Home page. So far, so good.

Now I'm getting logged out every other click. I switch between the View and Page module and suddenly I need to log in again.

I'm posting this here because I spotted NamelessCoder@c56a88e and assumed it's related to this issue. So I replaced my local copy of fluidpages with the from GitHub but the problem remains :\

It seems that there is an compatibility issue when using hype_html5.

Output:
Content element type "fed_fce" has no rendering definition!

Is there any workaround given?
Thanks.

Hello I have a big problem on a clients project with coping elements or pages.
I tested it on a fresh twitterbootstrap installation now and have the same problem.
When copying a Typo3 page with a lot of twitter bootstrap elements the server is running in an ERROR 500 and both pages gets broken.

I did a test with the page: "Examples extended / Bootstrap components"
I put 20x4 Accordions in a Column row element.

I have a Managed Server with PHP 5.4 and I know this problem can be solved with more RAM and power, but this cant be a sulution. Any help?

As Editor, I would expect the internal references of TYO3 being updated.

Scenario: 
----------------
When I am on module "Page"
And I create new Content Element
And I close and save the content Element
And I go to module "List"
Then I expect to to see Ref "1"

It does not work for any content used in module Page. Surprisingly enough, internal references work for nested content element. E.g. an Content Element in a FluidRow.

Updating the index by hand does not improve the situation.

php /Users/fudriot/Sites/Ecodev/wycliffe.fab/htdocs/typo3/cli_dispatch.phpsh lowlevel_refindex -e

I don't know whether we can do something.

What is the preferred way of translating hardcoded labels like 'Parent decides' in PageLayoutSelector.php? Give me something to commit please ;)

When opening a folder in the Page module (in my case the storage folder for News records), the following error is thrown:

PHP Catchable fatal error:  Argument 4 passed to Tx_Flux_Service_FluxService::getGridFromTemplateFile() must be of the type array, string given, called in /var/www/website/typo3/typo3conf/ext/flux/Classes/Provider/AbstractConfigurationProvider.php on line 166 and defined in /var/www/website/typo3/typo3conf/ext/flux/Classes/Service/FluxService.php on line 205, referer: http://website/typo3/backend.php
PHP   1. {main}() /var/www/typo3/typo3_src-6.1.1/typo3/sysext/cms/layout/db_layout.php:0, referer: http://website/typo3/backend.php
PHP   2. TYPO3\\CMS\\Backend\\Controller\\PageLayoutController->main() /var/www/typo3/typo3_src-6.1.1/typo3/sysext/cms/layout/db_layout.php:143, referer: http://website/typo3/backend.php
PHP   3. TYPO3\\CMS\\Core\\Utility\\GeneralUtility::callUserFunction() /var/www/typo3/typo3_src-6.1.1/typo3/sysext/backend/Classes/Controller/PageLayoutController.php:521, referer: http://website/typo3/backend.php
PHP   4. call_user_func_array() /var/www/typo3/typo3_src-6.1.1/typo3/sysext/core/Classes/Utility/GeneralUtility.php:3958, referer: http://website/typo3/backend.php
PHP   5. Tx_Fluidpages_Override_Backend_View_BackendLayoutView->getSelectedBackendLayout() /var/www/typo3/typo3_src-6.1.1/typo3/sysext/core/Classes/Utility/GeneralUtility.php:3958, referer: http://website/typo3/backend.php
PHP   6. Tx_Fluidpages_Backend_BackendLayout->postProcessBackendLayout() /var/www/website/typo3/typo3conf/ext/fluidpages/Classes/Override/Backend/View/BackendLayoutView.php:89, referer: http://website/typo3/backend.php
PHP   7. Tx_Flux_Provider_AbstractConfigurationProvider->getGrid() /var/www/website/typo3/typo3conf/ext/fluidpages/Classes/Backend/BackendLayout.php:97, referer: http://website/typo3/backend.php
PHP   8. Tx_Flux_Service_FluxService->getGridFromTemplateFile() /var/www/website/typo3/typo3conf/ext/flux/Classes/Provider/AbstractConfigurationProvider.php:166, referer: http://website/typo3/backend.php

This is with the current master (fluidpages:dd6f548e84d53fe6743b4db8aeff1a2c9da526c3, flux:82070c00241e2f687d257ed8fa474b264d258828) as of right now in TYPO3 6.1.1.

Hey there,

I have a question about the handling of "Page Configutation" when working with template inheritance by selecting a template for subpages. As it appears to me when selecting a template for subpages (Lets say on page A) and I create a new subpage (B) underneath that page the "Page configuration" is copied from page A into B.

If I ever want to change a setting in "Page configuration"-Section I have to change it on pages A and B and if i have 100 pages in the system I have to touch all of them.

Am I right or am I missing something?

If that's the behavior, wouldn't it at least be nice to have an "inherit page configuration" option in the subpages settings so one can have a true inheritance in "page configuration"? If so, I'd be willing to contribute to that.

kind regards,
Nabil

In method Tx_Fluidpages_Service_PageService::getColumnConfiguration() the used $page object lacks a definition.And so the following config handling fails.

First of all thanks for the great work.

I have one feature request. Unfortunately it is not possible at the moment to show preview-icons for page templates under the "Page Layout" - selectbox, like with templavoila or backend layouts.

Could you please add this feature?

Outputs

Page Configuration - subpages
Data Structure ERROR: No proper configuration!

When using flux dev (denoted by version 7.0-dev) the constraint for flux in fluidpages will not be matched in typo3 6.1.7, thus not being able to install fluidpages

When I upgraded from the original, working setup, I realized some errors turning up which i don't quite have a clue how to solve them

Following Message in BE-Layout with admin-user

No edit access

Following Messages are turning up in my FE

#1301648167: The requested page didn't have a proper connection to the tree-root!<br /><br />()
TYPO3\CMS\Core\Error\Http\ServiceUnavailableException thrown in file
/myserver/public_html/webshare/customer/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php in line 1476.

My Setup

• TYPO3 (6.1.7)
• Fluid Templating Engine - Fluid (6.1.0)
• Fluid Content Engine - fluidcontent (3.1.0)
• Fluid Pages Engine - fluidpages (2.1.0)
• Flux: Fluid FlexForms- flux (6.0.2)
• VHS: Fluid ViewHelpersVHS: Fluid ViewHelpers - vhs (1.8.4)

Any idea if it's my installation or a bug in fluidpages?

Hi Claus,

is it possible to set the page template for child pages in TypoScript? I am trying to integrate direct_mail and newsletter pages are contained in a sysfolder. Other hints or workarounds are of course welcome as well. Thanks in advance.

Cheers
Björn

Reproduce Issue with the following steps

• Create any kind of Elements (event the TYPO3 Default Elements): i.E. Header with Title "lalala"
• Copy this element. (click on the drag&drop element, and choose context menu copy)
• Rightlick there again, choose paste after

The Element is going to be placed before... which isn't the way TYPO3 does it.

Would it be useful to remove 'Backend Layout (this page only)' and 'Backend Layout (subpages of this page)' from the page properties because thy are not needed anymore?

Hi Claus,
I just gave 6.0 another try and can't get fluidpages to work. After enabling the extension editing of pages or folders is no longer possible because of an endless redirect loop reportedly caused by /typo3/sysext/cms/layout/db_layout.php. Can you help? Thanks in advance.

Cheers
Björn

TYPO3: 6.2beta5
fluidpages: git development

In the Page module, when in Language mode:
When using the XClasses provided by fluidpages with TYPO3 6.2beta5, the edit/hide/delete/etc-icons for the ce's do not show up anymore when hovering over a ce's title bar.

Hi Claus, it is verry important for me using workspaces in future development.

I noticed some troubles and possible improvements in /Service/PageService so I'm interesting in rewriting this class. I plan to do this in multiple steps:

1. using namespaces and replacing depricated methods/classes
2. improving code

I hope you have no objections.

Other classes should follow, but I think it would be stupid, fixing the code and keeping depricated methods/techniques.

kind regards
Heiko

Which is the correct way to translate grid comulns labels?

Hardcoded - works, but isn't translated

<flux:flexform id="pageOneColumn">
  <flux:flexform.grid>
    <flux:flexform.grid.row>
      <flux:flexform.grid.column colPos="0" name="Main Content" />
    </flux:flexform.grid.row>
  </flux:flexform.grid>
</flux:flexform>

LLL:EXT - works in page module, but isn't translated in field tt_content.colPos if you edit a CE

<flux:flexform.grid.column colPos="0" name="LLL:EXT:myext/Resources/Private/Language/locallang.xlf:flux.pageOneColumn.columns.0.name"/>

FLUID f:translate - works in page module and is translated in field tt_content.colPos if you edit a CE.

<flux:flexform.grid.column colPos="0" name="{f:translate(key: 'flux.pageOneColumn.columns.0.name' default: 'Content')}"/>

I now use the FLUID f:translate method. But it would be nice to have an auto-translate-featur for columns too. Or did I siply didn't set the translation key?

Hello!

I have problems:

PHP 5.4.x
TYPO3 6.0.10
Fluid Content Engine / fluidcontent 3.1.0
Fluid Pages Engine / fluidpages 2.1.0
Flux: Fluid FlexForms / flux 6.0.1
VHS: Fluid ViewHelpers / vhs 1.8.2

Default Root Template

Include static (from extensions):
Fluid Pages: PAGE (fluidpages)

Setup TS:

[GLOBAL]
plugin.tx_fed {
    fce {
        t3 {
            label = Fluid Content Elements - T3
            templateRootPath = fileadmin/tmpl/t3/Resources/Private/Elements/
            partialRootPath = fileadmin/tmpl/t3/Resources/Private/Partials/
            layoutRootPath = fileadmin/tmpl/t3/Resources/Private/Layouts/
        }
    }
}
plugin.tx_fluidpages {
    collections {
        t3 {
            templateRootPath = fileadmin/tmpl/t3/Resources/Private/Templates/
            partialRootPath = fileadmin/tmpl/t3/Resources/Private/Partials/
            layoutRootPath = fileadmin/tmpl/t3/Resources/Private/Layouts/
        }
    }
}

My tree dirs

 fileadmin
   tmpl
       t3
            Configuration
            Resources
                Private
                    Elements
                    Language
                    Layouts
                    Partials
                    Templates
                        Page/Default.html
                Public

Default.html

{namespace v=Tx_Vhs_ViewHelpers}
{namespace flux=Tx_Flux_ViewHelpers}
<f:layout name="Default" />
<div xmlns="http://www.w3.org/1999/xhtml" lang="en" 
    xmlns:flux="http://fedext.net/ns/flux/ViewHelpers" 
    xmlns:v="http://fedext.net/ns/vhs/ViewHelpers" 
    xmlns:f="http://typo3.org/ns/fluid/ViewHelpers">

        <f:section name="Configuration">
                [....]
        </f:section>

        <f:section name="Preview">
                [....]
        </f:section>

        <f:section name="Header">
                [....]
        </f:section>

        <f:section name="Content">
                [....]
        </f:section>

        <f:section name="Footer">
                [....]
        </f:section>        
</div>

I get error "Detailed Exception Description for error #1364685651"

What is wrong?

Hi,

my setup
TYPO3 (6.1.7)
Fluid Templating Engine - Fluid (6.1.0)
Fluid Content Engine - fluidcontent (3.1.0)
Fluid Pages Engine - fluidpages (2.1.0)
Flux: Fluid FlexForms- flux (6.0.2)
VHS: Fluid ViewHelpersVHS: Fluid ViewHelpers - vhs (1.8.4)

I get a a internal server error when I try to display the BE page view and the log file shows the following error:

mod_fcgid: stderr: PHP Fatal error:  Call to undefined method Tx_Fluidpages_Provider_PageConfigurationProvider::getGrid() in ***/typo3conf/ext/fluidpages/Classes/Backend/BackendLayout.php on line 97, referer: ***/typo3/backend.php

Is there any possibility to fix this error, or is a downgrade the only solution? Any suggestions?

Phil

I have set up a fresh TYPO3 4.7.12 site with latest TER versions of flux, fluidpages, vhs, fluidcontent_bootstrap and a random custom extension ("con_qna") which provides just an unspectacular list view of Q'n'A Items.

For testing purposes, I have a set up a page containing only the con_qna plugin (configured via flexform) and nothing else on the page.

Everything works fine until I throw an exception from within the con_qna listAction:
throw new Exception("This is an exception thrown in con_qna -> listAction controller!", $code, $previous);

Fluidpages / fluidpages_bootstrap now tries to resolve its errorView but fails:
Sorry, the requested view was not found. The technical reason is: No template was found. View could not be resolved for action "error".

Stack Trace until the point where the exception is thrown:
typo3conf/ext/con_qna/Classes/Controller/CategoryController.php.Tx_ConQna_Controller_CategoryController->listAction:77 typo3/sysext/extbase/Classes/MVC/Controller/ActionController.php.call_user_func_array:305 typo3/sysext/extbase/Classes/MVC/Controller/ActionController.php.Tx_Extbase_MVC_Controller_ActionController->callActionMethod:305 typo3/sysext/extbase/Classes/MVC/Controller/ActionController.php.Tx_Extbase_MVC_Controller_ActionController->processRequest:166 typo3/sysext/extbase/Classes/MVC/Dispatcher.php.Tx_Extbase_MVC_Dispatcher->dispatch:96 typo3/sysext/extbase/Classes/MVC/Web/FrontendRequestHandler.php.Tx_Extbase_MVC_Web_FrontendRequestHandler->handleRequest:85 typo3/sysext/extbase/Classes/Core/Bootstrap.php.Tx_Extbase_Core_Bootstrap->handleWebRequest:242 typo3/sysext/extbase/Classes/Core/Bootstrap.php.Tx_Extbase_Core_Bootstrap->run:212 typo3/sysext/cms/tslib/class.tslib_content.php.call_user_func_array:6584 typo3/sysext/cms/tslib/class.tslib_content.php.tslib_cObj->callUserFunction:6584 typo3/sysext/cms/tslib/content/class.tslib_content_user.php.tslib_content_User->render:55 typo3/sysext/cms/tslib/class.tslib_content.php.tslib_cObj->cObjGetSingle:615 typo3/sysext/cms/tslib/content/class.tslib_content_case.php.tslib_content_Case->render:52 typo3/sysext/cms/tslib/class.tslib_content.php.tslib_cObj->cObjGetSingle:615 typo3/sysext/cms/tslib/class.tslib_content.php.tslib_cObj->cObjGet:562 typo3/sysext/cms/tslib/content/class.tslib_content_contentobjectarray.php.tslib_content_ContentObjectArray->render:48 typo3/sysext/cms/tslib/class.tslib_content.php.tslib_cObj->cObjGetSingle:615 typo3/sysext/cms/tslib/content/class.tslib_content_case.php.tslib_content_Case->render:52 typo3/sysext/cms/tslib/class.tslib_content.php.tslib_cObj->cObjGetSingle:615 typo3/sysext/cms/tslib/class.tslib_content.php.tslib_cObj->cObjGetSingle:600 typo3/sysext/cms/tslib/content/class.tslib_content_records.php.tslib_content_Records->render:124 typo3/sysext/cms/tslib/class.tslib_content.php.tslib_cObj->RECORDS:877 typo3conf/ext/vhs/Classes/ViewHelpers/Content/AbstractContentViewHelper.php.Tx_Vhs_ViewHelpers_Content_AbstractContentViewHelper->getRenderedRecord:167 typo3conf/ext/vhs/Classes/ViewHelpers/Content/AbstractContentViewHelper.php.Tx_Vhs_ViewHelpers_Content_AbstractContentViewHelper->getContentRecords:139 typo3conf/ext/vhs/Classes/ViewHelpers/Content/RenderViewHelper.php.Tx_Vhs_ViewHelpers_Content_RenderViewHelper->render:55 typo3/sysext/fluid/Classes/Core/ViewHelper/AbstractViewHelper.php.call_user_func_array:233 typo3/sysext/fluid/Classes/Core/ViewHelper/AbstractViewHelper.php.Tx_Fluid_Core_ViewHelper_AbstractViewHelper->callRenderMethod:233 typo3/sysext/fluid/Classes/Core/ViewHelper/AbstractViewHelper.php.Tx_Fluid_Core_ViewHelper_AbstractViewHelper->initializeArgumentsAndRender:216 typo3temp/Cache/Code/fluid_template/FluidpagesBootstrap_Page_action_frontPage_cd5623277fb2d94852f1764611dea281cb428ba6.php.FluidCache_FluidpagesBootstrap_Page_action_frontPage_cd5623277fb2d94852f1764611dea281cb428ba6->section_4f9be057f0ea5d2ba72fd2c810e8d7b9aa98b469:919 typo3/sysext/fluid/Classes/View/AbstractTemplateView.php.Tx_Fluid_View_AbstractTemplateView->renderSection:239 typo3/sysext/fluid/Classes/ViewHelpers/RenderViewHelper.php.Tx_Fluid_ViewHelpers_RenderViewHelper->render:90 typo3/sysext/fluid/Classes/Core/ViewHelper/AbstractViewHelper.php.call_user_func_array:233 typo3/sysext/fluid/Classes/Core/ViewHelper/AbstractViewHelper.php.Tx_Fluid_Core_ViewHelper_AbstractViewHelper->callRenderMethod:233 typo3/sysext/fluid/Classes/Core/ViewHelper/AbstractViewHelper.php.Tx_Fluid_Core_ViewHelper_AbstractViewHelper->initializeArgumentsAndRender:216 typo3temp/Cache/Code/fluid_template/FluidpagesBootstrap_Page_layout_FrontPage_340dca62cae17e095e9e507df2f4be9792dd878a.php.FluidCache_FluidpagesBootstrap_Page_layout_FrontPage_340dca62cae17e095e9e507df2f4be9792dd878a->render:193 typo3/sysext/fluid/Classes/View/AbstractTemplateView.php.Tx_Fluid_View_AbstractTemplateView->render:199 typo3/sysext/extbase/Classes/MVC/Controller/ActionController.php.Tx_Extbase_MVC_Controller_ActionController->callActionMethod:310 typo3/sysext/extbase/Classes/MVC/Controller/ActionController.php.Tx_Extbase_MVC_Controller_ActionController->processRequest:166 typo3conf/ext/flux/Classes/Controller/AbstractFluxController.php.Tx_Flux_Controller_AbstractFluxController->renderAction:223 typo3/sysext/extbase/Classes/MVC/Controller/ActionController.php.call_user_func_array:305 typo3/sysext/extbase/Classes/MVC/Controller/ActionController.php.Tx_Extbase_MVC_Controller_ActionController->callActionMethod:305 typo3/sysext/extbase/Classes/MVC/Controller/ActionController.php.Tx_Extbase_MVC_Controller_ActionController->processRequest:166 typo3/sysext/extbase/Classes/MVC/Dispatcher.php.Tx_Extbase_MVC_Dispatcher->dispatch:96 typo3/sysext/extbase/Classes/MVC/Web/FrontendRequestHandler.php.Tx_Extbase_MVC_Web_FrontendRequestHandler->handleRequest:85 typo3/sysext/extbase/Classes/Core/Bootstrap.php.Tx_Extbase_Core_Bootstrap->handleWebRequest:242 typo3/sysext/extbase/Classes/Core/Bootstrap.php.Tx_Extbase_Core_Bootstrap->run:212 typo3/sysext/cms/tslib/class.tslib_content.php.call_user_func_array:6584 typo3/sysext/cms/tslib/class.tslib_content.php.tslib_cObj->callUserFunction:6584 typo3/sysext/cms/tslib/content/class.tslib_content_user.php.tslib_content_User->render:55 typo3/sysext/cms/tslib/class.tslib_content.php.tslib_cObj->cObjGetSingle:615 typo3/sysext/cms/tslib/class.tslib_content.php.tslib_cObj->cObjGet:562 typo3/sysext/cms/tslib/class.tslib_pagegen.php.TSpagegen::renderContent:259 typo3/sysext/cms/tslib/pagegen.php.include:73 typo3/sysext/cms/tslib/index_ts.php.require:353 index.php.{main}:76

The Exception then gets caught in typo3conf/ext/flux/Classes/Controller/AbstractFluxController.php.Tx_Flux_Controller_AbstractFluxController->renderAction:230 within this stack:

typo3/sysext/extbase/Classes/MVC/Controller/AbstractController.php.Tx_Extbase_MVC_Controller_AbstractController->forward:273 typo3conf/ext/flux/Classes/Controller/AbstractFluxController.php.Tx_Flux_Controller_AbstractFluxController->handleError:255 typo3conf/ext/flux/Classes/Controller/AbstractFluxController.php.Tx_Flux_Controller_AbstractFluxController->renderAction:230 typo3/sysext/extbase/Classes/MVC/Controller/ActionController.php.call_user_func_array:305 typo3/sysext/extbase/Classes/MVC/Controller/ActionController.php.Tx_Extbase_MVC_Controller_ActionController->callActionMethod:305 typo3/sysext/extbase/Classes/MVC/Controller/ActionController.php.Tx_Extbase_MVC_Controller_ActionController->processRequest:166 typo3/sysext/extbase/Classes/MVC/Dispatcher.php.Tx_Extbase_MVC_Dispatcher->dispatch:96 typo3/sysext/extbase/Classes/MVC/Web/FrontendRequestHandler.php.Tx_Extbase_MVC_Web_FrontendRequestHandler->handleRequest:85 typo3/sysext/extbase/Classes/Core/Bootstrap.php.Tx_Extbase_Core_Bootstrap->handleWebRequest:242 typo3/sysext/extbase/Classes/Core/Bootstrap.php.Tx_Extbase_Core_Bootstrap->run:212 typo3/sysext/cms/tslib/class.tslib_content.php.call_user_func_array:6584 typo3/sysext/cms/tslib/class.tslib_content.php.tslib_cObj->callUserFunction:6584 typo3/sysext/cms/tslib/content/class.tslib_content_user.php.tslib_content_User->render:55 typo3/sysext/cms/tslib/class.tslib_content.php.tslib_cObj->cObjGetSingle:615 typo3/sysext/cms/tslib/class.tslib_content.php.tslib_cObj->cObjGet:562 typo3/sysext/cms/tslib/class.tslib_pagegen.php.TSpagegen::renderContent:259 typo3/sysext/cms/tslib/pagegen.php.include:73 typo3/sysext/cms/tslib/index_ts.php.require:353 index.php.{main}:76

In typo3/sysext/extbase/Classes/MVC/Controller/AbstractController.php.Tx_Extbase_MVC_Controller_AbstractController->forward:273,
$extensionName $controllerName and $arguments are NULL, so the following variables are set for $this->request:
controllerExtensionName string "FluidpagesBootstrap" controllerName string "Page" controllerActionName string "error". arguments array[0]

setting plugin.tx_fluidpagesbootstrap.settings.displayErrors = 1 in TS, the errors are being thrown in frontend as an uncaught typo3 exception.

Static TS from fluidpages and fluidpages_bootstrap is included in root template. Object browser shows:
plugin.tx_fluidpagesbootstrap.view { templateRootPath = EXT:fluidpages_bootstrap/Resources/Private/Templates/ partialRootPath = EXT:fluidpages_bootstrap/Resources/Private/Partials/ layoutRootPath = EXT:fluidpages_bootstrap/Resources/Private/Layouts/ }
plugin.tx_fluidpages.view is not set.

When I do this manually:
plugin.tx_fluidpages.view.partialRootPath = EXT:fluidpages/Resources/Private/Partials/ plugin.tx_fluidpages.view.templateRootPath = EXT:fluidpages/Resources/Private/Templates/

I get:
Sorry, the requested view was not found. The technical reason is: No template was found. View could not be resolved for action "frontPage".

To me, it seems like the providers' controller Action and therefore the right Template location is somehow not being set correctly.

My configuration: TYPO3 6.1.1, latest flux/fluid..-extensions, multiple website starting points and multiple extensions. All caches/typo3temp cleared/truncated.

I got some strange warnings about missing TemplatePath (function sendWarningAboutMissingTemplatePath() in https://github.com/FluidTYPO3/fluidpages/blob/master/Classes/Service/ConfigurationService.php) and had a quick look at your code.

Problem 1: https://github.com/FluidTYPO3/fluidpages/blob/master/Classes/Service/ConfigurationService.php#L73 does not check if $extensionName is an empty string. Changing line 73 to if (empty($extensionName)) { solved it for me (at least the symptom - not the cause).

Problem 2:
The use of $nativeViewLocation in https://github.com/FluidTYPO3/fluidpages/blob/master/Classes/Service/ConfigurationService.php#L77 doesn't seem right. It is set later at Line 89 in the else-part of the condition.

Sunny greetings from Vienna!

Hello

I think there is something unclear about the pageController context.

If I decide to create a pageController in the extension which holds page templates, I must declare an action in this controller for every page template.

If I do not, my pageController is not chosen for processing the request, but the Tx_Fluidpages_Controller_PageController is. It is OK, because the template is finally well rendered.

But there is a pitfall : the context in the request is not my extension, but it is the fluidpages extension. (see renderAction in AbstractFluxController)
And when I want to use the translateViewHelper (f:translate), it looks for a translated string in the locallang.xml loaded for the current extension, and it will never use the locallang.xml of my extension.

So, if I want the request context belongs to my extension, I must declare an action in my pageController, named against the rendered template.

I think this should be wrote in the docs.

Sorry for my english, I hope you understand what I mean...

It would be nice if it would be possible to set custom column width (in percentage). So you can display a margin column with lower width and use the remaining space more efficient. I attached an example backend layout.

Hi Claus,

the dependency to flux is set to version 5.0.0. So the extension is not installable with the EM because flux is in TER only in version 4.7.x.

Best regards
Tobias

Hello Claus, the Weizen shows its effect. Now i have a stupid Q:
How can i refer to my EXT:fluidpages_most Directory for integrating something.

I am using cs_less so i wanted to set the path like this:

<less:style href="LLL:EXT:fluidpages_most/Resources/Private/less/bootstrap.less" />

but it wont work :(

17d800f fixes the problem with that "INVALID VALUE" as column. But it also adds the column "Fluid Content Area" to the colums view under the page module (see screenshot). This is a bit irritating for our editors to see all nested content elements unnested in the Fluid Content Area column. And if they scroll down they see the nested content elements a second time (correctly nested this time)

Is it possible to hide the Fluid Content Area column from column view?

Screenshot with Fluid column on top:

This one looks like it's related to #55. In 4.7 I am presented with the following:

The template files
"/var/www/t3sandbox_47/typo3conf/ext/fluidpages/Resources/Private/Partials/Exception/1289852422.html",    
"/var/www/t3sandbox_47/typo3conf/ext/fluidpages/Resources/Private/Partials/Exception/1289852422", 
"/var/www/t3sandbox_47/typo3conf/ext/fluidpages/Resources/Private/Partials/Exception/1289852422.html", 
"/var/www/t3sandbox_47/typo3conf/ext/fluidpages/Resources/Private/Partials/Exception/1289852422" could not be loaded.

1289852422 is the error code of Fluid's AbstractConfigurationManager::getConfiguration() for unexpected arguments ("You'll have to specify either both, extensionName and pluginName, or neither.").

t's very strange.. TYPO3 6.2rc with latest developemnt branches (flux, fluidcontent, fluidpages)

with flux having 'version' => '7.0.0', and fluidpages depending on 'flux' => '7.0.0-7.0.99', (so no "-dev" suffix around)

i get Could not resolve dependency for "flux" when installing fluidpages or fluidcontent

if i set the depends to: 'flux' => '', (instead of 'flux' => '7.0.0-7.0.99') it works

i think it's a Core problem.. do you confirm?

Steps to reproduce:

• Open the BE of the Bootstrap Package
• Module "Web" > "Page" > "General Storage"

I get quite a few of warnings (mostly all the same). The cause is most probabl there is no "Page Layout" set anywhere in the root line. However, the problem is that the field is not shown for a Folder record... Can we add some more check?

( ! ) Warning: file_get_contents(Page/.html) [function.file-get-contents]: failed to open stream: No such file or directory in htdocs/typo3_src/typo3/sysext/fluid/Classes/View/TemplateView.php on line 185
Call Stack
#   Time    Memory  Function    Location
1   0.0012  676856  {main}( )   ../db_layout.php:0
2   0.3201  27027248    TYPO3\CMS\Backend\Controller\PageLayoutController->main( )  ../db_layout.php:143
3   0.3278  27156008    TYPO3\CMS\Core\Utility\GeneralUtility::callUserFunction( )  ../PageLayoutController.php:471
4   0.3384  28131312    call_user_func_array ( )    ../GeneralUtility.php:4022
5   0.3384  28131392    Tx_Fluidpages_Override_Backend_View_BackendLayoutView->getSelectedBackendLayout( )  ../GeneralUtility.php:4022
6   0.3426  28539808    Tx_Fluidpages_Backend_BackendLayout->postProcessBackendLayout( )    ../BackendLayoutView.php:89
7   0.6078  30296904    Tx_Flux_Service_FluxService->getGridFromTemplateFile( ) ../BackendLayout.php:86
8   0.6079  30296984    Tx_Flux_Service_FluxService->getStoredVariable( )   ../FluxService.php:193
9   0.6312  31795000    Tx_Flux_MVC_View_ExposedTemplateView->getStoredVariable( )  ../FluxService.php:163
10  0.6320  31812608    Tx_Flux_MVC_View_ExposedTemplateView->getParsedTemplate( )  ../ExposedTemplateView.php:85
11  0.6326  31812912    TYPO3\CMS\Fluid\View\TemplateView->getTemplateSource( ) ../ExposedTemplateView.php:127
12  0.6326  31813008    file_get_contents ( )   ../TemplateView.php:185

When copying a contentelement the icons for "create copy" and "create reference" only appear when reloading the page. Would be nice if the frame reloads automatically like in TV.

I'm using the master-branch of fluidpages and fluidpages_bootstrap. I try to override the pathes by typoscript. But it seem not to be working on +ext:templates on sublevel pages. Thanks to kind help of NamelessCoder who said it should work as follows I think this is an issue....

To reproduce this it requires a few steps:

• copy all your /Resources into /Resources2 folder
• make some changes in .html template (I just changed the labels to xxxxTWO)

Then add typoscript to your rootlevel - page template to override your pathes to 'Resource2':
I did:

plugin.tx_fluidpagesbootstrap.view >
plugin.tx_fluidpagesbootstrap.view {
  templateRootPath = EXT:fluidpages_bootstrap/Resources2/Private/Templates/
  partialRootPath = EXT:fluidpages_bootstrap/Resources2/Private/Partials/
  layoutRootPath = EXT:fluidpages_bootstrap/Resources2/Private/Layouts/
}

Then you'll get the expected result, you'll get templates from /Resources2/ - Overriding works. [see screenshot 1]

After this:
What not works is....
CUT OUT the overriding typoscript from above out of your rootlevel page template and insert it instead into an +ext-Template of a subpage (in my Example called "Produkte" with PID#3).
But now NO overriding happens. The path settings are taken from the 'static template'. Not even "plugin.tx_fluidpagesbootstrap.view >" seem to have any impact.

Thank you for verifiying if this is really an issue. I tried everything multiple times and according to me it should be possible.

BTW: This does also not work when inserted by a completely own extension (a copy of fluidpages_bootstrap into own extension).

If I want to override the language file like this:

$GLOBALS['TYPO3_CONF_VARS']['SYS']['locallangXMLOverride']['EXT:fluidpages/Resources/Private/Language/locallang.xlf'][] = 'fileadmin/translation/de.xlf';

it doesn't work. instead i have to use the full path with LLL.

any chance to get this working?

TYPO3 dies with the following error:

Warning: require_once(/.../typo3conf/ext/flux/Classes/Provider/AbstractProvider.php) [function.require-once]: failed to open stream: No such file or directory in /.../typo3/sysext/core/Classes/Utility/GeneralUtility.php on line 4370

The Drag&Drop currently doesn't work in the Language mode because it depends on a class "t3-page-column" which doesn't exist in the Language mode.

if you disable this line here : https://github.com/FluidTYPO3/fluidpages/blob/master/Resources/Public/js/typo3pageModule.js#L139 you can make it work inside fluid content elements, but it sitll doesn't work for the content elements not currently contained inside an fce.

Environment:

TYPO3: 6.1.5
Browser: Chrome 31.0.1650.63
fluidpages: git master
flux: git master
vhs: git master
fluidcontent: git master

After updating fluidpages with git version I was getting some problems with rendering of options in tab 'Appearance'. I could fix the only after uninstalling fluidpages/flux and deleting the database fields and then reinstalling.

Could it be a sollution to add a function 'truncate all fluidpages/flux fields' or is there an other better solution.
This could also be a good solution if you played with flex field options and want to reset all to default.