Even the link you have provided in your question does not provide everything single thing that need to be change when migrating an extension. There are always fairly big API differences between each Long Term Release version of Joomla.
For Joomla 3.x, the main thing I tend to look at is the following:
Potential backward compatibility issues in Joomla 3
Here is a workaround to temporary reset your password for your account.
Login to your hosting panel and use the database tool that is available (probably PHPmyAdmin).
Load the appropriate database and then go to the jos_users table. (The database prefix might be different for your case).
Go to the browse view of the PHPmyAdmin, so you get view of the ...
This is not coming from Joomla core, but from a 3rd party (likely custom developed) component that exist in your site.
First see if you really need/use this component, or you can simply uninstall it. If you need it, then look for any information you can gather for this component - find the developer and his site/email and ask if there is an update for ...
In addition to FFrewin's fine answer, here's a couple of alternative ways to reset the admin password.
Remember that most of these methods will set your password to something simple like admin. It's very important to set a stronger password afterwards. If there is reason to believe the site has been hacked, you might want to remove other users with ...
You can try redmigrator(free) or SpUpgrade (commercial).
I try redmigrator four days ago and it works very well, if you only need the articles. If you follow the youtube redmigrator tutorial, it should be easy to migrate your content from J1.5 to J3.3
redmigrator Site: http://redcomponent.com/redcomponent/redmigrator
redmigrator Tutorial: https://www....
To answer 'what is the technical reason', I took a look through the tracker and GitHub notes. The issue seems to be two-fold - a failure to delete certain files during the upgrade, and failure to apply certain SQL updates. However, if only affects some and not others. See the bug tracker for additional info.
The general best practice option approach seems ...
While not an as extensive guide as Adapting a Joomla 1.5 extension to Joomla 2.5 these two backwards compatibility articles on Joomla Doc's helped us.
Potential backward compatibility issues in Joomla 2.5 and Joomla Platform 11.4
Potential backward compatibility issues in Joomla 3 and Joomla_Platform 12.2
Nick also found this non-Joomla Doc's ...
Yes, it is possible with a component, but it will take a little longer as there are more directories and files.
Create a folder on your desktop (e.g "gallery"), then copy the XML file from:
into your newly created folder.
Open the XML file and inside you will see something like:
Assuming that you're just migrating from one server to the next (e.g. development to production).
Look at Akeeba Backup. It is capable of transferring an entire site from one physical/virtual system to another, including the database.
If you're just looking to make it work, the links @Lodder provided will help massively when dealing with deprecated code. A bunch of 3.x code was backported while working on 2.5.5, so if you're only supporting that version or later, you could theoretically get a component working on both 2.5 and the 3.x releases with relative ease. What isn't documented is ...
Before you start anything, make sure you have a backup of both sites just incase any mistakes are made in the process.
For migrating Mambo to Joomla 1.0, have a look at the following tutorial.
you will need to download a copy of Joomla 1.0 for this which you can get from here:
Migrating Joomla 1.5 to 2.5 might be a complex process, depending on what extensions you have on your current website. It's almost never a one-click process. The same goes for Virtuemart. VirtueMart 2.x.x is a completely new shopping cart system which is not compatible with VirtueMart 1, and a one-click upgrade does not exist.
First of all, make sure you ...
Rather than migrating the users manually you could try some of the extensions available at Joomla Extensions Directory. This page contains several extensions, both free and commercial, you'd have to look through the list and see if any of them works for you.
My recommendation is that you try J2XML (free). I have used it before to export almost everything ...
If you have enough rights on the server, I do it without any downtime and without Akeeba. I use a script like
Make a dump of the mysql joomla database, store the file in a directory which is not readable by apache server (not accessable through user www-data [ubuntu, etc] or http [arch linux,..]):
mysqldump -h hostname -u user --password=password ...
A few troubleshooting questions to think:
Does your new hosting meet the system requirements for Joomla 3.3 ?
Are you sure this was not a problem before you move ?
Did you do the move at your own ?
Try to restore again the website on another directory - or on your computer and see if the issue persists.
Is it possible that you had file overrides or core ...
At first I was going to suggest sticking with the current version of jDownloads on your J3.x site but it won't even work in the slightest.
I do not know of any Download Directory extensions that will allow you to import your data from jDownloads and having checked the JED site, I don't think any exist as it is a relatively big/complex extension.
I think ...
Joomla 1.5's users table structure was this:
And 3 is this
It looks like somewhere "rawpassword", "blog" and "newsletter" have been added to your database. My guess would be that you've installed a badly-coded extension that has ...
There is a way by exporting required k2 tables in your hosting phpmyadmin in Site A and then import those tables in Site B database.in site B you have to have k2 installed, after export, to check if there are any k2 table column missing, you have to go extension manager->database page and need to click fix.
For this kind of exporting, you have to export ...
Try again a step by step migration:
Make a Backup first and then try this:
Follow this instruction to Upgrade Joomla 1.6.x to Joomla 2.5.x - http://www.ostraining.com/blog/joomla/upgrade-joomla-16-to-25/
Be sure every component, plugin, template is ready for Joomla 3.3
Deactivate the rememberme plugin.
Then go to Joomla! Update under Components Menu, then ...
So what I did was export the J1.5 jos_users table (minus the usertype and gid), and then process all the accounts through our audit and update processes, then imported them all into the J3.4 jos_users table.
SELECT `id`, `name`, `username`, `email`, `password`, `block`, `sendEmail`, `registerDate`, `lastvisitDate`, `activation`, `params` FROM `jos_users`;
I recommend you to use this plugin:
it will reintroduce the deprecated DS constant to ease the migration for 2.5.x sites whose extensions still use DS until they get fixed by its developers.
The best way to go about this issue is to persuade your client to undertake a migration to a modern stable version of Joomla (currently 3.6.4) or build a new site from scratch in case there is very little content. It may be and often is viewed by clients as unneccessary hustle and expense but in the long run it proves to be the best practice both for clients ...
There are a couple of approaches. Using @Tom Kuschel suggestion with rsync if you have such privileges is one. But there are others as well.
If the only changes are on the db level, you could simply create the new database, import your data and then connect Joomla to that database.
Connecting Joomla to another database (and remote databases) can work also ...
When we do a site upgrade like this we use a temp folder and Akeeba. Simply create a new folder for for the updated site and install it using Akeeba. Make sure you use a new database so the entire new site is fully functional in the folder. Once you are satisfied that everything works, move the entire current Joomla install into a folder, then move the new ...
I found this on the Joomla Site: http://forum.joomla.org/viewtopic.php?t=710302
Finally got it... I was reading about the "open_basedir" directive. "
Did a locate php.ini and there it was: /home/xxxxx/htdocs/xxxxxxx.net/administrator/php.ini
If you have a php.ini file in this location, change the following two items to the correct paths:
upload_tmp_dir = ...