ob_start()' conflicts with [SHORTCODES] in template

[Tez Oner]

Eeey,

for a page cache feature I need to add a 'ob_start();' to the template-index (first-line)
and an 'ob_end_flush();' on the last line, but there seems some conflict with another
ov_start that been called by the 'index wrapper' of WB to render [SHORTCODES] and
droplets.

Any workaround for this?

Cheerz,

Tez Oner

[Ruud]

WB will not function correctly if the buffers in the index.php are disabled.
Nesting multiple outputbuffers should be no problem though. I use them all the time.

Can you give more details on the "some conflict"?

[Tez Oner]

Hey Ruud,

WB will not function correctly if the buffers in the index.php are disabled.
Nesting multiple outputbuffers should be no problem though. I use them all the time.

Can you give more details on the "some conflict"?

Solved most of it, the main issue / conflict was that calling an ob_start
in the the template file was 'to late' for what I wanted to implement.

I found a workaround for the 'page cache' (as thats what I needed it for),
not that 'clean', as I need to modify the WB index-file (to make a ob_start
with the WB page-output in it).

But so far it runs smooth and servers static html-files when a page is in the
cache - very - very fast A pity WB doesn't have a 'hook' / blocks architecture
to implement code at certain positions. (and a cache would be nice feature and
easy to implement feature for upcoming WB).

The new thingy is how to define unique-pages (as news-pages / posts) have
the same id / title, which is i.m.o. pretty inconsistent.

Cheerz,

Tez Oner

[Ruud]

The new thingy is how to define unique-pages (as news-pages / posts) have
the same id / title, which is i.m.o. pretty inconsistent.

For News you can check for the existance of a $post_id variable.
Bakery has an $item_id (if I am correct)

Unfortunatly there are more modules that will do their own page creation, all with their own methods of identifying the page loaded. It will be hard to detect them all..

[Tez Oner]

The new thingy is how to define unique-pages (as news-pages / posts) have
the same id / title, which is i.m.o. pretty inconsistent.

For News you can check for the existance of a $post_id variable.
Bakery has an $item_id (if I am correct)

Unfortunatly there are more modules that will do their own page creation, all with their own methods of identifying the page loaded. It will be hard to detect them all..

Thanks! The new thingy is this Page Cache feature, but I resolved it by adding a 'page_id'
works fine for now:

http://forum.WebsiteBaker.org/index.php/topic,28202.0.html

Cheerz,

Tez Oner