Can't use {tag_itemid} in web app detail layouts

Hi Chris,

I think that this is something that was overlooked years ago when the itemid was developed for the list view. I think it makes a lot of sense to have it inside the detail view as well and I have created a feature request for you with the dev team under #3334550. They should implement this once they start tackling web apps.

Cheers,

-mario

Mario is there any existing tag that you could suggest to be used instead of the itemid in the meantime that would also be able to generate a unique output with no spaces or special characters present?

I also have a need for this as it would seem a fundamental option.

Alternatively how can you create an alternative webapp layout for a detailed view that is in based in the list realm - eg is there anyway to utilise the "alternative list template" to create a more detailed view that the list view will go to if you wish to view more detail (eliminating the need for the detail template)

I understand that you can now force alternative templates  in some modules (I've read some murmers about it being realeased recently) but I cannot find any definitative instruction of how to achieve this?

Can you shed any light on that option to force another template on the detailed view - and indicate if it is at all possible to  utilise list view tags in these custom templates

Thanks in advance

The only thing that's unique for every web app item on the detail view can be rendered by {tag_itemurl_nolink}. Nothing else. Also, in the last release we have enabled multiple list layouts but all the links from the list layout will lead to one detail layout. There's no ability to create multiple detail layouts.

Anyway, I'll email the product management team to see if this itemid tag for the detail layout is something they can squeeze in into one of the releases in the near future.

-m

Always amazes me some tags that could be added or do exist that just need to work in a large layout or list layout as well as the other seem so hard to do. Really that hard to make tags?

I don't want to promise you anything but getting this in the next couple of sprints looks promising.

brilliant!

what is the usual timeline for a sprint Mario lol?

Defintely agree with Liam in that most of the tags/module tags for both the list and detail layouts should be universal as there are some situations where you need to use the tags dynamically to create outputs that need to be shown in both...

for example

I'm using a polldaddy rating system for a webapp currently and to get it to show up on each listing item separately requires a unique ID so using {tag_itemid} made perfect sense as it wouldnt break any polldaddy coding... however I cannot call the same rating system into the detail page (where it would logically be repeated) because I cannot replicate the same ID with no {tag_itemid} availble.

Asecond example is:

Since we had managed to put a readers upload gallery into a nice compact layout in the list layout using litebox and the ?Action=thumbnail feature the client really wanted to keep the photo gallery commenting system simple aslo (not to many steps) so ideally we would have liked to only ustilise the list-template and put the comment feedback tag in a sliding div (to show & hide it) so that readers could stay on one list page... but once again this wasnt possible becuase the {module_ratingfeedback} was not available in the list view (forcing us to make them click through to the detail page).

FYI: heres a sample link to what we had to put together in the end for the above - still slightly in development

http://www.nzhunter.co.nz/test-gallery

Anyway I think you get the idea - more flexibility and universal usage options for tags/module calls would be great.

Look forward to the updates at some point.

We have monthly sprints at BC.

I too have had the same issue with item ID's it would be a massive use for us to be able to use this on the detail view. Whilst you are suggesting things, do you think it would be possible to use {tag_description} more than once in the list view too? It's important that we have this feature as sometimes we'll have a social share section where we need to replicate all the info and it would be great if I didn't have to work around it with jquery.

I will keep track of this also. I have just had a client request this feature.

Thank you.

Little thing for you all to help you out till you get the tag.

If you link the web app detail view using say this tag - {tag_itemurl_nolink} which renders the url and use the tag item id, you can use this in the detail view.

So in your list view you have your link:

<a href="{tag_itemurl_nolink}" title="Your Title">read more</a>

Would render the link

But if you do this:

<a href="{tag_itemurl_nolink}?itemID={tag_itemid}" title="Your Title">read more</a>

You will pass the itemID paramater across into the web app detail view.

Then you can retrieve the itemID using..

{module_url,itemId} which will render the paramater from the URL which is the itemID in your Detail Layout or template.

Impressive work around Liam! Thanks.

That is a fully sik work-around. And I just found out I can embed a module tag INSIDE another module tag. This enables one to call the Google Map Web App on the Detail page and render the map according to current ID of the Web App. YES!

Thank you Mr Dilley, your work is grouse.

Hi Liam

The workaround works fine for web app layouts.  However, I cannot figure out a way to pass the itemid value from a site search layout?  The {tag_name} renders a totally different url to that used in a web app - i.e. includes ObjectID etc.

As the results both point to the same detail layout my google map will not display when redirected from the link on a site search results page.

Any ideas would be most welcome!!

Regards

You are talking about tag name there. That is different from waht we are talking about here.

Tag item id renders in the list layout and a web app search will render that list layout.

A site search will not render the ID of web apps, There is nothing you can do to get that to do so.
A search link Objectid in that link though should be the web app item id so that can be fetched when from a search to use.

Appreciate that, but the site search listing will link to the relavant web app detail layout that the item relates to.  So if you have created a web app detail layout, including a google map for a specific item, then the map will show when redirected from the web app list layout but not if redirected from the site search list layout?

Forgive my ignorance but what would be the link code to use the objectid and get the map to render?

Many thanks.

You mean have a web app search that renders the results on a map?

I do not understand why you need web app item id for detail view via search to render a map. Should not need to.

Perhaps I am doing something wrong then, forgive me.  Refer to http://forums.adobe.com/docs/DOC-2482

This seems to suggest that you need to put some specific coding on the detail layout ie.e you cannot simply insert the webappsmap module on the page?  I was using {module_webappsmap,6378,i,{module_url,itemId},,600,400,1} on the detail page and it works fine / shows the individual webapp item poistion without the need for the specific code.

The {module_url,itemId} doesn't work however when redirected from the site search results as the itemID is not passed via the url.