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"
] |
Original report on https://fr.piwigo.org/forum/viewtopic.php?id=29105
There are still some `$data{anything}` in profile.php. Not compatible with PHP 7.4
|
curly braces is deprecated in profile.php
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1313/comments
| 0 |
2021-02-02T13:42:43Z
|
2021-02-05T10:50:36Z
|
https://github.com/Piwigo/Piwigo/issues/1313
| 799,292,897 | 1,313 |
[
"Piwigo",
"Piwigo"
] |
admin.php?page=tags results in a broken dysfunctional page.
Both, the pagination arrows and the Display 100,200,500,1000 buttons don't work. Typing into the Filter box doesn't. Also, when selection mode is activated the All,None,Invert buttons don't do anything. Adding a keyword works, deleting does not. Editing works, but confirming spins forever until x hit but the change is accepted after. I also noticed that the left sidebar menu is spoiled (i.e. all submenus are opened at once).
In the Firefox 78.7.0esr Web Console there are these errors:
```
Uncaught TypeError: dataTags.filter is not a function
getNumberPages https://erack.net/gallery/_data/combined/1y747fn.js:151
<anonymous> https://erack.net/gallery/_data/combined/1y747fn.js:162
Uncaught TypeError: AdminTools is undefined
<anonymous> https://erack.net/gallery/admin.php?page=tags:3243
```
Firefox 84.0.2 reports even more locations of "dataTags.filter is not a function".
See also forum thread [Tags edition](https://piwigo.org/forum/viewtopic.php?id=30993).
|
Dysfunctional keywords/tags admin page in 11.2.0
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1312/comments
| 2 |
2021-02-02T13:14:49Z
|
2021-02-05T08:53:39Z
|
https://github.com/Piwigo/Piwigo/issues/1312
| 799,270,746 | 1,312 |
[
"Piwigo",
"Piwigo"
] |
On my tags page (back office), I have this JS error:
```
Uncaught TypeError: dataTags.filter is not a function
getNumberPages https://photos.loeuillet.org/_data/combined/1jg4dkm.js:151
<anonymous> https://photos.loeuillet.org/_data/combined/1jg4dkm.js:162
1jg4dkm.js:151:48
```
With this issue, I can't delete the tag.
|
Can't delete orphan tag
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1311/comments
| 4 |
2021-02-01T11:08:27Z
|
2021-02-05T08:54:20Z
|
https://github.com/Piwigo/Piwigo/issues/1311
| 798,243,950 | 1,311 |
[
"Piwigo",
"Piwigo"
] |
JShrink version 0.5.1 is included in piwigo/include/jshrink.class.php .
This is very out of date - this version was released by upstream some 6+ years ago. Version 1.5.0 was released in December 2020:
https://github.com/tedious/JShrink
This also includes some fixes that help php-8 work better and is supported by upstream. Prior to upgrading I was experiencing issues with image rendering hanging, but with this updated version and a minor tweak to piwigo/include/template.class.php to call the updated function name, I've now a functional piwigo 11.2.0 system that seems to work (with some warnings but it works nonetheless).
|
Upgrade bundled JShrink to latest upstream (1.4.0) to fix php-8 issues
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1310/comments
| 2 |
2021-02-01T01:28:19Z
|
2021-08-02T16:59:02Z
|
https://github.com/Piwigo/Piwigo/issues/1310
| 797,875,194 | 1,310 |
[
"Piwigo",
"Piwigo"
] |
It appears Piwigo currently ships with a version close to Smarty 3.1.29, based on the change_log.txt file in piwigo/include/smarty .
This is very out of date, and subsequent upstream versions have fixed many bugs including most recently a php-8 compatiblity issue which I am now running into, that was fixed in the latest 3.1.37. Version 3.1.37 is also the first upstream version where php-8 is tested.
There are also some security updates mentioned in the changelog (see version 3.1.32, and 3.1.33-dev-4, bugfix on 21.7.2017 as examples).
Can we please have an updated Smarty commited to the release code to fix these issues?
|
update Smarty (required for php-8)
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1309/comments
| 4 |
2021-01-31T23:43:28Z
|
2021-08-06T14:02:56Z
|
https://github.com/Piwigo/Piwigo/issues/1309
| 797,843,573 | 1,309 |
[
"Piwigo",
"Piwigo"
] |
The website seems disconnected from the _data folder.
Here is the error when clicking on the "Administration" link:
```Fatal error: Uncaught RuntimeException: SplFileInfo::getSize(): stat failed for /config/www/Piwigo-10.0.2/_data/_data in /config/www/Piwigo-10.0.2/admin/include/functions.php:644 Stack trace: #0 /config/www/Piwigo-10.0.2/admin/include/functions.php(644): SplFileInfo->getSize() #1 /config/www/Piwigo-10.0.2/admin/intro.php(415): get_fs_directory_size('/config/www/Piw...') #2 /config/www/Piwigo-10.0.2/admin.php(298): include('/config/www/Piw...') #3 {main} thrown in /config/www/Piwigo-10.0.2/admin/include/functions.php on line 644```
Note that it seems to be looking for the _data folder inside the _data folder so _data/_data.
|
[11.2] admin dashboard is unavailable
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1308/comments
| 2 |
2021-01-31T16:42:32Z
|
2021-02-05T09:16:35Z
|
https://github.com/Piwigo/Piwigo/issues/1308
| 797,753,924 | 1,308 |
[
"Piwigo",
"Piwigo"
] |
Original report on https://fr.piwigo.org/forum/viewtopic.php?id=29101
Name not rendered on new album move admin page + gallery menubar related albums.
|
[11.x] album name not rendered on new features
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1307/comments
| 0 |
2021-01-31T12:32:31Z
|
2021-01-31T13:00:14Z
|
https://github.com/Piwigo/Piwigo/issues/1307
| 797,700,541 | 1,307 |
[
"Piwigo",
"Piwigo"
] |
>
>
> Seems to be broken with php 8:
> ```
> [Fri Jan 29 18:24:24.149797 2021] [php:error] [pid 11906] PHP Fatal error: Uncaught Error: Call to undefined function get_magic_quotes_gpc() in /usr/share/webapps/piwigo/include/common.inc.php:20
> Stack trace:
> #0 /usr/share/webapps/piwigo/index.php(11): include_once()
> #1 {main}\n thrown in /usr/share/webapps/piwigo/include/common.inc.php on line 20
> ```
> and this function is removed since php 8: https://www.php.net/manual/en/function.get-magic-quotes-gpc.php
>
> any news upstream?
>
as reported on the AUR: https://aur.archlinux.org/packages/piwigo/#comment-788761
|
Error when running with php8
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1305/comments
| 3 |
2021-01-29T17:45:57Z
|
2022-10-25T05:38:17Z
|
https://github.com/Piwigo/Piwigo/issues/1305
| 797,067,229 | 1,305 |
[
"Piwigo",
"Piwigo"
] |
When the activity table is absolutely empty (may happen right after an upgrade from 2.9), the new dashboard shows this `undefined offset:0 line 324`
|
[11.x dashboard] Undefined offset: 0 in admin/intro.php on line 324
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1304/comments
| 0 |
2021-01-29T13:26:41Z
|
2021-01-29T13:35:37Z
|
https://github.com/Piwigo/Piwigo/issues/1304
| 796,880,808 | 1,304 |
[
"Piwigo",
"Piwigo"
] |
in the dashboard, when you refresh there is a bug on the activity peak : all the weeks are named as "week 0"
|
[11.1 dashboard] week 0
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1303/comments
| 0 |
2021-01-29T13:22:14Z
|
2021-01-29T13:34:44Z
|
https://github.com/Piwigo/Piwigo/issues/1303
| 796,877,361 | 1,303 |
[
"Piwigo",
"Piwigo"
] |
clicking on the new (11.x) filter input is a loss of time. A keyboard shortcut (like "/") would be interesting for power users (like me, who activates 10 plugins per day)
|
[Plugin Manager] keyboard shortcut for filter
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1302/comments
| 0 |
2021-01-28T15:23:24Z
|
2021-01-28T15:24:39Z
|
https://github.com/Piwigo/Piwigo/issues/1302
| 796,104,306 | 1,302 |
[
"Piwigo",
"Piwigo"
] |
When you delete photo cache sizes, the "cache" size on dashboard stay the same.
|
[11.x] cache size stay the same after sizes deletion
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1301/comments
| 0 |
2021-01-27T19:23:03Z
|
2021-01-27T19:26:34Z
|
https://github.com/Piwigo/Piwigo/issues/1301
| 795,377,921 | 1,301 |
[
"Piwigo",
"Piwigo"
] |
On some specific installations, see https://piwigo.org/forum/viewtopic.php?id=30920 and https://piwigo.org/forum/viewtopic.php?id=30933 the new "pure PHP" algorithm to calculate cache directory size, introduced by #1290 simply times out.
The fix is not good enough, need a better solution.
|
[11.1 admin/intro] new cache size calculator times out
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1300/comments
| 0 |
2021-01-27T18:44:11Z
|
2021-01-27T18:49:14Z
|
https://github.com/Piwigo/Piwigo/issues/1300
| 795,351,412 | 1,300 |
[
"Piwigo",
"Piwigo"
] |
A tooltip would be useful.
|
[11.x] plugin manager, add tooltip on unavailable settings button
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1299/comments
| 0 |
2021-01-27T18:38:50Z
|
2021-01-27T18:40:29Z
|
https://github.com/Piwigo/Piwigo/issues/1299
| 795,348,158 | 1,299 |
[
"Piwigo",
"Piwigo"
] |
The "Configuration" button should always be displayed, but inactive when there is no configuration available.
|
[11.x] incoherent buttons for theme manager
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1298/comments
| 0 |
2021-01-27T18:32:56Z
|
2021-01-29T13:38:18Z
|
https://github.com/Piwigo/Piwigo/issues/1298
| 795,344,540 | 1,298 |
[
"Piwigo",
"Piwigo"
] |
Hi,
I recently updated to version 11.1.0 and noticed that image downloads were corrupted and could not be opened.
I checked the file with a hex editor and found the problem. A PHP notice at the start of the file:
`Notice ob_clean(): failed to delete buffer. No buffer to delete in action.php on line 224`
I changed the line with an additional check, I am no PHP expert, so the solution might not be good:
However image downloads are currently working again. I am not sure if its a problem with Piwigo or my server.
Andy
|
[11.x] ob_clean(): failed to delete buffer - corrupted downloads
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1297/comments
| 3 |
2021-01-24T10:48:31Z
|
2022-10-04T08:42:40Z
|
https://github.com/Piwigo/Piwigo/issues/1297
| 792,768,557 | 1,297 |
[
"Piwigo",
"Piwigo"
] |
Hi,
I'm using Piwigo 11.1.0
I have a problem syncing IPTC tags on an updated gallery with batch manager. It pretends doing the job "Metadata synchronized from file : 12 files", but no IPTC are updated.
Workaround : it is still possible to update IPTC with:
- album sync, with meta_all checked "even already synchronized photos"; and also with
- edit single photo, sync metadata.
So I investigated with a fresh install, and the problem is confirmed. I would like "meta_all checked" like behaviour in batch manager, but is it what piwigo team wants ?
Within (piwigo)/local/config/config.inc.php there are still:
```
$conf['show_iptc'] = true;
$conf['use_iptc'] = true;
```
|
batch_manager metadata sync meta_all
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1296/comments
| 11 |
2021-01-23T16:08:52Z
|
2024-07-15T14:53:22Z
|
https://github.com/Piwigo/Piwigo/issues/1296
| 792,592,214 | 1,296 |
[
"Piwigo",
"Piwigo"
] |
In the plugins list after clicking "Show inactive plugins" and activating a new plugin, the list hides again.
I think it should stay visible.
Actually I don't see the point on hiding inactive plugins in the first place, at least my "preference" could be store in localStorage.
|
[UX] Do not hide Inactive plugins after activating a new one
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1295/comments
| 1 |
2021-01-23T08:56:24Z
|
2021-01-28T14:29:37Z
|
https://github.com/Piwigo/Piwigo/issues/1295
| 792,511,648 | 1,295 |
[
"Piwigo",
"Piwigo"
] |
With the versionning change, Piwigo 11.0.0 will try to download 11.0.x_to_11.1.0.zip instead of 11.x_to_11.1.0.zip. We need to slightly change the download code generator, to generate 11.x_to_11.2.0.zip, 11.x_to_11.3.0.zip... for the upcoming versions.
Of course, we will still have to deal with a 11.0.0 trying to update to 11.2.0 :-/ But that will end with 12.0.0 :-)
|
[11.x] incorrect download code for upgrade
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1294/comments
| 0 |
2021-01-22T15:58:48Z
|
2021-01-22T16:32:46Z
|
https://github.com/Piwigo/Piwigo/issues/1294
| 792,117,754 | 1,294 |
[
"Piwigo",
"Piwigo"
] |
See https://fr.piwigo.org/forum/viewtopic.php?id=29036 for original report.
After investigation, the problem is that there are 200k+ lines of "recent" activity. The current (11.0.0) algorithm manages activities line by line after putting them all in an array. The algorith must be changed.
|
11.x Dashboard, Fatal error: Allowed memory size
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1293/comments
| 0 |
2021-01-22T10:54:10Z
|
2021-01-22T15:27:29Z
|
https://github.com/Piwigo/Piwigo/issues/1293
| 791,906,057 | 1,293 |
[
"Piwigo",
"Piwigo"
] |
In https://github.com/Piwigo/Piwigo/commit/2e70ebf777e416748fcc3b2831b403eb30d51daa#diff-68e19e1f78d7f667fc58d480a5da7163da3939e1f6833fd22f62a7e21ae17ec0 (and https://github.com/Piwigo/Piwigo/commit/fd8394df07268b024c01ab54abea3e000f65c143#diff-68e19e1f78d7f667fc58d480a5da7163da3939e1f6833fd22f62a7e21ae17ec0) Piwigo 11 now escapes the word `groups` with backticks. Unfortunately a string like this:
```
a:13:{s:6:"`groups`";a:0:{}s:5:"level";i:0;s:4:"what";a:3:{i:0;s:10:"categories";i:1;s:8:"specials";i:2;s:11:"collections";}s:10:"photo_size";s:8:"original";s:9:"multisize";b:1;s:14:"archive_prefix";s:6:"piwigo";s:15:"archive_timeout";i:48;s:12:"max_elements";i:500;s:8:"max_size";i:100;s:10:"last_clean";i:1611238136;s:11:"one_archive";b:0;s:12:"force_pclzip";b:0;s:6:"direct";b:0;}
```
Can't be unserialized, because `groups` is escaped. For now, I have fixed the problem locally to Batch Downloader https://github.com/Piwigo/Piwigo-BatchDownloader/commit/9ddff8fb67815bf21c9747d1b66b823534f696c7
but it needs to be fixed at Piwigo level. I see 2 solutions:
1) avoid the automatic escape (added by `pwg_query`) when called from `conf_update_param`
2) remove the escapes in `safe_unserialize`
|
escaped word `groups` can't be unserialized
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1292/comments
| 4 |
2021-01-21T15:06:50Z
|
2021-01-22T15:27:29Z
|
https://github.com/Piwigo/Piwigo/issues/1292
| 791,195,520 | 1,292 |
[
"Piwigo",
"Piwigo"
] |
Original report (in French) on https://fr.piwigo.org/forum/viewtopic.php?id=29045
```
Parse error: syntax error, unexpected '[' in admin/stats.php on line 215
...
Parse error: syntax error, unexpected '[' in admin/batch_manager.php on line 608
```
It's due to an old PHP 5.3 version and the use of "recent" syntax. Let's keep Piwigo 11 compatible with PHP 5.3 (but we will certainly increase PHP version required for Piwigo 12)
|
[11.x] Parse error: syntax error, unexpected '['
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1291/comments
| 0 |
2021-01-21T10:00:44Z
|
2021-01-21T10:03:05Z
|
https://github.com/Piwigo/Piwigo/issues/1291
| 790,891,641 | 1,291 |
[
"Piwigo",
"Piwigo"
] |
See https://piwigo.org/forum/viewtopic.php?id=30891 for the original report
The `popen()` executing `du -sk` is not very universal. Can/should be done in pure PHP.
|
[11.x admin/intro] popen() has been disabled for security reasons
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1290/comments
| 0 |
2021-01-21T09:39:13Z
|
2021-01-22T15:27:29Z
|
https://github.com/Piwigo/Piwigo/issues/1290
| 790,873,001 | 1,290 |
[
"Piwigo",
"Piwigo"
] |
Piwigo tells me that I have 12 inactive plugins, however nothing happens when clicking on the "Show inactive plugins" button.
Apache error log doesn't print anything either.
|
Cannot show inactive plugins on "Plugin page" after upgrading to Piwigo 11
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1289/comments
| 8 |
2021-01-20T20:46:51Z
|
2021-02-01T07:26:32Z
|
https://github.com/Piwigo/Piwigo/issues/1289
| 790,309,097 | 1,289 |
[
"Piwigo",
"Piwigo"
] |
After upgrading to Piwigo 11, the user managment page does not show any users.
There is no error shown in Apache error log
Thanks in advance for looking into this! really appreciating Piwigo !
|
User manage page does not list any user, and looks broken after upgrading to Piwigo 11
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1288/comments
| 3 |
2021-01-20T20:43:31Z
|
2021-01-23T12:23:37Z
|
https://github.com/Piwigo/Piwigo/issues/1288
| 790,307,057 | 1,288 |
[
"Piwigo",
"Piwigo"
] |
Apache error log:
PHP Parse error: syntax error, unexpected '!' in /var/www/html/language/nb_NO/common.lang.php on line 358
Content at line 358
Velkommen!';
|
Syntax error in Norwegian language file after upgrading to Piwigo 11
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1287/comments
| 2 |
2021-01-20T20:39:29Z
|
2021-01-22T15:28:13Z
|
https://github.com/Piwigo/Piwigo/issues/1287
| 790,304,596 | 1,287 |
[
"Piwigo",
"Piwigo"
] |
Hello, I would like to contribute to this project for the next few months now that v11 is released.
I want to focus on: security, performance and porting code to new PHP version syntax.
But on the project organization side I would like to contribute by reviewing and closing very old Pull request (some from 2016) and Open Issues. Having this many issues and pull requests is crazy.
On main Readme file, it says Requirements `PHP 5.3 or greater (7+ recommended)`. I think we should support only 7.3+ or 7.4 for the next v12 release since its the official PHP version supported.
Thanks.
|
Contributing
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1285/comments
| 0 |
2021-01-19T17:21:35Z
|
2021-01-19T17:21:35Z
|
https://github.com/Piwigo/Piwigo/issues/1285
| 789,210,865 | 1,285 |
[
"Piwigo",
"Piwigo"
] |
With version 11.0.0 I'm getting the error "infinite loop?" displayed whenever I click on next page in an album. The URL it calls looks like this https://myhost/piwigo/index.php?/categories/startcat-12
Is this known?
|
"Infinite loop?" error when going on page 2 of albums
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1284/comments
| 2 |
2021-01-19T13:36:15Z
|
2021-01-22T15:27:28Z
|
https://github.com/Piwigo/Piwigo/issues/1284
| 789,028,598 | 1,284 |
[
"Piwigo",
"Piwigo"
] |
With Piwigo 11beta5, if you create a new user and then go on the Groups Manager, "Manage Users" on any group, the new users are not in the list for addition.
It's a UsersCache issue.
|
new users are missing from groups/addUser new form
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1283/comments
| 0 |
2021-01-18T15:52:36Z
|
2021-01-18T16:05:15Z
|
https://github.com/Piwigo/Piwigo/issues/1283
| 788,377,230 | 1,283 |
[
"Piwigo",
"Piwigo"
] |
Hi,
Surprisingly, I couldn't find an existing issue on this topic, so opening one.
It would be astonishing to be able to zoom in pictures with Piwigo. Currently, this is not as user friendly as other software such as google photo for example. In Piwigo, you have to select a small, medium, large, extra large, original picture size. However I believe most of the time, users want to zoom in an image on their phone to a specific part of the image. This is where image tiling comes in handy. This could maybe be performed on the fly, or as a pre-process part.
See other projects such as:
https://openseadragon.github.io/examples/creating-zooming-images/
|
Feature Request: image tiling for zooming capability
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1281/comments
| 0 |
2021-01-18T02:15:51Z
|
2021-01-18T02:15:51Z
|
https://github.com/Piwigo/Piwigo/issues/1281
| 787,862,037 | 1,281 |
[
"Piwigo",
"Piwigo"
] |
It appears piwigo requires php-mbstring but doesn't check this. When installing piwigo the installer stops (shows a blank screen) and my nginx error log shows the below error. Perhaps add a library check?
```
2021/01/14 21:48:33 [error] 4068718#4068718: *1701 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught Error: Call to undefined function mb_convert_encoding() in /var/www/html/photos/include/emogrifier.class.php:434
Stack trace:
#0 /var/www/html/photos/include/emogrifier.class.php(411): Emogrifier->getUnifiedHtml()
#1 /var/www/html/photos/include/emogrifier.class.php(233): Emogrifier->createXmlDocument()
#2 /var/www/html/photos/include/functions_mail.inc.php(955): Emogrifier->emogrify()
#3 /var/www/html/photos/include/functions_mail.inc.php(853): move_css_to_body()
#4 /var/www/html/photos/install.php(524): pwg_mail()
#5 {main}
thrown in /var/www/html/photos/include/emogrifier.class.php on line 434" while reading response header from upstream, client: redacted.invalid, server: redacted.invalid, request: "POST /photos/install.php?language=en_GB HTTP/2.0", upstream: "fastcgi://unix:/var/run/php/php-fpm.sock:", host: "redacted.invalid", referrer: "https://redacted.invalid/photos/install.php"
```
|
Check for php-mbstring before installing
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1280/comments
| 1 |
2021-01-14T20:53:53Z
|
2022-01-23T04:56:00Z
|
https://github.com/Piwigo/Piwigo/issues/1280
| 786,333,723 | 1,280 |
[
"Piwigo",
"Piwigo"
] |
**Description**
A Stored XSS was found in Piwigo 2.10.2 when creating a new photo album. The XSS is reflected in various endpoints of the web application, such as the main page and the Manage section of Albums.
Stored XSS occurs when a malicious script is injected directly into a vulnerable web application.
**Steps To Reproduce**
1. Login and access the administrator panel (/admin.php)
2. In the vertical menu, click on Albums -> Manage
3. Press the button that says "create a new album"
4. In the input of "Album name" enter the following payload: `<script>alert(document.location)</script>`
5. Press the "Create" button and the alert will be displayed
**Impact**
An attacker can execute arbitrary JavaScript code in the victim's browser, an example of an attack would be to steal users cookies.
**Request**
```
POST /piwigo/admin.php?page=cat_list HTTP/1.1
Host: localhost
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:84.0) Gecko/20100101 Firefox/84.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
Accept-Language: es-ES,es;q=0.8,en-US;q=0.5,en;q=0.3
Accept-Encoding: gzip, deflate
Content-Type: application/x-www-form-urlencoded
Content-Length: 122
Origin: https://localhost
DNT: 1
Connection: close
Referer: https://localhost/piwigo/admin.php?page=cat_list
Cookie: phavsz=1461x793x1.2; pwg_id=83520dfa9c3701fe6d3530b52d0c74fd; __cfduid=debbf939b4bbaba7d59417eb2d9c5b0e11609899072
Upgrade-Insecure-Requests: 1
pwg_token=4263dfb7b56f80a9c3512e0280801624&virtual_name=%3Cscript%3Ealert%28document.location%29%3C%2Fscript%3E&submitAdd=
```
**Attachments**
|
Stored XSS vulnerability found on creating Albums option
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1279/comments
| 2 |
2021-01-06T03:17:45Z
|
2021-01-10T23:11:11Z
|
https://github.com/Piwigo/Piwigo/issues/1279
| 779,939,570 | 1,279 |
[
"Piwigo",
"Piwigo"
] |
Some plugins have a settings page, but this page is only for webmasters, not for administrators. With Piwigo 11 and the `Has Settings: true` header parameter, activating the link is more straightforward but less flexible. As suggested by @ddtddt a `Has Settings: webmaster` would keep things simple (without breaking the new header parameter).
|
[plugins] activate settings button only for webmasters
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1277/comments
| 0 |
2020-12-29T16:45:36Z
|
2021-01-06T14:03:41Z
|
https://github.com/Piwigo/Piwigo/issues/1277
| 775,986,511 | 1,277 |
[
"Piwigo",
"Piwigo"
] |
Piwigo 11 is coming soon, there won't be any more migration task, let's add the upgrade from Piwigo 2.10
|
upgrade script to 11
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1276/comments
| 0 |
2020-12-22T14:36:34Z
|
2020-12-22T15:36:45Z
|
https://github.com/Piwigo/Piwigo/issues/1276
| 772,993,486 | 1,276 |
[
"Piwigo",
"Piwigo"
] |
I order to avoid a (quite complex) security issue, Piwigo should delete the password reset key when the email address is changed.
This vulnerability was privately reported by Ivan Tagsa. We thank the reporter for that.
|
delete password reset key when email address is changed
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1275/comments
| 0 |
2020-12-22T14:03:06Z
|
2020-12-22T14:25:30Z
|
https://github.com/Piwigo/Piwigo/issues/1275
| 772,970,089 | 1,275 |
[
"Piwigo",
"Piwigo"
] |
Does this have paypal integration to charge for image upload?
|
Paypal Integration
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1273/comments
| 1 |
2020-12-18T17:08:11Z
|
2021-01-23T05:09:22Z
|
https://github.com/Piwigo/Piwigo/issues/1273
| 771,039,702 | 1,273 |
[
"Piwigo",
"Piwigo"
] |
The table piwigo_images needs an index on the field path in order to remove table scans when looking for images that are locally synchronised. I looked at Mysql query performance on Mariadb and found lots of first row and table scan warnings in the performance logs, due to Select * from piwigo_images where path='<absolute path of local image>'
My server is a quad core and each image would spike to 240% CPU load in Mysql when fetched by the browser at the API GET /_data/i/galleries/<image name>
https://github.com/Piwigo/Piwigo/blob/a641b9eb08650272b3bf8f9e9db92ffd3e529d1f/install/piwigo_structure-mysql.sql#L215
adding an index to the path field on this table resulted in a 200% reduction in load, and a massive speed up in image retrieval.
|
Please add index to piwigo_image.path field.
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1272/comments
| 2 |
2020-12-17T16:31:40Z
|
2020-12-18T14:37:19Z
|
https://github.com/Piwigo/Piwigo/issues/1272
| 770,192,915 | 1,272 |
[
"Piwigo",
"Piwigo"
] |
Trying to get the install going and all I get is this:
Fatal error: Uncaught Error: Call to undefined function get_magic_quotes_gpc() in C:\Apache24\htdocs\testsite\galleries\include\common.inc.php:20 Stack trace: #0 C:\Apache24\htdocs\testsite\galleries\index.php(11): include_once() #1 {main} thrown in C:\Apache24\htdocs\testsite\galleries\include\common.inc.php on line 20
The program is not installed - this is a first time install.
Windows Pro 10 version 20H2 (64bit)
PHP 8.0.0 64 bit
MySQL community edition 8.0.22
Piwigo 2.10.2
What other information can I provide to assist?
|
First Time Install/Setup: Fatal Error...
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1271/comments
| 1 |
2020-12-03T23:53:15Z
|
2020-12-08T23:45:12Z
|
https://github.com/Piwigo/Piwigo/issues/1271
| 756,682,132 | 1,271 |
[
"Piwigo",
"Piwigo"
] |
If you delete the user , while he is browsing the page.
Then its dies.
"Share Album" plugin creates a user, and if you revoke (Cancel sharing) the access while the user is browsing.
functions_user_inc.php dies at row 348.
**I added these rows to avoid the problem:**
`
$user_infos_row = pwg_db_fetch_assoc($result);
if (is_null($user_infos_row)) {
unset($_SESSION["pwg_uid"]);
redirect(get_absolute_root_url());
}
`
**The error message:**
`Warning: array_merge(): Expected parameter 1 to be an array, null given in ...\www\piwigo\include\functions_user.inc.php on line 356
Warning: Invalid argument supplied for foreach() in ...\www\piwigo\include\functions_user.inc.php on line 358
Notice: Undefined index: id in ...\www\piwigo\include\functions_user.inc.php on line 380
Notice: Undefined index: status in ...\www\piwigo\include\functions_user.inc.php on line 380
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 cat_id
FROM pwg_user_access
WHERE user_id =
; in ...\www\piwigo\include\dblayer\functions_mysqli.inc.php on line 856
Fatal error: Uncaught Error: Call to a member function fetch_assoc() on bool in ...\www\piwigo\include\dblayer\functions_mysqli.inc.php:917 Stack trace: #0 ...\www\piwigo\include\functions_user.inc.php(545): query2array('\nSELECT cat_id\n...', NULL, 'cat_id') #1 ...\www\piwigo\include\functions_user.inc.php(380): calculate_permissions(NULL, NULL) #2 ...\www\piwigo\include\functions_user.inc.php(273): getuserdata(5, true) #3 ...\www\piwigo\include\user.inc.php(60): build_user(5, true) #4 ...\www\piwigo\include\common.inc.php(154): include('C:\\Users\\szabog...') #5 ...\www\piwigo\index.php(11): include_once('C:\\Users\\szabog...') #6 {main} thrown in ...\www\piwigo\include\dblayer\functions_mysqli.inc.php on line 917`
|
User delete while browsing
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1270/comments
| 0 |
2020-11-26T12:09:10Z
|
2020-11-26T12:09:27Z
|
https://github.com/Piwigo/Piwigo/issues/1270
| 751,540,632 | 1,270 |
[
"Piwigo",
"Piwigo"
] |
Creating an album with the name as that of the following payload results in the stored xss at the following endpoint,
Endpoint:- */admin.php?page=cat_list*
Payload:- *<script>alert('xss')</script>*
POC Demo:- [Demo](https://drive.google.com/file/d/1B3yip5wqYOXUESLCANWnuY45nBMKuysK/view?usp=sharing)
|
Stored XSS in Piwigo Version 11.0.0beta5
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1267/comments
| 0 |
2020-11-20T18:02:16Z
|
2020-11-21T10:38:22Z
|
https://github.com/Piwigo/Piwigo/issues/1267
| 747,693,185 | 1,267 |
[
"Piwigo",
"Piwigo"
] |
Feature #626 breaks pagination completely
System: nginx 1.19, php-fpm 7.4, mariadb 10.5
Symptoms: when clickin' "next" link or any link to specific pagenumber, nothing happen, browser start waiting for response until timeout
Web server logs has no meaning information that could point to a root of problem.
It only says that "client xxx.xxx.xxx.xxx closed keepalive connection" or "epoll_wait() reported that client prematurely closed connection while sending request to upstream".
When taking back the earlier version of include/functions_url.inc.php this problem goes away
|
Feature #626 breaks pagination completely
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1266/comments
| 0 |
2020-11-20T15:20:59Z
|
2020-12-17T15:35:04Z
|
https://github.com/Piwigo/Piwigo/issues/1266
| 747,573,428 | 1,266 |
[
"Piwigo",
"Piwigo"
] |
User Manager page redesign
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1265/comments
| 0 |
2020-11-20T14:46:23Z
|
2021-06-25T13:41:25Z
|
https://github.com/Piwigo/Piwigo/issues/1265
| 747,547,052 | 1,265 |
|
[
"Piwigo",
"Piwigo"
] |
Maintenance page redesign
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1264/comments
| 0 |
2020-11-18T16:47:05Z
|
2021-06-25T13:42:23Z
|
https://github.com/Piwigo/Piwigo/issues/1264
| 745,824,666 | 1,264 |
|
[
"Piwigo",
"Piwigo"
] |
Note: Having raised this issue, I'm not clear that I'm right, my PHP is what I've gleaned from reading the Piwigo source code, and as a result very minimal in understanding. I understand why you've got these triggers - they should in theory allow extension of the core Piwigo code without copy and paste like I've had to, but, in order to maximise that possibility and standardise the approach, could all calls be perhaps given an object with all WS-API params, and the source method as a default, then extra details as the code Piwigo developers feel are needed to determine where the call is coming from in the logic - e.g. for categories.getList, you'd need the loop variables. This would give you more than you need in most cases, but by being standard, would allow less instances of having to change stuff in the core code stream and allow more work-arounds to be handled by plugins as quick fixes for example. I would have liked to have pushed a fix to the Extended Details plugin source repo, but because my fix also needs to go into the Piwigo repo, I don't think this is possible.
The following is one example where the param and the caller method name appear to have been muddled up, but there are a few more if I'm right. If I'm wrong, perhaps the docs could be clearer in the method declaration
_pwg.categories.php_ : **line 268**
```$row['comment'] = strip_tags(
trigger_change(
'render_category_description',
$row['comment'],
'ws_categories_getList'
)
);
```
_ws_core.inc.php_ : **line 586** has the call
```$result = trigger_change('ws_invoke_allowed', true, $methodName, $params);```
`trigger_change` is defined in _functions_plugins.inc.php_ **line 185**
```
* @param string $event
* @param mixed $data data to transmit to all handlers
* @param mixed $args,... optional arguments
* @return mixed $data
*/
function trigger_change($event, $data=null)
```
|
trigger_change: Mixed up parameter order in API calls in Piwigo Source code and Extended Details Plugin
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1263/comments
| 0 |
2020-11-16T20:28:38Z
|
2020-11-17T08:03:02Z
|
https://github.com/Piwigo/Piwigo/issues/1263
| 744,159,828 | 1,263 |
[
"Piwigo",
"Piwigo"
] |
group list page no styling on the help pop-in
|
No styling on the help pop-in group page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1262/comments
| 0 |
2020-11-13T16:38:46Z
|
2020-11-13T16:39:52Z
|
https://github.com/Piwigo/Piwigo/issues/1262
| 742,591,728 | 1,262 |
[
"Piwigo",
"Piwigo"
] |
old reziable class in site_update.tpl for exemple, getting rid of it
|
old resizable
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1261/comments
| 0 |
2020-11-13T15:24:11Z
|
2020-11-13T15:26:09Z
|
https://github.com/Piwigo/Piwigo/issues/1261
| 742,532,660 | 1,261 |
[
"Piwigo",
"Piwigo"
] |
you have to refresh the page to see the changes made
|
Notification by mail form doesn't reload parameters correctly
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1260/comments
| 0 |
2020-11-13T10:22:11Z
|
2020-11-13T10:24:45Z
|
https://github.com/Piwigo/Piwigo/issues/1260
| 742,340,446 | 1,260 |
[
"Piwigo",
"Piwigo"
] |
/admin/batch_manager_global.php, lines #569 and #660 generates warning/error "Object should implement 'Countable' interface"
I suggest following change:
`if (count($page['cat_elements_id']) > 0)`
to
`if (!empty($page['cat_elements_id']))`
|
"Countable" interface - /admin/batch_manager_global.php
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1259/comments
| 0 |
2020-11-12T23:21:39Z
|
2020-11-12T23:22:35Z
|
https://github.com/Piwigo/Piwigo/issues/1259
| 742,000,355 | 1,259 |
[
"Piwigo",
"Piwigo"
] |
When syncing a local images directory with piwigo, if an image filename contains a "rank" substring, then file name, path and image name will be added to a database with backquotes. For instance, source file has the name as "battleship-rank-1.jpg", it will be written to a database in following form: "battleship-`rank`-1.jpg" (without doublequotes of course)
|
Strange artifacts during filenames processing.
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1258/comments
| 1 |
2020-11-12T23:17:56Z
|
2020-11-14T20:16:43Z
|
https://github.com/Piwigo/Piwigo/issues/1258
| 741,997,726 | 1,258 |
[
"Piwigo",
"Piwigo"
] |
When syncing a local images directory with piwigo, the /admin/batch_manager.php, line #363 generates error, saying that $linked_to_virtual cannot be empty or null.
I suggest insert a new line between #354 and #355: `$linked_to_virtual = [];`
|
admin/batch_manager.php some errors/warnings on php7.4
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1257/comments
| 0 |
2020-11-12T23:12:25Z
|
2021-01-22T15:27:28Z
|
https://github.com/Piwigo/Piwigo/issues/1257
| 741,995,219 | 1,257 |
[
"Piwigo",
"Piwigo"
] |
when adding in a group it changes the height of the input
http://g.recordit.co/C6mPoFTmEF.gif
|
height of input changing in group list
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1256/comments
| 0 |
2020-11-12T14:16:05Z
|
2020-11-12T14:17:15Z
|
https://github.com/Piwigo/Piwigo/issues/1256
| 741,636,727 | 1,256 |
[
"Piwigo",
"Piwigo"
] |
I'm using docker-compose.yml and need to define an SMTP host/user/pass etc.
Otherwise password reset and emails won't work.
|
How do I configure an SMTP server?
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1255/comments
| 1 |
2020-11-12T05:45:28Z
|
2020-11-13T22:57:59Z
|
https://github.com/Piwigo/Piwigo/issues/1255
| 741,299,031 | 1,255 |
[
"Piwigo",
"Piwigo"
] |
Hi,
I'm using piwigo with the ldap plugin. One of my users have a quote (') in its password. Piwigo badly handles it by quoting it and not removing the quote. I did some tests and see that "let'sgo" is stored as "let\'sgo" in $_POST['password'] (due to quote encoding) and it seems to never be decoded (same for $_POST['username'] even if I did not see a username with a quote)
I fixed my installation with this patch :
```php
diff --git a/piwigo/identification.php b/piwigo/identification.php
index 9059ef2..84a2ac1 100644
--- a/piwigo/identification.php
+++ b/piwigo/identification.php
@@ -60,7 +60,7 @@ if (isset($_POST['login']))
$redirect_to = isset($_POST['redirect']) ? urldecode($_POST['redirect']) : '';
$remember_me = isset($_POST['remember_me']) and $_POST['remember_me']==1;
- if ( try_log_user($_POST['username'], $_POST['password'], $remember_me) )
+ if ( try_log_user(stripcslashes($_POST['username']), stripcslashes($_POST['password']), $remember_me) )
{
// security (level 2): force redirect within Piwigo. We redirect to
// absolute root url, including http(s)://, without the cookie path,
```
I found strange that piwigo use magic quoting (doing it manually if it is disabled on the server) instead of properly managing input and doing quoting when required (SQL requests, ...)
Regards
Vincent
|
Bad handling of passwords with quote (') character
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1254/comments
| 2 |
2020-11-11T20:55:34Z
|
2023-01-10T17:08:53Z
|
https://github.com/Piwigo/Piwigo/issues/1254
| 741,064,313 | 1,254 |
[
"Piwigo",
"Piwigo"
] |
progress bar of batch manager should be like 2.11 version progress bar like when you upload photos
|
Progress bar of batch manager old style
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1253/comments
| 0 |
2020-11-10T09:14:14Z
|
2020-11-10T09:19:49Z
|
https://github.com/Piwigo/Piwigo/issues/1253
| 739,729,533 | 1,253 |
[
"Piwigo",
"Piwigo"
] |
If I Start Upload a photo on the web UI via the url
http://[fd00::5054:ff:fe90:a01a]/admin.php?page=photos_add
the upload does not start.
If I add the line
00::5054:ff:fe90:a01a piwigo6
to the
/etc/hosts
of the machine which runs the browser and access piwigo via
http://piwigo6/admin.php?page=photos_add
the upload works.
|
Cannot add photo via literal IPv6 address in URL
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1252/comments
| 0 |
2020-11-06T21:44:12Z
|
2020-11-06T21:44:12Z
|
https://github.com/Piwigo/Piwigo/issues/1252
| 738,060,290 | 1,252 |
[
"Piwigo",
"Piwigo"
] |
tooltip when hovering dropdown option empty and useless, should delete, also dropdown is underlined on hover
|
Empty tooltip on plugin page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1251/comments
| 0 |
2020-11-05T10:42:40Z
|
2020-11-05T10:44:19Z
|
https://github.com/Piwigo/Piwigo/issues/1251
| 736,819,431 | 1,251 |
[
"Piwigo",
"Piwigo"
] |
for exemple the dropdown option on hover is white in plugins page and black on themes page
alse you can delete a theme before it is deactivated which is not intended
|
ThemeBox and PluginBox not similar
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1250/comments
| 0 |
2020-11-05T09:49:15Z
|
2020-11-05T09:50:33Z
|
https://github.com/Piwigo/Piwigo/issues/1250
| 736,779,918 | 1,250 |
[
"Piwigo",
"Piwigo"
] |
font size is not the same for dashboard and plugins. Bigger than other menubars like Albums
|
Dashboard and plugin menubar bigger than others
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1249/comments
| 0 |
2020-11-05T09:12:36Z
|
2020-11-05T09:13:35Z
|
https://github.com/Piwigo/Piwigo/issues/1249
| 736,753,294 | 1,249 |
[
"Piwigo",
"Piwigo"
] |
javascript error due to str_no variable in french translation
|
Javascript error when editing photo in french
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1248/comments
| 0 |
2020-10-30T15:47:22Z
|
2020-10-30T15:48:06Z
|
https://github.com/Piwigo/Piwigo/issues/1248
| 733,293,902 | 1,248 |
[
"Piwigo",
"Piwigo"
] |
The Hungarian version of piwigo.org has been deactiated, due to lack of activity. Piwigo should not send visitors on it.
|
remove hu.piwigo.org from list of available Piwigo websites
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1247/comments
| 0 |
2020-10-28T15:09:45Z
|
2020-10-28T15:13:18Z
|
https://github.com/Piwigo/Piwigo/issues/1247
| 731,532,242 | 1,247 |
[
"Piwigo",
"Piwigo"
] |
To make support more efficient, it would be nice to be able to copy the environment information (to paste it on the forum)
Suggested by piwent on https://piwigo.org/forum/viewtopic.php?id=30700
|
[Maintenance] environment section, copy info with a button
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1246/comments
| 0 |
2020-10-28T12:35:13Z
|
2020-10-28T12:35:13Z
|
https://github.com/Piwigo/Piwigo/issues/1246
| 731,402,149 | 1,246 |
[
"Piwigo",
"Piwigo"
] |
As suggested by piwent on https://piwigo.org/forum/viewtopic.php?id=30700 it would be useful, for support purpose, to have the list of active plugins on the Tools/Maintenance/Environment section.
|
[Maintenance] environment section, list active plugins
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1245/comments
| 0 |
2020-10-28T12:32:41Z
|
2021-07-23T11:04:14Z
|
https://github.com/Piwigo/Piwigo/issues/1245
| 731,400,469 | 1,245 |
[
"Piwigo",
"Piwigo"
] |
Can't leave group list -> add user menu with esc or right click outside box
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1244/comments
| 0 |
2020-10-27T17:17:50Z
|
2020-10-27T17:21:55Z
|
https://github.com/Piwigo/Piwigo/issues/1244
| 730,657,237 | 1,244 |
|
[
"Piwigo",
"Piwigo"
] |
I have private albums with access granted by groups membership.
For some users it just don't work as it should for a reason I can't figure and with apparently incoherent behavior.
I check group membership for the concerned users, it's ok
Albums are listed in the "Albums authorized thanks to group associations" screen as they should.
And still, users don't have access to some of the albums in the list, nor by navigating in the public interface nor by direct access to the url (access not authorized message)
For others users in exactly the same groups and configuration, access is ok
For others private albums, access is ok, so I'm sure that users are well authiticate and recognize.
For the record, users and groups are synchronized and authentification is manage from a external source with a plugin of my own but I don't think this could be the cause as, like I said, I checked that my users are well registred in the Piwigo users and group configuration and authentification is correct.
does anyone have ever seen this kind of problem ?
thanks,
Pascal
|
Access to private album sometimes don't work
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1243/comments
| 1 |
2020-10-21T12:11:19Z
|
2020-10-22T08:01:21Z
|
https://github.com/Piwigo/Piwigo/issues/1243
| 726,421,079 | 1,243 |
[
"Piwigo",
"Piwigo"
] |
Dear community,
I'm working with Piwigo since 2015 and I like it. For me the one thing that is a pain is the spam we receive through comments. We want guests to be able to participate and leave comments. The few responsive and modern templates that are available do not work with the anti-spam extensions.
Bootstrap Darkroom: https://github.com/tkuther/piwigo-bootstrap-darkroom/issues/222
Bootstrap Default: https://github.com/Philio/bootstrapdefault/issues/47
With Bootstrap Darkroom being [promoted by Piwigo](https://piwigo.com/blog/2020/03/12/bootstrap-darkroom-new-theme-piwigo-com/) I thought it would work with those anti-spam extensions. But it did not.
Therefore I'd like to request a new feature that I think is simple to implement but very effective against spam. If it would be possible to optionally add a security question to comment forms, the number of spam posts will drop drastically. The question and the answer should be configurable, so admins could change them whenever they want over time. It is probably best to be able to set multiple answers and/or optionally make use of lowercase validation.
Example:
> What is the color of grass?
> "Green" / "green" / "GrEEn" / "GREEN" are all valid.
Another benefit would be that no plugins/extensions are required to prevent spam, unless the security question does not fit ones needs.
Kind regards
|
Add a security question to comment forms to prevent spam
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1242/comments
| 0 |
2020-10-18T11:38:12Z
|
2020-10-18T11:51:07Z
|
https://github.com/Piwigo/Piwigo/issues/1242
| 723,987,654 | 1,242 |
[
"Piwigo",
"Piwigo"
] |
This is quite a specific use case, but we have discovered that if you follow these steps, you get stuck:
1. right after install, log in with your webmaster credentials (user created during install)
2. in the administration, do not add photos, create a new user "user1", with no admin status
3. log out
4. log in as "user1". The identification seems to fail (it doesn't) and you can't log out. You're stuck.
What happens is that the step 4 works: you're logged in as "user1", but since the gallery is empty, no_photo_yet is triggered and displays the login form because you're not admin. When trying to log in, identication.php says "you're already logged in" with a redirection to gallery home.
no_photo_yet page should not be triggered if the visitor is a connected user, without admin status.
|
Identification fails when gallery is empty
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1241/comments
| 1 |
2020-10-16T08:15:05Z
|
2021-05-13T12:07:55Z
|
https://github.com/Piwigo/Piwigo/issues/1241
| 723,008,947 | 1,241 |
[
"Piwigo",
"Piwigo"
] |
Alert should be like when you remove a tag, an alert via jconfirm
|
Alert via browser on multiple page to confirm an action
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1240/comments
| 0 |
2020-10-15T15:16:47Z
|
2020-10-31T16:08:01Z
|
https://github.com/Piwigo/Piwigo/issues/1240
| 722,431,055 | 1,240 |
[
"Piwigo",
"Piwigo"
] |
if you filter for "research" then add the tag "research" it won't show up in the list of tags
|
Tags not refreshing after adding a new tag
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1239/comments
| 0 |
2020-10-15T09:46:19Z
|
2020-10-15T09:48:27Z
|
https://github.com/Piwigo/Piwigo/issues/1239
| 722,175,922 | 1,239 |
[
"Piwigo",
"Piwigo"
] |
when adding a tag and clicking to get in input mode, tags list goes down by 1 pixel
|
Tag input mode moves the tags list by 1 pixel
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1238/comments
| 0 |
2020-10-15T09:20:18Z
|
2020-10-15T09:21:34Z
|
https://github.com/Piwigo/Piwigo/issues/1238
| 722,156,393 | 1,238 |
[
"Piwigo",
"Piwigo"
] |
There is no need for it to be an open menu like photos anymore
|
Admin panel, plugin page should be standalone like dashboard
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1237/comments
| 0 |
2020-10-14T14:05:56Z
|
2020-12-18T11:40:31Z
|
https://github.com/Piwigo/Piwigo/issues/1237
| 721,491,883 | 1,237 |
[
"Piwigo",
"Piwigo"
] |
Missing translation album edit page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1236/comments
| 0 |
2020-10-13T15:54:23Z
|
2020-10-13T15:57:20Z
|
https://github.com/Piwigo/Piwigo/issues/1236
| 720,460,350 | 1,236 |
|
[
"Piwigo",
"Piwigo"
] |
Only capitalize the first letter
|
Every word in Album Edit Page Actions are capitalized
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1235/comments
| 0 |
2020-10-13T15:45:47Z
|
2020-10-13T15:50:59Z
|
https://github.com/Piwigo/Piwigo/issues/1235
| 720,448,584 | 1,235 |
[
"Piwigo",
"Piwigo"
] |
Multiple translations missing on this page in this selection mode for example or even the title of the page
|
Missing translations in Tag Manager page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1234/comments
| 0 |
2020-10-13T14:30:11Z
|
2020-10-13T14:31:44Z
|
https://github.com/Piwigo/Piwigo/issues/1234
| 720,339,199 | 1,234 |
[
"Piwigo",
"Piwigo"
] |
The skeleton looks weird on big screen because there are only 3 <div> evertyime
|
Search album skeleton doesn't fit the whole page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1233/comments
| 0 |
2020-10-12T14:53:34Z
|
2020-10-12T14:55:15Z
|
https://github.com/Piwigo/Piwigo/issues/1233
| 719,443,562 | 1,233 |
[
"Piwigo",
"Piwigo"
] |
Unnecessary help button in search album page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1232/comments
| 0 |
2020-10-12T14:41:06Z
|
2020-10-12T14:42:20Z
|
https://github.com/Piwigo/Piwigo/issues/1232
| 719,434,539 | 1,232 |
|
[
"Piwigo",
"Piwigo"
] |
no translation for the placeholder,
neither for the label search albums.
|
Missing translations on new album search page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1231/comments
| 0 |
2020-10-12T14:34:44Z
|
2020-10-13T16:16:19Z
|
https://github.com/Piwigo/Piwigo/issues/1231
| 719,429,936 | 1,231 |
[
"Piwigo",
"Piwigo"
] |
PHP error message when there are no groups
|
Error message when there are no groups in groups page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1230/comments
| 1 |
2020-10-12T14:19:59Z
|
2020-10-13T07:25:15Z
|
https://github.com/Piwigo/Piwigo/issues/1230
| 719,419,160 | 1,230 |
[
"Piwigo",
"Piwigo"
] |
Album properties table is small and doesn t fit the whole screen same for a lot of the double Select table pages
|
Album properties table is graphically wrong
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1229/comments
| 0 |
2020-10-12T14:04:37Z
|
2020-10-13T07:47:38Z
|
https://github.com/Piwigo/Piwigo/issues/1229
| 719,407,703 | 1,229 |
[
"Piwigo",
"Piwigo"
] |
API calls with response format XML RPC like https://example.com/ws.php?format=xmlrpc yield (with PHP 7.2)
`Fatal error: Cannot redeclare xmlrpc_encode() in .../include/ws_protocols/xmlrpc_encoder.php on line 46`
where line 46 is end of xmlrpc_encode() function definition. xmlrpc_encode() is a PHP experimental function since long, https://www.php.net/manual/en/function.xmlrpc-encode.php
|
API response format XML RPC yields Fatal error: Cannot redeclare xmlrpc_encode()
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1228/comments
| 0 |
2020-10-11T13:47:42Z
|
2020-10-11T13:47:42Z
|
https://github.com/Piwigo/Piwigo/issues/1228
| 718,839,925 | 1,228 |
[
"Piwigo",
"Piwigo"
] |
After doing a new netinstall (on a Dreamhost shared server) of Piwigo 2.10.2, the file piwigo/local/config/database.inc.php (which contains the database authentication information) has protection 666, world readable and writable.
>dh_akhcfg@william-floyd:~/gal02.dd-b.net/piwigo/local/config$ ls -l
>total 8
>-rw-rw-rw- 1 dh_akhcfg pg75234 319 Oct 7 13:48 database.inc.php
>-rwxr-xr-x 1 dh_akhcfg pg75234 610 Oct 7 13:36 index.php`
|
database.inc.php is world read and write after install
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1227/comments
| 0 |
2020-10-10T17:48:29Z
|
2020-10-10T17:48:29Z
|
https://github.com/Piwigo/Piwigo/issues/1227
| 718,669,269 | 1,227 |
[
"Piwigo",
"Piwigo"
] |
In an enterprise setting, it is important to be able to distinguish between content administrators and technical administrators.
Usually, distinguished, trained users will be responsible for content administration like setting up albums, uploading, renaming, deleting photos etc., while the IT department is responsible for the technical administration like configuration and maintenance, maybe also user management.
Currently, in Piwigo, you can only distinguish between _Users_ who can do basically nothing except from viewing photos and _Administrators_ who are allowed to mess up everything. Even with the [Community plugin](https://piwigo.org/ext/extension_view.php?eid=303), _Users_ can only create albums and upload photos, but they cannot rename or delete them.
An additional [user status](https://piwigo.org/doc/doku.php?id=user_documentation:use:features:user_status) in-between these two would be useful. I would suggest to call it _Editor_ (as in [Wordpress](https://wordpress.com/support/user-roles/)) and give it access to the Administration panel sections "Photos" and "Albums".
Access to the "Users" section might be granted optionally to individual _Editors_, but all other sections stay accessible by _Administators_ only.
|
[users & groups] Add user status "Editor" which is allowed to administrate all Photos and Albums, but not Plugins, Tools, Configuration (and Users)
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1226/comments
| 24 |
2020-10-05T09:17:44Z
|
2023-10-15T11:49:52Z
|
https://github.com/Piwigo/Piwigo/issues/1226
| 714,669,578 | 1,226 |
[
"Piwigo",
"Piwigo"
] |
In addition of albums organization, we would need to be able to use a thesaurus, with organized hierarchized tag attached to photos.
It was mentionned in https://github.com/Piwigo/Piwigo/issues/626
It has also been discussed here : https://fr.piwigo.org/forum/viewtopic.php?id=25378
I often hear that it is something missing to Piwigo.
Are there some projects to include a thesaurus in Piwigo or would it be something that could be added to Piwigo ?
|
Manage photos with a thesaurus ?
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1225/comments
| 3 |
2020-10-05T07:13:38Z
|
2023-09-04T13:26:18Z
|
https://github.com/Piwigo/Piwigo/issues/1225
| 714,583,408 | 1,225 |
[
"Piwigo",
"Piwigo"
] |
In the administration, we have many fields with auto-complete to find a specific album. Unfortunately, we can't apply action to the found albums. For example we can't edit it.
I would love to have a new admin page that let me search for an album and once found, edit it the way I want.
|
search albums
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1224/comments
| 1 |
2020-09-30T09:42:28Z
|
2020-09-30T09:44:09Z
|
https://github.com/Piwigo/Piwigo/issues/1224
| 711,797,168 | 1,224 |
[
"Piwigo",
"Piwigo"
] |
See https://piwigo.org/forum/viewtopic.php?id=30587
> - add a new virtual album
> - go into Edit, notice it's unlocked (under Publication)
> - type something into the description field, and Save
> - notice the album is now locked
> - try to unlock album, then Save; album locks again
> - remove description, Save
> - now the album is unlocked
> - try to lock the album, then Save; album stays unlocked
|
[2.11beta3] lock/unlock album does not work
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1223/comments
| 0 |
2020-09-22T14:13:40Z
|
2020-09-22T14:18:55Z
|
https://github.com/Piwigo/Piwigo/issues/1223
| 706,422,635 | 1,223 |
[
"Piwigo",
"Piwigo"
] |
> Notice: Constant CYEAR already defined in include/calendar_weekly.class.php on line 16
Is what you get in the Batch Downloader history if you have lines with a weekly calendar and another one with a monthly calendar. That's because constant CYEAR (and CDAY) are defined in both `calendar_weekly.class.php` and `calendar_monthly.class.php`
|
Constant CYEAR already defined in include/calendar_weekly.class.php on line 16
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1222/comments
| 0 |
2020-09-11T08:31:27Z
|
2022-03-29T14:25:45Z
|
https://github.com/Piwigo/Piwigo/issues/1222
| 699,023,383 | 1,222 |
[
"Piwigo",
"Piwigo"
] |
Thanks to #343 if you have a photo in album "wild bear" it will show up in a search for word "bear", even if the photo itself has no text property with "bear" in it (not in the title, description or tags...). If the same photo is now in album "wild bear / grizzly" it won't show up in the results of the same search.
I think we should add a parameter `$conf['quick_search_include_sub_albums'] = false;` (by default, to keep the current behavior).
|
[quick search] include sub-albums photos in search results
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1221/comments
| 0 |
2020-09-11T08:04:17Z
|
2020-10-30T17:01:39Z
|
https://github.com/Piwigo/Piwigo/issues/1221
| 698,991,594 | 1,221 |
[
"Piwigo",
"Piwigo"
] |
Hi,
I'm seeing this:
instead of this:
I've tried to set "charset utf-8" in nginx but it doesn't work. When I view through the Sophos WAF's reverse proxy https://mydomain.com/ I get the crippled result. When viewing locally through https://myserver.local/ I'm getting the correct result.
Any advice how to fix this? Other web applications I'm hosting over Sophos WAF don't have this problem.
Many thanks.
Catfriend1
|
v 2.10.2 Nginx behind Sophos WAF cripples icons?
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1219/comments
| 1 |
2020-09-05T20:40:44Z
|
2020-09-06T12:52:26Z
|
https://github.com/Piwigo/Piwigo/issues/1219
| 694,178,214 | 1,219 |
[
"Piwigo",
"Piwigo"
] |
The firewall considers the stream unsafe and prone to be exploitable.
Firewall Log:
```
2020:09:05-21:44:17 firewall httpd[1092]: [security2:error] [pid 1092:tid 3715890032] [client IP:63981] [client IP] ModSecurity: Warning. Pattern match "<b>Warning<\\\\/b>.{0,100}?:.{0,1000}?\\\\bon line\\\\b" at RESPONSE_BODY. [file "/usr/apache/conf/waf/modsecurity_crs_outbound.conf"] [line "28"] [id "970009"] [rev "2"] [msg "PHP Information Leakage"] [data "Matched Data: <b>Warning</b>: array_diff(): Expected parameter 2 to be an array, null given in <b>/var/www/piwigo/admin/batch_manager.php</b> on line found within RESPONSE_BODY: <html><body><br>\\x0a<b>Notice</b>: Undefined variable: linked_to_virtual in <b>/var/www/piwigo/admin/batch_manager.php</b> on line <b>365</b><br>\\x0a<br>\\x0a<b>Warning</b>: array_diff(): Expected parameter 2 to be an array, null given in <b>/var/www/piwigo/admin/batch_manager.php</b> on line <b>365</b><br>\\x0a<br>\\x0a<b>Warnin..."] [severity "ERROR"] [ver "OWASP_CRS/2.2.7"] [maturity "9"] [accuracy "9"] [tag "OWASP_CRS/LEAKAGE/ERRORS_PHP"] [tag "WASCTC/WASC-13"] [tag "OWASP_TOP_10/A6"] [tag "PCI/6.5.6"] [hostname "DNS"] [uri "/admin.php"] [unique_id "X1Pqkfz2tZPCakGeaw5R7AAAADE"], referer: https://DNS:Port/admin.php?page=batch_manager
2020:09:05-21:44:17 firewall httpd[1092]: [security2:error] [pid 1092:tid 3715890032] [client IP:63981] [client IP] ModSecurity: Rule 92036c8 [id "970003"][file "/usr/apache/conf/waf/modsecurity_crs_outbound.conf"][line "123"] - Execution error - PCRE limits exceeded (-8): (null). [hostname "DNS"] [uri "/admin.php"] [unique_id "X1Pqkfz2tZPCakGeaw5R7AAAADE"], referer: https://DNS:Port/admin.php?page=batch_manager
2020:09:05-21:44:17 firewall httpd[1092]: [security2:error] [pid 1092:tid 3715890032] [client IP:63981] [client IP] ModSecurity: Access denied with code 403 (phase 4). Pattern match "(.*)" at TX:0. [file "/usr/apache/conf/waf/modsecurity_crs_outbound_blocking.conf"] [line "24"] [id "981200"] [msg "Outbound Anomaly Score Exceeded (score 4): Last Matched Message: PHP Information Leakage"] [data "Last Matched Data: ><br>"] [hostname "DNS"] [uri "/admin.php"] [unique_id "X1Pqkfz2tZPCakGeaw5R7AAAADE"], referer: https://DNS:Port/admin.php?page=batch_manager
2020:09:05-21:44:17 firewall httpd[1092]: [security2:error] [pid 1092:tid 3715890032] [client IP:63981] [client IP] ModSecurity: Warning. Operator GE matched 4 at TX:outbound_anomaly_score. [file "/usr/apache/conf/waf/modsecurity_crs_correlation.conf"] [line "40"] [id "981205"] [msg "Outbound Anomaly Score Exceeded (score 4): PHP Information Leakage"] [hostname "DNS"] [uri "/admin.php"] [unique_id "X1Pqkfz2tZPCakGeaw5R7AAAADE"], referer: https://DNS:Port/admin.php?page=batch_manager
```
|
v 2.10.2 - PHP Info Leak detected by WAF
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1218/comments
| 0 |
2020-09-05T19:46:56Z
|
2020-09-05T19:47:08Z
|
https://github.com/Piwigo/Piwigo/issues/1218
| 694,156,367 | 1,218 |
[
"Piwigo",
"Piwigo"
] |
No options to pick a thumb
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1217/comments
| 1 |
2020-08-31T19:26:15Z
|
2020-08-31T19:26:53Z
|
https://github.com/Piwigo/Piwigo/issues/1217
| 689,447,612 | 1,217 |
|
[
"Piwigo",
"Piwigo"
] |
Hi, I can't set more than 999 photos per page. Is there a reason for this? if not, how can I set it to a higher number?
|
Max number of photos per page > 999
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1216/comments
| 0 |
2020-08-25T00:47:14Z
|
2020-08-25T00:47:14Z
|
https://github.com/Piwigo/Piwigo/issues/1216
| 685,074,910 | 1,216 |
[
"Piwigo",
"Piwigo"
] |
Currently (version 2.10) Piwigo activates all languages it finds in the language folder. With many years of adding new languages, the result is now a list of 70 languages. It's far too many and not very relevant.
In addition to the language chosen for installation, I would like Piwigo to only activate the top 10 languages used by its community. To find them, I have extracted the number of unique IP addresses on each language that perform an HTTP request like this one:
```
20200801_access.log:piwigo.org:- IP.ADD.RES.S - - [01/Aug/2020:00:00:09 +0200] 200 "POST /ext/api/get_revision_list.php?format=php&last_revision_only=true&version=80&lang=en&get_nb_downloads=true HTTP/1.0" 317552 "-" "Piwigo" "-/-"
```
Here the language is `en` for English
```
# grep 'api' 202008*_access.log |grep lang | perl -ne 'm/51.38.(\d+)\.(\d+):([^\s]+) .*lang=(\w+)/; print "$1 $2\n";' | sort | uniq| awk '{print $2}' | sort | uniq -c | sort -rn | head -10
2688 en
1490 de
944 fr
452 zh
216 pl
213 es
206 nl
150 it
118 ru
118 cs
```
English (which one, we have 3), Deutsch, French, Chinese (we have 3), Polish, Spanish, Dutch, Italian, Russian and Czech.
|
limit the number of languages activated by default
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1215/comments
| 1 |
2020-08-23T11:01:14Z
|
2020-10-28T14:57:41Z
|
https://github.com/Piwigo/Piwigo/issues/1215
| 684,161,553 | 1,215 |
[
"Piwigo",
"Piwigo"
] |
If you filter your user list and get only 4 users among your 300 users, if you "select all", Piwigo selects the 300, not the 4. Even if Piwigo tells you it selects the 300, it's a UX flaw in my opinion.
|
[user manager] select all does not care about current filter
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1214/comments
| 0 |
2020-08-22T10:38:52Z
|
2020-11-05T14:59:32Z
|
https://github.com/Piwigo/Piwigo/issues/1214
| 683,974,106 | 1,214 |
[
"Piwigo",
"Piwigo"
] |
can't use the community upload form nor the admin upload form because piwigo claims I don't ahve html5 on my phone
|
Issue with uploading images from an ios device
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1213/comments
| 5 |
2020-08-15T16:06:15Z
|
2020-12-03T15:56:43Z
|
https://github.com/Piwigo/Piwigo/issues/1213
| 679,601,192 | 1,213 |
[
"Piwigo",
"Piwigo"
] |
Change in functions :
function pwg_db_concat($array)
function pwg_db_concat_ws($array, $separator)
from
$string = implode( $array,',');
to
$string = implode( ',', $array);
|
implode(): Passing glue string after array is deprecated.
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1212/comments
| 0 |
2020-08-14T08:53:32Z
|
2020-08-14T08:53:32Z
|
https://github.com/Piwigo/Piwigo/issues/1212
| 679,009,109 | 1,212 |
[
"Piwigo",
"Piwigo"
] |
In the actual version of Piwigo, the relation between image/album, album/sub-album, group/user are not available in the addition, movement and deletions activities.
It could be useful for creating activity log's pages.
I suggest add object's id in details of these activities.
|
Cannot get relations between objects in Piwigo activities
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1211/comments
| 2 |
2020-08-13T13:29:12Z
|
2020-09-28T21:59:13Z
|
https://github.com/Piwigo/Piwigo/issues/1211
| 678,438,062 | 1,211 |
[
"Piwigo",
"Piwigo"
] |
Based on Hannah's mock up
|
Creation of an Album Activity Log Page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1210/comments
| 0 |
2020-08-13T12:08:13Z
|
2020-08-13T12:08:13Z
|
https://github.com/Piwigo/Piwigo/issues/1210
| 678,386,232 | 1,210 |
[
"Piwigo",
"Piwigo"
] |
Hi!
I would like to report an issue I discovered while using Piwigo. As the title says if you use "@" character in quick search, Piwigo stops with SQL error:
PHP message: PHP Warning: [mysql error 1064] syntax error, unexpected '@', expecting $end
SELECT * FROM piwigo_tags
WHERE (MATCH(name) AGAINST( '@xxxx @xxx' IN BOOLEAN MODE)) in /xxx/include/dblayer/functions_mysqli.inc.php...
Piwigo is the last official version.
I hope it will be easy to fix.
Thanks!
PS: Thank you for this great software :-)
UPDATE: I think I found the reason, I'm using InnoDB and @ is reserved in fulltext search. Anyway is there some way how to fix it and still using InnoDB?
|
"@" in quick search causes SQL error
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1209/comments
| 0 |
2020-08-12T19:09:32Z
|
2020-08-12T20:13:50Z
|
https://github.com/Piwigo/Piwigo/issues/1209
| 677,913,896 | 1,209 |
[
"Piwigo",
"Piwigo"
] |
New design for edit album page, mock-up by Hannah
|
Redesign Album Edition
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1208/comments
| 0 |
2020-08-10T08:56:15Z
|
2020-09-28T14:21:36Z
|
https://github.com/Piwigo/Piwigo/issues/1208
| 675,976,012 | 1,208 |
[
"Piwigo",
"Piwigo"
] |
Hello,
I'm from Germany and as you know we use ö ä ü and other special keys, that now leads to a problem, over 600 files cannot be imported because the name is not correct...
But I think it's stupid to make Köln, to Koeln , or to make Attila & Luan, Attila_and_Luan, is there a way to use special characters?
|
German language
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1207/comments
| 3 |
2020-08-08T22:32:26Z
|
2020-08-21T09:54:27Z
|
https://github.com/Piwigo/Piwigo/issues/1207
| 675,598,486 | 1,207 |
[
"Piwigo",
"Piwigo"
] |
Redesign Album List page for a "card" design, mock-up by Samuel
|
Redesign Album List Page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1206/comments
| 0 |
2020-08-04T13:40:55Z
|
2020-09-28T14:21:56Z
|
https://github.com/Piwigo/Piwigo/issues/1206
| 672,800,300 | 1,206 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.