Problems in migrating magento to a new server - magento

I have moved magento to a new server, updated all the database requirments, cleared the cache. but still it is picking up the old database name , userid and password. Thus i cannot connect to my store any help will be appreciated.
Thanks

Remove
app/etc/local.xml
var/cache/*
var/session/*
Then visit the store URL - you should see the installer (and subsequently complete it).
If you don't see the installer, are you sure you don't have any other applications integrated into your store, eg. Wordpress (which would show "Error establishing database connection" in a big H1)

If your old database is still used, the only possibility is that you did not change the database properties in the file app/etc/local.xml.

change var and cache folder permission to 777

Related

How to run magento files on local server?

I have done one work which is stored in the webserver. I downloaded all the files and the database and uploaded onto the local server.When I am typing the local server url ,its going to the web server url.Also when i am logging onto the admin panel in magento in local server, its going to the admin panel in the webserver.How can it be corrected ? Actually I am new to Magento.
You should have to update base url in your database. Open your phpmyadmin, go to core_config_data and update your new url. Use below mysql query,
UPDATE core_config_data SET value="http://localhost/your-magento-location" WHERE path='web/unsecure/host';
Don't forget to clear cache.
Note: Please consider that, before ask question here, you should have search in google. If you are not able to find answer, then you can ask
here.

Locking Out Admin After Migration - Magento

So I've gotten myself into a bit of a pickle and need assistance from StackOverflow Gods.
We're trying to transfer a Magento site from one server (Godaddy) to another (Private Virtual Server) for the purpose of becoming a test site.
I'm not familiar with Magento (my first mistake) but I researched migration, and I ran across an article that said all you need to transfer is the database, theme files, catalog files and skin files.
So that's just what we did. We setup a fresh install, added the files and the site (http://boulderfootandankle.com/apv-test/) looks like it's got some formatting errors. We figured we could fix those after adding the database.
As soon as we connected the database through the local.xml file, the theme changed to a generic one (I imagine a fallback) and we were locked out of the admin.
I tried a number of the solutions offered for this very problem, which included:
Clearing the var/cache and var/session folders.
Altering the core config data values for the unsecure and secure web base urls.
Deleting the unsecure and secure web base urls and cookie values form the database.
Changing the sessions save CDATA from "files" to "db"
Changing the install date to the original
Altering the varien file
...and nothing seems to work.
At this point, I'm just wondering if doing a fresh transfer of the site from one server to another, instead of transferring specific files into a fresh install, would work
Did you use the same encryption key as the previous installation? The encryption key is set in the local.xml file and needs to be the same on both extensions. When you did a fresh install it would have given you a new encryption key and this could be why you are unable to login.
just my quick list for transferring sites...
1. run files backup and mysql dump (from source)
2. Copy local.xml (from Target)
3. Restore backup and mysql dump (to Target)
4. Restore local.xml(from step 2 to Target)
5. Correct base_url (in Target)
The only time I have ever had a problem with this is when I run things locally for dev in that case there is varien specific check that monks with admin login(but, sounds like you know this).
https://magento.stackexchange.com/questions/26071/magento-1-9-can-t-login-to-admin-panel
I am on 1.14 and the posters suggestion essentially is the same fix I found. Of course the responder is totally correct on the horror of this solution but, since this is a test site as long as you leave yourself the right notes you should be able to undo this when you move to production.

Megento dev site re-directing to live site URL

I'm having a huge issue with accessing my dev site. I two magentos sites on different servers. One is the dev site, the other live. However I needed to copy the database from the live to the dev site.
Ever since i did this i've had problems with accessing the dev URL. As it keeps re-directing me to the live site. I've googled the issue and tried the following:
Accessed the 'core_config_date' and changed the unsecure/BASE_URL & secure/base_url and changed them back to the dev URL.
I then went to clear the cache on the dev site, which had already been cleared from when i was installing a plugin.
Set everything to 0 in 'core_cache_option'.
Cleared cache on my browser
But i'm still getting the issue of the site re-directing to the live URL.
I've noticed a few people had had the same problem, but the above solution doesn't seem to be working for me. Any help would be much appreciated.
Thanks
Right so managed to sort it. It was a permissions issue. I overlooked it as I didn't have a linux user setup for this site. However the folder user was set to 'root' as opposed to 'www-data'.
For anyone with this issue in the future, I strongly recommend checking permissions on the server/folder for caching.
Steps to fix the issue:
Change base URL in the 'core_config_data' table (can be found on line 5 or 6, give or take)
Check permissions on your siteroot/var folder. Delete everything from /var/session & /var/cache
Run 'chown websiteuser -R siteroot' and then 'chmod u+w -R siteroot' for permissions changes.
That should be enough to get it working.
Do the below steps in your development server :
1) Check the development server database hostname,username, password in your config.xml file in below path : app/etc/.
2) Open your live server database in any editor and find the live site url entirely.
and replace with your development server url with searched result.
above two steps will solve your issues.
here after it will now solve.
3) Check your .htaccess file in your root folder to check the any redirection rule.
Check your file permissions and set them properly so Magento doesn't end up creating a MagicCache in the system /tmp folder which is where your core configs are being cached, allowing for you to clear var/cache till the end of time and have the settings in the database never take.
All over here Can't change Magento base URL -> Stuck in cache

Magento Admin login kicks me out back to the Admin login

After I enter my username and password and click "Login" it sends me back to the Login page with NO error messages. The URL changes to include a session key and that's it. Everytime I click Login again, the session key is regenerated and I still can't log into the admin interface.
I just encountered this problem on one of my servers (not a localhost installation). Turns out the system account was over quota, so I presume Magento was unable to create the necessary temporary files. (I noticed this when trying to create a directory on the server over ssh.)
So... maybe check to make sure the account under which Magento is running isn't over quota on your server? At the very least, it might not be a Magento problem directly.
Clear the contents of the directory var/cache and try again.
If that doesn't help check the table core_config_data in the database for records with a path value of "web/secure/base_url", "web/unsecure/base_url" and "admin/url/custom". These should match the page you are trying to log into (but without "index.php/admin/" at the end)
Finally check your browser's cookie settings and that the server's PHP is able to set cookies.
I was having the same problem running Magento 1.5.1 on my production server. I would log in to the admin, the url would show the address for the dashboard (with the secure key), but the screen would still be the login screen. There was no error. This happened with FF, Safari, and Chrome.
I fixed it by manually setting two core_config_data values in the database. They are as follows:
web/cookie/cookie_path = /
web/cookie/cookie_domain = "mydomain.com"
clear out var/cache and try to log in. For me, it worked.
Version 1.7.0.2 I have been moving my magento store from on server to another one, and I had the same problem. Use phpamdin to edit your database on new server, search for web/cookie/cookie_domain in 'config path row', the value is probably your old domain name: yourdomain.com, change that to your new domain name OR to your new IP address (new server). If you attend to use your old domain on new server environment you will probably want to set your story ready before you switch your name servers. That was the case for me, after I added my new server IP to web/cookie/cookie_domain instead of domain I was finally able to log into my magento backend.
I had some problems when on a local server. It was on http://server/username/ and so didn't have dots in it. If we changed the settings to be the IP address of the server then it was fine.
There can be several things that cause this behavior. This is my checklist. One of them will eventually fix it.
Click the "forgot password link" and then the "back" link. This will remove any possibly misplaced params in the URL as well as make sure you're on the right server (some installations have separate admin servers)
Clear cookies or use an incognito window
Try another browser
Local installations: Try using 127.0.0.1 instead of localhost (and update the base URL in the core_config_data table)
Clear Magento cache, full_page_cache, and session directories in the magento/var/ directory (and repeat 1 and 2)
Truncate the core_session table
Verify your Magento has correct memory settings
Check Magento system.log and exception.log files and debug
Check PHP's error logs and debug
I've experienced this issue using Opera, while in other browsers it worked fine.
Also, make sure to set correct cookie options in:
System > Configuration > Web > Cookie Settings
Also, make sure that your system time / time zone on the server and php and magento match up.

Taking over a Joomla created site

So i have a client, who has a disc of an entire site. Root server files, all the way to /httphome/ files...
However, it looks like it was created using Joomla. Now, i know my HTMl and CSS but have never used a CMS like Joomla.
To get this site up and running, am i going to have to install Joomla on my clients server, and then upload the files?
i am going to assume its not that easy.... anyone got any insight into this process and what im looking at?
thanks
Keep in mind that Joomla content resides in a MySql database.
You need the following:
Database export
Create a DB on you MySQL server
Upload the files
Edit configuration.php to work with you db and also set your path there
Also, some components might need some more setup, as some of them have their own cfg files.
To get this site up and running (if the file is really the entire site) should be as simple as setting up a web server and pointing it to the directory with the index in it. Joomla should already be in that file. Let me know if i can elaborate on the process.
Since you are new to Joomla, you might want to try loading the disc contents up on your localhost first. Personally, when I'm trying something new, I hate for my first attempts to be somewhat public - I always feel a little safer if I do the first install someplace local where I'm the only person who can see it.
Best of luck with your project! If you run into any problems, or if you want to confirm that the site is definitely Joomla, let us know and we will get you sorted out.
Do you have the related database? The files that make up Joomla are useless without the database. You could install Joomla and upload your files over the top, but any database changes made by any installed extensions wouldn't be made to that install. You'd also be missing all of the actual site content without the database.
If you do have the database, then all you need to do is import the database in you your mySQL, then upload the files you have on the disc and edit configuration.php file with the new database user and password.

Resources