Thread

I’ve tried creating a new site twice now (rolling back to a previous copy of the database before attempting the second time), and the same thing happened both times…

1) The “Pages URI” and “Template” information is not duplicated.
2) The custom fields do not duplicate correctly. For example, our “meta description” custom field is “field_id=192” from the admin screen, and “id=field_id_5” on the Weblog entry page (in the source code). So, what happens is that none of the custom field information is displayed via the rendering template, such as {meta-description}.

Any insight you can provide is appreciated, and we are using EE 1.6.9.

Thanks!
Scott

Hi, Scott!

Pages information is not part of the MSM duplication process; that would at this point be a feature request.

Template information should be included if you’ve told it to copy or move it.  Can you show us a screenshot of the options you chose when creating the new site?

For your number 2, I’m not quite following.  Do you mean that it looks as if it’s getting two separate IDs after the site creation?  Are you using any extensions or third-party custom fields on this site?

Thank you!

Re: #1- The template information I was referring to was the template choice that is used to render the page (from the pages tab). Since pages information is not part of the MSM duplication process, that explains it.

Re: #2- << Do you mean that it looks as if it’s getting two separate IDs after the site creation? >>

Yes- from the admin screen:
Site ›  Admin ›  Weblog Administration ›  Field Groups

The “meta-description” custom field edit URL is:
/system/index.php?S=7e685e8ffb4b3c01ed57edce8e3555ff513d9ae0&C=admin&M=blog_admin&P=edit_field&field_id=192

However, when I open a Weblog entry that uses this field group (via the “edit” tab), the field ID numbers are different. For example, the “meta-description” custom field value is “id=field_id_5” (in the source code). Also, the “meta-description” custom field value is “5” in the original site that was used to duplicate this new site.

I’m thinking that because of this, none of the custom fields from this field group render to the page when using the identical template from the original site (which is the real problem).

<< Are you using any extensions or third-party custom fields on this site? >>
Yes, we are using: jQuery for the Control Panel (v.1.1.1), Category Checkboxes (v.1.1.5), LG Live Look (v.1.1.0), and NSM Publish Plus (v.1.1.1).

The interesting thing is that the first time I created a new site, everything worked fine. However, I neglected to duplicate Weblog entries and comments, and the following two attempts resulted in the issues noted in this thread.

ssebner, I can’t tell, did you find out a way to fix the problem with custom fields?

No, I haven’t- none of the custom fields from this field group render to the page when using the identical template from the original site (which is the real problem).

So to paraphrase, if I may.. the template you got from the original site won’t work because the fields are now different.. is that correct?

Are you saving templates as files?

When I created the new site, I duplicated the Weblogs (including entries and comments), the template groups, and the template global variables. But now, when I view a page, none of the custom Weblog field content renders to the page. I even tried dumbing down the rendering template to only display the custom fields, but alas, nothing appeared.

When I was initially troubleshooting, the only difference between this new site and the original (that I could find) was the field ID numbers, but really I’m just guessing. So, I’m not sure if this isn’t working because the field IDs are now different, or it could be something else. All I can say for sure is that it isn’t working.

We are not saving templates as files.

Let me be more specific about the steps I took creating this new site:

1) I created the new site (#2), but neglected to duplicate the Weblog entries and comments. However, I did copy over all of the content for one Weblog entry, and everything worked perfectly. I then renamed this site to “test”, because I could not delete it because of an SQL error- see this thread.

2) I created the new site again (#3), including the Weblog entries and comments, but this time I noticed that none of the custom Weblog field content rendered to the page. This is when I began troubleshooting, and discovered that the field IDs were different. I then deleted this site (#3), and figured I’d try again.

3) I created the new site again (#4), including the Weblog entries and comments, and once again, none of the custom Weblog field content rendered to the page. I confirmed that the field IDs were different (and they had the same ID numbers as site creation #3), and then opened this thread. After that, I deleted this site #2 after some solid advice from Sue in another thread, and here we are.

Because we have done countless hours of work to site #1 during this time, a database rollback to before the first site creation should be avoided if at all possible. However, I do have an export from that time that is separated by table, and I could use that to compare to our current instance.

Thanks again for your help, and please let me know if I need to provide any additional information.

Scott

Hi Scott,

Can you clarify what’s happening here? Is it the case that on a template for your second site nothing appears at all i.e. there is nothing at all in the source code or that static text appears (and CSS links etc) but just nothing from weblog entries tags?

Cheers

Greg

Everything from the template renders correctly to the page except for the custom field content.

When I tried dumbing down the rendering template to only display the custom fields (see below), that is the only time when nothing appeared.

{exp:weblog:entries  weblog="pages" require_entry="yes"}
{meta-description}
{meta-keywords}
{language}
{additional-body-tag-content}
{left-nav-id}
{number-of-page-columns}
{additional-head-code}
{breadcrumb}
{page-title}
{callout}
{multiple}
{tagline}
{page-body}
{dymanic-collateral-number}
{content-above-contact-portlet}
{left-nav-contact-portlet}
{content-below-contact-portlet}
{right-nav-01}
{right-nav-02}
{right-nav-03}
{right-nav-04}
{right-nav-05}
{right-nav-06}
{right-nav-07}
{right-nav-08}
{/exp:weblog:entries}

BTW- This exact template code on the original site renders all of the custom field content correctly.

ssebner,

have you tried using the site= parameter

{exp:weblog:entries  weblog="pages" require_entry="yes" site="site_short_name"}

Unfortunately, I had already tried that, but it did not have any effect. I also just tried it again, and had the same results- a blank page using the dumbed-down custom-field-only template posted in this thread.

Hi Scott,

Do you have a backup of your database from just before performing the initial site duplication? Can you also show us a screenshot of your duplication settings?

The site creation screen shot is attached. Because we have done countless hours of work to site #1 during this time, a database rollback to before the first site creation should be avoided if at all possible. However, I do have an export from that time that is separated by table, and I could use that to compare to our current instance.

Do the different ID numbers noted in my initial post have anything to do with this issue? And if so, shouldn’t there be a way to fix this in the database? (Every other working Weblog on our site that I’ve checked has identical ID numbers.)

ssebner, this is worth taking a closer look. Please check your email