Thread

I’m having trouble pulling content from other sites under MSM (previously I thought this was related to Playa, but I’ve distilled the issue to pure EE).

I’ve reduced my template to

{exp:weblog:entries site="news" weblog="directory" dynamic="off"}
<h1>{title}</h1>
{/exp:weblog:entries}

This template is in a different site on the MSM installation.

Template debugging says “Returning No Results Content”. What am I missing?

Spurlock:
Can you tell us which version/build of EE1.x you’re using? See EEWiki:// HowTo Determine My EE Version

We’re using 1.6.8, Build 20100121

Is the short name of the site news?

It is.

Unfortunately site= and search: do not work together.  search: will always be on the current site.

You’re welcome to make a feature request for an expansion to this behavior.  For now, you might need some custom queries to pull that data across.

Lisa,

Thanks for the tip, it will probably save me a lot of headache down the road. However, the code sample above doesn’t use the search parameter. Unless I’m mistaken, it ought to simply pull all entries from the specified weblog on the other site. Is search somehow implicit in what I posted?

As far as I can tell, I’m unable to use weblog:entries to pull data from one site to another in any way.

Sorry Spurlock.  I saw something that wasn’t there.  That’s my fault.

Are you sure you have a weblog “directory” on the “news” site?  Does that code work on the originating site?

Those would be good things to double check first. =)

I completely understand your skepticism 😊

Screenshots: http://imgur.com/miThh

It seems like a really weird issue, I sort of hoped there might be some kind of admin setting for “allow cross-site entry queries” or something, because I’m not sure what else would explain it. Is there anything about the server environment to look out for?

Actually, that other suggestion about the code working on the originating site turned out to fruitful.

The “news” site is one that I didn’t set up myself, and unbeknownst to me the “directory” weblog was making (bizzare and unnecessary) use of custom statuses…

Adding the status group to the query fixed it. Sorry for the trouble, and thanks for the help!

Hey Spurlock!  Those custom statuses, they do sometimes manage to catch people out.  Glad you figured it out!

If anything else comes up, please start a new thread so that we can help you out.