how to update my own joomla 1.5 components? - joomla

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.

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.

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.

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.

Magento 1.3.4 --> 1.5.1 upgrade. Dev site updated...how to upgrade live site?

So, we had the hosting service set up a dev site with the intentions to then upgrade our live site once that was done. After a ton of back and forth the hosting service bailed on us, and we're left with an updated dev site and not much of a clue on how to update the live site.
While I'm not asking for a foolproof way of updating the live site, I do need something that won't impact sales by being down....or something that won't be a problem to roll back on in case there's issues.
any guidance / tutorials would be a big help. when I set up our original site we weren't live yet, so I could grind away without losing $$$. That's not the case now.
Thanks!
There are two things that happen for upgrades: new functionality from the updated / additional files themselves, and database upgrades which are triggered by each module's version.
Above all, it may be advisable to find a freelancer or shop with a good Magento track record and experience in 1.3 to >= 1.4 upgrades. They should be able to set you up for the clearest upgrade path moving forward. That said, here's a procedure:
Backup database and filesystem.
Perhaps, make another backup.
Create your own dev environment from this backup: install files, duplicate database, change the db settings in app/etc/local.xml. You likely will need only to change the base_url settings in the core_config_data table: SELECT * FROM core_config_data WHERE path LIKE %base_url).
Check the big core files: Diff your app/code/core/, js/, lib/* files with a known-good copy of the 1.3.2.4 or 1.3.3 (there is no 1.3.4) - check Mage::getVersion(). Any changes will need to be accounted for. And slap whoever changed them :-)
Once you've verified that you have a healthy core / fixed your core, you are ready to test the upgrade. Simply copy the files from 1.5.1 over.
Make sure that you have set a substantial timeout if you have lots of orders.
If you have issues with this upgrade, you may opt to step through versions. Particularly, you can go from 1.3.2.4 to 1.4.0.0 to 1.4.2.0 to 1.5.1.0. At the very least, this might help you spot where along the upgrade sequence things are going to pot.
Also, you will need to fix your templates. Between 1.3 and 1.4 Magento implemented a base design package and default theme; other themes should build from this. You'll almost certainly need to merge your changes from your layout templates (under template/page/; 1column.phtml, etc.).

Joomla Component Automated Update

I develop a Joomla component. At the moment whenever I release a new version I ask the user to download a zip file and to manually upload the changed files via FTP. While this is ok for small releases, when a lot of files have been modified it is a slow, painful and error prone process. As alarming as it may be, many users installed Joomla via Fantastico one-click install and are not familiar with or comfortable using FTP.
I have recently added support for Joomla 1.6 which seems to provide a nice update facility for automated updates. Unfortunately the documentation seems to be lacking, e.g. what is the tags element, can the download type not be "full" and if so what would that look like?
Can any one explain the update process better or provide any good examples?
Joomla 1.5 is going to be around for a long time, is there a similar update process for 1.5?
For Joomla 1.5 at least, there is no need to use FTP for updating. In your XML manifest you can set the component to update. Rather than download, upzip, and FTP up, all your users would need to do is download the entire package, then install via the Joomla admin.
I am not sure about 1.6, your best bet would be to take apart a 1.6 component. It is my understanding that it is a rather simple process.

Resources