Install Modx on FTP Server - joomla

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.

Related

Can sites built with Rapidweaver be worked on without Rapidweaver?

A friend has asked me to do some work on his existing site which was built in Rapidweaver. I'm on Windows, so is there another way I can access and edit his site?
The Rapidweaver project file is meant to be edited only in Rapidweaver, really. As far as I know, the only way around would be to use an HTML editor to modify the pages that are already in the server. However, I would not reccomend you to do it unless you are not going back to Rapidweaver anymore. Because changing the files in the server does not update your local Rapidweaver files. So, you could end up editing something in the server, then getting back to Rapidweaver and upload a "new" version that would not be completely up to date (the previous changes in the server version would be overriden by the older rapidweaver project).
For that kind of work, a CMS (Content Management System) is a more flexible way to work. Nowadays, one of the most common is Wordpress. It will require an inicial setup but after it is working it can be updated from anywhere via web browser, or even from an app in your iPhone. But it is not a Rapidweaver based sollution.
There are a couple CMS related plugins or stacks (Dropkick CMS, Armadillo, Easy CMS, Total CMS...) for Rapidweaver that could also be useful in this context. Once again, first you would need to buy a licence and to setup the website using one of those plugins or stacks. Only then you would be able to edit on the go.

Moving a large Joomla site over SSH

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...

How to restore a website offline. using XCloner on Joomla thats run on Xampp

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.

No style after migrating Joomla to localhost

I'm a total newbie with Joomla.
I'm the new man in charge of a website and they want a full redesign.
I have already downloaded everything by ftp into my WampServer and exported the BD.
I changed the configuration.php to point my new BD.
I could access the web but I got lots of Deprecated Errors so I turned off the display_errors in the php.ini
Now I can finally see te content of the web but with no templates and no style.
Any idea what's happening?
(I'm not sure what version of Joomla it was working with.)
Well, the first thing I would do is wipe out what you have moved. Then go download and install Akeeba backup. Take a full site backup, then use that to install on localhost. Doing this will make your life a lot easier when it comes to moving the site easily. If the site has issues after moving it this way, then you can pretty much bet it's a server configuration issue and not a Joomla issue.
Next thing you need to do is determine what version of Joomla you have. The 1.5.x series should have the version in the admin in the top right. The 1.6/1.7/2.5 series will have it in the admin in the footer. You can probably check the source on the front end and it will tell you in the meta generator tag. Unless you are on 2.5.2, then you will want to start planning for a migration to the newest version. 1.5 reaches end of life next month and 1.6/1.7 are no longer supported.

What is the correct way of migrating a Magento installation from WAMP to an online domain?

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.

Resources