Discuss Joomla! 3.6 Beta 2

[pe7er]

Here you can discuss about the release of Joomla 3.6 Beta 2

See Announcement: http://forum.joomla.org/viewtopic.php?f=8&t=926772

[DonnieDarko]

Hi,
I understand that the Joomla 3.6 stable will be released very soon.

Does anyone know by now if the release would contain important security patch meaning that we would be highly recommended to update from 3.5.1 asap?

I remember when there is a Joomla update release, there is always an assessment in terms of how urgent it is to update. It would be really good if someone can let me know. I am going on holiday for 2 weeks and I have to think of contingency plans if it is the case.

[mandville]

there are no security issues mentioned in the release of j3.6 see https://github.com/joomla/joomla-cms/is ... a+3.6.0%22+

any security issues in j3.5.1 would be dealt with i the j3.5. branch

[DonnieDarko]

Thank you Mandville, that makes sense.

[deleted user]

Even if there were security patches scheduled for 3.6, news of that wouldn't get out beyond a very small circle of people until release day for security reasons. Very rarely has a pre-announcement gone out regarding that, and when it does, it's usually for a major issue.

There might be a minor security patch included in the stable release. There might not be. Depends on what types of security reports have been received and the types of patches the security team is working on. But if there were anything critical a 3.5.2 release would have gone out with that patch had an issue been reported by now and that would presumably still be the case if such a major issue were reported relatively soon.

[rogereric]

In the version of Joomla 3.6.0 Beta 2 does not work the method

$user =JFactory::getUser();
$user->get('isRoot')

When Super User is logged the method does not return the value true.

Regards

[deleted user]

Relevant mailing list discussion - https://groups.google.com/d/topic/jooml ... discussion

Long and short, don't rely on that protected property to give you the information you need. It cannot be relied upon until at least one check to JUser::authorise() has been completed and data has been cached.

You should use JUser::authorise('core.admin') instead to consistently check if a user is a root user.