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"
] |
Hello dear friends, you should fix this serious problem!
KR
|
XSS Critical vulnerability {admin} account
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1424/comments
| 8 |
2021-06-03T07:10:21Z
|
2021-06-25T14:17:22Z
|
https://github.com/Piwigo/Piwigo/issues/1424
| 910,181,248 | 1,424 |
[
"Piwigo",
"Piwigo"
] |
Hello,
We recently received a vulnerability disclosure against your repository. I couldn't find an e-mail to contact or a security process to follow, so created this issue instead.
If you would like me to e-mail over the details or put them on the GitHub Issue, I'm more than happy to facilitate this for you. Otherwise, you can access the advisory [here](https://huntr.dev/bounties/1-other-Piwigo/Piwigo/).
It is private to you and the discloser of the report.
If you have any questions, let me know.
-- Jamie from huntr.dev
|
Potential Security Issue
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1423/comments
| 4 |
2021-06-01T17:58:39Z
|
2023-07-07T13:59:28Z
|
https://github.com/Piwigo/Piwigo/issues/1423
| 908,553,961 | 1,423 |
[
"Piwigo",
"Piwigo"
] |
Dear friend, please fix your query request to your parameter (no_photo_yet), from outside!
This could be a serious vulnerability!
proof: https://streamable.com/nek9tf and https://www.nu11secur1ty.com/2021/05/cve-2021-32615-new-vesion-broken.html
KR @nu11secur1ty
|
The new version is broken frontend - MySQL sending query - request to parameter (no_photo_yet) vulnerability
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1422/comments
| 4 |
2021-05-31T13:27:05Z
|
2021-06-25T14:20:35Z
|
https://github.com/Piwigo/Piwigo/issues/1422
| 907,471,790 | 1,422 |
[
"Piwigo",
"Piwigo"
] |
Related to problem described on https://piwigo.org/forum/viewtopic.php?id=28338
> More and more frequently I encounter a major performance issue with Piwigo when combining these conditions:
>
> * many photos/albums, like 100k photos and 1k albums
> * private albums or photos
> * photos are being uploaded with web upload or API
> * each photo is uploaded in a few seconds (small photos or big bandwidth)
> * visitors are active on gallery side
My current researches goes to a "lounge" where photos are added (bufferized) before being really added to their actual albums.
|
add photos to a lounge = less user cache rebuilts
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1419/comments
| 1 |
2021-05-28T08:35:23Z
|
2021-06-25T14:02:58Z
|
https://github.com/Piwigo/Piwigo/issues/1419
| 904,952,235 | 1,419 |
[
"Piwigo",
"Piwigo"
] |
As described on https://piwigo.org/forum/viewtopic.php?id=31263 some users have received security warnings when using PHP 7.4. Updating PHPMailer to version 5.2.28 seems to remove the warning.
PHPMailer 5.2.28 is the latest version of branch 5.2 but there are much more recent versions 6.x. Piwigo does not include them because it would imply increasing the minimum PHP version to 5.5 at least, or maybe 7. We can plan that for Piwigo 12 or 13.
|
Security warning on PHPMailer with PHP 7.4
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1417/comments
| 0 |
2021-05-21T12:22:09Z
|
2021-08-22T17:58:22Z
|
https://github.com/Piwigo/Piwigo/issues/1417
| 897,992,984 | 1,417 |
[
"Piwigo",
"Piwigo"
] |
This issue is for small style adjustments in the batch manager
|
[11.x Batch Manager] broken display in Unit Mode
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1416/comments
| 1 |
2021-05-21T12:06:55Z
|
2022-03-29T14:07:24Z
|
https://github.com/Piwigo/Piwigo/issues/1416
| 897,982,150 | 1,416 |
[
"Piwigo",
"Piwigo"
] |
New design for the plugin manager in 12.0 with 3 different views : Line, Compact, Classic
Classic :
Line :
Compact :
Removing page reload when activating a plugin.
|
New plugin manager redesigned
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1415/comments
| 0 |
2021-05-20T10:01:54Z
|
2021-06-23T07:39:15Z
|
https://github.com/Piwigo/Piwigo/issues/1415
| 896,579,148 | 1,415 |
[
"Piwigo",
"Piwigo"
] |
In the batch manager's single mode the area that allows to zoom in the photo takes the whole width of the page.
It needs to be reduced to the size of the photo.
|
Limit "zoom photo" area in batch manager single mode to just the photo
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1414/comments
| 0 |
2021-05-20T09:19:04Z
|
2022-03-29T14:11:49Z
|
https://github.com/Piwigo/Piwigo/issues/1414
| 896,529,399 | 1,414 |
[
"Piwigo",
"Piwigo"
] |
At the moment, to create an album, you need to reload the page. The album is created by calling the function ```create_virtual_category``` in functions.php
The objective here is to remove the reload of the page and create the new album by using Ajax calls.
|
[Album creation] Rework album creation with Ajax calls
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1413/comments
| 1 |
2021-05-14T08:50:41Z
|
2022-06-06T14:38:24Z
|
https://github.com/Piwigo/Piwigo/issues/1413
| 891,742,614 | 1,413 |
[
"Piwigo",
"Piwigo"
] |
In the plugin view selector, the view type changes after first reload when we don't do anything.
The view type is stored in the cookie ```pwg_plugin_manager_view```. In this case the cookie doesn't changes but the view does wich is not good.
The view displayed must match the cookie view type.
|
[Plugin Manager, 11.x] View selector changes after first page reload
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1412/comments
| 0 |
2021-05-14T07:01:12Z
|
2021-05-14T08:01:11Z
|
https://github.com/Piwigo/Piwigo/issues/1412
| 891,671,825 | 1,412 |
[
"Piwigo",
"Piwigo"
] |
Hi, I don't want to use apache auth to login piwigo, but the contrary.
I want to use piwigo identifiers (in piwigo_users) to identify my users in another app, by apache mysql auth.
My apache config is good, tested with another table (MD5, BCRYT or SHA), but I always get an error with piwigo idents :
`AH01617: user Chris: authentication failure for "/video": Password Mismatch`
I spent a moment on it, and found that modifying "$portable_hashes" to false did the trick.
```
--- functions_user.inc.php.orig 2021-05-03 17:59:18.044738074 +0200
+++ functions_user.inc.php 2021-05-13 22:08:51.727449387 +0200
@@ -1000,7 +1000,7 @@
// We use the portable hash feature from phpass because we can't be sure
// Piwigo runs on PHP 5.3+ (and won't run on an older version in the
// future)
- $pwg_hasher = new PasswordHash(13, true);
+ $pwg_hasher = new PasswordHash(13, false);
}
return $pwg_hasher->HashPassword($password);
```
But, it would be better to use a configuration option than modify the code, of course.
Is there a way to do it ? Or is it possible to include an option in the future ?
|
piwigo and apache auth
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1411/comments
| 1 |
2021-05-13T20:28:49Z
|
2021-05-14T14:12:25Z
|
https://github.com/Piwigo/Piwigo/issues/1411
| 891,348,074 | 1,411 |
[
"Piwigo",
"Piwigo"
] |
As reported by Harry Goodman from NCC Group:
> The ‘order[0][dir]’ parameter in admin/user_list_backend.php is vulnerable to SQL injection
>
> I believe this is because of the following pieces of code:
```
68 if ( $_REQUEST['columns'][$col]["searchable"] == "true" )
69 {
70 $sOrder .= $aColumns[ $col ].' '.$_REQUEST["order"][0]["dir"].', ';
71 }
```
> I would suggest either using the check_inputs function that your application seems to rely on, or depending on how much functionality is needed, just do a check to ensure the parameter is either ASC or DESC.
>
> CVE-2021-32615
|
[11.x, user manager] SQL injection
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1410/comments
| 0 |
2021-05-13T10:37:45Z
|
2021-05-13T10:40:24Z
|
https://github.com/Piwigo/Piwigo/issues/1410
| 890,930,565 | 1,410 |
[
"Piwigo",
"Piwigo"
] |
Piwigo is very nice and can be used on smartphones without any problems, for example with the modus-theme. I use Piwigo to share photos with the whole family. A2HS would be very helpful on smartphones, especially for the older members. But apart from that, Piwigo becomes even more modern and user-friendly, also on the desktop.
Here is the description: https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Add_to_home_screen
Here's an example: https://mdn.github.io/pwa-examples/a2hs/
|
Fit Piwigo for A2HS
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1409/comments
| 0 |
2021-05-11T12:50:45Z
|
2021-05-11T12:50:45Z
|
https://github.com/Piwigo/Piwigo/issues/1409
| 887,182,543 | 1,409 |
[
"Piwigo",
"Piwigo"
] |
I sent a notification to subscribers in Admin->Users->Notification->Send to alert users about new photos. That process seems to work. My email is on the list of subscribers. I have received no mail. Mail server is configured properly, I'm able to send test mails and users have received registration messages.
I checked the error logs and saw this:
```
[Mon May 10 12:16:38.583180 2021] [:error] [pid 2288:tid 138134857471744] [client XXX.XX.X.XXX:48222] [client XXX.XX.X.XXX] ModSecurity: Rule 7da21f4d54e0 [id "932140"][file "/dh/apache2/template/etc/mod_sec3_CRS/REQUEST-932-APPLICATION-ATTACK-RCE.conf"][line "413"] - Execution error - PCRE limits exceeded (-8): (null). [hostname "redacted.ca"] [uri "/admin.php"] [unique_id "YJmGltOTuJ3a6Ui7ymKHoQAAAAE"], referer: https://redacted.ca/admin.php?page=notification_by_mail&mode=param
[Mon May 10 12:18:03.534715 2021] [:error] [pid 2095:tid 138135045023488] [client XXX.XX.X.XXX:48242] [client XXX.XX.X.XXX] ModSecurity: Rule 7da21f4d54e0 [id "932140"][file "/dh/apache2/template/etc/mod_sec3_CRS/REQUEST-932-APPLICATION-ATTACK-RCE.conf"][line "413"] - Execution error - PCRE limits exceeded (-8): (null). [hostname "redacted.ca"] [uri "/admin.php"] [unique_id "YJmG69CmbTaUzuGVfbUmrQAAAAE"], referer: https://redacted.ca/admin.php?page=notification_by_mail&mode=send
```
|
Notifications email did not appear to send
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1408/comments
| 0 |
2021-05-10T19:44:40Z
|
2021-06-29T09:11:57Z
|
https://github.com/Piwigo/Piwigo/issues/1408
| 884,965,423 | 1,408 |
[
"Piwigo",
"Piwigo"
] |
Why: JPEG XL is the future of all image formats. It is a new royalty-free image codec targeting the image quality as found on the web, providing about 60% size savings when compared to original JPEG at the same perceptual quality, while supporting modern features like HDR, animation, alpha channel, lossless JPEG recompression, lossless and progressive modes. It is based on Google's PIK and Cloudinary's FUIF, and is in the final steps of standardization with ISO.
Explanation here: https://www.slideshare.net/cloudinarymarketing/imagecon-2019-jon-sneyer
Reference implementation here: https://gitlab.com/wg1/jpeg-xl
Chromium/Chrome and Firefox's dev versions already have initial implementations, so I'm hopeful that this will start becoming available within months.
Imagemagick already supports jpegxl, and I filed a [request in gd](https://github.com/libgd/libgd/issues/699).
I think it would be worthwhile for Piwigo to prepare for this. Once it is supported across browsers (see https://caniuse.com/jpegxl particularly its "notes" tab) I believe it should be the default public-facing format for Piwigo.
It can even losslessly recompress existing JPEG images (though in the case of Piwigo, assuming it keeps the `uploads/` folder's contents as standard behavior, it doesn't have to, it could probably get even better-optimized results by re-generating all the sizes in `_data/i/` from the `uploads` folder to do it "cleanly").
Currently my piwigo uploads/ folder weighs 1.6 gigabytes and the corresponding _data/i/ folder weighs 1.4 GB. I would look forward to that data folder shrinking to 400-700 MB...
|
Use JPEG XL for generated multiple sizes (lighter than JPEG)
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1407/comments
| 10 |
2021-05-08T13:27:22Z
|
2024-04-05T09:05:49Z
|
https://github.com/Piwigo/Piwigo/issues/1407
| 880,823,341 | 1,407 |
[
"Piwigo",
"Piwigo"
] |
adding to this forum topic:
https://piwigo.org/forum/viewtopic.php?id=31229
It seems that on some cases Piwigo goes mad and tries to do like 1.5MB mysql query (included in the attachment.)
when the url is like
https://-filtered-/picture.php?/478517
or
https://-filtered-/picture.php?/478517/categories
The picture even HAS CATEGORY, but when someone tampers with the URL and removes it there from there...
it's a 7zip file, not a zip, because github doesn't allow to upload .7z, but 7z file was like 126k, whereas actual zip was 532k.
[dafuq.7z.zip](https://github.com/Piwigo/Piwigo/files/6444037/dafuq.7z.zip)
It's like serious DDOS vulnerability in Piwigo 11.4.x
And then when someone lets a crawler bot / script loose into this url that just starts "clicking" the next and previous arrow urls under there it's like game over for the site. It just kills MySQL, 100% CPU usage for hours;
When it was accidental or something, then restarting mysql service helps to stop this, until next bot comes along. Or even site own admin browsers prefetch or whatever.
|
excessive mysqld usage on big piwigo instances
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1406/comments
| 9 |
2021-05-07T20:11:41Z
|
2022-03-29T14:04:04Z
|
https://github.com/Piwigo/Piwigo/issues/1406
| 879,667,899 | 1,406 |
[
"Piwigo",
"Piwigo"
] |
When creating a user in the user manager, you can't connect with it.
The user is saved in db.
|
[Create User] Creating a user in the User Manager page doesn't work
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1405/comments
| 3 |
2021-05-07T10:05:57Z
|
2021-05-12T08:34:30Z
|
https://github.com/Piwigo/Piwigo/issues/1405
| 878,713,284 | 1,405 |
[
"Piwigo",
"Piwigo"
] |
:hover on edit username and change password in dark mode should be removed
|
[Dark Mode] littles fixes in edit User popIn
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1404/comments
| 1 |
2021-05-07T09:18:09Z
|
2021-05-12T08:37:40Z
|
https://github.com/Piwigo/Piwigo/issues/1404
| 878,651,857 | 1,404 |
[
"Piwigo",
"Piwigo"
] |
default user must not be in the associate user list
|
[Group Manager] Remove "guest" from "Associate user" list
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1403/comments
| 0 |
2021-05-07T08:16:45Z
|
2022-03-29T14:02:06Z
|
https://github.com/Piwigo/Piwigo/issues/1403
| 878,593,023 | 1,403 |
[
"Piwigo",
"Piwigo"
] |
Dark mode css needs to be added to the edit user popIn.
|
[Dark Mode] User Manager's popIn isn't done in dark mode
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1402/comments
| 1 |
2021-05-07T08:03:03Z
|
2021-05-12T08:38:16Z
|
https://github.com/Piwigo/Piwigo/issues/1402
| 878,581,561 | 1,402 |
[
"Piwigo",
"Piwigo"
] |
Currently the User manager in dark mode look like this :
DarkMode needs to be added on user lines/cards and on some buttons and in the advanced filter box.
|
[User Manager] DarkMode for user manager isn't done
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1401/comments
| 1 |
2021-05-06T12:51:16Z
|
2021-05-12T08:38:53Z
|
https://github.com/Piwigo/Piwigo/issues/1401
| 877,463,747 | 1,401 |
[
"Piwigo",
"Piwigo"
] |
The dark mode for the view selector in Plugin Manager, Album Manager, User Manager isn't properly made.
Need to add the colors in themes.css files so it is the same for all view selectors.
|
[ViewSelector] DarkMode theme needs to be added
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1400/comments
| 0 |
2021-05-06T12:28:09Z
|
2021-05-13T12:09:31Z
|
https://github.com/Piwigo/Piwigo/issues/1400
| 877,443,788 | 1,400 |
[
"Piwigo",
"Piwigo"
] |
When searching in albums if the number of albums you have is small the search will be fin but if you have 30k + albums, searching through them take too much time that is why we try to limit the number of albums displayed in the search results
|
[Album Search] Limit search results to 100 albums
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1399/comments
| 0 |
2021-05-06T08:07:06Z
|
2021-05-13T12:09:14Z
|
https://github.com/Piwigo/Piwigo/issues/1399
| 877,205,634 | 1,399 |
[
"Piwigo",
"Piwigo"
] |
Make the vertical '...' smaller.
|
[Plugin Manager] Size of drop down menu icon is too big
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1398/comments
| 0 |
2021-05-06T07:16:50Z
|
2021-05-13T12:09:58Z
|
https://github.com/Piwigo/Piwigo/issues/1398
| 877,163,761 | 1,398 |
[
"Piwigo",
"Piwigo"
] |
If a user is deactivated (status set to "guest") then her (or his) sessions should all be deleted.
|
deactivating a user should terminate her sessions
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1397/comments
| 0 |
2021-05-05T15:02:06Z
|
2021-05-05T15:06:48Z
|
https://github.com/Piwigo/Piwigo/issues/1397
| 876,547,003 | 1,397 |
[
"Piwigo",
"Piwigo"
] |
Need to add translation lines in album move page
|
[Album Move] Translation lines needs to be added for translation
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1396/comments
| 0 |
2021-05-05T13:46:25Z
|
2021-05-13T12:10:25Z
|
https://github.com/Piwigo/Piwigo/issues/1396
| 876,469,471 | 1,396 |
[
"Piwigo",
"Piwigo"
] |
Add new translation line to display good error message when group name field is empty.
|
[Group Manager] Displaying wrong message when group name field is empty
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1395/comments
| 0 |
2021-05-05T13:17:54Z
|
2021-05-13T12:10:47Z
|
https://github.com/Piwigo/Piwigo/issues/1395
| 876,441,341 | 1,395 |
[
"Piwigo",
"Piwigo"
] |
Need to get the focus on the input when adding an album.
|
[Group Manager] Focus problem when adding an album
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1394/comments
| 0 |
2021-05-05T12:05:38Z
|
2021-05-13T12:11:21Z
|
https://github.com/Piwigo/Piwigo/issues/1394
| 876,379,391 | 1,394 |
[
"Piwigo",
"Piwigo"
] |
If the album name or the path to album is too long, the title is messing.
The objective is too make text-ellipsis to the left and see the last item of the path
|
[Album search] Title size is not good when path/title is too long
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1393/comments
| 0 |
2021-05-05T11:20:47Z
|
2021-05-05T11:36:53Z
|
https://github.com/Piwigo/Piwigo/issues/1393
| 876,345,390 | 1,393 |
[
"Piwigo",
"Piwigo"
] |
As described on https://piwigo.org/forum/viewtopic.php?id=31187 we have a performance issue when Piwigo tries to find related albums of a "too big" set of photos. Indeed if a tag is associated to 10k photos and you open the page of the this tag, then Piwigo has to find related albums for these 10k photos. The resulting SQL queries are huge and slow.
They are also useless since you will probably find that "all" albums are related albums. Making the "related albums" menu the exact same as the "albums" menu.
For me, the solution comes in 2 steps:
1. do not try to find related albums if the current set is "too big"
2. only display heaviest related albums (just like we do for tags)
|
related albums, performance issues
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1392/comments
| 0 |
2021-05-04T15:16:35Z
|
2021-05-13T12:12:22Z
|
https://github.com/Piwigo/Piwigo/issues/1392
| 875,568,874 | 1,392 |
[
"Piwigo",
"Piwigo"
] |
I get PHP Notice: Trying to access array offset on value of type bool in .../album_notification.php on line 142
while sending notification from an album to a user
Linux/Gentoo
piwigo 11.4.0
php-7.4.16
mysql-8.0.23
|
PHP Notice: Trying to access array offset on value of type bool in album_notification.php on line 142
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1391/comments
| 0 |
2021-05-03T19:52:50Z
|
2023-08-02T10:32:41Z
|
https://github.com/Piwigo/Piwigo/issues/1391
| 874,860,204 | 1,391 |
[
"Piwigo",
"Piwigo"
] |
The "Photos sort order" edit view for albums is not paginated.
Hence, when you try to modify an album with a large amount of pictures (in my case, ~32K), it just doesn't work. You can wait until the page ends loading or timeouts but this is a terrible experience and, so far, I've not managed to even change the custom sort setting and save.
|
Paginate Admin > Albums > Manage > <Album> > Edit > Photos sort order
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1390/comments
| 0 |
2021-05-03T12:32:49Z
|
2021-05-03T12:32:49Z
|
https://github.com/Piwigo/Piwigo/issues/1390
| 874,532,933 | 1,390 |
[
"Piwigo",
"Piwigo"
] |
Somehow we got an undeletable (because can't open "edit page" where the delete button is) zombie album.
Any help how to get rid of it?
Piwigo 11.4.0
When I try to "Visit the gallery" from admin, I get:
URL: /index.php?/category/60460
```
<pre><br />
<b>Warning</b>: [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 7
SELECT
id, name, permalink, nb_images, global_rank,
date_last, max_date_last, count_images, count_categories
FROM categories INNER JOIN user_cache_categories
ON id = cat_id and user_id = 51
WHERE
(id_uppercat is NULL OR id_uppercat IN ())
; in <b>/var/www/html/galerii/include/dblayer/functions_mysqli.inc.php</b> on line <b>864</b><br />
</pre><br />
<b>Fatal error</b>: Uncaught Error: Call to a member function fetch_assoc() on boolean in /var/www/html/galerii/include/dblayer/functions_mysqli.inc.php:228
Stack trace:
#0 /var/www/html/galerii/include/functions_category.inc.php(106): pwg_db_fetch_assoc(false)
#1 /var/www/html/galerii/include/menubar.inc.php(98): get_categories_menu()
#2 /var/www/html/galerii/include/menubar.inc.php(15): initialize_menu()
#3 /var/www/html/galerii/index.php(103): include('/var/www/html/g...')
#4 {main}
thrown in <b>/var/www/html/galerii/include/dblayer/functions_mysqli.inc.php</b> on line <b>228</b><br />
```
When I click edit on it in admin.php I get:
URL: /admin.php?page=album-60460
```
<pre><br />
<b>Warning</b>: [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
DISTINCT(image_id)
FROM image_category
WHERE category_id IN ()
; in <b>/var/www/html/galerii/include/dblayer/functions_mysqli.inc.php</b> on line <b>864</b><br />
</pre><br />
<b>Fatal error</b>: Uncaught Error: Call to a member function fetch_assoc() on boolean in /var/www/html/galerii/include/dblayer/functions_mysqli.inc.php:925
Stack trace:
#0 /var/www/html/galerii/admin/cat_modify.php(199): query2array('\nSELECT\n DIS...', NULL, 'image_id')
#1 /var/www/html/galerii/admin/album.php(60): include('/var/www/html/g...')
#2 /var/www/html/galerii/admin.php(298): include('/var/www/html/g...')
#3 {main}
thrown in <b>/var/www/html/galerii/include/dblayer/functions_mysqli.inc.php</b> on line <b>925</b><br />
```
|
zombie album (category with NULL uppercats)
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1389/comments
| 6 |
2021-04-30T17:40:24Z
|
2021-05-11T12:58:02Z
|
https://github.com/Piwigo/Piwigo/issues/1389
| 872,950,434 | 1,389 |
[
"Piwigo",
"Piwigo"
] |
Need to make the max-width of the album name bigger si that longer album names are displayed correctly.
Issue is also present in Albums -> Manage.
Link to forum-> : https://piwigo.org/forum/viewtopic.php?id=31218
|
Album name max-length is too short in Album -> Move
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1388/comments
| 0 |
2021-04-30T07:14:15Z
|
2021-05-13T12:12:04Z
|
https://github.com/Piwigo/Piwigo/issues/1388
| 872,102,009 | 1,388 |
[
"Piwigo",
"Piwigo"
] |
When dragging an Album to reorder it, If you go over an album that has sub-albums, It will drop-down the sub-albums list.
If you have few sub-albums this is OK but when you have 50+ sub-albums it becomes pretty annoying.
Objective : Prevent albums from opening when dragging other albums over them.
|
[Album move] prevent auto-opening while drag & drop
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1387/comments
| 0 |
2021-04-28T09:30:52Z
|
2021-05-13T12:13:34Z
|
https://github.com/Piwigo/Piwigo/issues/1387
| 869,739,300 | 1,387 |
[
"Piwigo",
"Piwigo"
] |
Hi,
i use Piwigo 11.4 on AWS behind a firewall and a ALB Loadbalancer. If a upload a image, i get a html 504 error. The reason is, that after the upload piwigo tries in the function fetchRemote to reach the file via curl or fopen. But the url is only available from outside of the firewall and not from inside from the server. So i see SYN_SENT packets and after a timeout, the apache sends a html 504 error code.
If i deactivate the curl and fopen check, it seems to working perfect.
Now i have some questions and it would be great, if someone has a hint for me:
1. Is there a recommendation for using Piwigo behind a firewall and load balancer?
2. Is there a configuration to deactivate the curl and fopen check?
3. Is it safe to deactivate the curl and fopen check?
4. Is there a way to configure the server url? So that not the firewall address but the internal address is used for the checks?
Thank you very much.
Best regards, Holger Koch
Piwigo 11.4.0
Operating system: Amazon Linux 2
PHP: 7.2.34 (Show info) [2021-04-21 07:10:20]
MySQL: 8.0.20 [2021-04-21 07:10:20]
Graphics Library: External ImageMagick 6.9.10-68
|
Piwigo 11.4 behind a Loadbalancer: Image Upload fails, because fetchRemote tries to reach external IP
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1386/comments
| 1 |
2021-04-21T07:40:45Z
|
2021-06-09T11:35:20Z
|
https://github.com/Piwigo/Piwigo/issues/1386
| 863,546,239 | 1,386 |
[
"Piwigo",
"Piwigo"
] |
I attempted to move an image from one folder to another from piwigo. An error message flashes up for less than a second. I made a video and paused it to type the error below: (Text in {}'s intentionally omitted by me. Odd newline placement as displayed.)
```Notice
: Undefined index: move in
{path to domain}/piwigo/admin/batch_manager_global.phpon line
201
Warning
: Cannot modify header information - headers already sent by (output started at {path to domain}/piwigo/admin/batch_manager_global.php:201)in
{path to domain}/piwigo/include/page_header.php
on line
94
```
This looks like the same problem as https://piwigo.org/forum/viewtopic.php?id=26773 from 2016 (probably version 2.8.0. Line 197)
As I am getting a similar message. I am hesitant to just edit the php code as indicated in that post, since that is a 5 year old problem (we're not the only ones to move images I assume) and I am not that familiar with php. Assuming this edit "fixes" it, wouldn't it just break again at the next update?
Environment details: (Running on a dreamhost server)
Piwigo 11.4.0
Operating system: Linux
PHP: 7.2.34 (Show info) [2021-04-11 18:44:30]
MySQL: 5.7.29-log [2021-04-11 18:44:35]
Graphics Library: ImageMagick 6.9.7-4
|
Unable to move image to another album
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1383/comments
| 0 |
2021-04-13T22:55:28Z
|
2021-04-13T22:55:28Z
|
https://github.com/Piwigo/Piwigo/issues/1383
| 857,379,099 | 1,383 |
[
"Piwigo",
"Piwigo"
] |
In Piwigo 2.7 we introduced a browser-side localStorage cache for lists of tags/albums/users/groups. It works fine **BUT** the LocalStorage is limited in size. Once you have reached, let's say... 10k albums, then your list of albums in administration listboxes become empty and forms are broken.
The solution to manually edit the browser configuration to increase LocalStorage cache is fine as a temporary fix, but cannot be considered as valid on the long run.
The most obvious solution I see is to simply avoid LocalStorage beyond a limit of albums/tags/users/groups. It means Piwigo will have to download the full list, but it will work.
|
fallback when localstorage is full
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1382/comments
| 2 |
2021-04-13T17:23:28Z
|
2021-05-13T12:14:03Z
|
https://github.com/Piwigo/Piwigo/issues/1382
| 857,170,638 | 1,382 |
[
"Piwigo",
"Piwigo"
] |
To make a better solution than the one implemented for #1380 we should calculate the number of photos that would become orphan if the album was deleted only if the administrator asks for deletion. Because it's totally useless 99% of the time, when you just want to display the album edition page.
|
album deletion, calculate potential orphans only when relevant
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1381/comments
| 0 |
2021-04-13T17:18:50Z
|
2021-07-28T14:52:51Z
|
https://github.com/Piwigo/Piwigo/issues/1381
| 857,167,378 | 1,381 |
[
"Piwigo",
"Piwigo"
] |
Following #972 and b29ab344e9d727f483613f244d11e8971cb03df1 it seems the 30k threshold is a bit high. For example, on a low energy CPU server on Piwigo.com, an album containing 19k photos made the SQL query run for a huge 98 seconds.
Let's lower the limit to 1k. The pure PHP solution remains fine.
Actually, this calculation (of the number of photos that would become orphan if the album was deleted) should be done **only** if the administrator asks for deletion. Totally useless 99% of the time.
|
album edition, timeout
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1380/comments
| 0 |
2021-04-13T07:52:26Z
|
2021-05-13T12:11:02Z
|
https://github.com/Piwigo/Piwigo/issues/1380
| 856,687,183 | 1,380 |
[
"Piwigo",
"Piwigo"
] |
In Group Management of Piwigo 11.4.0, the drop-down menu allowing to "Duplicate", "Delete" and "Set as a group for new users" is not presented in Safari 14.1 as can be seen in the below screenshot:
<img width="1006" alt="Screenshot 2021-04-09 at 20 37 59" src="https://user-images.githubusercontent.com/7103032/114226782-58342300-9974-11eb-8742-b6c059c2360f.PNG">
What is expected is shown below with Firefox 87.0 on the same computer:
<img width="754" alt="Screenshot 2021-04-09 at 20 37 45" src="https://user-images.githubusercontent.com/7103032/114226660-2458fd80-9974-11eb-92da-3fd79a064c07.PNG">
|
Drop-down menu of a group not visible with Safari
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1379/comments
| 3 |
2021-04-09T18:49:10Z
|
2023-10-11T09:33:16Z
|
https://github.com/Piwigo/Piwigo/issues/1379
| 854,771,960 | 1,379 |
[
"Piwigo",
"Piwigo"
] |
Creating tab in user manager to see activity logs.
Adding API methods and page design.
|
Activity tab in user manager
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1378/comments
| 0 |
2021-04-08T11:50:30Z
|
2021-06-22T16:24:01Z
|
https://github.com/Piwigo/Piwigo/issues/1378
| 853,390,757 | 1,378 |
[
"Piwigo",
"Piwigo"
] |
Problem -> https://fr.piwigo.org/forum/viewtopic.php?pid=232243#p232243
Choosing album when moving or associating causes problem when there is a lot of albums.
Styling not done correctly.
Adding placeholder and style to make it easier to understand
|
Associating / Move to album in batch manager
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1377/comments
| 0 |
2021-04-07T11:58:28Z
|
2021-05-13T12:08:57Z
|
https://github.com/Piwigo/Piwigo/issues/1377
| 852,332,565 | 1,377 |
[
"Piwigo",
"Piwigo"
] |
Thank you for Piwigo, it is an immensely useful program!
When I upgraded to version 11, I disabled the video.js plugin because it was listed as incompatible. Things looked great with the native player. However, the next time I ran a local synchronization... all my movies disappeared from the library! (The underlying files were still there.) I realized that video.js is mandatory for indexing videos, so I reinstalled it, run the synchronization again, and got my video albums back. Except now all their album thumbnails are gone. :-/
It would be worth avoiding the dependency on an incompatible addon. Here are some ideas to prevent the various effects of this dependency.
- [ ] Upgrade the video.js plugin and mark it as compatible so that people will be less tempted to remove it.
- [ ] Warn users who want to remove video.js that it is critical and that its removal will cause all videos to disappear from the library.
- [ ] Warn people who want to synchronize the library, and who have videos in that library, and who are lacking video.js, that they are about to lose all their videos from the library.
- [ ] Store the album thumbnails even if the underlying album is gone from the library. It seems like other info, like the album name, was preserved when I recovered my video albums.
- [ ] Better yet, bring video indexing / thumbnailing into the Piwigo core. Video.js is just a web video player, so why would it be necessary for core functionality?
Sorry to request one billion changes. It costs me nothing. :-) But perhaps items 1-3 are relatively easy.
|
Clarify dependency on video.js for video albums
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1375/comments
| 1 |
2021-04-01T16:06:04Z
|
2021-04-01T16:26:52Z
|
https://github.com/Piwigo/Piwigo/issues/1375
| 848,598,586 | 1,375 |
[
"Piwigo",
"Piwigo"
] |
I'd love to have an option to disable the pagination on albums, as otherwise I'm wasting my precious screen size.
Half of my display is an empty space, still I see there next page.
|
Option to disable pagination for albums
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1374/comments
| 1 |
2021-03-31T06:47:43Z
|
2021-05-07T12:53:21Z
|
https://github.com/Piwigo/Piwigo/issues/1374
| 846,021,367 | 1,374 |
[
"Piwigo",
"Piwigo"
] |
I wanted to access my piwigo today and got greeted by this:
> Fatal error: Uncaught Error: Call to undefined function session_set_save_handler() in /usr/local/www/Piwigo/include/functions_session.inc.php:18 Stack trace:
> #0 /usr/local/www/Piwigo/include/functions.inc.php(16): include_once()
> #1 /usr/local/www/Piwigo/include/common.inc.php(98): include('/usr/local/www/...')
> #2 /usr/local/www/Piwigo/index.php(11): include_once('/usr/local/www/...')
> #3 {main} thrown in /usr/local/www/Piwigo/include/functions_session.inc.php on line 18
Can anyone help me?
> Piwigo Page: https://fotos-alexacr.eu.loclx.io/
> Piwigo is running on `TrueNAS-12.0-STABLE`
|
Error even tho Piwigo was working fine
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1373/comments
| 2 |
2021-03-27T08:48:26Z
|
2021-03-27T13:14:53Z
|
https://github.com/Piwigo/Piwigo/issues/1373
| 842,455,218 | 1,373 |
[
"Piwigo",
"Piwigo"
] |
On Piwigo 11.4.0, the group manager is broken in nl_NL language because there is line return at the beginning of a string and javascript does not like that.
|
nl_NL (Dutch/Nederlands) group manager broken
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1372/comments
| 0 |
2021-03-22T15:03:38Z
|
2021-03-22T15:11:59Z
|
https://github.com/Piwigo/Piwigo/issues/1372
| 837,807,639 | 1,372 |
[
"Piwigo",
"Piwigo"
] |
See #1361 and https://github.com/Piwigo/Piwigo/issues/1361#issuecomment-802057278
|
related albums, filter (on recent photos) is not applied
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1371/comments
| 0 |
2021-03-19T09:54:28Z
|
2022-09-12T13:19:31Z
|
https://github.com/Piwigo/Piwigo/issues/1371
| 835,775,698 | 1,371 |
[
"Piwigo",
"Piwigo"
] |
Hello,
I'm using my instance (v. 11.3.0) for the first time and I'd like to add photos, but once connected, i only have this:
An empty gallery where i can literally do nothing, not even disconnect. The only present options are about photos viewing, wich are useless for now because the gallery is empty, and the "How to" explained in the doc doesn't help me because there's no menu with the "add photos" option.
|
Can't add photos
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1370/comments
| 7 |
2021-03-19T01:27:46Z
|
2021-03-19T12:39:05Z
|
https://github.com/Piwigo/Piwigo/issues/1370
| 835,431,960 | 1,370 |
[
"Piwigo",
"Piwigo"
] |
After changing or clearing the filter, some or even all tags are marked with no photos in the pull down menu. I fixed this bug in the file:
admin/themes/default/js/tags.js
`function updatePage() {
return new Promise((resolve, reject) => {
newPage = actualPage;
dataToDisplay = tagToDisplay();
tagBoxes = $('.tag-box');
$('.pageLoad').fadeIn();;
$('.tag-box, .tag-pagination').animate({ opacity: 0 }, 500).promise().then(() => {
let displayTags = new Promise((res, rej) => {
boxToRecycle = Math.min(dataToDisplay.length, tagBoxes.length);
for (let i = 0; i < boxToRecycle; i++) {
let tag = dataToDisplay[i];
recycleTagBox($(tagBoxes[i]), tag.id, tag.name, tag.url_name, tag.counter)
}
if (dataToDisplay.length < tagBoxes.length) {
for (let j = boxToRecycle; j < tagBoxes.length; j++) {
$(tagBoxes[j]).remove();
}
} else if (dataToDisplay.length > tagBoxes.length) {
for (let j = boxToRecycle; j < dataToDisplay.length; j++) {
let tag = dataToDisplay[j];
->>> newTag = createTagBox(tag.id, tag.name, tag.url_name, tag.counter);
newTag.css('opacity', 0);
$('.tag-container').append(newTag);
setupTagbox(newTag);
}
}`
The call of function "createTagBox" missing a parameter "tag.counter"
|
[Tag Manager] incorrect number of images when filtering
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1369/comments
| 0 |
2021-03-17T19:10:36Z
|
2021-05-13T10:46:19Z
|
https://github.com/Piwigo/Piwigo/issues/1369
| 834,095,941 | 1,369 |
[
"Piwigo",
"Piwigo"
] |
The "guest" user status is supposed to be equivalent to "deactivated" user. Meaning the user still exists in the users list, but can't be used anymore.
Actually, I'm able to "silently" log in. The UI does "as if" I was not logged in, but actually I am (checked in the sessions table).
When trying to log in with a "guest" user, Piwigo should simply refuse the connection, as if the password was invalid.
|
user with status "guest" can still silently log in
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1368/comments
| 0 |
2021-03-17T13:39:11Z
|
2021-05-05T15:06:48Z
|
https://github.com/Piwigo/Piwigo/issues/1368
| 833,786,370 | 1,368 |
[
"Piwigo",
"Piwigo"
] |
As discussed on https://piwigo.org/forum/viewtopic.php?id=28338 we have a problem on high volume galleries when an upload is running and each photo is uploaded very quickly. The problem comes from the cache regeneration.
In `include/user.inc.php` we already have:
```
$user = build_user( $user['id'],
( defined('IN_ADMIN') and IN_ADMIN ) ? false : true // use cache ?
);
```
Meaning we avoided to regenerate cache if we were in the administration. That was perfectly valid when we didn't use the API to upload photos. Now that we use `pwg.images.upload` (and other methods) we skip this `IN_ADMIN` test and the cache is regenerated each time we call `ws.php`. We should replace it with something like:
```
$use_cache = true;
if (defined('IN_ADMIN') and IN_ADMIN)
{
$use_cache = false;
}
if (isset($_REQUEST['method']) and 'pwg.images.upload' == $_REQUEST['method'])
{
$use_cache = false;
}
$user = build_user( $user['id'], $use_cache);
```
|
avoid rebuilding cache during upload
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1367/comments
| 5 |
2021-03-16T17:05:25Z
|
2024-07-01T13:18:13Z
|
https://github.com/Piwigo/Piwigo/issues/1367
| 833,021,121 | 1,367 |
[
"Piwigo",
"Piwigo"
] |
Steps to reproduce:
0. log in as the non-admin user in a private webbrowser session.
0. log in as the admin user in a private webbrowser session.
1. set default album permissions to admin only
2. create new folder - pwg.categories.add - status:private
3. call pwg.categories.getList cat_id:<parent id>
4. observe new album not visible (this is correct)
5. pwg.permissions.add - group:<the non-admin user containing group>, cat_id:<the newly created album id>
7. call pwg.categories.getList cat_id:<parent id>
8. observe - album is not visible
9. log out, and log in - still no visible album
10. Add image to the new folder (accessible to all users) using the pwg.images.setInfo method.
11. observe - album still not visible to non-admin user
12. observe - album contents not visible to non-admin user if queried direct
If these steps are instead followed on the website webpages, then the album is visible to the user.
I suggest that the website webpage calls something extra when linking a photo to a folder other than that contained inside "pwg.images.setInfo".
I've spent a few hours reading through the php code but cannot find the necessary change.
I *think* the problem is that the USER_CACHE_CATEGORIES_TABLE is not being updated with a list of users who have indirect permission. I think this because of the album_notification.php file line 294 that merges direct and indirect permissions, but, maybe this is totally unrelated.
Needless to say, once the user is given explict rather than indirect permission to view the album, they can see it immediatly,
|
Piwigo 11.3.0 - user unable to view folder and contents they DO HAVE permission to view when newly created folder permissions updated and images added via webservice calls
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1366/comments
| 2 |
2021-03-15T12:34:02Z
|
2021-03-18T11:58:34Z
|
https://github.com/Piwigo/Piwigo/issues/1366
| 831,766,078 | 1,366 |
[
"Piwigo",
"Piwigo"
] |
The server(piwigo 11) is hosted on linux.
My upload_dir is set in the conf file as $conf['upload_dir'] = './upload';#
method called: pwg.images.upload
URL parameters method=pwg.images.upload&chunks=1&name=PiwigoClient_Upload_-8984915979986137847.jpg&chunk=0&pwg_token=3014efb2bb01b2b6be41c14e6de1fa32&category=1525&file=STREAM
Web Http Response:
[prepare_directory] cannot create directory "././upload/2021/03/15"
The path has ./ appended.
I'm not sure which version of "define('PHPWG_ROOT_PATH'...." is used in this instance, but every instance I found would suggest that the "./" prefix on my $conf['upload_dir'] setting is superfluous. That said, it has always worked with this incorrect setting, and indeed worked when I retried the upload.
Does it sometimes repair multiple ././ to ./ ?
|
Piwigo 11.3.0 - Error creating upload folder when attempting to upload file using webservice call pwg.images.upload
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1365/comments
| 0 |
2021-03-15T11:07:59Z
|
2021-03-15T11:07:59Z
|
https://github.com/Piwigo/Piwigo/issues/1365
| 831,698,949 | 1,365 |
[
"Piwigo",
"Piwigo"
] |
The call of TagManager not include the {$ROOT_URL}plugins/AdminTools/template/admin_style.css correctly. The webpages shows following:
The Problem is, the stylesheet of the admin_tools was not loaded. I can fix the problem as workaround, with a manual load in the admin/thmes/default/template/header.tpl file
(add the line
<link rel="stylesheet" type="text/css" href="{$ROOT_URL}plugins/AdminTools/template/admin_style.css">
).
I have test with Firefox and Chrome.
I think on both pages there is a small irregularity which causes Smarty not to correctly load the AdminTols CCS. On the other pages it works.
|
Problem with plugin AdminTools in "Tag Manager" and "Move Albums"
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1364/comments
| 5 |
2021-03-13T13:45:59Z
|
2021-05-13T12:13:06Z
|
https://github.com/Piwigo/Piwigo/issues/1364
| 830,902,417 | 1,364 |
[
"Piwigo",
"Piwigo"
] |
Hello,
I recently got this error (this happened with php 7.4 afaik).
Deprecated: Invalid characters passed for attempted conversion, these have been ignored in include/template.class.php:1024
This is because crc32 can return negative integers. According to php documentation, this happens a lot with 32 bit systems, and sometimes with 64 bit systems.
I changed the `base_convert` call to `base_convert(hash("crc32b", $compile_id), 16, 36)`, and this fixes the problem. Unless I'm mistaken this should be equivalent to the current code.
Sorry I'm too lazy too submit a PR for a one-liner.
|
Deprecated: Invalid characters passed for attempted conversion, these have been ignored in include/template.class.php:1024
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1363/comments
| 10 |
2021-03-10T19:42:01Z
|
2022-07-22T21:45:42Z
|
https://github.com/Piwigo/Piwigo/issues/1363
| 828,245,606 | 1,363 |
[
"Piwigo",
"Piwigo"
] |
In Piwigo 11.3, when you duplicate a default group, the new group is a default group but the icon-star is not show (until full reload of the page)
|
duplicate group, default icon not shown
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1362/comments
| 0 |
2021-03-08T13:24:32Z
|
2021-05-07T14:41:55Z
|
https://github.com/Piwigo/Piwigo/issues/1362
| 824,554,451 | 1,362 |
[
"Piwigo",
"Piwigo"
] |
when on an album or a photo that appears in several albums including private albums to which the current user does not have access, the name of these albums is displayed and active in the "related albums" menu .
The related album menu should not show album names to which the current user have no access.
This poses a double problem for me:
- security / confidentiality : a user or an anonymous visitor does not have to know the existence or the name of private albums to which he does not have access
- ergonomics and use since, obviously, if I click on the name of this inaccessible album, I have nothing in my search, since I cross with an album which I do not do not have access to and I am afraid this will be very confusing for an unsuspecting user.
piwigo 11.3.0
|
related albums shows forbidden albums
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1361/comments
| 17 |
2021-03-08T08:26:18Z
|
2021-03-19T09:54:37Z
|
https://github.com/Piwigo/Piwigo/issues/1361
| 824,313,325 | 1,361 |
[
"Piwigo",
"Piwigo"
] |
Hello,
I recently upgrade piwigo and then I uploaded a few photos to a new album I created. When viewing the album in gallery view the photos weren't showing just a broken link was showing. The broken link for one of the photos was this:
vinny_and_steve_ski_002-xl.JPG
Using WinSCP (FTP client) I browsed to the file location and sure enough this file was not there.
So I then went to batch manage and attempted to generate a "XL - extra large" but I get the error "1 photos can not be regenerated". Interestingly, the generate image option works just fine if I try to generate a "M - medium" photo.
Any help on how to fix this would be greatly appreciated.
Thanks, Paul
|
XL photos can not be regenerated
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1360/comments
| 0 |
2021-03-07T17:20:14Z
|
2021-03-07T17:20:24Z
|
https://github.com/Piwigo/Piwigo/issues/1360
| 823,968,696 | 1,360 |
[
"Piwigo",
"Piwigo"
] |
Description of problem:
You have got a galleries directory tree with hidden folders and files.
```
galleries/folder/file.jpg
galleries/folder/._file.jpg
galleries/folder/.hidden.jpg
galleries/folder/.hide/it.jpg
```
https://piwigo.org/forum/viewtopic.php?pid=179889
https://piwigo.org/forum/viewtopic.php?pid=180115
Excluding hidden files can be done with editing $conf['sync_chars_regex'], but this may make synchronization display a lot of Error messages.
Could Piwigo update process be slightly changed ?
|
Improvment: Could Piwigo silently exclude *nix hidden files ?
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1359/comments
| 1 |
2021-03-06T08:26:50Z
|
2021-03-06T15:05:42Z
|
https://github.com/Piwigo/Piwigo/issues/1359
| 823,595,525 | 1,359 |
[
"Piwigo",
"Piwigo"
] |
ie the automatic call to `pwg.extensions.checkUpdates`
|
[dashboard] ability to deactivate search for updates
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1358/comments
| 0 |
2021-03-05T11:09:36Z
|
2021-03-05T11:21:38Z
|
https://github.com/Piwigo/Piwigo/issues/1358
| 822,985,567 | 1,358 |
[
"Piwigo",
"Piwigo"
] |
On this example, it's written "Sunday ..." on the column of Monday. It's certainly a Monday actually, but the tooltip says otherwise.
|
[Dashboard] activity chart, 1 day offset
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1357/comments
| 0 |
2021-03-05T09:32:48Z
|
2021-03-05T10:28:59Z
|
https://github.com/Piwigo/Piwigo/issues/1357
| 822,914,241 | 1,357 |
[
"Piwigo",
"Piwigo"
] |
When the `uploadAsync`extension is installed on Piwigo 2.x or when using Piwigo 11.x, Community users cannot upload photos with third party apps like the iOS app. The server replies "Admin status is required".
This issue may have some relation with the issue #1344?
|
[BUG] Community users cannot upload photos with uploadAsync
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1356/comments
| 4 |
2021-03-03T18:02:20Z
|
2021-10-07T13:02:02Z
|
https://github.com/Piwigo/Piwigo/issues/1356
| 821,351,620 | 1,356 |
[
"Piwigo",
"Piwigo"
] |
Coding alternative view for plugin manager and switch between the views available.
|
[11.x] Alternative view for the plugin manager
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1355/comments
| 1 |
2021-03-03T09:03:54Z
|
2021-03-18T14:44:50Z
|
https://github.com/Piwigo/Piwigo/issues/1355
| 820,902,915 | 1,355 |
[
"Piwigo",
"Piwigo"
] |
while they should be "photo". The check on extension should be case insensitive.
|
[11.x] storage calculation error, JPG files considered as "other"
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1354/comments
| 1 |
2021-03-02T09:59:23Z
|
2021-03-05T16:07:12Z
|
https://github.com/Piwigo/Piwigo/issues/1354
| 819,852,794 | 1,354 |
[
"Piwigo",
"Piwigo"
] |
Hi,
when adding an accentuated char 'é' in permitted characters, you can import directories and files with this char. Great.
```
// permitted characters for files/directories during synchronization
$conf['sync_chars_regex'] = '/^[a-zéA-Z0-9-_.]+$/';
```
There is a remaining problem when this accentuated char is the first one in the name of a directory, because this makes this directory to be imported as a new one everytimes you sync.
The problem is coming from PHP basename function, which depends on locale, and maybe on the system itself. I thought this problem was a poor utf8 support.
https://github.com/Piwigo/Piwigo/blob/1233694048c47910432c3c29b81338fed73516c5/admin/site_update.php#L236
My workaround was simply to replace it with that function, declared before the loop:
```
function my_utf8_simili_basename($path, $suffix='') {
$tab = explode('/', rtrim($path, '/'));
return end($tab);
}
```
_NB: As $suffix is not handled, one may found a much better basename replacement._
|
leading accentuated char in directory name
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1353/comments
| 2 |
2021-03-02T09:57:54Z
|
2021-03-02T11:34:06Z
|
https://github.com/Piwigo/Piwigo/issues/1353
| 819,851,570 | 1,353 |
[
"Piwigo",
"Piwigo"
] |
1. Login with admin or users can set the language;
2. Send the following payload and follow redirect:
db user :http://xxx/admin.php?page=languages&language=zh_CN%27%20or%20updatexml(1%2Cconcat(0x7e%2C(user()))%2C0)%20or%20%27&action=activate
db version:http://127.0.0.1/admin.php?page=languages&language=zh_CN%27%20or%20updatexml(1%2Cconcat(0x7e%2C(version()))%2C0)%20or%20%27&action=activate
|
SQL injection in settings-language in version 11.3.0
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1352/comments
| 0 |
2021-03-01T11:44:16Z
|
2021-03-08T13:59:50Z
|
https://github.com/Piwigo/Piwigo/issues/1352
| 818,783,675 | 1,352 |
[
"Piwigo",
"Piwigo"
] |
**Reproduce it**: Let's assume you want to import a new subdirectory tree in your gallery. One of your directories comes with a char space in its name.
```
./galleries/directory_02/Apples Pears/
./galleries/directory_02/Apples Pears/apple/
./galleries/directory_02/Apples Pears/pear/
```
Despite the error message after synchronization simulation, it is possible to proceed.
`[./galleries/directory_02/Apples Pears] PWG-UPDATE-1 (wrong filename)`
This directory (with space in its spelling) is then rejected (not created as an album), but its subdirectories are like becoming phantom first level albums.
**Expected**: Subdirectories must get rejected too.
**Workaround solving**: Hopefully, after removing spaces from directory names in the file system, and a synchronization, every phantoms are going away !
If many subdirectories were using the same name, in different rejected directories, several synchronizations may be needed.
**Environment**: Piwigo 11.3.0 with default conf:
```
// permitted characters for files/directories during synchronization
$conf['sync_chars_regex'] = '/^[a-zA-Z0-9-_.]+$/';
```
**Reference**: That's a bug discussed on forum: How-To and Troubleshooting » Can't synchronise directory listing
https://piwigo.org/forum/viewtopic.php?id=31088
|
sync/import directory with char space in its name, phantom albums
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1351/comments
| 0 |
2021-03-01T11:41:16Z
|
2021-03-01T11:44:05Z
|
https://github.com/Piwigo/Piwigo/issues/1351
| 818,781,412 | 1,351 |
[
"Piwigo",
"Piwigo"
] |
I'm getting this error
```
Notice: Undefined offset: 71311 in D:\piwigo\include\category_cats.inc.php on line 283
Fatal error: Uncaught Error: Call to a member function get_size() on null in D:\piwigo\themes\modus\themeconf.inc.php:278 Stack trace: #0 D:\piwigo\include\functions_plugins.inc.php(214): modus_index_category_thumbnails(Array) #1 D:\piwigo\include\category_cats.inc.php(342): trigger_change('loc_end_index_c...', Array) #2 D:\piwigo\index.php(301): include('D:\\piwigo\\inclu...') #3 {main} thrown in D:\piwigo\themes\modus\themeconf.inc.php on line 278
```
After synchronising a folder with lots of images and videos in it.
List of installed plugins:
- Admin Tools
- Batch Manager, Added By
- Color Palette
- Community
- Crop Image
- Filtre fsrmp
- jplayer
- Manage Properties Photos
- Memories
- Meta Open Graph
- Panoramas
- Permalink Generator
- PhotoSphere
- Physical Photo Move
- Presync AutoRename
- Read Metadata
- Rotate Image
- SortOrders
- stereoZoom
- Upload 1 menu
- Virtualize
|
PHP Error after uploading a lot of files
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1350/comments
| 1 |
2021-03-01T06:48:26Z
|
2021-03-21T21:03:03Z
|
https://github.com/Piwigo/Piwigo/issues/1350
| 818,538,082 | 1,350 |
[
"Piwigo",
"Piwigo"
] |
Hi, is it possible that URL protection just _does not work_?
### What I've done
- set `$conf['original_url_protection'] = 'all';`, so images (and other media) get referenced via `i.php` instead of direct links
- set `$conf['derivative_url_style'] = 2;`, so the same happens to derivatives (i.e. resized cached copies in /_data/i/)
- Protected /upload, /galleries and /_data/i with .htaccess (`Deny from all`).
- Searched the documentation
- Read the [TakeATour info](https://github.com/Piwigo/TakeATour/blob/62e395f9388a23406311646a8a131059acb219ca/language/en_GB/tour_privacy.lang.php#L62)
> <em>For Advanced Users</em><br><br>In Piwigo, you can protect the original photos using your local configuration. Use the variable $conf[\'original_url_protection\']: by default empty, you set the value to "images" to protect only the photos or "all" to protect also all type of media, which can be ressource consumming or might simply don\'t work on your server.<br><br>This option works for public and private content. This option currently requires you to deny the acces to the folders /upload and /galleries, by using an .htaccess file (usually a text file with "Deny from all" for content) or the server configurations.<br><br>Please note that filenames of photos uploaded using other method than FTP are <b>randomized</b>, so they are impossible to guess: that filename and so the path to the original photo can be known only if the visitor has access to a resized version of that photo, like the thumbnail. $conf[\'original_url_protection\'] and denying access to the folders /upload and /galleries are meant to avoid that case.
All images get now loaded through i.php and are otherwise inaccessible via direct links.
### The Problem
**But:** If a user knows a direct link, they can still access the image without logging in, share the link, or even request other variants (i.e., the -xl variant if they know only the -xs link). And is this not what the last sentence in the TakeATour text promises to solve?
I have seen [this thread](https://github.com/Piwigo/Piwigo/issues/261#issuecomment-124893435) talk about i.php checking against the users session, so users may only access files for which a link has been generated for them. However, it does not seem like any session checks are done in the current i.php whatsoever. Basically it just forwards the image with some extra steps.
Now then, what have we even gained by using the two config options? The URLs have been somewhat randomized before, and directory listing is (obviously) turned off on my server. If that is all that's happening, are we not better off just serving the images statically through the webserver?
Am I missing something? Is there some cache I have to rebuild for the new settings to take effect properly?
If not, this is not real access control, is it? Or is there anything I can do so images only ever get served to logged in users?
|
URL Protection and Access Control
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1349/comments
| 4 |
2021-02-28T17:36:13Z
|
2023-04-16T16:47:58Z
|
https://github.com/Piwigo/Piwigo/issues/1349
| 818,261,138 | 1,349 |
[
"Piwigo",
"Piwigo"
] |
videoJS isn't available for the latest version, so I've gone back to jplayer after an upgrade.
Apptempting to watch a video results in the above error at line 285. The break in question is on the line right after throwing an exception, so is never reached (which begs the question, should it be an error at all, PHP?)
Commenting the line with the break on it resolved the issue.
|
plugins/piwigo-jplayer/include/getid3/getid3.lib.php break outside of appropriate construct
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1348/comments
| 1 |
2021-02-25T20:03:30Z
|
2021-02-25T20:13:00Z
|
https://github.com/Piwigo/Piwigo/issues/1348
| 816,751,370 | 1,348 |
[
"Piwigo",
"Piwigo"
] |
I'm not clear what has started causing it, just creating and deleting categories all day in this folder I think.
I've tested using the /tools/ws.htm file and I fill in each field with the following values.
name: ```<doesn't matter>```
parent: ```<valid parent album id>```
comment: ```<doesn't matter>```
visible:``` false```
status: ```private```
commentable: ```false```
It appears that you can opt to either create a new PRIVATE folder under the root, OR a PUBLIC folder under any other folder.
Is this expected behaviour? If so, a response to explain would be helpful. In any case, dumping the sql to the client isn't ideal.
The other field values are irrelevant for getting this error. When I say irrelevant, I mean that it doesn't matter if you send them or not. What is important is sending either status:private AND parent: ```valid parent album id>```
```
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 '1401)
AND status = 'private'' at line 3
SELECT id
FROM piwigo_categories
WHERE id IN (,1401)
AND status = 'private'
; in /config/www/Piwigo-11.3.0/include/dblayer/functions_mysqli.inc.php on line 864
```
|
pwg.categories.add - SQL error returned to client with piwigo 11.0.3 - private folder in non-root folder
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1347/comments
| 0 |
2021-02-25T19:38:00Z
|
2021-02-25T19:40:06Z
|
https://github.com/Piwigo/Piwigo/issues/1347
| 816,734,520 | 1,347 |
[
"Piwigo",
"Piwigo"
] |
I've been reading the release notes, searched the gh issues, but this info cannot be found anywhere.
Please, tell us which PHP versions are supported by Piwigo.
There are a bunch of issues that state some error when using PHP X. But these issues are always dragged along and there's never a proper resolution that says: PHP X will be supported in release x.y.z of piwigo.
The info in the readme: `PHP 5.3 or greater (7+ recommended)` is kind of useless, since there are issues open for 7.4 and 8.
PHP 5 is EOL, so are 7.0, 7.1, an d 7.2.
Can you please list the proper PHP versions that are supported by each version of Piwigo?
Also, it's strange that Piwigo rather supports PHP versions that are EOL and most of the time has issues with the ones that are actually used by people and providers (hosters).
|
please tell us which PHP versions are supported
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1346/comments
| 7 |
2021-02-23T04:26:32Z
|
2021-02-23T17:50:27Z
|
https://github.com/Piwigo/Piwigo/issues/1346
| 814,089,368 | 1,346 |
[
"Piwigo",
"Piwigo"
] |
The version 11 displays the size of images to be uploaded in "mb" where "m" is the "milli" prefix and "b" an unknown unit.
The unit symbol for the byte is specified in IEC 80000-13, IEEE 1541 and the Metric Interchange Format as the upper-case character "B". The SI standard prefix for 1.000.000 is "M" and the megabytes unit should therefore be written "MB" in the Piwigo UI.
PS: In systems based on power of 2, the standard unit is MiB for 1.024x1.024 bytes.
|
Web upload UI not in conformance with the International System of Units
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1345/comments
| 5 |
2021-02-22T16:48:15Z
|
2024-06-16T10:23:03Z
|
https://github.com/Piwigo/Piwigo/issues/1345
| 813,673,670 | 1,345 |
[
"Piwigo",
"Piwigo"
] |
Since the version 11, adding `$conf['guest_access'] = false;` in LocalEditor prevents from uploading images with the iOS app:
- The version 2.6 of the iOS app calls the method `uploadAsync` without cookie (asynchronous ephemeral sessions).
- For each uploaded chunk, the Piwigo method `ws_isInvokeAllowed` is triggered and returns an error 401 (access denied).
|
[BUG] Cannot upload photos with uploadAsync when guest access disallowed
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1344/comments
| 0 |
2021-02-18T07:44:08Z
|
2021-03-05T16:06:36Z
|
https://github.com/Piwigo/Piwigo/issues/1344
| 810,848,036 | 1,344 |
[
"Piwigo",
"Piwigo"
] |
`pwg_query` is escaping 'groups' and 'rank' in the query, without taking into account if the word is not already in a quoted part of the query (in strings in particular).
This bug already shows up in #1292
I've also been hit by this bug with the Ldap_Login plugin.
This plugin calls `mass_updates` that calls `mass_insert` that calls `pwg_query`
Managing ldap config, it tries for example to insert the following data (from mariadb logs):
```
2021-02-15T20:53:01.691167Z 265 Query INSERT INTO `piwigo_ldap_login_config_1613422381676754`
(`param`,`value`)
VALUES
[...]
, ('ld_group_basedn','cn=`groups`,dc=domain,dc=tld')
[...]
```
You see the problem: the `group` in the data must not be quoted here.
I'm under the impression that the decision of escaping word in query without parsing it in detail (to avoid to quote in quoted string) is wrong.
What do you suggest? I'm thinking of various fixes:
1) changing the default behavior of `pwg_query` to avoid quoting by default
2) adding the `$escape_reserved_words` to all core functions that calls `pwg_query` (at least `mass_updates` and `mass_insert` for the Ldap_Login plugin (seems intrusive to me)
3) fixing the quoting in `pwg_query` to avoid to modify already quoted strings (probably difficult to implement)
4) removing the whole quoting stuff in `pwg_query` and fixing code that does not quote correctly its data/column names/etc (seems the good way for me)
Regards
Vincent
|
escaping 'groups' and other reserved words by default in pwg_query leads to various bugs
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1343/comments
| 7 |
2021-02-15T21:25:40Z
|
2021-08-03T17:29:32Z
|
https://github.com/Piwigo/Piwigo/issues/1343
| 808,827,497 | 1,343 |
[
"Piwigo",
"Piwigo"
] |
If your photo gallery contains 1 million photos, the current (11.3) algorithm to calculate the storage space used by each kind of files (photos/videos/formats/other) will reach memory limit.
Furthermore, there is no need to calculate the sum in the PHP. The database can do it, more efficiently.
On my test database with 960k photos, it takes 800ms to fetch all individuals photos and 4000ms to generate the whole page. With an aggregation query, the SQL takes 1700ms (that's longer) but the page generates in 3000ms (that's faster). Here is the aggregation query I used to test:
```
$query = '
SELECT
SUBSTRING_INDEX(path,".",-1) AS ext,
SUM(filesize) AS filesize
FROM `'.IMAGES_TABLE.'`
GROUP BY ext
;';
$file_extensions = query2array($query, 'ext', 'filesize');
```
Even optimized, it takes too much time in my opinion. Next step would be to cache this.
|
storage usage broken with big galleries
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1342/comments
| 1 |
2021-02-15T15:26:22Z
|
2021-03-05T09:53:10Z
|
https://github.com/Piwigo/Piwigo/issues/1342
| 808,627,955 | 1,342 |
[
"Piwigo",
"Piwigo"
] |
Hi,
thanks for providing piwigo!
## Background Info
I encountered the following issue in my piwigo installation:
I added some photos to my galleries folder and afterwards wanted to perform a quick sync.
The docker container where piwigo is running (linuxserver/piwigo) did not properly show contents of my image folder and hence it seemed empty for piwigo.
Without asking my entire picture gallery was deleted via the quick sync.
A quick restart of the docker container made the galleries folder show files again, but by that time I had to recreate my entire albums, ordering, etc. in Piwigo.
## Feature request:
* If a user clicks on "Synchronization", check, if the galleries folder is empty first: If that is the case: Show warning to user, like "Your galleries folder seems to be empty. If you proceed all your albums will be deleted. Do you want to continue?" with two options: "Yes, delete albums", "No, abort synchronization".
With that security mechanism other users don't fall into the this trap in the future.
|
Feature Request - Check empty galleries folder & show warning before executing sync
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1341/comments
| 1 |
2021-02-15T07:51:41Z
|
2021-03-08T10:54:50Z
|
https://github.com/Piwigo/Piwigo/issues/1341
| 808,281,031 | 1,341 |
[
"Piwigo",
"Piwigo"
] |
To change the number the photos per page, admin need to use a slider.
The problem with that slider is that once you get over 50 you only can chose 60, 70, 80.
What if I want to set 75? How if I want to set 120 or 150?
Please allow admin to set a custom number of photos per page like a input text box, like you allow for albums per page.
|
please allow custom number of pictures per page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1340/comments
| 4 |
2021-02-14T20:18:31Z
|
2023-12-06T12:06:23Z
|
https://github.com/Piwigo/Piwigo/issues/1340
| 808,038,564 | 1,340 |
[
"Piwigo",
"Piwigo"
] |
I have a 2560x1440 pixels display set on 100% magnification.
I installed Piwigo.
I let the default settings, factory defaults:
- theme: default (modus)
- the thumbs: default (square)
- square thumbs size: default (120x120 pixels)
- number of pictures per page: default (15)
Then uploaded 100 pictures in one album.
When I go to see how the pictures look, I see this:
For comparation when I enter on Flickr the interface look like this:
There is something very wrong with Piwigo default settings.
Problem 1) That screen filling is a lot too small - Piwigo problem
In my opinion the default theme should use a interface optimized for most common screens 1920x1080 pixels, while mobile optimized themes should use a recalculated pagination (example: half the number of pictures per page of the default for desktop screen).
Problem 2) Pagination navigator fonts and visibility is bad - Modus problem
My suggestion to fix the problem is:
-More bigger font size for pages navigator
-Put a border square around the selected page number (a css border?), to make it more visible. Now it's using only italic fonts
|
please optimize default interface of Piwigo for 1920x1080 screens
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1339/comments
| 5 |
2021-02-14T20:08:40Z
|
2021-02-24T10:12:44Z
|
https://github.com/Piwigo/Piwigo/issues/1339
| 808,036,541 | 1,339 |
[
"Piwigo",
"Piwigo"
] |
Hi,
I don't find how to launch the sync without going on the admin UI, but just with a command I could put in the crontab.
Thanks,
Claire.
|
Launching a synchronization in command line
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1338/comments
| 2 |
2021-02-12T23:21:18Z
|
2022-02-11T06:37:49Z
|
https://github.com/Piwigo/Piwigo/issues/1338
| 807,609,633 | 1,338 |
[
"Piwigo",
"Piwigo"
] |
Hi,
I have been thinking it could be nice to have some kind of tag filtering mechanism when viewing an album in Piwigo.
In the sidebar we already have the "Related tags" section, however by clicking those tags, we will then see all pictures with that tag.
It would be nice to be able to apply that action on the current album instead.
Also, it would be very nice to not just only see pictures with a given tag e,g "Nature", however also be able to exclude tags. So if you have an album with nature and family pictures, you could view both sets by either "Including" the nature tag, or "Excluding" the nature tag.
I have been thinking that the the design could be simmilar to the "Related tags" section, like it has the "+" sign in front of a tag.
"+Tag" would include pictures with that tag
"-Tag" would exclude pictures with that tag
All of this could also just be an extention to the search feature in Piwigo if that would be simpler.
|
Filter album (Feature request)
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1337/comments
| 1 |
2021-02-11T18:29:26Z
|
2023-11-14T15:03:46Z
|
https://github.com/Piwigo/Piwigo/issues/1337
| 806,637,435 | 1,337 |
[
"Piwigo",
"Piwigo"
] |
Coding of alternate views for the album manager.
|
[11.x] Alternative view for the album manager
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1336/comments
| 0 |
2021-02-10T08:23:32Z
|
2021-03-05T16:06:00Z
|
https://github.com/Piwigo/Piwigo/issues/1336
| 805,289,126 | 1,336 |
[
"Piwigo",
"Piwigo"
] |
Hello,
I'm running my Piwigo installation with a lot of useful plugins. On my sandbox installation, I already upgraded to 11.3.0. The upgrade went smooth and I started activating my plugins. Some of them are marked as not compatible, but they seem to work.
I would like to know how Piwigo checks which plugins are compatible and which are not. Is there a file in every plugin that lists the versions of Piwigo that are supported?
Please give me a hint .... :-)
Merci beaucoup!
Thanks and best regards
Jens
|
Compatibility check for Plugins
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1335/comments
| 2 |
2021-02-08T17:36:48Z
|
2021-02-09T20:31:40Z
|
https://github.com/Piwigo/Piwigo/issues/1335
| 803,778,960 | 1,335 |
[
"Piwigo",
"Piwigo"
] |
Hello,
I was in the process of manual installation of Piwigo version 11.3.0 on PHP 5.3.29, MYSQL 5.5.62, Apache 2.2.34. However after successful manual installation when I visit inside the admin panel i.e :
Users->Groups->Add Group and enter group name and click on 'Add' button, group isn't added and following is thrown in Apache error logs:
`
PHP Parse error: syntax error, unexpected '[' in /{{PATH}}/{{TO}}/{{PIWIGO}}/include/ws_functions/pwg.groups.php on line 362`
Could you please replicate this at your end and fix this?.
I checked on another server with PHP 5.4 and adding groups works there.
Also documentation shows that PHP 5.3 is the minimum required version for Piwigo
https://piwigo.org/doc/doku.php?id=user_documentation:learn:install:before
Are the minimum PHP requirements for installing Piwigo changed?.
|
Piwigo version 11.3.0 throws syntax error while adding 'Groups' on PHP 5.3
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1334/comments
| 3 |
2021-02-08T12:19:11Z
|
2021-03-22T12:13:25Z
|
https://github.com/Piwigo/Piwigo/issues/1334
| 803,511,440 | 1,334 |
[
"Piwigo",
"Piwigo"
] |
Hello,
my gallery uses a lot of keywords or tags to navigate through the collection of pictures. When I click on one of the tags in the tags cloud, I get a view which is similar to an album view. The main difference between this view and the display of an album is that there is no description available for the pictures matching the selected keyword. Would it be possible to add a description to the tag in the tag manager and display this discription similar to the album discription?
I know that there would be a workaround using smart albums, but then I have to deal with extra albums, extra permissioning etc.
Best regards and keep up the great work!
Jens
|
Keyword / Tag description compared to Album description
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1333/comments
| 0 |
2021-02-07T12:48:49Z
|
2021-02-07T12:48:49Z
|
https://github.com/Piwigo/Piwigo/issues/1333
| 802,944,864 | 1,333 |
[
"Piwigo",
"Piwigo"
] |
For example:
`for ($i=0; $i<count($page['chronology_date']); $i++)`
This means on each loop, we call and recount count($page['chronology_date']).
For performance reasons we could do this:
`for ($i=0, $pagecount = count($page['chronology_date']); $i<$pagecount; $i++)`
|
Loops optimization
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1331/comments
| 2 |
2021-02-06T18:12:34Z
|
2021-02-07T18:03:58Z
|
https://github.com/Piwigo/Piwigo/issues/1331
| 802,756,716 | 1,331 |
[
"Piwigo",
"Piwigo"
] |
We can improve performance on some things:
- We are using in_array in some parts, when we are just hardcoding one element. Replace with just === is faster and compatible.
- We are using `in_array($variable, array_keys($array))` when we could use array_key_exists(). This improves performance and is compatible.
|
Array functions optimization
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1328/comments
| 0 |
2021-02-06T17:49:45Z
|
2021-02-06T17:49:45Z
|
https://github.com/Piwigo/Piwigo/issues/1328
| 802,752,275 | 1,328 |
[
"Piwigo",
"Piwigo"
] |
Replacing calls to array_push() function with $arr[] = $new is compatible but will improve performance. This change would not break anything.
|
Replace array_push() function call with $arr[] = $add code style.
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1326/comments
| 0 |
2021-02-06T17:32:57Z
|
2021-02-06T17:45:51Z
|
https://github.com/Piwigo/Piwigo/issues/1326
| 802,749,155 | 1,326 |
[
"Piwigo",
"Piwigo"
] |
On the photo property page there is a block with the following text : "Posted the 4 August 2016"
It should be "Posted on August 4th, 2016"
|
international date formats
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1325/comments
| 10 |
2021-02-06T11:03:07Z
|
2024-07-15T08:21:42Z
|
https://github.com/Piwigo/Piwigo/issues/1325
| 802,674,014 | 1,325 |
[
"Piwigo",
"Piwigo"
] |
It seems that all users with status {webmaster, administrator} receive the "a new version is available". Only the webmasters should.
|
only webmasters should receive/display new version availability message
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1324/comments
| 0 |
2021-02-06T08:31:47Z
|
2021-02-06T08:31:47Z
|
https://github.com/Piwigo/Piwigo/issues/1324
| 802,644,959 | 1,324 |
[
"Piwigo",
"Piwigo"
] |
When moving A/A1 to the root of the gallery, I think `pwg.categories.move` and `pwg.categories.setRank` are called in parallel. That's a problem because `setRank` relies on the current list of albums in the same parent album. The JS code must wait for the response of `pwg.categories.move` before calling `pwg.categories.setRank`.
Currently, it generates a random result. If you have luck you will think it's fine, but another time you get an inverted rank at page reload...
|
[11.x admin/album move] wrong album rank when moving
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1323/comments
| 1 |
2021-02-05T17:32:27Z
|
2021-05-14T13:51:05Z
|
https://github.com/Piwigo/Piwigo/issues/1323
| 802,346,658 | 1,323 |
[
"Piwigo",
"Piwigo"
] |
With an old Google Chrome (version 67 I can't update) I get this error in web console:
> Uncaught SyntaxError: Unexpected token =
For common.js line 146
|
[11.x tag manager] SyntaxError: Unexpected token =
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1322/comments
| 0 |
2021-02-05T10:32:41Z
|
2021-02-05T10:37:02Z
|
https://github.com/Piwigo/Piwigo/issues/1322
| 802,049,944 | 1,322 |
[
"Piwigo",
"Piwigo"
] |
From version 11.0.0 the search for keywords in the keyword manager is no longer possible. The reason for this is a missing "toLowerCase" in the JavaScript function isDataSearched in the file admin/default/js/tags.js
My fixed version:
function isDataSearched(tagObj) {
let name = tagObj.name.toLowerCase();
let stringSearch = $("#search-tag .search-input").val();
if (name.includes(stringSearch.toLowerCase())) {
return true;
} else {
return false;
}
}
I also use the includes function instead of the startWith function. This means that the search pattern is also searched for within the keyword. Find that personally more comfortable.
|
Search in Keyword Manager not working
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1320/comments
| 2 |
2021-02-04T16:22:09Z
|
2021-02-05T08:54:57Z
|
https://github.com/Piwigo/Piwigo/issues/1320
| 801,436,416 | 1,320 |
[
"Piwigo",
"Piwigo"
] |
Moving a sub-album on the top of the album list works graphically but the change isn't saved after page reload.
Similar thing when moving a sub-album at the bottom of the list, on page reload it comes back on top of the list (2nd place).
This bug seem to appear only when moving sub-albums, moving albums this way works.
|
[11.x] Moving sub album at the beginning/end of the list
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1319/comments
| 0 |
2021-02-04T13:43:05Z
|
2021-02-05T17:00:43Z
|
https://github.com/Piwigo/Piwigo/issues/1319
| 801,294,923 | 1,319 |
[
"Piwigo",
"Piwigo"
] |
when you click on any numbers (20, 50, 100, all) to change the display, when your page is refreshing the number's display disappear and you have to go back if you wan't them to appear
<img width="960" alt="bug numéros d'affichage" src="https://user-images.githubusercontent.com/65904580/106737877-86655180-6617-11eb-9a8e-e748383f962d.PNG">
|
bug on the number's display on the batch manager
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1318/comments
| 0 |
2021-02-03T11:02:00Z
|
2021-02-03T11:02:00Z
|
https://github.com/Piwigo/Piwigo/issues/1318
| 800,218,513 | 1,318 |
[
"Piwigo",
"Piwigo"
] |
Despite #1300 we have received several reports, see https://fr.piwigo.org/forum/viewtopic.php?pid=231642#p231642 that show the calculation of `_data` directory size takes far too long on some filesystems. This piece of information is absolutely not important enough to deserve such a performance failure. Let's remove it (and make it come back later, see #1316)
|
[11.x] remove cache directory size calculation from dashboard
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1317/comments
| 0 |
2021-02-02T20:37:47Z
|
2021-02-05T09:12:48Z
|
https://github.com/Piwigo/Piwigo/issues/1317
| 799,665,060 | 1,317 |
[
"Piwigo",
"Piwigo"
] |
Instead of displaying cache size on dashboard, which has lead to numerous performance issues, it would be better to display the cache size where it matters most : on the maintenance page.
We can display it "on request only" (with an AJAX call) and display "(calculated 1 month ago)" for instance.
|
display cache size on maintenance page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1316/comments
| 0 |
2021-02-02T20:37:07Z
|
2021-07-15T07:59:44Z
|
https://github.com/Piwigo/Piwigo/issues/1316
| 799,664,498 | 1,316 |
[
"Piwigo",
"Piwigo"
] |
When using the filter in the new 11.x tag manager, it's not possible to find a tag which starts with an uppercase. "pasta" can be found, but not "Pasta".
|
[11.x admin/tags] filter does not work with uppercase
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1315/comments
| 0 |
2021-02-02T20:28:52Z
|
2021-02-06T09:50:00Z
|
https://github.com/Piwigo/Piwigo/issues/1315
| 799,657,674 | 1,315 |
[
"Piwigo",
"Piwigo"
] |
When you confirm you want the orphan tags to be deleted, you get no success message (while the code seems to be designed for it)
|
[11.x, tag manager] missing success message after orphan deletion
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1314/comments
| 0 |
2021-02-02T15:13:21Z
|
2021-02-02T17:20:55Z
|
https://github.com/Piwigo/Piwigo/issues/1314
| 799,370,590 | 1,314 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.