Thread

I have:
- created a new site in MSM
- duplicated a channel and it’s fields. Not the entries, though.
- created an entry in the newly duplicated channel.
- duplicated a template.

In the template, there is the following code - which worked perfectly in the existing site:

{exp:weblog:entries weblog="weblog_name"}
{custom_field}
{/exp:weblog:entries}

But now in the new site - which has the same custom field name - I can’t display any custom fields.
If I put {title} in the loop, that outputs just fine. The custom fields just output literally {custom_field} with curly braces.
So, the entries are definitely being read. There’s just a problem with the fields.

But as far as I can tell, the channel is associated to the field group just fine.

Is there any advice you can give? Or steps to troubleshoot this?
Thanks!

Hi Jason Varga,

What version of ExpressionEngine and MSM are you using?

Have you tried adding the site= parameter to your weblog entries tag?

{exp:weblog:entries site="new_site_name" weblog="weblog_name"}
{custom_field}
{/exp:weblog:entries}

EE may just be confused due to the sameness.

Cheers,

EE 1.7.3 and MSM 1.1

Even with the site parameter its the same problem.
The weblog is on the current site.

The page I’m trying to display the entries on is the homepage template.
The weird thing is, if I have the 404 set as the homepage, and I throw some dummy text into the second segment… the entries display correctly.

For example:
Assuming the template code from the first post…
Viewing http://mysite.com/ renders the literal {custom_fields} on the page.
Viewing http://mysite.com/dummy_segment/ renders the custom fields correctly. Even without the site param.

This seems bizarre to me.

That does seem bizarre. Let’s have a look first-hand and see what’s going on here, Jason. Be on the lookout for an email from me.

It seems that only text inputs and textareas are affected. Wygwam fields are rendered properly.
I’ve changed the field from textarea to wygwam and everything seems fine for now.

Still, very strange that native fields wont work.

You can ignore the email I sent across. I’d say this is ‘resolved’.

Thanks!

Hi Jason,

Thanks for the follow up!

If you need anything else, please let us know.

Cheers,