Hello Robert,

Sorry for the late reply. We are still investigating the issue but for now I have added a hot fix for you in the file

JOOMLA/libraries/joomla/table/table.php

There seems to be some issue with the addIncludePath in Joomla 3.2 where EasyBlog can't load the tables which is causing the fatal error We will continue to check this out and provide a proper fix for this.

Thanks!

I have same problem and are not able to login to my joomla backend

I do have a question, how come that you never make sure when Joomla update there systems that you never try out your self if your extension match the new update for Joomla, before your costumers are telling you that your extension dos not work with new joomla just something that just came to my head.. It will as I am thinking resolve allot of tickets and time for everyone

Hello Tom,

Sorry for the late reply. Please download the file here and replace it at

JOOMLA/libraries/joomla/table/table.php

This is a temporary fix. Please backup the original table.php file.

I have to admit this is an oversight on our part :P We were quite swamped and kinda missed the Joomla 3.2 release. We apologise for the inconvenience caused here.

Thanks!

Thanks for the quick fix Adelene..

Hello Robert,

You are most welcome. Glad that your issue is solved.

Thanks!

Yes thanks for the fix Adelene but I have just backup my site back to 3.1.5 I do wait to I am sure that all my extension will work with joomla new update.

I think it's a responsibility of the users to wait until the developer confirms their products are x.x compatible before they upgrade. That I think is worth making clear to everyone when they buy products. I can't wait to move to Joomla 3.2 but I'm not moving until my StackIdeas SuperHeroes announce it's all clear

Hello Andy,

Thanks for your input here We really appreciate this. We're a little short handed this week but we'll strive to have a proper fix out within the next few weeks.

Cheers!

you are kidding me?

within the next few weeks.

surely you can do better than in the next few weeks? the next few days would be better. It seems such a small fix to take a few weeks to fix?

Hi,

Please understand that we only consist of a very small team and as much as we strive to do everything we can, we only have 3 developers on hand to handle 4 huge components on our hand.

As Andy said, we haven't confirmed our status with J3.2, and as with every new update, there are always unexpected changes that we need to take time to explore and understand what changes are applied.

The fix applied here is a quick fix, and of course we can just release 1 quick fix to the public now, but I am sure users wouldn't want to be bothered with daily updates if we were to include 1 quick fix and release it on a daily basis. Hence, we need time to actually test it out with J3.2, to ensure that our component works.

I'm sorry Jason I wasn't trying to be insolent I was merely pointing out that something that seems relatively easy to fix shouldn't take weeks to provide a universal fix for, but should be days, as this is in my opinion, is quite an important glitch (joomla 3.2 not working)

On the other hand it might be worth placing somewhere on the Stack Ideas site (blog etc) that your components are not quite Joomla 3.2 ready and customers should hold off updating to it until your components are ready!

As well, Joomla states quite clearly on their recommended upgrade path that as long as your extensions are Joomla 3 series compatible then it should be fine to upgrade. Now I appreciate that there can and normally will be small glitches, that all being said the Joomla 3.2 update has been in Beta for a while and you guys should have tested your components out with it. Even just to find out if all is ok or otherwise and to inform your members of any compatibility issues. AND THEN STATING QUITE CLEARLY ON YOUR WEB SITE OR VIA AN INFO EMAIL AS TO ANY ISSUES

Hi,

Noted and I will bring this up with our marketing department.

Hey guys,

Thanks for updating us on this and like my colleagues mentioned, we are shorthanded this week. I am currently at Boston attending the Joomla world conference. We will try to update them as soon as possible

Well it's not to be rude, I have full understanding for all this. But I must also agree with Richard, and also as Jason started to pointed out don't ever going to make it as an excuse you are a small team, because people are paying for this product and can't never and will never be the costumers fault that you are in shorthanded/small team. I know it was not meant to be put in that way, but it just sounds really wrong The problem for me was last morning when I was going to work one my site there was an update for Joomla I did believe fine lets do it, then after all kind of weird error come and I was not in the end able to logout or login to my joomla site. I asked my hosting provider for help they did what they could but was not able to to anything with out put my site backup to an older date! That could have cost me allot of money but they was very nice to do this for free. So yes I was kinda a little angry at that time. Give us an update when your products are up to date with Joomla 3.2.0 so I also can update my Joomla. I like what you are providing here at Stackideas it's some nice and clean extension for Joomla. Now I wish you all a good weekend.

Thanks for the heads up on this Tom I totally agree with you here and it never has been an excuse that we are a small team. It's just that I am currently not available in the office this weekend as I am attending the Joomla World Conference in Boston currently and the stable release of 3.2 was pretty sudden which we did not paid attention to earlier (We'll definitely pay more attention to the release updates for Joomla in the future).

Thanks again everyone for the heads up on this, we appreciate all these feedback!

Mark just keep up the good work your people are doing here at Stackideas

Hello Tom,

Thanks We will do our best.

Cheers!