[TYPO3-mvc] Advanced configuration for RealUrl with Extbase

[Franz Koch]

Hey there,

...
> So, a URI must look like this:
> host/page/category/a-category/
>
> Or this:
> host/page/category/a-category/a-category-in-another-category/product/a-product/

no, not necessarily. Have a look at "fixedPostVars" in realUrl. If you 
know the piVars structure for certain pages, you can strip the keywords 
"category" and "product" in the URL. But that only works if you have a 
fixed number of postVars and might not easily work with a "unlimited" 
number of categories AFAIK.

> But this imho is quite long and I'm still not sure if it's possible to
> convert "tx_hypestore_category[path]=4,2" to
> "/a-category/a-category-in-another-category/"?!

AFAIK it's not easily possible. Altough you could create such a URI 
using a custom function you can assing to realURL paths, but it will be 
hard to decode it (extract the original GETvars) without a keyword like 
"category" in the URL that's telling you when to stop parsing for 
categories. One possibility might be to add a special concatenation sign 
to the URLs in the path and use pre- and postprocessing hooks to make 
them look nicer.

Like:
host/page/a-category+/another-category+/yet-another-category/a-product/

So your custom function would create a category path segment like this:
a-category+another-category+yet-another-category

and via post processing you add additional slashes. You could also 
completely remove the "+" sign and only use slashes, but in that case 
you might need to use a own cache table to be able to decode that stuff.

You might say now - why do I need my own cache when realURL has a encode 
and decode cache. Well - those can be empty and then you need still a 
way to decode the URL.

-- 
kind regards,
Franz Koch