Thread

I’m borrowing the title from this bug report since it addresses exactly the problem I’m having. I’ve followed the simple steps outlined in the solution several times to be sure and unfortunately it isn’t doing it for me.

The problem is occurring on both the site the channel and entries were copied from, and the site they were copied to. I’m running 2.5.1.

Thanks for any help in advance!

By the way I’ve performed channel+entry duplication before without problems on this same installation, the only difference being that this time I noticed the following comment on the MSM setup instructions:

“Please note that if you import or duplicate channel entries you’ll need to Recount the Statistics in the Site afterwards.”

I did that and I’m thinking that this could have had something to do with the problem I’m now experiencing, since I hadn’t done this in the past when duplicating to a new site.

Can someone look into this for me, please? It’s a pretty huge problem that’s blocking my progress with an urgent project.

Hi roadRUNN3R,

Since you posted near the weekend it takes a bit longer to catch up, but we are still within the Support Policy

We aim to answer all support requests within 2 business days.

You mention your ExpressionEngine version, thanks for that! But ExpressionEngine and MSM are meant to work together in the proper version. For 2.5.1 that was MSM 2.1.2 - can you confirm that for me?

I would also ask that you update to EE 2.5.3 and MSM 2.1.4 and see if the bug persists.

Cheers,

Thanks Dan. I apologize for not realizing the delay was due to the weekend; I’ve been so busy lately I hardly know what day it is! EE support has always proved to be fantastic in my experience and I didn’t mean to imply otherwise.

Ok, so here’s the MSM info: Version: 2.1.3 Build: 20120529

I’m going to start working on updating EE to 2.5.3 and I’ll let you know if that helps.

Thanks again!

This is weird. As I went through the update process to EE 2.5.3, I noticed at some point (before finishing) that the problem had taken care of itself. I then happily completed the update process, including updating to MSM 2.1.4. But when I checked again the problem had reemerged.

I have no idea why this could have happened, because all I did to the site was to follow the update instructions exactly as described in the EE docs. In an attempt to backtrack to a state where things had mysteriously just started working again, I restored the old index.php and admin.php files on the MSM sites in question, and reinstalled MSM 2.1.3. This should have taken me to the point where the sites had begun working normally, but it didn’t help. I’ve now reinstalled 2.1.4 and re-updated the index.php and admin.php files, so I’m all updated.

Any idea why for a brief period there the problem disappeared, and then suddenly came back again? Hopefully that offers some kind of clue as to what’s going on, though it’s beyond me to guess what that may be…

Hey roadRUNN3R,

Let’s cut to the chase and get in for a first-hand look here. Be on the lookout for an email from EllisLab!

Cheers,

Info sent. Thanks!

Hi all,

Just a note to let everyone know we are working with roadRUNN3R on this and will reply here when we have it sorted out!

Cheers,

Thanks so much for your help Dan! Everything is working normally again 😊

Excellent!

For posterity, there were remnants of an old site in the database. Clearing out the lingering site_id from the affected tables cleared things up.

If you need anything else, please let us know!

Cheers,