plegall
e62f90fe4c
issue #420 , remove pLoader from list of applications
2017-03-06 15:32:02 +01:00
plegall
4d800292c2
fixes #178 , hide menu identification on identification page
...
+ redirect to gallery root when opening idenfication page while identified
2017-03-02 14:25:01 +01:00
plegall
c594112746
fixes #424 , update mdetect.php to version 2015.05.13
2017-03-02 11:15:52 +01:00
plegall
812892e6be
next version is 2.9.0beta2
2017-01-28 19:52:47 +01:00
plegall
309b2f4476
feature #606 , check pwg_token and display error (if any)
2017-01-24 17:29:28 +01:00
plegall
3466c432e1
feature #606 , backend API method pwg.images.deleteOrphans
...
This method will delete a block of orphans and return the number of remaining orphans.
2017-01-24 15:09:52 +01:00
modus75
828bb42ce3
Fix quick search (in php 0=='' but 0!=='') !!!
2017-01-13 21:22:20 +01:00
modus75
37fc55e6b6
issue 593 - batch manager block deletion; simpler php code + exact progress feed back ...
2017-01-10 21:24:25 +01:00
plegall
bf5b50c979
Merge branch 'feature/593-delete-by-blocks'
2017-01-10 16:15:11 +01:00
plegall
743bbb61f4
feature #593 , simplify detailed output for pwg.images.delete
2017-01-09 14:33:26 +01:00
Thomas Kuther
c2b456ba0f
fix PHPMailer smtp class loading when using SMTP transport (['smtp_host'] set) ( #599 )
2017-01-04 14:30:03 +01:00
Thomas Kuther
beee647b74
update PHPMailer to 5.2.21 ( #595 )
2016-12-29 16:09:39 +01:00
Thomas Kuther
d94e9b6cde
update PHPMailer to 5.2.19 ( #594 )
2016-12-27 15:29:16 +01:00
plegall
e6e7465b9d
fixes #593 , delete by blocks of 100 photos, with a progress bar
2016-12-26 23:24:29 +01:00
modus75
af3472324b
fixes #586 session_start() error with PHP 7.1 Windows/IIS10
2016-12-26 17:23:01 +01:00
modus75
9b6ec85f09
Merge branch 'master' of https://github.com/Piwigo/Piwigo
2016-12-09 22:01:41 +01:00
modus75
25e2954490
fixes #563 quick search filter, wrong limits on upper range limit
2016-12-09 21:59:34 +01:00
plegall
a4bb90c2e4
feature #416 , return a structured list
...
... instead of string with comma separated values
2016-12-09 09:49:26 +01:00
modus75
0a90a68915
fixes #563 quick search filter, wrong limits on upper range limit
2016-12-08 22:14:37 +01:00
plegall
5c8528afec
fixes #416 , returns available_sizes in pwg.session.getStatus
2016-12-06 19:28:22 +01:00
plegall
102e0f0608
Merge branch 'jeremydurand-bug/403-configuration-new-album-position'
2016-12-05 15:36:50 +01:00
plegall
90a0e8c26c
fixes #512 , set session garbage collector probability
2016-12-03 20:07:14 +01:00
plegall
a2e6a2670a
Merge branch 'feature/optimize-history'
2016-11-25 18:38:56 +01:00
plegall
e43d48f296
Merge branch '2.8'
2016-11-21 15:22:27 +01:00
plegall
906f8d57b8
fixes #306 , operator precedence issue in load_language
2016-11-21 15:20:36 +01:00
plegall
419bb72802
feature #370 , details on config setting
2016-11-21 15:01:43 +01:00
plegall
eef8a27f5e
feature #370 , automatic purge on history
2016-11-21 12:13:21 +01:00
plegall
5fb18eda36
feature #509 summarize history more often
...
Every 1000 log entry inserted, Piwigo performs an history summarize.
The summarize process has also been optimized: no longer used column
history.summarized (no longer need to update it, which took a lot in time),
we now save the history_id_from and history_id_to in history_summary table.
This way we know from where to start on next summarize.
For now, for a simple performance reason, we keep column history.summarized,
because removing it may take a long time on huge tables. Once we will have
automatic purge on history, it will be safer to drop this column.
2016-11-18 15:08:03 +01:00
Marc Poulhiès
e35a560759
fix single_insert when a field is null ( #477 )
...
fix #449
Signed-off-by: Marc Poulhiès <dkm@kataplop.net >
2016-11-17 14:26:46 +01:00
Marc Poulhiès
9b9ec600ea
fix single_insert when a field is null ( #477 )
...
fix #449
Signed-off-by: Marc Poulhiès <dkm@kataplop.net >
2016-11-17 14:20:50 +01:00
plegall
dde2426bbf
Merge branch '2.8'
2016-11-17 14:14:16 +01:00
plegall
9a93d1f44b
fixes #548 , escape HTML chars from search expression
...
before sending them to HTML comment on frontend
2016-11-17 14:10:27 +01:00
plegall
b3157cbfd8
fixes #547 , strong checks on url format
2016-11-17 13:43:40 +01:00
plegall
a9fa61adfe
Merge branch '2.8'
2016-10-20 10:43:41 +02:00
plegall
25d2305839
fixes #542 , do not always use browser language on register
2016-10-20 10:14:28 +02:00
Matthew Petroff
7fcfc33d04
Fix typos in default config file comments. ( #540 )
2016-10-15 11:12:08 +02:00
plegall
4e24768989
fixes #533 , add a "messages" box (blue colorscheme)
2016-10-06 11:46:42 +02:00
plegall
843ccb89c1
Merge branch '2.8'
2016-08-29 14:15:12 +02:00
plegall
a09d6e0623
Merge branch 'bug/376-mysql-5.7-order_by' into 2.8
2016-08-29 14:14:35 +02:00
plegall
10da5801ef
next version is 2.8.3
2016-08-29 13:55:03 +02:00
plegall
78bf53f45a
typo fixed in comment
2016-07-26 16:02:01 +02:00
plegall
b87094ac2f
fixes #376 , remove option ONLY_FULL_GROUP_BY in sql_mode
...
based on solution provided by Mercury_LABBS on piwigo.org forums
2016-07-26 15:54:22 +02:00
plegall
374f341d0b
next release is 2.8.2
2016-07-07 18:27:11 +02:00
plegall
ee737aeed7
Merge branch '2.8'
2016-07-07 18:22:22 +02:00
plegall
1f0e95c22c
bug #476 , set http code to 401 only when not redirecting
2016-07-05 12:17:28 +02:00
plegall
724befb35d
feature #478 , improve performances
...
By reducing frequency of update on user_infos.last_visit. Instead of updating
on each page visit, we wait at least a session length, which is 30 minutes by
default.
@modus75 suggested to use function log_user instead, which is a better design.
Unfortunately it would lead to much less accuracy, because on many systems PHP
sessions are never purged (Debian with default settings). It would be possible
to come back everyday and never update the last_visit, as long as the web
browser is not closed.
2016-07-04 15:47:02 +02:00
jeremydurand
ba940dd503
fixes #403 configuration of new album position
2016-06-13 17:37:55 +02:00
plegall
4560e2d824
fixes #478 , add new column user_infos.last_visit
...
This will speed up user edit popin opening, by avoiding to search in history for the last user visit.
The column user_infos.last_visit_from_history true/false says if the last_visit has already been search in history (to avoid making it twice). I could have implemented the search of last_visit for all users in the migration task 149 but in case of many users and long history, it would have taken years to execute...
2016-05-31 16:00:03 +02:00
plegall
db0e02b5d4
fixes #476 , in case of guest_access=false, redirect_http instead of redirect_html
2016-05-30 10:53:29 +02:00
plegall
bd0d2ae645
Merge branch '2.8'
2016-05-13 11:05:15 +02:00
