Thread

Hi, havenswift-hosting.

You can download EE 1.7.1—see EEWiki:// HowTo Download 1.x Version of EE

I’d recommend you get everything working correctly in that version first. If you look at the path.php file, you’ll see where EE placed the system folder, and what it was named. It would be easier to rename the system folder to match the old system folder.

As far as licenses go, EllisLab can’t really assist in the issues between your client and their previous host, unfortunately.

Does that help?

This sounds like a headache either way, if I were you I’d manually re-create the old site in 2.1.3. Would be roughly the same amount of work as battling to get 1.7 working from a 1.6 database, then upgrading to 2.1.3. We’ve needed to do similar things in the past, just needs patience and coffee, and a client with deep pockets

This sounds like a headache either way, if I were you I’d manually re-create the old site in 2.1.3. Would be roughly the same amount of work as battling to get 1.7 working from a 1.6 database, then upgrading to 2.1.3

Huh? =)  All getting EE 1.6.9 takes to upgrade to EE 1.7.1 is uploading the latest files,  setting up the config.php (should take about 30 seconds if you have your db details handy), path.php (renaming ./system if that folder is renamed) then running the update wizard.

Get that up and running, and we can troubleshoot anything that comes up, then update to 2.1.3.  It’s the closest thing we can get to simply getting the existing site running, since the host won’t supply the site files.

Hi

OK I have managed to find and download 1.7.1 (easy when you know that it is hidden away a bit !) and have uploaded and installed it.  Next I presume is to do a database and file restore of some / all of the following :

I have the following directories in the backup : assets, dav3n5haw, images, js , themes and then a few files in the top level which are index.php, styles.css and license.txt

Which of these should I be restoring please ?

Is there anything else I need to do within these files or within the database ?

Thanks
Ian

Hi again,
I would restore the files you have to the root directory of the server you’ll be on.

You’ll then need to alter your config file (inside the system folder) to change the system folder url.

Then I’d run your db backup and see how that goes.

Thanks for the assist, Steven.

havenswift-hosting - where are you with this?

Hi

Thanks for all the help so far from people and apologies for the delay in responding - several other critical issues needed sorting !

I have all of the data restored and the website now appears to load - the problem that I currently have is that if I click on any of the menu items the url changes to what it should be, but the content stays exactly the same which is the homepage content.  Hopefully this is a very simple thing to fix but I dont know where to start looking.

Thanks
Ian

do you have an .htaccess file?

Hi

Yes, there is an .htaccess file that came over from the old hosting

Thanks
Ian

mod rewrite is enabled?

did you upgrade the site to EE2 or have you stuck with 1.6/1.7 ?

assets sound like files, themes aren’t probably going to be needed, since EE 1.7.1 has its own themes folder. index.php should remain what you have now. styles.css - not one of ours, you may find you need it. I’d tend to put them back in if you find they’re needed, we have no idea what the previous person used.

As long as the initial install works, then you shouldn’t have to modify the database.

Hi

Steven - mod rewrite is enabled and the .htaccess file is exactly that same as on the old system. Using 1.7.1

Sue - I thik I have got passed all of that and have the database restored.  Site now comes up but have this issue with the same content being shown regardless of which menu option / page is chosen

Thanks
Ian

In that case, does http://example.com/index.php?/sometemplate work? Note the ? after index.php. You may need to force query strings.

Sorry - I dont understand

The problem you may be having is that the server you’re on requires you to use a ? after the index.php.

So if you have a template group called site, and you want to view that template, you have to use:

http://example.com/index.php?/site

instead of

http://example.com/index.php/site

See the difference?