[TYPO3-dev] parsing TSconfig in BE-module?

bernd wilke t3ng at bernd-wilke.net
Mon Mar 10 09:04:13 CET 2014


Am 07.03.14 22:00, schrieb Jigal van Hemert:
[...]
> I mentioned the page type because I needed the content of pages and not
> all the extra stuff such as header, menu, footer, etcetera but it's not
> something that is required.

I export not HTML but HTML-snippets in PHP-variables for later includes. 
So I don't use HTML-Header either.


[...]
> $domainName =
> t3lib_BEfunc::firstDomainRecord(t3lib_BEfunc::BEgetRootLine($this->id));
> $url = 'http://' . $domainName . '/index.php?id=' . $this->id . '&type='
> . $this->type;
> $content = file_get_contents($url);
>
> To retrieve a page from the frontend.

as I use the realurl-path to decide the export-path I use ext:pagepath 
to get nice URLs ;-)

>
> You can do similar things (settings and retrieving page content) when
> you pass uid's of records using the right URL formats.
>
that's all stuff I'm already doing.
I have different types for normal FE (editors preview) and export 
(&type=50).
As long as pages have no variants it is an easy way and already working.

My problem lays in the news pages where on one page different variants 
are to be exported and where I want a possibility of configuration.
with the TS-rendering of the FE I'm able to build a list of urls to 
export all these variants, but in the BE I only have page- (and 
user-)TSconfig which does not render any TS-Objects.

AS I mentioned I used extra pages to just render a List of URLs to 
export. including a list of news-pages. This is done by sitemap-menu-CE 
and the news-plugin in list mode (and a further pagetype ;) ). But this 
is a very static selection of pages to export.
My BE-module starts at any page and the editor is able to select the 
recursion depth dynamic. So the variation of the news-detail-page should 
be configured in the news-detail page available for the BE-module. 
Editors should just select the news-page to export and all Varaints 
should be exported.

the news-detail page is one page with variants. there are two other 
pages with news-list views which vary in year selection.
There might be pages with addresses.

I don't want hardcoded variations for these 4 pages but a configuration 
which can handle all kind of stuff.


bernd
-- 
http://www.pi-phi.de/cheatsheet.html



More information about the TYPO3-dev mailing list