Project

General

Profile

Actions
Copy link

Bug #18114

closed

$MCONF['navFrameScript'] problem with new backend.php

Added by Stefano Cecere almost 17 years ago. Updated over 16 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Ingo Renner
Category:
-
Target version:
-
Start date:
2008-02-04
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.2
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

hallo

i am testing latest trunk and i love new backend.php, but there is a problem:

i have a custom module, with uses standard alt_db_navframe.php as navFrameScript,
done via

$MCONF['navFrameScript'] = $BACK_PATH.'alt_db_navframe.php';

in its conf.php

with old backend (alt_main.php) it works perfectly (ie: my index.php is called correctly in main content frame passing the page id)

with new backend.php it doesn't work anymore:
everytime i select a page in the tre, it reloads both the iframes (nav and content)
and the id is not passed to my content.

anybody already tried/solved this bug?

many thanks
stefano

(issue imported from #M7382)

Actions
Copy link
 #1

Updated by Stefano Cecere almost 17 years ago

solved:

the problem is that i was setting the $MCONF['navFrameScript'] in submodule, and not in the MAIN module.

(maybe the old backend was a bit more flexible about this behaviour)

Actions
Copy link
 #2

Updated by Ingo Renner almost 17 years ago

so can we close this one?

Actions
Copy link
 #3

Updated by Steffen Kamper almost 17 years ago

yes, Stefano marked it as "solved by myself"

Actions
Copy link

Also available in: Atom PDF