piwigo - copy of piwigo repo

	Commit message (Collapse)	Author	Files	Lines
2011-08-24	feature 2027 implemented: the "lost password" feature was rewritten.	plegall	1	-0/+1
	The algorithm is highly inspired from WordPress : 1) in a single field, you give a username or an email 2) Piwigo sends an email with the activation key 3) the user clicks on the link in the email (with the activation key) and is able to set a new password The "lost password" feature is no longer limited to "classic" users: administrators and webmasters can use it too (no need to tell webmasters that they can only change their password in the database) git-svn-id: http://piwigo.org/svn/trunk@11992 68402e56-0260-453c-a942-63ccdbb3a9ee
2011-08-02	rename #images.average_rate to rating_score	rvelices	1	-2/+2
	git-svn-id: http://piwigo.org/svn/trunk@11893 68402e56-0260-453c-a942-63ccdbb3a9ee
2011-04-09	bug:2224 one parameter for change thumnails number (needs some translations)	mistic100	1	-2/+1
	git-svn-id: http://piwigo.org/svn/trunk@10198 68402e56-0260-453c-a942-63ccdbb3a9ee
2011-04-08	bug:1791 display hd dimensions instead of websize dimensions	mistic100	1	-0/+2
	git-svn-id: http://piwigo.org/svn/trunk@10157 68402e56-0260-453c-a942-63ccdbb3a9ee
2011-01-20	bug 937 fixed: makes sure a user won't see the thumbnail of a photo that has a	plegall	1	-0/+1
	higher privacy level than user privacy level. For an acceptable solution at performance level, I have implemented a cache: for a given user, each album has a representative_picture_id. This cache also avoids to perform numerous "order by rand()" SQL queries which is the case when $conf['allow_random_representative'] = true; git-svn-id: http://piwigo.org/svn/trunk@8802 68402e56-0260-453c-a942-63ccdbb3a9ee
2011-01-13	feature 2108 added: user upload removed from core. It will come back as a	plegall	1	-20/+0
	"new generation" user upload in the Community plugin. git-svn-id: http://piwigo.org/svn/trunk@8651 68402e56-0260-453c-a942-63ccdbb3a9ee
2011-01-04	feature 2095 added: new column images.added_by (foreign key on users.id)	plegall	1	-0/+1
	git-svn-id: http://piwigo.org/svn/trunk@8464 68402e56-0260-453c-a942-63ccdbb3a9ee
2010-12-14	feature 2060: Remove adviser from db structure.	patdenice	1	-1/+0
	Remove adviser from user_list page and some db queries. git-svn-id: http://piwigo.org/svn/trunk@8131 68402e56-0260-453c-a942-63ccdbb3a9ee
2010-05-12	SQLite cannot drop tables on cascade	nikrou	1	-1/+1
	git-svn-id: http://piwigo.org/svn/trunk@6166 68402e56-0260-453c-a942-63ccdbb3a9ee
2010-03-29	Fix some issues with database engines :	nikrou	1	-0/+13
	- insert into syntax not correct for posgresql or sqlite - add languages table - incorrect function for row count (sqlite) git-svn-id: http://piwigo.org/svn/trunk@5452 68402e56-0260-453c-a942-63ccdbb3a9ee
2010-03-19	Fix some sql issues :	nikrou	1	-0/+13
	- permalink that use if() syntax - add tables themes for other database engines that mysql git-svn-id: http://piwigo.org/svn/trunk@5192 68402e56-0260-453c-a942-63ccdbb3a9ee
2010-03-13	feature 1502: based on Dotclear model, P@t has reorganized the way Piwigo	plegall	1	-1/+1
	manages template/theme in a simpler "theme only level" architecture. It supports multiple level inheritance. git-svn-id: http://piwigo.org/svn/trunk@5123 68402e56-0260-453c-a942-63ccdbb3a9ee
2010-02-26	Feature 1459 : add support for SQLite3 via PDO	nikrou	1	-0/+0
	git-svn-id: http://piwigo.org/svn/trunk@4967 68402e56-0260-453c-a942-63ccdbb3a9ee
2010-01-28	Feature 511 : add support for sqlite database engine	nikrou	1	-191/+74
	Using session_write_close function when session handler use database because write is called after object destruction. git-svn-id: http://piwigo.org/svn/trunk@4781 68402e56-0260-453c-a942-63ccdbb3a9ee
2009-12-02	Feature 1255 :	nikrou	1	-0/+649
	- add postgres database engine - change installation process to allow postgres or mysql database git-svn-id: http://piwigo.org/svn/trunk@4410 68402e56-0260-453c-a942-63ccdbb3a9ee