[TYPO3-dev] Usability of the Columns view

[Erik Svendsen]

Hello Tapio,

>> page = PAGE
>> page.typeNum = 0
>> page.10 = USER
>> page.10.userFunc = tx_templavoila_pi1->main_page
>> Should be enough for detection. If this isn't put there, TV do not
>> work.
> that is in some TS-template - but I need it here and I can't use here
> any TS template

As I know you need to use TS to get TV to work, like you are doing with

page = PAGE
page.typeNum = 0
page.10 < temp.mainTemplate ......

when you are using the MTB way.

And I can't find anything else in TS who turn on and off TV. It's no use 
testing if it installed, because you can install TV, but you don't need to 
use it. And you do need to have the correct TS in your root template.

And you activate TV on site basis, and every user has to use it. As I understand, 
but haven't read all documentation.
 
> class ux_t3lib_tsfeBeUserAuth extends t3lib_tsfeBeUserAuth {
> 
> ...
> 
> function ext_makeToolBar()	{
> ...
> $newContentWizScriptPath =
> TYPO3_mainDir.'sysext/cms/layout/db_new_content_el.php';
> $tmpTSc =
> t3lib_BEfunc::getModTSconfig($this->pageinfo['uid'],'mod.web_list');
> $tmpTSc = $tmpTSc
> ['properties']['newContentWiz.']['overrideWithExtension'];
> $newContentWizScriptPath = t3lib_extMgm::isLoaded($tmpTSc) ?
> (t3lib_extMgm::extRelPath($tmpTSc).'mod1/db_new_content_el.php') :
> (TYPO3_mainDir.'sysext/cms/layout/db_new_content_el.php');
> 
> that needs more conditions
> 
> '$tmpTSc' relates with
> 
> mod.web_list.newContentWiz.overrideWithExtension=1
> 
> BUT that works just for users/user groups, which means that for every
> change from TemplaVoila to standard page module or reverse needs
> changing of this. Not very handy.
> 
> I tested mod.web_list.newContentWiz.overrideWithExtension=1 for TS
> config for page - no effect.

If you somehow can get the value of page.10.userFunc = tx_templavoila_pi1->main_page, 
don't know how it looks, but it has to be used a lot of places to render 
the page, you can test for it with if - else, case or something similar. 
Looks like if - else is the best solution.

function ext_makeToolBar()    {
....
case "value TV not activated"
     ...code
break;

case "value TV activated"
     ...different code
break;

Look in pi1/class.tx_templavoila_pi1.php and see if you find any value there. 
I think it is this class who render the page in frontend. What renders it 
in backend I don't know.

>> It's also another way I suppose. Who also I think are simple enough.
>> Make settings in tm_contentaccess who has classic web>page as default
>> (0), and the need for something like
>> 
>> plugin.tx_tmcontenaccess_p1.enable = 1
>> 
> That is nonsense because that plugin isn't FE plugin.
> And what I would disable in templavoila is not FE-functionalities.
> If that works only FE-features, it is useless (note that frontend
> editing belogs to BE-functionalities).

My fault, was reading wrong place. But I know you have the possibility to 
use similar technics to make values to use for conditional testing in backend 
modules to.

>> customer. If the frontend editing isn't suitable, sell it without
>> 
> I would not do that way - I want to give for them as good frontend
> editing as I can build - with some AJAX-functionality it would be
> really
> cool, full 10.
> I have tested visual demo - because it didn't save changes it was as
> such useless. It is just a great pleasure to move content element from
> one place to another with AJAX - fast, fun, enjoyable - and you can
> get that BE-functionality today using the standard page module!

AJAX is cool, but I never give editors the ability to move around content 
element (or very restricted ability). And I advice my customer not to do 
it. My experience with fancy functionality aren't very good, it tend to ruin 
the layout of pages and somehow the sorting of content change in a way the 
main editor don't want.



WBR,
Erik Svendsen
www.linnearad.no