Update 3.2 Fatal error: Call to a member function getTag() o

[menonuo]

I've just updated Joomla 3.1 to 3.2
Everything seems to be ok till I visit the public web page. I get this fatal error:

Fatal error: Call to a member function getTag() on a non-object in /htdocs/public/vi/libraries/cms/application/site.php on line 436

I can login to the admin site without problems and all the content is there.
Probably I am not the the only one with this issue. Actually I've already read some post about a problem with the admin site but that's not my case.
The web site was a bilingual (italian and spanish), and I had personal templates (one on each language).
Probably I need to fix something in the db or some code but I don't have much idea where to begin from.
The code below is the line 436 in the site.php file that the error calls, i don't think it will help much but ...just in case.
Thank you

Code: Select all

		if ($this->_language_filter)
		{
436			$tag = $this->getLanguage()->getTag();
		}
		else
		{
			$tag = '';
		}

		if (!$templates = $cache->get('templates0' . $tag))

Thank you.

[Evanion]

I can confirm this issue.

[voxace]

I am also having the same issue.

[qovvop]

I have also this issue, I can get it away if I deactivate the "System - Language Filter" plugin.... But If I do the multilanguage function crash... I really hope it's a solution on this...

[albertorp]

I have the same problem
Please, need urgent help!

[y_anniks]

Are there any updates?
I have the same problem.

[DavidBoggitt]

Same problem. Let's hope there's a 3.2.1 coming soon that addresses some of the issues raised. I suspect there are extension developers too that need to update some code to 3.2 compatibility.

[virnoche]

Same here! This update brakes the website to an internal server 500 error. Disabling the language filter brings it back online but this isn't right......

[DavidBoggitt]

Ok... I've solved this on my installation... I needed to update the extension 'Chameleon' to version 2-36

Dave

[kentacoder]

Hi
We have investigated somewhat around the problem. Its related to running a site in multilanguage mode having the lang switcher active and having Helix plugin activated. We get the problem as reported earlier at line 436 in libraries/cms/application/site.php .
If you change line 436 to "$tag = '';" the helix template is working OK.
It is a temporary fix.
Some debugging needed to spot the real source of the problem.

Helix plugin activated is disturbing presentation even if you have another template like Beez active.
Running site with Beez and lang switcher ( 2 languages) and deactivating Helix plugin going fine.

For now I think the problem is more in Helix than Joomla 3.2.
Hope this helps to find a solution.

Kenneth
Actionwave

[bobbus]

The problem is not only with your HELIX plugin, I'm using Falang instead and I have the same issues.
This looks more like a bug in the core language switcher of J3.2.
I only get Internal Error 500 pages when hitting the browser navigation buttons, which is still something many users are doing on websites. So I'm hoping to get this fixed soon...

[bobbus]

And yes Kenneth, simply replacing the code to what you say solves my issue too...

[willows]

Hi

we have a fix for this here.

http://www.willows-consulting.com/Jooml ... a-3-2.html

This fixes the issue where the language plugin has an error when activated.

Hope this helps folks

regards
Sean

[vianhtu]

replace "$tag = $this->getLanguage()->getTag();"
by $tag = JFactory::getLanguage()->getTag();
ok 100% working

[ramadji]

replace "$tag = $this->getLanguage()->getTag();"
by $tag = JFactory::getLanguage()->getTag();

Works great for me. Thanks Vianhtu! You rule!

[Peter Sachs]

replace "$tag = $this->getLanguage()->getTag();"
by $tag = JFactory::getLanguage()->getTag();

2.5 years later, and still your fix did the job for me. Thank you!

[tomonzo]

replace "$tag = $this->getLanguage()->getTag();"
by $tag = JFactory::getLanguage()->getTag();
ok 100% working

Yes, works 100% as promised. Thank you vianhtu!

[atomik]

replace "$tag = $this->getLanguage()->getTag();"
by $tag = JFactory::getLanguage()->getTag();
ok 100% working

THANK YOU it works for 3.3.1 as well!

[Sasa Banker]

Working like a charm

[atomik]

I am surprised, that this bug is still present in new releases. I have to repair it over and over after any upgrade

[gulp]

Found this error after the latest update and install of JoomSEF.
Just replacing

$tag = $this->getLanguage()->getTag();

is not enough,
I've replaced both the lines like:

Code: Select all

$lang_code = $this->getLanguage()->getTag();

with:

Code: Select all

$lang_code = JFactory::getLanguage()->getTag();

What should be the danger to a patch like this ?
I'm not aware of what should happens ...

[sovainfo]

Considering you are using a different getLanguage() method you might end up with the wrong tag.

[gulp]

In fact it doesn't works fine !
I hope in a good update on the next official release !

[atomik]

I've posted this question http://forum.joomla.org/viewtopic.php?f=728&t=860808 on bug reporting forum few days ago and still NO ANSWER.
Does it mean, that nobody cares?

[sovainfo]

@gulp Have you tested all scenario's? Doubt that very much, the fact you get the desired tag in one situation doesn't mean it works fine. You would need to research which tag is returned by both functions.

[gulp]

Hello,
I'm still facing this issue on J3.4.5.
I've tested each of the suggestion but none of these are working!

[gulp]

No way to solve this issue with the next release ?

[mhoerner]

I was having the same issue and when I updated to 3.4.5, the fix mentioned above didn't work either. I noticed that I was only having this issue on sites that ran JoomSEF. I submitted a support ticket with them and got the following response that fixed the issue:

We know about this problem, it is caused by the "Auto update URLs" option being enabled in JoomSEF's Configuration on the Advanced page. Just disable the option and the problem should go away.
I'm sorry for the inconvenience.

[gulp]

WWWWOOOOOOWWWWW GREAT !!
Thank you so much, you saved me
How long will still wait Artio JoomSEF to solve this issue ?

[mhoerner]

Glad it worked for you as well! Not sure why I didn't think to go straight to JoomSEF first but since the patch worked, didn't think anything of it until it didn't work.

I asked that same question as to how long until a fix would be provided and got the following response

We plan to fix this function eventually, but it is quite complicated to make it work correctly with all the options, so we'll probably remove it temporarily in next version until we manage to fix it.

Sounds like it could be a couple updates away, especially since this issue has been reported for some time now.