I want to update a Magento 1.4.2.0 to 1.6.x.y. instead of the latest version 1.7.x.y
There are many articles on how to update a Magento installation to the latest version, but that´s not what I want. There are some forum threads where people are asking how to update to a specific version, but those all don´t sport a solution.
It seems like it is only possible to unpack the tar.gz of the specific version, but it is not possible to use the command line tool, i.e.
./mage config-set preferred_state stable
./mage upgrade-all --force
Is there a way to use the command line tool to update to a specific version?
Two different ways of handling this, 1) Manually...
From my experience, what you end up doing is scrapping Magento Connect (which often is the source of all evil, when you've had it do partial upgrades two or three times in a row), downloading the whole package from the download archive (you have all the versions available from there on the Release Archives tab), unzipping them to a directory and then either on the server, copying them into your Magento root directory or from a remote workstation, ftp/scp uploading them to the server Magento root directory.
If you're serious about running Magento, you will have a development server that you do this to several times to find out where all the upgrade breakages are so you can weed out busted templates, detect forgotten core modifications, curse third party modules that don't survive, etc. It's really important to do this if you're depending on that e-commerce site for your income as intense suckage occurs when you aren't ready and sink the live site.
If you've modularized all your module overrides, created your own skin folders and custom template or used a well written template from a developer, it truly is just simply dumping the new version files on top of the old version files and overwriting everything (only after disabling all Magento caching and the compiler if you were using it and manually deleting all var/cache--? folders).
If, however, you've modified any of the files you are overwriting, you are in a world of hurt because you didn't do things properly.
Also, you have to deal with upgrading third party modules to work with the new version.
Then before committing the live site, backup all Magento application files and do a database dump.
2) Or use the command line tool as follows...
Since the original question was, "can you use the command line tool?" yes you can. Once you have the file saved from the download archive, use the following:
./mage install-file /home/login-name/path-to-download-file/magento-1.5.x.x.tgz
I've also used this on various module packages to inspect the contents. The mage command has a download only, download the package file, inspect the contents. If you like what it does, install it.
Related
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.
I am running Joomla 3.1.5. I have a custom component installed and I have made some minor changes to some of the files. How do I create an uploadable/installable zip file to install these changes to my production Joomla site?
Please disregard the discussion on templates in the comments above.
You don't need to rename your component it seems.
If you need to install on a single site:
on the prodution site, install the installer you first installed on
your development site
sync the files with a version control system
such as git / rsync / scp / sftp / ftp whichever you're most
comfortable with
If you need to install on multiple sites:
You need to repackage it, and add to the xml manifest any files/folders you added.
Simply explode the original zip installer somewhere on your drive, and figure out the folder structure (could be admin,site,media for example).
For each browse the custom_component_name.xml section and ensure it contains the files you added, if any.
Then copy the updated files over the folder structure, zip it, and upload it to production.
Once you do this the component will be registered in the other Joomla installation. You can also keep the copies aligned between the two servers with a code versioning system such as git.
If it's a component you plan on distributing, create a script to package it, look at the Joomla docs there's plenty of info, you could use a bash script, phing, ant, maven, choose one that suits you any will do the job
This is my first time building a Joomla template so I'm not quite sure if I'm doing it right.
I setup my joomla installation on my machine and added extensions to it - plus the customizations needed for the extensions and the template.
Once I install the template to a website, how do I include all the extensions with it (and the configuration of the extensions)? Or do I have to setup it all up all over again?
Thanks!
You have to set it up again. Extensions aren't part of the template. The Template defines the layout of the site, and the locations on the page where extensions can be added, but it doesn't include the extensions themselves.
There is an easy way. Rather than messing around with installing everything again, simply install Akeeba Backup. You really should have that installed anyhow. In any case, you can make a backup of the entire site including the database, then upload it to your host and run the built in install. It takes longer to upload the file than it does to make the backup and install it. When you are done you will have an exact copy of the site including extensions, templates, and configuration.
I'm having issues with my Magento store and I'm feeling like I may need to re-install the website. The first thing I'd like to attempt is simply re-installing the core data that comes from the installation zip file. The files are exactly as they were when I first uploaded them to install (in other words, config files are configured properly). Is this safe to do or have these core files been modified by the installation in such a way that re-uploading and replacing the current core files will break it?
Keep in mind that some developers do modify the core files (inappropriately). Not sure if anyone other than yourself has made changes, but it would be smart to do a diff on the core files against a clean copy to see what differences there are.
If you are re-installing the same version of Magento, then no problem. You can re-upload the core data files until and unless there is no changes done in core files before.
If the Magento version if different then you shouldn't.
Can I create a symlink to the local extension from aonther project folder? I have a common local-server and i need to implement same extension on all local project-installations. I tried to put the symlink, but some times i do not get expected output. I get it only after clearing the cache of that perticular project.
Your scenario is a common one I guess. But as Omar said, linking to the same code base of the extension through several typo3 instances is not a good practice.
But we have the same structure as yours, we realize this through SVN. All of our projects got a SVN repository and common extensions have their own repository. Through svn:externals the extensions are linked into the concrete project. This has the advantage that you can change the extension in the concrete project and after committing all other projects (that do have to update from svn though) contribute from it. I Think this would fit your needs, too.
If I understand your question correctly you have several Typo3 sites on the same server and want to share an extension between them using a symlink. I don't think that is a very great idea because many extensions use tables and every site normally has it's own database so you would have to do a lot of tinkering to get that to work.
Instead you could make all the modifications to the extension files in the typo3conf/ext/extension_name folder and then export the extension to a t3x file (Ext Manager in the Backend). This t3x file can be installed as a extension (Import extension) on all your other sites.
If you extension does not use a database and you are planning to make frequent changes then I guess you should be able to make that work (the symlink). Otherwise I recommend you use the first approach I described.
I have not tried this, but you should be able to install extensions globally in Typo3. What this means is that the given extension is placed inside '(typo3_src/)typo3/ext/' instead of 'typo3conf/ext/', presuming both sites use the same Typo3 Core/Source (and thus typo3_src is a symlink to the location of the core).
You can enable installing global extensions via the Install Tool. Once inside the tool, click on 'All Configuration', then search for allowGlobalInstall. Or put the following line into your localconf.php:
$TYPO3_CONF_VARS['EXT']['allowGlobalInstall'] = '1';
At last, but not least, you need to make sure the 'typo3/ext/' directory is writeable.
Hope this will be to some help. If you have any further questions, let me know :)
As Björn mentioned, I'd sugegst to install them globally. Mind you, updating the source will require to move the extensions accordingly..
As for "expected output": be aware that the code in these folders is cached in various ways (mainly page content and config settings), and hence not always run. This is the reason a change done from "outside" the current installation is likely not to propagate to your output without clearing these caches (as you have observed).
When you actually install an extension via the extension manager, the cache should (if correctly configured) be cleared (interested parties may search for clearCacheOnLoad in class.em_index.php to reveal a clear_cacheCmd('all')). There is a small checkbox, which is normally checked, during the installation process to accomplish this.
Omar's first approach is therefore, as I see it, the more easy way to get "expected output" and less jumbling around with global extensions.