Thread

In my 1.6.8 Expression Engine Installation: Build: 20091201 I have a news article page that displays numerous fields: date, body, author, image, etc.

All the fields are displaying except one field, which happens to be the body of the article.

The template worked, for a couple of years now, no changes were made, but the body field stopped displaying today.

This is happening on every news weblog entries, it’s not an isolated incident or one news article.

Any suggestions on what I should look for or troubleshoot? I’ve created a new template but it’s still not displaying. 

Thank you, 

—
Charlee

Hi, Charlee. Is the content still in the database? Do you still have that particular field showing when you go to edit or add a new entry?

Hey Sue,

I checked and the content is still in the database and also in its weblog entries. The field is also displaying when I try to add a new entry. 

I did some further investigating and a custom field with the same name “article-body” was created on another site we’re developing. These sites are located under the same installation of EE, we’re using Multiple Site Manager.

I tried renaming the second “article-body” on the site #2, hopefully to remove any conflict, but site 1 or 2 is still not displaying the “article-body”. 

Thanks for your help,

—
Charlee

Hi Charlee,

Can I clarify what the situation is? You have 2 (or more sites) running under MSM and on 2 of these sites you have custom fields defined that are called ‘article-body’. Both sites used to display these fields on the front end but now neither one is doing so. You can see each custom fields defined in its field group under each site and entries using those field groups are accessible and editable in the CP. Is that correct?

If so, were these fields duplicated when creating a site? Have you upgraded the sites from earlier versions of EE and MSM? What type of field in ‘article-body’ in each site (Textarea or some other type)? Please list the extensions and modules you have installed.

Cheers

Greg

Can I clarify what the situation is? You have 2 (or more sites) running under MSM and on 2 of these sites you have custom fields defined that are called ‘article-body’. Both sites used to display these fields on the front end but now neither one is doing so. You can see each custom fields defined in its field group under each site and entries using those field groups are accessible and editable in the CP. Is that correct?

Yes you are correct. To be specific, site #1 never attempted to display site #2’s “article-body” field. But site #1’s “article-body” field was displaying on both site #1 and site #2’s front ends , but it’s not anymore. Hope that wasn’t confusing.

If so, were these fields duplicated when creating a site? Have you upgraded the sites from earlier versions of EE and MSM? What type of field in ‘article-body’ in each site (Textarea or some other type)? Please list the extensions and modules you have installed.

I’m not sure if the fields were duplicated when creating the site (I was not working on site #2), but looking at the other fields in the field group, it doesn’t look like the fields were duplicated. I have upgraded the site from earlier versions of EE, I believe we started with EE 1.6.4 back in 2008. On site #1 the “article-body” field is a textarea, on site #2 the field is a “Wygwam” 

Here is the list of Modules and Extension

Modules: Blacklist and whitelist module, Blogger API, Comment, Deeploy Helper, eeFlickr, Email, Emoticon, File Upload, Freeform, Fresh Variables, Photo Gallery, IP to Nation, Mailing List, Member, Metaweblog API, Moblog, Pages, Playa, Query, Rating, Referrer, RSS, Search, Simple Commerce, Statistics, Structure, Tag, Template Inspector, Template Morsels, Trackback, Updated Sites, Weblog, Wiki, Wygwam

Extensions: Edit Tab AJAX (v.1.2.1) , Comment Spam Prevention (v.1.1), Category Checkboxes (v.1.1.5), Fresh Variables (v.1.0), onSubmit (v.1.0.1) , Parse Rating Stats (v.1.0.0) , Textile Editor Helper (TEH) (v.1.0.4), Tag Submit (v.2.6.6), LG Social Bookmarks (v.2.0.2), jQuery for the Control Panel (v.1.1.1) , SL Combinator (v.2.1.0) , FieldFrame (v.1.4.3), Publish Tweeks (v.0.8), MD Dulee Noted (v.1.2.1), Edit Menu (v.1.0.2), Template Inspector (v.1.0.1), Template Morsels (v.1.1.1.d2), Clone Entries (v.1.1) , NB Show custom field data (v.0.8.1.1), Custom CP Home Panels (v.1.1), Structure Extension (v.2.0.8), Geotagger (v.1.1.5)

Thank you Greg

—
Charlee

Hi Charlee,

Okay. Can you please create a test template group in each site. On those templates put just this code:

{exp:weblog:entries weblog="{weblog}" show_future_entries="yes" show_expired="yes"}
{entry_id} - {title}
{article-body}
{/exp:weblog:entries}

Please adjust the weblog variable to be appropriate for the custom fields. What is the output from these templates?

Cheers

Greg

Hey Greg,

The output for site #1 just shows the ID and Title, but not the contents of “article-body” from the “news” weblog on site #1.

The output for site #2 shows the ID, Title, and the content of the “article-body” from the “news” weblog on site #2. 

I also created another test template:

{exp:weblog:entries weblog="news" show_future_entries="yes" show_expired="yes" site="site#1|site#2"}
{entry_id} - {title}
{article-body}
{/exp:weblog:entries}

Output: The ID, Title, and the content of the “article-body” for site #2’s “news” weblog shows, but only the ID, Title, for the site #1’s “news” weblog shows, the “article-body” from site #1’s “news” weblog doesn’t show. 

Thank you,

—
Charlee

Charlee,

You mentioned you tried renaming site 2’s custom field. Can you try that again please and amend your test template to this please

<h1>Site 1 Entries</h1>
{exp:weblog:entries weblog="news" limit="10" dynamic="off" status="not closed" show_future_entries="yes" show_expired="yes" site="site#1"}
{entry_id} - {title}
{article-body}
{/exp:weblog:entries}  
<hr>
<h1>Site 2 Entries</h1>
{exp:weblog:entries weblog="news" limit="10" dynamic="off" status="not closed" show_future_entries="yes" show_expired="yes" site="site#2"}
{entry_id} - {title}
{article-body-two}
{/exp:weblog:entries}

Next step is to disable Wygwam for that field and see if that is the culprit.

You can disable all extensions globally without deleting individual extension settings by using the large green button in the top right of your extensions page. Try your test template after doing this. Has anything changed?

What version of MSM are you using?

If none of the above isn’t working for you we will be recommending you upgrade to EE1.6.x and the recent version of MSM also.

Thanks renaming the fields worked. I appreciate all your help.

Take care,

Glad things are working again. Don’t hesitate to post again as needed.