Copying Standalone Instance to New Server Without Affecting Current Server

[nathanjosiah]

We are in the process of moving away from a contractor that was providing web development services for many years. We have duplicated the entire server onto a new host and it is running parallel to the production environment but on our own cloud servers. The only problem is that CiviCRM is not wanting to work on the new host. We are running 3.0.1 of the standalone version. How do I get this setup correctly on this new server until we are ready to push our version of the site as the production site. The database and file systems have already been moved but we can't see the username and password fields on the login form to change anything through the admin.

Can somebody please help?

[Michael McAndrew]

Hey there,
You are running quite an old and supported version of CiviCRM.

The only problem is that CiviCRM is not wanting to work on the new host.

The database and file systems have already been moved but we can't see the username and password fields on the login form to change anything through the admin

From what you have said so far, there are quite a few things that could be wrong and it us really hard to help you here without quite a few more specifics and details from you (what URL are you visiting. Screen shots etc. would "help us to help you", as they say.

Personally, if I were you, I would enlist the services of someone who has done this kind of work before. Someone like Hershel from CiviHosting springs to mind or anyone else that has a lot of experience in migrating and updating old sites: https://civicrm.org/providers/ and ask them how much experience they have in this area / can they provide references, etc.

Good luck1

[nathanjosiah]

I can simplify the question now that I have made more changes. The new server is now setup the same as the old production. The whole database has been transferred as well as the whole site filesystem. Civi's files are in /crm and I am accessing /crm/standalone. The difference now is that we can't login because there is no username and password fields. When trying to use the /crm URL as the OpenID URL it gives the error "Authentication error; not a valid OpenID."

[Michael McAndrew]

Thanks for the extra information.

You might find it difficult getting support here for this particular issue because you are on an old version of CiviCRM, and you are using it in standalone mode (support for which was dropped in 2010 (see this blog post: https://civicrm.org/blogs/lobo/dropping-support-civicrm-standalone-v32).

It might be helpful to get in touch with Nicolas at CiviHosting since his company now runs a standalone version of CIviCRM, which if I am not mistaken is not too dissimilar from the old standalone. He might have some good ideas.
I don't have any experience with openID or standalone, so can't be useful here.

Another option would be to move your put your CiviCRM into a Drupal site, and switch to using Drupal rather than open id for the user authentication. You could then upgrade from 3.2 to the latest version 4.5 (which is really a lot better that 3.0.1).