Hi Piwigo team,
It's time for a new release, don't you think? What we currently have:
* plugins with multiple language description
* avoid compatibility warnings with PHP 5.3
* automatic connection at the end of install
* hide categories when no photo inside
* italian/german/spanish users can subscribe to Piwigo newsletter in their own language
* fix Internet Explorer 8 (IE8) display bugs
Are we waiting for something specific or can we just say we're ready?
P@t told me it would be good this time to promote [extension by P@t] Piwigo Auto Upgrade
On my side, I know there is a problem with [extension by plg] Community + [Bugtracker] ticket 1053 (details on [Forum, post 108236 by plg in topic 15227] categories with no photo due to privacy levels), but I think I can live with this bug, it's not blocking for the release.
Offline
I'm ok , but what do you mean below ?
plg wrote:
* plugins with multiple language description
Im my mind, plugins already used l10n() to translate, no ? Or I miss your point.
Offline
mathiasm wrote:
I'm ok , but what do you mean below ?
plg wrote:
* plugins with multiple language description
Im my mind, plugins already used l10n() to translate, no ? Or I miss your point.
I added multilanguage description for plugins' admin pannel...
It's a description.txt file in each language directory.
Offline
Go ahead.
;-)
Offline
plg wrote:
It's time for a new release, don't you think? What we currently have:
* plugins with multiple language description
* avoid compatibility warnings with PHP 5.3
* automatic connection at the end of install
* hide categories when no photo inside
* italian/german/spanish users can subscribe to Piwigo newsletter in their own language
* fix Internet Explorer 8 (IE8) display bugs
Are we waiting for something specific or can we just say we're ready?
What's about [Bugtracker] ticket 1041 ?
Offline
It's ok for me...
Offline
Eric wrote:
What's about [Bugtracker] ticket 1041 ?
You have committed it on trunk. Would you like me to review this on trunk before giving a GO for merging on branch 2.0? Or did you simply forget to merge on branch 2.0? Let me know.
Offline
I don't understand this feature at all.
1 - We are on the admin side... not in public. If I have to set a password, I want to see it and I check if I am alone.
2 - It was the only way to create a second guest profile with no password. Now I can't. Password is mandatory. 2nd guest profile is used for domain filtering (a tip given by P@t).
3 - I am a specialist in IT security. On the professional side, I am building an Super Admin interface to define hundred Clients Administrators, and we have a secured office to use this interface. The password field is seen only by our Super administrator and not by anyone else. There is no reason to hide it and duplicate that one. No body else than administrator can see that one.
We must apply the 4 eyes principle (isolated creation and validation) with a such logic, we can't.
4 - I disscuss 15 days ago, with nicolas about this feature. I think it is a conceptual error to add this. Please don't merge it in branch.
We have time to arg on that.
Maybe two ways on the same screen, I don't know if it is acceptable for your case?
On one hand a "silent" creation, and in an other hand a visible "creation" (with no check on the password field).
Maybe a configuration parm to activate "silent" creation.
Again, please don't merge it in branch.
Thanks.
Offline
Other
Italian description.txt of distributed plugins are in French.
Rio could you translate them asap.
Thanks.
Offline
plg wrote:
You have committed it on trunk. Would you like me to review this on trunk before giving a GO for merging on branch 2.0? Or did you simply forget to merge on branch 2.0? Let me know.
In fact, i'ven't merge it to branch because the initial discussion about this feature wasn't fixed (VDigital and Nicolas seem to not agree this) and it's the reason of my question.
Any way, this feature is not so important to be merge right now. We can continue to discuss on it and merge (or not) after concertation, isn't it ?
Offline
Eric wrote:
Any way, this feature is not so important to be merge right now. We can continue to discuss on it and merge (or not) after concertation, isn't it ?
I agree.
And at least, Eric, offer a $conf to switch to a double password input in admin.
Like by default:
$conf['double_password_type_in_admin'] = false;
=> True is as you want it (double input + type="password").
=> False is as today (single input + type="text").
Offline
VDigital wrote:
And at least, Eric, offer a $conf to switch to a double password input in admin.
I'm OK with that. But do not delay the release of the next release so far. This is not a major feature and I don't have much free time right now to do that quickly.
Offline
In a few minutes, I'll start to build release 2.0.4.
Offline
Thanks
Offline
The newsletter engine is running :-)
http://piwigo.org/releases/2.0.4
P@t, I have tested [extension by P@t] Piwigo Auto Upgrade and it works really nice. Congratulations!
Offline