I have a Magento site running on a live e-commerce server.
I downloaded the whole site for offline use in a development environment. I changed the Base URL values in the database and edited the local.xml file but my local development site is still referring to the online store.
How do I correct this?
The usual problem, changing your base urls and local.xml is only a minor part of the equation.
Step 3 was missed on moving the website to the development server.
Moving stuff is actually pretty darn simple.
a. Tar the public_html directory on the old server
b. Reinstall on the development system.
a. Disable caching in Magento on the old server, dump the database and then reenable the Magento cache.
b. Create a mysql database, user and grant permissions on the development system. Load the database dump into the database on the development system.
Do the one thing that most people ignore, go set your file permissions and ownership.
Change your base URLs using either mysql command line or phpMyAdmin.
Go eliminate every subfolder in the var/ folder, Magento will recreate it.
Finally, go make changes to your local.xml file to change the database access credentials assigned to the new database and bring Magento up.
If you have complete ownership of the server, do the above steps with the Apache server down until you've loaded all the data and made the permissions and file corrections. This prevents accidentally starting Magento in an unprepared state which can cache Magento's configuration which is why you are having this problem.
If you do not have proper permissions on the var/ folder and subfolders, Magento will write your Magento temporary and cache to the system temp and you end up with Mage's magically redirected Magento which eternally points to the original website.
Also, if you copy local.xml to another file to save it, name it something like local.xml.sv0 otherwise if it ends in .xml, Magento autoload each .xml file in app/etc/ and try to merge it with the contents of your local.xml file.
NOTE: What happens when you don't properly set file/folder permissions before running Magento for the first time after a move.
Related
We had a company that developed a website for us, for a large amount of money. When the site was done we wanted to put it up on GoDaddy's hosting and the company said that it wouldn't work on GoDaddy and that we would have to leave it on their hosting servers at a cost of $300/mo, they say that because they have custom-built software that allows the customer to edit the website, that looks just like Joomla's editor. I am about 90% sure that the website was built with Joomla. I have built many websites, none with Joomla, so my question is, I want them to just give us the website files and database that we paid for, so we can go to another hosting company with our website that is a lot cheaper $25/mo. So what files do I ask the company for that developed the website to make sure we have all the correct files to transfer the website to another hosting company?
They are being very difficult to work with so I just want to make sure I know what files to ask for.
Any help on this would be greatly appreciated.
A Joomla install consists of files and the database so you need to ask for the files (probably as a zip file or similar) and an export of the database.
You can then restore the files and database on the destination server.
You will need to update the configuration.php file with the new database host, database name, database user and database password once you have restored the files to the destination host.
Alternatively you could ask for an Akeeba Backup file if they are using Akeeba Backup (which most Joomla website owners do). Akeeba backups up files and the database into one convenient compressed backup file which makes it easy to restore to the destination using the free Kickstart install tool.
Browsing certain urls can help verify if they are using Joomla. For example:
/administrator/manifests/files/joomla.xml
/index.php?option=com_content
/index.php?option=com_users&view=login
/index.php?option=com_search&view=search
I am trying to set up a copy of a Magento site for development use. I have copied the code from the server and grabbed a copy of the database.
I setup Apache, PHP, redis, MySQL, php-curl.
I added the DB user with all privileges and imported the DB.
When I load the Magento site up it loads with the default theme. Going to System > Configuration > Design shows it has defaulted all the options and they are not what they are on the live site.
Where is this configuration stored that it wasn't copied with the rest of the data? Products are all there etc, it just seems to be system configuration like cache enabling and theme etc.
The problem came down to the DB export script which wasn't including data for the core_config_data table. After doing a manual export myself the site had all its options.
Magento has switched the cache directory to /tmp on the server for 1 of the sites on a Magento multisite installation. How do we get this to go back to the normal cache folder in the Magento folder.
If this is multiple instances of Magento being installed on a single server, the usual reason for this happening is that the var/ directory has become non-writable to the web server process due to a change in permissions or ownership.
You will need to figure out what has changed either in web server/cPanel/WHM/suPHP configuration or if a backup or restore process has messed with file/directory permissions/ownership.
Example of Magento cache being written to system /tmp
i want a live site to be on local host and without effecting any functionality of live magento site. i have tried many way of doing that but have not get any result from it.
steps i tried are :
1. taken database from magento live site by entering into cpanel(by ftp access) > phpmyadmin > exported all the files to my local machine and i imported all the data to my local phpmyadmin.
2.taken all neccessary files from cpanel > file manager > all files (for example p_html, .htpassword, .trash, access log, etc file and many more) and put it on my local machine and then i put the file in folder and kept it into C:\xampp\htdocs\ all file ( in folder ).
3 Replaced the path of live site with localhost:1234 in the all sql files where applicable taken in step one.
but still not working .
Any help will be appreciated....
Copy your LIVE Magento store to your Local computer:
Download the magento files using any ftp client.
Export the database from live server.
Put the downloaded Magento files in your localhost root folder.
Create a blank database(lets say it 'local-database') in your local computer and import the database backup that you exported from the live one.
Delete/Rename the file app/etc/local.xml
Re-install the Magento using the local-database.
After installation, go to Admin section and then
(i)Flush all cache. (ii)Re-Index all data. (iii)Flush all cache.
That's it. You are done.
N.B. If you have domain specific Modules installed, those modules will not work here.
Seems very simple right. Believe me, it is that simple.
If you face any problem in installing your Magento in localcomputer, here is a post that may come in handy: http://www.insync.co.in/how-to-install-magento-on-wamp-server-localhost-localcomputer/
Steps:
Download the files to the local project folder.
Create a new local DB and import the live database backup/dump.
Update app/etc/local.xml file with local DB parameters(Host name, DB
name, DB username, DB password)
Magento have the project URL saved in 2 places(secure URL and
unsecure URL) in the table core_config_data. We need to update
that in imported local DB to the local URL(9th and 10th record in
the table).
Delete the cache: Delete the contents in var folder(That folder
contains reports and logs too. I assume that you won't need it as
this is a separate installation)
The local copy will most probably work by now but there are possibilities that it would not. Things to do in this case:
If you are getting redirected to the live site, check the .htaccess
file for redirects(For various reasons there may be a redirect
defined in the file)
If you are getting forbidden error, this will come in handy(Usually occurs in linux systems)
There may still be some problems probably theme or module specific. In this case you will need to debug the project and find out what the problem is. Xdebug will come in handy in this situation for boosting the debug process :)
Subrata's solution will conflict with some of the Magento Modules installed and will not allow you to re-install Magento in local. I follow these steps and everything works fine.
Just give a permission (0777) after take a backup to that folder in your local PC
First of all you will have to change the secure and unsecure base_url in your database.
These can be found in the 'core_config_data' table.
Paths:
web/unsecure/base_url
web/secure/base_url
If you want to access your local version of Magento via localhost, you'll have to set localhost as your base_url.
After that you need to clear your cache folder.
EDIT:
To install and run Magento on your local PC using XAMPP, please follow these steps:
http://www.magentocommerce.com/wiki/1_-_installation_and_configuration/installing_on_windows_with_xampp_and_wamp
I made one simple project, at training center and I want to continue that in my home.
I tried by transferring files from WAMP www director to pendrive and storing in my home pc Wamp WWW directory but Getting 404 ARTICLE NOT FOUND ERROR.
I already attached database related with my Joomla project but could not get into Front end.
Two basic options:
I. Have a look at a took like akeebabackup.com.
II. Do it manually
You need to sync the files.
You need to dump the database and import it to the other installation.
You need to update the configuration.php file to match the settings for database and log / temp folder.