Thread

I hope this is in the right section, and pray that I will not be beaten with a wet noodle if it is not.

I’m very excited about the Multiple Site Manager, and I think it’s priced rather reasonably given what it can do, but I can’t afford it. I can’t afford much of anything right now.

I’m looking to launch a new site in July, and I was hoping to use the MSM to make my existing EE install power both my existing site and the new site. Now it looks as if I’ll be using EE Core to power the new site.

My question is this: how easy (or difficult) will it be to migrate content from the EE Core installation to the EE installation later on, once I have the bucks to purchase the MSM? Should I head out onto the street and start begging for spare change so that I can start out with the MSM right away? Or will the migration be relatively painless when it’s time to do it?

Oops! Oops! I forgot about the old method of doing multiple sites (actually, I’m not even sure I ever knew about the old method. ), but then I read this thread. Sorry for the errant post. I suppose this is the natural solution to my problem.

Just in closing: Upgrading from Core is very painless. Actually, nothing changes as far as the db is concerned, ulpoading a few additional modules is all that’s required.

Right, but in this case I’d be importing a Core DB into an existing full personal EE install. Would that be basically the same process?

Well, that’s basically merging two EE sites; it doesn’t really matter whether they are Core or Personal. Yes, it can be done. What I have used with some success was exporting one site in the MT import file format, then importing that at the other site. That way EE does all the heavy lifting.

Hmm.  How dependable is this MT format, and does it cover the bases such as tables used by Extensions, Plugins, & Modules, provided you add those also to the new installation?

I’m pondering what to do to bring my site work into 1.6 licensed, since a simple upgrade from 1.5.2 EEcore to 1.6 EEcore seems to have failed at least on first try.

Nice if the export format can be used as a safe way.

Regards,
Narration

The MT format would be solely for entries.

Upgrading from core to full should be easy, as per the docs.  If you had problems with an update, I would recommend you post a detailed account in the installation forum so that we can troubleshoot.

Hi Lisa,

It’s very late here, and just getting out of one your site blackouts so I can answer.  I will post a traceroute in the thread about that to show what happened - nothing past Washington, DC passed in the routing, after crossing the ocean fine.

I also thought the EE update should be very simple, and believe I followed directions exactly, as well as making some recovery attempts by unzipping on the server and re-replacing directories.  However, it exactly did not work, starting with refusing to create the new table(s) needed by 1.6.

I don’t have a lot of time to mess with this, as the site content’s the thing, so have been trying to plot a sensible course.  For the last effort tonight I’ve made a new database and a completely fresh 1.6 licensed installation, to prove there’s no problem with it working. 

Past that, I thought about the fact that there are some symbolic links in the original arrangement.  Maybe PHP doesn’t like those.  So I thought I’d move the old site, fresh from backups and working, to a non-symbolic-linked place, and see if the update would work there.

More when I know more, and I will report it to the EECore area where first posted, if it can help anyone there.

Kind regards, and please bear in mind it’s late here,
Narration

Site blackouts?  Huh?  I’ve been refreshing these forums every 30 seconds for the last two+ hours (I’m slightly obsessed, I love it here) and the site has definitely been responsive…

But yes, if you want to post the details of what you did and what errors or difficulties you’re seeing over in the installation forum, we can work with you through this =)

It’s very late here, and just getting out of one your site blackouts so I can answer.  I will post a traceroute in the thread about that to show what happened - nothing past Washington, DC passed in the routing, after crossing the ocean fine.

Yeah I hate to say it, but if nothing in the traceroute is getting past Washington, DC then there is very little anyone can do about routing issues on the “open” areas of the net.  Please feel free to private message me the traceroute, but outside of our network and our direct upstream providers, routing issues through other networks out there are beyond control really.

Hi Lisa and Nevin,

I posted the traceroutes before seeing your message - they’re here:  http://ellislab.com/forums/viewthread/54229/

I know there’s a lot of monkey-business around peering - have dealt with it before.  Maybe this can help you get the big boys to play fair, can’t say, but anyway it is information.

Best to both, and Lisa, let me try my careful attack so not to take too much time.  I am sure to be glad of your services - have learned a lot out of the history here already.

Kind regards,
Narration

Well, we’re here to help troubleshoot, so you’re welcome to take advantage of that, and encouraged to.  But if you’d like to work on it on your own, I understand that too.  Your call, keep us updated! =)

Please see my note.

Thank you.

I did…and response there.

I love the hairball cat, by the way 😉 

C.

Please see my note.

Thank you.

Hi Lisa,

Ok, last actions of tonight, and will talk to you tomorrow.

- I did a quick fresh (db) install of 1.6 licensed.  It works fine, and tantilizes.
- I had recovered my original EECore site from backup, and it worked fine again on original db.
- I pulled a fresh unzip of the EECore1.6 for the upgrade.
- I followed the instructions, and made an EECore upgrade of original site to 1.6.
- when I reached the step of running [(renamed)system]/update.php from web browser, it failed as before, with a ‘Site Error: Unable to Load Site Preferences; Invalid Preference Data’
- I backed up and dropped the table and initial row I had added, exp_sites, and ran upgrade.php again.  This time it failed the way it originally first had on my initial try, with the following indicating it had not built this table itself, as the upgrades/ud_160.php script suggests it should.  Error message:

MySQL ERROR:
Error Number: 1146
Description: Table ‘seventh_expression.exp_sites’ doesn’t exist
Query: SELECT es.* FROM exp_sites AS es WHERE es.site_id = ‘1’

That’s where I was, that’s where I am.  Ideas welcome, and now I’m confident it isn’t anything about Unix symbolic links, because those are gone in this try.  And not in EE1.6 on that host either, since the fresh commercial install works fine.

Thanks,
Clive

Well, we’re here to help troubleshoot, so you’re welcome to take advantage of that, and encouraged to.  But if you’d like to work on it on your own, I understand that too.  Your call, keep us updated! =)