I'm wondering if anyone can shed some light on how to use the GET and POST options in the dynamic parameters - and give a few examples of how they might be used.
You probably want to use GET most of the time.
If you configure an asset listing, for example, to use a query string var for the replacement root node, you need to give it a name. This can be anything you like. In my example, I’ll use “root” as the GET variable name.
Lets say we have an asset listing with a URL of:
http://www.example.com/listing
The default root node we have set is the Site asset.
If you access the page with the URL:
http://www.example.com/listing
the asset listing will use asset #123 as the root node.
Note that any assetid you pass as the replacement root node MUST be under the normal root node that is set in the asset listing (under, as in lower than it in the tree).
Just Quick on on this, if say you are grouping by category, is there anyway to add the navigation to the top of the asset listing page…
for example
cat1 | cat2 | cat3 etc etc…
each linked with the appropriate GET parameter?
Not that I know of. You'd have to use 2 asset listings, one for the navigation and one for the body.
The navigation would print the links and not actually print any assets and the body would prin the assets, grouped, and with anchors.
I've used this for FAQs in the past (questions at the top, answer below) and it works well.