Hi - I'm trying - unsuccessfully - to upgrade from J2.5 to J3.

I'm following the step by step instructions here docs.joomla.org/Joomla_2.5_to_3.x_Step_by_Step_Migration but uninstalled my J2 template Responsive as well, and reverted to beez20.

I read somewhere this was a good thing to do.

Now I a 404 the front end, and this error message on the admin page www.financingfirst.co.uk/joomla3/administrator

'Fatal error: Class 'JParameter' not found in /home/financin/public_html/joomla3/plugins/system/jbtype/jbtype.php on line 23'

Googling around tells me this could be because beez20 is not compatible with J3.

Is there any way to fix this other than reinstalling from a backup (which I do have )

Thanks

Ian

Are you far along working the upgrade?

Cheers
Paul

Hi Paul - many thanks for getting back to me.

This is the admin login

www.financingfirst.co.uk/joomla3/administrator/index.php?option=com_installer&view=manage

You'll see I can't get in to uninstall jbtype so I'm a bit stuck.

Not the template then?

Perhaps best to restore from the backup and try again?

I can't find a definitive answer to this, when restoring from an akeeba backup, is it best to delete all the existing files first, or let let kickstart.php overwrite the existing files?

Thanks

Ian

Hi Ian,
Just unpublishing JB Type should solve that issue for you.

Pretty sure you have to install in an empty folder, but I would test the backup in an empty folder before deleting the current installation.

Thanks

Thanks for this guys - I'll give it another try today.

Hmm. I'm not having much luck.

I uninstalled JBtype and the upgrade worked - up to a point.

I tried to get into global config to turn off error reporting, but I got another fatal error:

Fatal error: JModelBase cannot implement JModel - it is not an interface in /home/financin/public_html/joomla3/libraries/joomla/model/base.php on line 20

I got a different fatal error when I looked into ACL.

I checked out the Akeeba forum and found this reply from Nicholas to a similar problem:

---

Your upgrade has failed. The error message comes from Joomla! itself, not Admin Tools. Normally this doesn't happen and I have a few dozen Joomla! 3.3.6 sites running on all combinations of Ubuntu Server, Mac OS X and Windows with PHP 5.3, 5.4, 5.5 and 5.6 to prove it – let alone knowing exactly which part of Joomla!'s code this error message comes from and why.

You simply have to redo the 2.5 to 3.3.6 upgrade. Make sure that ALL your files and directories are WRITEABLE when performing the upgrade. It is IMPERATIVE that the upgrade process removes old Joomla! 2.5 files. If it doesn't, well, you've seen what the problem is.

---

This doesn't really help me as I don't know why the upgrade failed.

I'm going to try again (I did do the restore in an empty directory) - just wondered if you guys had any thoughts on this?

Thanks

Ian

Hi Ian,

The error is likely due to an extension that is not compatible with Joomla 3 which is trying to access the files shown in the error message.

You would be best to disable all 3rd party extensions while perfoming the upgrade.

Regards,

Rob

Hi Rob - thanks for getting back to me so quickly.

I think the problem was that I was using an existing database - one I had used for a previous unsuccessful attempt at the upgrade.

I did it again with a fresh database, and it's looking much better.

However, I'm getting an error 500 on the front end, and the following error message appears when I go into ACL:

DataTables warning (table id = 'groups'): DataTables warning: JSON data from server could not be parsed. This is caused by a JSON formatting error.

I've googled it, but not yet found anything I understand. I'm still looking…

Thanks again

Ian

Hi Ian,

I would probably take a backup of the site and then try the upgrade on a fresh install on a localhost.

A 500 is an ambiguous server error which could mean many different things from a htaccess rule to php extensions.

The admin error sounds like the database might not have updated properly which you might be able to fix through the database tab of the extensions installe, but I would start locally with a fresh install.

Rob

Hi Rob - thanks for this.

I'm getting a bit depressed now

Fixing the database seems to have got rid of the admin error - thanks for that - but the 500 error is annoying.

I've never managed to set up WAMP to test sites locally - I've always had loads of server space to do it remotely and not bothered too much.

What's the advantage of doing it on a localhost?

Ian

I've always done it locally as I can problems relating to working on a live server and a server I know works fine

I've found xampp to be a better option than wamp - I've used both

www.apachefriends.org/download.html

I installed 5.5.30 / PHP 5.5.30 version just before Christmas

I'd test it works by installing a template quickstart

If on windows right click on xampp-control.exe and run as administrator

Cheers
Paul

Hi Paul - I'll have to revisit this and give it another try.

Meanwhile I've installed Responsive2 and set it to the default template which has taken me right back to the error:

500 - JHtmlBehavior::mootools not found.

Which is where I came in before I was sick!

I'm now going through all the extensions again to see if I've missed anything.

I take it anything from joomlabamboo, or akeeba should be fine?

There are some - including PHPpass - which I am not familiar with.

If I post a list of them here could you check it out for me please?

Btw, the back end seems absolutely fine…

Thanks

Ian

By the way I have lots of other J 3.4.8 sites running on this server, so I can't believe it's a server issue...

Hi Ian,

Any error code that starts with 5 (500 503 etc) is a server issue. There is no question of it being anything else.

How that error is created is another matter.

If you have errors related to mootools then it is again an issue with a third party extension as mootools in not included in Joomla 3 and is never called for by the Joomla core.

The issue could be from any extension maker if you have an extension installed that is not compatible with Joomla 3. This could be an old akeeba extension or bamboo extension/framework.

You can easily compare which are core extensions by installing a blank copy of Joomla and checking which extensions come installed by default. This is not something we can do for you.

Regards,

Rob

Hi Rob

Sorry to be a pain on this one, and thanks for your help.

I'll keep uninstalling extensions until I find the right one.

The actual error I'm getting is

500 - JHtmlBehavior::mootools not found.

Does this mean I have a server error as well as an out of date extension?

I'll see if I can set up a local host as well.

Thanks again,

Ian

Hi Ian,

That's in internal server error caused by an extension trying to load the mootools javascript library which does not exist in Joomla 3.

It can only be coming from a 3rd party extension which is not compatible with Joomla 3.

Regards,

Rob

Thanks for clearing that up Rob.

I'll soldier on

Thanks again

Ian

Thanks Ian

Good luck with it

Cheers
Paul

Found it!

It was somewhere in K2 setup.

I unpacked all the files in a folder on my desktop and did a global search moo tools. Once I found it inK2 I uninstalled everything I could and it worked

But I'm not sure which extension was causing the problem.

I can't uninstall all the K2 stuff - I get this error message with a lot of the modules:

Warning
JFolder: :delete: Path is not a folder. Path: /home/financin/public_html/joomla3/modules/mod_k2_user

Module Uninstall: Manifest file invalid or not found.

Any thoughts?

Thanks

Ian