Access TV in diffrent context via GetResources

Hi,

I got a multidomain project based on revo.
The mutidomain ist based on this tutorial:
http://www.h-quadrat.com/techblog/111-modx-revolution-multi-domain-context-installation-english.php

So I got the web context and an other context for the other domain.
The web context contains a folder with TV-based documents in it.
I can call the documents via the getResources-snippet from within the web context. But I want call this documents (with the getResources snippet) from wihin the other context too.
But it doesent work. I want cross-centext content.

Can anyone help me please?

If nobody there who got an idea for this problem?

I did not understand why modx canot access cross-context by default. What is the reason?

Hello,

seems that is a very big problem? Nobody there with an idea?

Could one of the developer say someting for that problem, please?
Becaus I did not find an answer or hint on the internet or inside of the documentation.

If it’s possible or not. But if it’s not possible it would make the whole context-concept obsolete. (imho)

I’m not sure if getResources will do that at this point, but did you include the &includeTVs and &processTVs parameters and use the proper prefixes on your TV’s (or set the &tvPrevix parameter to an empty string)?

I did not set the tvPrefix Parameter. But in the chunk I worte it like tv. etc.
When I call getResource from the same context the TVs will show. So from that piont it works. But I want call the dokuments
from within an nother context.

The call that I use:

Be sure to create the appropriate context settings for site_url, base_url, and http_host for every front-end context.

This things are created in both contexts.

Quote from: elgato at Jul 30, 2010, 02:34 AM

This things are created in both contexts.

Is it possible they are not all accurate?

I checked it. Its all correctly.
I got this things in it:

site_name (This is the site name)
site_start (1)
base_url (/)
http_host (www.domainname.de)
site_url (http://www.domanname.de)

The only think I can think of is a www/non-www issue.