Moving a large Joomla site over SSH - joomla

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

Related

Transferring Joomla Addons from One host to another

Good day/night great minds,
I have a perfectly functional website hosted online at the following url: www.gmaworld.com (malware infected). Unfortunately This site is infected with malware. I am looking to transfer the contents to another setup to get rid of the malware.
My concern however is how to backup/retain the current addons that i have in the current set up so i dont loose them during the new setup.
I have read through most of the migration/upgrade articles for joomla and none seem to mention anything in this regard. If it does help, I am using the shaper_qubic theme.
I will appreciate every bit of advice to help me ensure a successful transfer of my addons.
Thank you.
If you are rebuilding your website to eradicate malware, the best course of action is to re-download Joomla and third party extensions from the official websites and start again.
It's possible (by examining the contents of the extension XML install file) to download all the relevant folders and files which you could then zip back into a Joomla install file but this would be a tedious process, likely prone to manual error and possibly still have vulnerabilities if these aren't the latest versions.
To keep a website secure, you should be installing Joomla and third party extension updates on a regular basis. If you have commercial extensions on your website, you'll need to renew your subscriptions in order to have access to updates.
If cost is an issue, then try to replace commercial extensions with free extensions or try to implement features using core Joomla instead. This is often possible when new features are implemented in the core.
An alternative way to retain your extensions is to clean up the malware without rebuilding your site.
The myjoomla.com audit / clean up tool does this quite well and is a much quicker way to recover your website compared to a complete rebuild.
You will probably still need to update Joomla and third party extensions to the latest versions to prevent a recurrence.
You have best free options available and not only that it is super easy to take backup and restore your site anywhere either in localhost or any other webhost. I hope you have access to backend Administrator side
Steps
Download Akeeba backup http://extensions.joomla.org/extension/akeeba-backup and install it.
Take a backup of your entire site going to components->Akeeba Backup .backup will have extension JPA backup.jpa format. it wont open in normal extractors. To open the zip file follow the next step.
Download the extract wizard from https://www.akeebabackup.com/products/akeeba-extract-wizard.html . This will help you to extract the backup file in your desktop.
To Clean the website files use kaspersky Internet Security demo version. it cleaned many of my infected files. And do a vulnerability scan installing it in localhost to know where are the loopholes.

Install Modx on FTP Server

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.

Does it "damage" a joomla website to test extensions?

I have a bit of bad habbit, I install joomla on xampp and test all extensions and things im planning to add on the website there. Then I go to live website and try to start it from scratch, but it get very confusing and stressing this way..
I am thinking of just uploading the xampp joomla site to a live server but I am worried about these things:
I have installed/uninstalled some extensions (10+) do these leave behind any corrupted files in general or cause any problems?
Any tips cause im really worried now, the website has grown a lot and I cant start it from start even looking at the notes I took while making it. Uninstalled extensions do they leave any files behind or cause any problems? Right now the website works good on XAMPP.
Any tips or suggestions greatly appreciated,
Ammy
Most extensions uninstall fairly cleanly. You can be sure by using an FTP client and looking under /components, /plugins, and /modules (and/or their counterparts under /administrator) for leftover directories with the extension's name. You can also use PHPMyAdmin or somesuch to look for leftover database tables with similar names.
Even if files and tables are left behind, they're unlikely to cause problems with the site. I understand the desire to keep a tidy codebase, but that's not a good reason to build a site twice.
Most extensions delete their files on an uninstall. This is because Joomla does this job itself, the extension doesn't have to do anything for this to work.
However the tables are a different beast. While it would be very easy for extensions to delete their tables on uninstall, there are different ideas about this. Some argue that they don't want to be responsible for deleted data and thus leave the tables behind.
Also entries in the assets, categories, tags mappings and menu tables are likely to be lying around after an uninstall. Most extensions will not clean those tables up during uninstall.
There may also be leftovers in files, if the extension used some library like fof or similar. There is no ckeck if the uninstalled extension was the last one that used that library. So you need to uninstall those manually, but you need to know if it's used or not.
The leftover tables and entries don't generate any problems except for a bit more memory usage. However a leftover library may be a huge security issue as it may contain a bug which could be abused. Since no extension is using it anymore, it will never get updated and the bug doesn't get fixed.

how to update my own joomla 1.5 components?

how to update my own joomla 1.5 components?
i have 2 components i made with my team, that we use on our web site. (on joomla 1.5..... we didn't upgrade for the moment)
we often make updates to fix bugs, to add new featers etc...
to put update on production server , we use FTp, and we change the files that have to be changed........ needless to say, how bad it is.....
i am looking for joomla component, plugin .... to make me able to make updates on my components/template , faster and safer (i imagine, a Zip file containing what have to be changed, and a rollback function, that allow to restore a version if there is problems)
All i found is components that allow to update the joomla core (to 2.5 for exemple).
any idea?
You could use Akeeba Live Update. It's basically a 1 click update system that downloads the update zip you upload to the FTP or other host, then unzips it, updating the extension. The first time you try it out, it might be a bit hard to get used to and will probably take a little trial and error, however its the best and I think only out there at the moment. The likes of Kunena also use this system.

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