@zuluu8 please try an default template to make sure that it is not a template issue.

Please confim that you use the last version of the template. If it work with the default template please contact your template provider ;)

Thanks.

@zero-24 i´m using the last version of the template, in fact is the default template of Gantry 5 (hydrogen template)

At gantry website told me i should explain this problem in this forum.

thank you.

Great that you found it can you close here than? Thanks.

@zero-24 i haven´t found the solution, please, what can i do?

At gantry website told me i should explain this problem in this forum.

this is no forum this is a issue tracker for bugs in the core system of Joomla ;) The forum is at forum.joomla.org

@zero-24 ok, i´m sorry i didn´t know it is a issue tracker, but an user of Gantry support send me this URL to explain the problem...

what can i do please? in the forum.joomla.org i posted the problem but users told me somebody broke something in the last version of joomla...

thanks.

i should finish this problem this week to finish my job :(

I can't see any response that told you it is a problem with the core: http://forum.joomla.org/viewtopic.php?f=737&t=916009&p=3383413

I have just installed joomla-pkg_gantry5_v5.2.13.zip and joomla-tpl_g5_hydrogen_v5.2.13.zip. I can't see any logo that return a error 500.

At gantry website told me i should explain this problem in this forum.

What gantry webseite?

This is not an issue for the tracker

@zero-24 so, what do you think is the problem please?

Behaviour of JURI::base(true); changed, which is fully described in issue #9554 which were then fixed in #9575.

JUri behavior did NOT change. The system SEF plugin previously dealt with
scenarios where the href attribute was completely empty, doesn't in 3.5.0,
and does again in 3.5.1.

On Wednesday, March 30, 2016, Matias Griese notifications@github.com
wrote:

Behaviour of JURI::base(true); changed, which is fully described in issue
#9554 #9554 which were then
fixed in #9575 #9575.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#9667 (comment)

Thanks @mbabker, I'm seeing the issue now. :)