Say i have a Magento installation which i've configured and developed on a WAMP server (perhaps also adding products, etc.), what is the correct way to migrate this to an online domain.
I had pretty good luck with this approach when I did it. The WAMP install was on my own box so I didn't use SSH on that side.
http://www.magentocommerce.com/wiki/groups/227/moving_magento_to_another_server
I did have a couple errors related to the new domain that their help desk were able to resolve by modifying a couple entries in my .htaccess file. But other than that it was pretty seemless.
I've also done a full backup/restore by simply copying the entire contents from one box to the other. Copying up the MySQL DB, and then I reran the install procedure by simply deleting the app/etc/local.xml file (which forces Magento to run re-install scripts).
The script asks you for the location of the DB, passwords, etc... all the data, products, order history etc, survives a reinstall.
Oh, and make sure to clear your cache/cache folders before you move everything. That saves a lot of head-aches later and reduces the size of files you have to copy.
Related
I am pretty new to cms and hope you can help me. I'd like to install modx on a ftp server. My problem is my predecessor created a website with joomla. Now I want to create a completely new website out of the old one (just content, layout and design will be new), but with modx. I know how to built it, but i do not understand how to install modx and building the new website without crashing the existing.
Can someone give me a little step by step (if possible as simple as you can, cause i'm really not so familiar to the topic) on where to install (some kind of subdirectory?!); and what i have to adjust in modx so while developing the old website can be used without some kind of crossing (or if possible, to install modx localy on a flashdrive and upload the website somehow when finished?).
And how, if the website is finished, to delete the old one (deinstall joomla,...) and get the new one to the root directory.
Ps. Sorry for my English, isn't the best... I am a German :)
Thanks :))
I you have access to the server management or some kind of control panel, I would suggest create a new subdomain, such as new.yourdomain.com and install MODx there. I would also suggest using a separate database, evenou though that is not crucial as you can use the default modx_ prefix to easily tell one set of tables from the old joomla ones.
Once you are happy with the new site, either transfer it:
http://rtfm.modx.com/revolution/2.x/administering-your-site/moving-your-site-to-a-new-server
or just change the DNS of your server to point the main domain to the new subdirectory. That would depend on your hosting prvider.
I'm moving a large Joomla site on version 2.5 with over 20,000 articles, images, etc into a new account I created in WHM because the current install has alot of bugs and 'work-a-arounds' to keep it going whenever there's an issue. I'm installing Joomla 3 in the new account, but with the large number of articles and images that are linked into it, I was going to use the J2XML Plugin to export the articles and import them, but not sure that's the best route to go with this.
I considered using terminal to SSH into the old account and copy that over into the new one and just do an upgrade of Joomla from there. Once again, I don't know if that's the wisest choice to go with this doing that there may still be underlying issues with the install itself even if it's upgraded.
Any advice is appreciated.
J2XML will not handle this number of articles, it also misses a lot of articles and doesn't maintain IDs (if I'm not mistaken). The only reason you might want to use SSH is to copy over the images.
You will need to re-create the website from scratch, or at least do many things manually, such as content migration, re-installation of extensions and re-creation of modules, etc...
I am totally new to this stuff. I have installed Joomla on my windows pc to test my changes to the site before I try them on the actual site and mess things up.
I was given a backup using XCLONER. I installed xcloner but cant seem to restore the website.
I am using XAMPP.
I am also unsure where to place the directory where the restore file should be.
Any help will help. Any tutorials on this? again, just starting out with this stuff.
Thank you in advance.
There are so many references and tutorials out there:
Google
Also Joomla.org has adequate documentation for this.
I can't say exactly about how the XCloner works, but the general steps to replicate Joomla is:
Copy and place the files and folders at the new location
Download the database
Create a new database at the new host (your computer) and import the data from the one you downloaded.
Configure Joomla (configuration.php) to connect to the new local database (host,user, password, prefix -if changed).
At this point you should be able to run your site to the new location, but you probably want to change also the path for logs and tmp folders, to reflect the new location.
So I have been given the task of upgrading one of our companies' old websites that is based on 1.5 to something newer (because a second site of ours on the same version just got hacked).
I know some php and some other web stuff, but I'd never used Joomla.
I have setup a lamp server on a local VM (ubuntu) for me to test it all out on, then upload the upgraded version as is suggested. My problem now is that I know the permissions are not correct because when I tried installing Akeeba Backup, it kept throwing errors such as "could not copy to /var/www/components and /var/www/administrator etc. I went in and chmod'd those 2 (and then the rest of www because of more errors) to 757 (from 755 for the most part) - which i know at that point might as well be 777. Then when I've tried to use Kickstart to restore from the JPA file I have, it just right away throws an error "could not create j_backup/ folder".
I know this slackening of all permissions on the root folder is wrong, but it was the only way to get it to 'work', which it's not even now, so my question is what did I do wrong in the setup and how do i fix it? I'm not great with Linux, but I'm thinking I have to make PHP owner of www? is that right? or terrible practice?
The other issue I see now is that I just installed the latest php and everything and I see Akeepa says not to use php 5.4... not sure how much of a problem that's going to be....
Some direction would be great because I'm more than a little lost.
Thanks!
This is certainly a headache. Most often, as you stated, the issue is the ownership of the files on your server. Files uploaded via FTP will be owned by your FTP user and may not be editable by the Apache/PHP user. Similarly, files created by installing extensions in Joomla! will be owned by the Apache/PHP user and your FTP user will not be able to modify them. Here is an article discussing the problem with a couple of possible solutions:
http://docs.joomla.org/Why_can%27t_you_install_any_extensions%3F#File_ownership_advice_from_ianmac
In the past, I have used an Apache Module called suPHP (http://www.suphp.org/Home.html) to solve this problem and keep it from reoccurring. suPHP executes PHP scripts with the permissions of their owners.
As for file permissions other than ownership, please refer to the Joomla! documentation for the correct settings: http://docs.joomla.org/Verifying_permissions. One quick way to handle this (if you can install extensions after correcting the ownership issue) is to use the AdminTools extension (http://extensions.joomla.org/extensions/access-a-security/site-security/site-protection/14087). One of its tools ‘fixes’ the file permissions on your server by resetting them to the Joomla! default.
Good luck!
I did a cPanel move of a Joomla 1.5 website and a PHPBB3 forum from one server to another, and when the DNS changes kicked in all I see is a blank page. The administrator panel works without any problems whatsoever. cPanel works. Website and forum (which is separate from the website) are both blank.
I have then manually downloaded and then uploaded all files (didn't move the databases manually), and some files wouldn't upload because of 555 file permissions. I changed the permissions to 777 temporarily to overwrite the file with the manually uploaded one. So all files are now the same as they were on the old server.
Even when I turn the Site Debugging on, the screen is blank.
There is no hidden index.html or default.html file which could be causing the problem.
The entire account was moved with cPanel so it's the same on the old server and the new server. The hosting provider reports no problems. The DNS changes kicked in two days ago.
PHP is working, as this link works: http://oklade.net/findpath.php
In configuration.php, there is nothing specifically pointing to the old site.
var $dbtype = 'WeboMySql';
var $host = 'localhost';
All roads in these cases generally lead to configuration.php Check spelling and punctuation for mistakes. Also, enable one of the default Joomla Templates to be sure that whatever template you're using isn't also using old values.
Problem is solved.
The configuration.php file was to blame, as everyone suggested, but there was no possible way to change it manually and get it right, I had to make the system determine its own configuration.
I installed a fresh version of Joomla in a separate folder, and a fresh version of PHPBB3 in a separate folder.
Then I took the configuration.php and config.php files for those two things and put them in the existing folders of the website which didn't work.
Changed the minor details such as database prefixes (as I couldn't have entered the existing ones while installing), and that's it. Now it works.
So this might be a good workaround for anyone facing the same problem. Install a dummy version of Joomla and use the generated configuration.php file for the old, non-functioning website.
Before starting to debug the server, turn debug-mode on (in the admin CP)
First thing I would try is to delete the cache by running: rm –rf /var/www/html/<your website directory>/var/cache/*
The next thing I would try is to switch to another template - make sure that the template is not the issue.
Also, make sure to check the apache access log - just in case. also, you can check .htaccess for stuff like 301 redirect rules or any other problematic configuration (same applies for httpd.conf and configuration.php)
Good luck!