Discuss Joomla! 2.5.18 Released

[pe7er]

Here you can discuss about the release of Joomla 2.5.18.
See Announcement: http://forum.joomla.org/viewtopic.php?f=8&t=834692

[leolam]

We have a corrupt installer

I am sorry but i get on 4 different Joomla 2.5.17 sites when choosing the update to J2.5.18

"The Archive file is corrupted, truncated or archive parts are missing"

Direct download from url: "Unable to open archive"

Leo

[abernyte]

I get the same result with J3.2 upgrade on three different sites too.

[naimless]

Hi - quick question, just saw phpass, which looks interesting. Is phpass automatically used in 2.5.18 or is there no way yet to migrate existing 2.5 user table to phpass hashing?

[Morthraine]

I've tried the update using the 2.5.x release and the 2.5.17 release to 18. Neither works and I get the error message:

JFolder::create: Could not create directory Path: /home/proear
Warning: Failed to move file!

I'm using Bluehost and the domain is www.miracellproear.com. This is a subdomain of the main domain, calmear.com. The full path for the installation is /home3/calmearc/public_html/miracellproeart. This is the first time I've had a Joomla upgrade not work.

[deleted user]

Hi - quick question, just saw phpass, which looks interesting. Is phpass automatically used in 2.5.18 or is there no way yet to migrate existing 2.5 user table to phpass hashing?

As users log into your updated site, their passwords will be rehashed from the legacy method to a PHPass hash. No action required on the site admin's part.

[abqsue]

I upgraded to 2.5.18 yesterday and now no one can log into the site. Any ideas what might be causing this?

I rolled the site back to 2.5.17, and it seems to be working better.

When I used 2.5.18, I could log in once, but the second time I tried it told me Wrong username or password. I'd request a new password, and could log in once, again, but not a second time.

[ExSpirit]

I have just updated my Joomla to 2.5.18 (from 2.5.17) and my code for checking if password is correct or not no longer works. This is what I had and worked at 2.5.17:

Code: Select all

$user = "myname";
$password = "mypass";
$db->setQuery("SELECT username, password FROM #__users ".
  "WHERE username = '$user'");
if ($result = $db->loadObject()) {
	$parts = explode(':', $result->password);
	$crypt = $parts[0];
	$salt = $parts[1];
	$testcrypt = JUserHelper::getCryptedPassword($password, $salt);
	if ($crypt == $testcrypt) {
		echo "Correct password for this user";
	} else {
		echo "Wrong password";
	}
} else echo "Wrong user";

I noticed in release notes "the enhanced password hashing via PHPass", and I think this is the reason. How can I disable this new password hashing or modify my code to work?

[nicol]

Hello,

I upgraded three live sites from 2.5.17 to 2.5.18 and now users can't login. I'm using CiviCRM and the CiviAuthentication Plugin https://github.com/lcdservices/CiviCRM-CiviAuthenticate

I've taken a look at the plugin to see what needs updating to handle Joomla's changes to password handling, but I cannot find this documented anywhere. Indeed when I check here - which I checked before upgrading - http://developer.joomla.org/version-2-5 ... notes.html - I can't see any mention of the shift to PHPass.

Any suggestions about what to change would be appreciated - I think the defunct code is around line 70 or 85 here - https://github.com/lcdservices/CiviCRM- ... ivicrm.php

I appreciate the Joomla team improving security but I'm a bit stuck now (am not a PHP dev), have done other upgrades on top so can't really roll back.

Thanks
Nic

[deleted user]

I don't see any immediate issues with CiviCRM's code you've linked to; it's properly using the API and not doing any custom handling of the password data.

[deleted user]

I have just updated my Joomla to 2.5.18 (from 2.5.17) and my code for checking if password is correct or not no longer works. This is what I had and worked at 2.5.17:

Code: Select all

$user = "myname";
$password = "mypass";
$db->setQuery("SELECT username, password FROM #__users ".
  "WHERE username = '$user'");
if ($result = $db->loadObject()) {
	$parts = explode(':', $result->password);
	$crypt = $parts[0];
	$salt = $parts[1];
	$testcrypt = JUserHelper::getCryptedPassword($password, $salt);
	if ($crypt == $testcrypt) {
		echo "Correct password for this user";
	} else {
		echo "Wrong password";
	}
} else echo "Wrong user";

I noticed in release notes "the enhanced password hashing via PHPass", and I think this is the reason. How can I disable this new password hashing or modify my code to work?

You should not be directly querying the database to check the password. You can pass the data to JUserHelper::verifyPassword() as of 2.5.18 and 3.2.1 to handle this.

[nicol]

Just a little update for anyone coming here with the same CiviCRM problem - or looking for possible fixes to authentication handling: Brian Shaugnessey of LCD Services has updated his plugin so it works with 2.5.18. More info at http://forum.civicrm.org/index.php/topic,31593.0.html - and details of the changes - https://github.com/lcdservices/CiviCRM- ... e94b11b8db

[abqsue]

I upgraded to 2.5.18 yesterday and now no one can log into the site. Any ideas what might be causing this?

I rolled the site back to 2.5.17, and it seems to be working better.

When I used 2.5.18, I could log in once, but the second time I tried it told me Wrong username or password. I'd request a new password, and could log in once, again, but not a second time.

For me, the issue appears to have been Community Builder. They have put out a new update (1.9.1), which fixed the problems I was having (YAY!)

[GavinErickson]

I'm getting lots of reports the past few days (following update 2.5.17->2.5.18) from people who haven't logged in for a while, and then request a password reset - the reset password never works. When i reset from the backend, the password works.

any ideas?

thanks,

Gavin

[abqsue]

I'm getting lots of reports the past few days (following update 2.5.17->2.5.18) from people who haven't logged in for a while, and then request a password reset - the reset password never works. When i reset from the backend, the password works.

any ideas?

thanks,

Gavin

Do you have a login/registration module other than the core Joomla one?

[GavinErickson]

Looks like i am using the community builder 1.9.1

[abqsue]

Looks like i am using the community builder 1.9.1

Even though CB 1.9.1 fixed the problems I had, the Joomla update left a bunch of mangled passwords behind. It seemed that anyone who had tried to log on (I'm guessing on this - it appeared that those who had not touched their password were okay) during the period before I upgraded CB had to have his/her password reset. But once reset, it was fine. And once CB was upgraded, no additional members had their passwords mangled.

[GavinErickson]

Cheers - I have a slightly different problem in that people can login fine. Those that have forgotten passwords are the problem - there seems to be some problem in sending a new password. Makes me think that the password reset in CB is still using the old hashing technique. (or whatever has changed) But i guess this does point to CB. I'll run a test to the standard module to check.

thanks,

Gavin

[GavinErickson]

My issue turned out to be down to using the jfusion authentication plugin. once i deactivated that and turned on joomla authentication, then the system generated password reminders worked fine.

[teichfeld]

Hello,

I updated my joomla 2.5.18, but rolled it back (by removing the files on disk) because I did not want to deploy quite yet. However, my admin panel still says 2.5.18. Im guessing this comes from the database. How can I get this to show the true 2.5.17 installation (files) again, so when I want to update to 2.5.18 I can ?

Thanks much,
-TImothy

[abqsue]

Hello,

I updated my joomla 2.5.18, but rolled it back (by removing the files on disk) because I did not want to deploy quite yet. However, my admin panel still says 2.5.18. Im guessing this comes from the database. How can I get this to show the true 2.5.17 installation (files) again, so when I want to update to 2.5.18 I can ?

Thanks much,
-TImothy

Timothy - I'm by no means an expert, but did you try reinstalling version 17?