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,
It would be nice to share the albums under:
mydomain.com/albumname
instead of
mydomain.com/index.php?/category/albumname
|
Friendly URL for Album URL address
|
https://api.github.com/repos/Piwigo/Piwigo/issues/949/comments
| 2 |
2018-12-05T17:15:46Z
|
2024-01-09T02:00:23Z
|
https://github.com/Piwigo/Piwigo/issues/949
| 387,860,086 | 949 |
[
"Piwigo",
"Piwigo"
] |
Just upgraded to latest version of Piwigo and get this error. can no longer access admin or even see images on site.
|
upgraded to Latest got [mysql error 1054] Unknown column 'rank' in 'order clause'
|
https://api.github.com/repos/Piwigo/Piwigo/issues/948/comments
| 7 |
2018-12-02T15:45:08Z
|
2019-08-30T09:55:28Z
|
https://github.com/Piwigo/Piwigo/issues/948
| 386,571,413 | 948 |
[
"Piwigo",
"Piwigo"
] |
There are plugins out there setting $page['section'] to something own, like the the Guestbook plugin or the Contactform.
This causes problems with pwg_log. pwg_log only checks of a section was given, and if so it pushed the new row to the database. Now mysql.history.section is an enum with the members
'categories','tags','search','list','favorites','most_visited','best_rated','recent_pics','recent_cats','additional_page'
This means, the insert fails and prints an ugly warning to the Piwigo page.
Of course IMO it is bad style to abuse section this way, maybe this is based on historic grounds. However, the issue is there and is live. I guess people will not recognize it since it is just a warning which is not shown in most productive environments.
`Warning: [mysql error 1265] Data truncated for column 'section' at row 1
INSERT INTO piwigo_history
(
date,
time,
user_id,
IP,
section,
category_id,
image_id,
image_type,
format_id,
auth_key_id,
tag_ids
)
VALUES
(
CURRENT_DATE,
CURRENT_TIME,
2,
'192.168.0.22',
'guestbook',
NULL,
NULL,
NULL,
NULL,
NULL,
NULL
)
; in /media/sf_piwigo/include/dblayer/functions_mysqli.inc.php on line 845`
But it is still a bug. In my opinion this should be fixed by a check inside pwg_log, if the given section is part of the enum. If it is not, just null it and pwg_log will go on. By doing so, all these plugins don't have to be rewritten.
BR,
Peter
|
pwg_log is not checking if given $page['section'] is part of the enum in the table
|
https://api.github.com/repos/Piwigo/Piwigo/issues/945/comments
| 1 |
2018-11-25T22:32:05Z
|
2019-04-08T15:58:33Z
|
https://github.com/Piwigo/Piwigo/issues/945
| 384,126,296 | 945 |
[
"Piwigo",
"Piwigo"
] |
The current definition of IP field in history table is
`IP` VARCHAR(15)
(from upgrade_1.6.2.php if i am correct)
which is fine for IPv4 but IPv6 are 39 characters longs and cannot be stored
|
[history] IPv6 cannot be stored
|
https://api.github.com/repos/Piwigo/Piwigo/issues/942/comments
| 2 |
2018-11-01T12:33:34Z
|
2024-07-31T15:16:05Z
|
https://github.com/Piwigo/Piwigo/issues/942
| 376,374,003 | 942 |
[
"Piwigo",
"Piwigo"
] |
Hi,
I had a problem to allow guest to rate pictures. My Piwigo is behind a reverse proxy. All of guests are recognized as same user (even if there ip changes).
I looked at the code. I replaced `$_SERVER["REMOTE_ADDR"]);` with `$_SERVER["HTTP_X_FORWARDED_FOR"]);` and deleted the block
```
if (count($ip_components) > 3)
{
array_pop($ip_components);
}
```
in file functions_rate.inc.php, picture_rate.inc.php, functions.inc.php and functions_session.inc.php
It's just a little patch to correct the bug, but does it plane to manage reverse proxy or not in this situation ?
Regards
|
rate behind reverse proxy
|
https://api.github.com/repos/Piwigo/Piwigo/issues/941/comments
| 0 |
2018-10-29T17:15:14Z
|
2018-10-29T17:15:14Z
|
https://github.com/Piwigo/Piwigo/issues/941
| 375,125,257 | 941 |
[
"Piwigo",
"Piwigo"
] |
Can move a batch of photos in the manual sort
|
manual sorting
|
https://api.github.com/repos/Piwigo/Piwigo/issues/940/comments
| 0 |
2018-10-27T08:46:44Z
|
2018-10-27T08:46:44Z
|
https://github.com/Piwigo/Piwigo/issues/940
| 374,622,840 | 940 |
[
"Piwigo",
"Piwigo"
] |
Hi,
Just setup piwigo to move from Google Photos at the moment I use fuse to mount GDrive to a network drive then have sym link in ./galleries
Everything seems to be working apart from Apache error 408 timeout have cleared all timeout config from apache/PHP & mysql and still have same issue.
Can someone help....I do believe it to be as their are 20,000 odd photos to sync....if anyone can suggest a better way would be thank full.
|
Uploading Pictures (FTP seems to crash-408 timeout in Apache logs)
|
https://api.github.com/repos/Piwigo/Piwigo/issues/939/comments
| 1 |
2018-10-26T09:12:37Z
|
2018-10-26T09:14:18Z
|
https://github.com/Piwigo/Piwigo/issues/939
| 374,294,324 | 939 |
[
"Piwigo",
"Piwigo"
] |
I realized pictures taken from for instance Huawei mobile phones do not have creation date in piwigo. There is just NULL in date_creation column in piwigo_images database table. This is bad as then features like grouping by creation date does not work properly.
You can test on some samples: https://www.flickr.com/photos/146228843@N02/sets/72157677734463334/
|
Exif creation date is not saved for photos taken by certain devices (Huawei)
|
https://api.github.com/repos/Piwigo/Piwigo/issues/938/comments
| 9 |
2018-10-26T07:36:57Z
|
2018-10-29T05:54:54Z
|
https://github.com/Piwigo/Piwigo/issues/938
| 374,262,628 | 938 |
[
"Piwigo",
"Piwigo"
] |
Configuring all my albums by copying/deleting/moving images and folders in galleries folder.
Every hour a script does syncing automatically. (https://github.com/pommes-frites/piwigo-scripts/issues/2)
Now I miss the ability to set a default group to a new created parent PARENT/ROOT category/album.
With "newcat_default_status" album is set private and with "inheritance_by_default":
```
// newcat_default_status : at creation, must a category be public or private
// ? Warning : if the parent category is private, the category is
// automatically create private.
$conf['newcat_default_status'] = 'private';
// https://github.com/Piwigo/Piwigo/issues/892
// Set groupacess for child-categories
$conf['inheritance_by_default'] = true;
```
all children inherit the parents group permission.
I would need a new parameter to set parent's default_group, like:
`$conf['rootcat_default_group'] = 'anyUserGroup';`
Or is there another way to do this? A script or a unknown config parameter?
Thank You!
|
Configure default permission/group when creating new PARENT category/album
|
https://api.github.com/repos/Piwigo/Piwigo/issues/937/comments
| 0 |
2018-10-25T09:29:12Z
|
2018-10-25T11:54:38Z
|
https://github.com/Piwigo/Piwigo/issues/937
| 373,854,819 | 937 |
[
"Piwigo",
"Piwigo"
] |
I get this warning after installing a new galley (piwigo-2.9.4) on the server. When I try to find the reason for this warning, I found one syntax error in the file "\admin\themes\clear\themeconf.inc.php" on the line number six:
'colorscheme' => 'clear', <redundant comma at the end of line>
|
Warning: Cannot modify header information - headers already sent by (...\piwigo\admin\themes\clear\themeconf.inc.php)
|
https://api.github.com/repos/Piwigo/Piwigo/issues/935/comments
| 0 |
2018-10-23T16:22:57Z
|
2018-10-23T16:23:53Z
|
https://github.com/Piwigo/Piwigo/issues/935
| 373,086,672 | 935 |
[
"Piwigo",
"Piwigo"
] |
Warning: [mysql error 1146] Table 'hdpics_piwi767.piwiyr_comments_categories' doesn't exist
SELECT COUNT(*)
FROM piwiyr_comments_categories
; in /home/hdpics/public_html/include/dblayer/functions_mysqli.inc.php on line 845
Fatal error: Uncaught Error: Call to a member function fetch_row() on boolean in /home/hdpics/public_html/include/dblayer/functions_mysqli.inc.php:231 Stack trace: #0 /home/hdpics/public_html/plugins/Comments_on_Albums/include/events.inc.php(35): pwg_db_fetch_row(false) #1 /home/hdpics/public_html/include/functions_plugins.inc.php(279): coa_admin_intro() #2 /home/hdpics/public_html/admin.php(311): trigger_notify('loc_begin_admin...') #3 {main} thrown in /home/hdpics/public_html/include/dblayer/functions_mysqli.inc.php on line 231
|
getting this error code while entering admin dashboard alone(/admin.php) ,using many plugins
|
https://api.github.com/repos/Piwigo/Piwigo/issues/934/comments
| 3 |
2018-10-14T08:41:28Z
|
2019-04-12T13:27:24Z
|
https://github.com/Piwigo/Piwigo/issues/934
| 369,881,043 | 934 |
[
"Piwigo",
"Piwigo"
] |
On servers using for example fr_FR.UTF-8 file system encoding, Piwigo API methods return non percent-encoded URLs (containing spaces, accentuated characters, etc.). This requires third party apps to "guess" how to percent-encode each URL so that images can be downloaded.
So would it be possible to [percent-encode URLs](url
https://tools.ietf.org/html/rfc3986#section-2) so that Piwigo always returns RFC compliant URIs whichever file system encoding is used?
|
[web API] returns non RFC compliant URLs
|
https://api.github.com/repos/Piwigo/Piwigo/issues/933/comments
| 0 |
2018-10-13T17:52:14Z
|
2019-05-12T17:35:59Z
|
https://github.com/Piwigo/Piwigo/issues/933
| 369,825,154 | 933 |
[
"Piwigo",
"Piwigo"
] |
Recently we've noticed that new pictures uploaded to our gallery have an incorrectly sized watermark on the thumbnails.. This is most noticable for the thumbnails used for the album preview.
When you get to the original sized image, the watermark is displayed
This is happening on at least two galleries at (http://www.mylittlecakeco.co.uk/) and an internal test gallery . Deleting the images and/or gallerties have no effect,
Both sites are running v2.9.4 and there have been no changes to the sites other than updates
It also does not appear to be a plugin/theme conflict as the internal site has no plugins installed on it.
The watermark in use has not been changed since the site was launched.
|
Watemark not rescaling for thumbnails
|
https://api.github.com/repos/Piwigo/Piwigo/issues/932/comments
| 2 |
2018-10-13T15:01:18Z
|
2019-01-09T13:58:03Z
|
https://github.com/Piwigo/Piwigo/issues/932
| 369,810,008 | 932 |
[
"Piwigo",
"Piwigo"
] |
Greetings! The University IT Security office scans our systems using a Nessus System. They seem pretty worked up over the result below. Any assistance would be appreciated. **We are running Piwigo 2.94.**
High and Critical Risk Vulnerability Details
Nessus Plugin 42424
SQL Injection (blind)
Plugin Output:
Using the GET HTTP method, Nessus found that :
+ The following resources may be vulnerable to blind SQL injection :
+ The 'redirect' parameter of the /identification.php CGI :
/identification.php?username=&login=Submit&password=&remember_me=1&redir
ect=zz&login=Submit&password=&remember_me=1&redirect=yy
-------- output --------
</nav>
-------- vs --------
</nav>
<div class="container-fluid">
<div class="alert alert-danger alert-dismissible fade show" ro [...] <button type="button"
class="close" data-dismiss="alert">< [...]
------------------------
Synopsis: A CGI application hosted on the remote web server is potentially prone to SQL injection
attack.
Description: By sending specially crafted parameters to one or more CGI scripts hosted on the
remote web server, Nessus was able to get a very different response, which suggests that it may
have been able to modify the behavior of the application and directly access the underlying
database.
An attacker may be able to exploit this issue to bypass authentication, read confidential data,
modify the remote database, or even take control of the remote operating system.
Note that this script is experimental and may be prone to false positives. Solution: Modify the
affected CGI scripts so that they properly escape arguments. First Discovered: Jan 25, 2018
13:33:20 CST
Last Observed: Sep 26, 2018 23:43:07 CDT
Exploit Frameworks:
|
Possible CGI Generic SQL Injection - From Experimental Nessus script
|
https://api.github.com/repos/Piwigo/Piwigo/issues/930/comments
| 0 |
2018-09-28T15:09:38Z
|
2018-09-28T15:09:38Z
|
https://github.com/Piwigo/Piwigo/issues/930
| 364,930,298 | 930 |
[
"Piwigo",
"Piwigo"
] |
Based on this french report http://fr.piwigo.org/forum/viewtopic.php?pid=224646#p224646 Freegeoip seems to no longer work.
|
[history] geolocalization based on IP (freegeoip) no longer works
|
https://api.github.com/repos/Piwigo/Piwigo/issues/928/comments
| 0 |
2018-09-25T08:37:00Z
|
2018-09-25T08:37:00Z
|
https://github.com/Piwigo/Piwigo/issues/928
| 363,467,334 | 928 |
[
"Piwigo",
"Piwigo"
] |
I am unable to login - even though I am using the Username and password sent to me by email.
|
Unable to login
|
https://api.github.com/repos/Piwigo/Piwigo/issues/927/comments
| 0 |
2018-09-17T16:49:02Z
|
2020-10-16T08:02:42Z
|
https://github.com/Piwigo/Piwigo/issues/927
| 360,954,660 | 927 |
[
"Piwigo",
"Piwigo"
] |
Progress bar plugin
|
https://api.github.com/repos/Piwigo/Piwigo/issues/926/comments
| 1 |
2018-09-16T06:18:09Z
|
2019-01-09T08:40:31Z
|
https://github.com/Piwigo/Piwigo/issues/926
| 360,608,353 | 926 |
|
[
"Piwigo",
"Piwigo"
] |
Hi,
I have a problem with users mails, they received links to :
> X new photos [url is **http**]
> X albums updates [url **http**]
>
> Go to _gallery_ [url is https]
>
> unsubscribe [url https]
> subscribe [url https]
then in the details
> 1 new photo (recent) [url **http**]
> (photo thumb) [url **http**]
and so on.
for some reason I can't expose the 80 port so my users have to know that they have to copy / paste url in mails to change http to **https.**
I have the same problem with the **"forgot password"** url in mail.
> user"xxx" on gallery https://_public_domain_name_
>
> to renew ... :
> **http**://_public_domain_name/xxxxxxx_
>
> ----
> send by "_gallery_name_" https://_public_domain_name_"
my configuration is a little bit complex :
- piwigo on docker, **mathieuruellan** (_2 dockers, piwigo + mysql 5.5_)
- piwigo docker port mapping is **9443:80**
- docker on synology DS916+
- synology with HSTS
- synology embeded nginx
- certificate let's encrypt with multiple domain names
- reverse proxy DSM rule : https://_piwigo_public_domain_name_:443 ==> http://_local_address_:9443
- adding a rule to reverse piwigo on 80 to 443 bypass the https connection and the certificate
- force https plugin cause too many redirection problem (loop)
- port 80 & 443 used by synology internal, so I can't use it
https URLs in mail have been forced with the
> $conf['gallery_url'] = _https://public_domain_name_
so the option updates only some url in the mail generation
piwigo environment :
- Piwigo 2.9.4
- Système d'exploitation: Linux (_in real PRETTY_NAME="Debian GNU/Linux 9 (stretch)" NAME="Debian GNU/Linux" VERSION_ID="9" VERSION="9 (stretch)"_)
- PHP: 7.2.9-1+0~20180901081133.4+stretch~1.gbpdaac35 (_the image came with 7.0, update to latest version yesterday_)
- MySQL: 5.5.61 [2018-09-07 14:52:49]
- Bibliothèque graphique: External ImageMagick 6.9.7-4
thanks
|
$conf['gallery_url'] not update all URLs in mail generation
|
https://api.github.com/repos/Piwigo/Piwigo/issues/924/comments
| 0 |
2018-09-07T15:03:42Z
|
2018-09-07T15:08:12Z
|
https://github.com/Piwigo/Piwigo/issues/924
| 358,103,408 | 924 |
[
"Piwigo",
"Piwigo"
] |
I did a fresh install on a new server, Ubuntu 18.04. The install went fine and I landed on the admin page. However, when I tried to create my first album, I got:
SyntaxError: JSON Parse error: Unrecognized token '<'
There was no JSON or HTML manually entered by me. I merely gave the album a name and hit "create."
|
JSON parse error
|
https://api.github.com/repos/Piwigo/Piwigo/issues/923/comments
| 2 |
2018-09-05T21:26:30Z
|
2023-01-24T08:36:42Z
|
https://github.com/Piwigo/Piwigo/issues/923
| 357,410,455 | 923 |
[
"Piwigo",
"Piwigo"
] |
Hi
I have set my upload folder to a symbolic link to an attached volume. The file upload seems to work, I get the green tick and I can download the file successfully. However the thumbnails are not displaying
in the admin or in the front end. When I copy the thumbnail url from the admin, the page has this error:
`Db file path not found`
Any ideas?
Thanks for your help.
|
No thumbnails: thumbnail url shows error 'Db file path not found'
|
https://api.github.com/repos/Piwigo/Piwigo/issues/921/comments
| 1 |
2018-08-29T08:01:42Z
|
2018-09-17T14:28:38Z
|
https://github.com/Piwigo/Piwigo/issues/921
| 355,043,028 | 921 |
[
"Piwigo",
"Piwigo"
] |
When I go to upload a file using the webform, nothing happens. The uploader just sits there and spins. I get the following error in the console.
Version 2.9.4
```javascript
SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data[Learn More]
jquery.min.js:5:15991
TypeError: uploadCategory is null[Learn More]
```
|
File Upload Hangs
|
https://api.github.com/repos/Piwigo/Piwigo/issues/920/comments
| 11 |
2018-08-28T11:28:29Z
|
2023-05-05T09:40:41Z
|
https://github.com/Piwigo/Piwigo/issues/920
| 354,688,328 | 920 |
[
"Piwigo",
"Piwigo"
] |
Warning: [mysql error 1064] You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ', status
FROM piwigo_categories
WHERE id_uppercat IS NULL
ORDER BY rank AS' at line 1
SELECT id, name, permalink, dir, **rank**, status
FROM piwigo_categories
WHERE id_uppercat IS NULL
ORDER BY rank ASC
; in D:\www_root\piwigo-2.9.4\include\dblayer\functions_mysqli.inc.php on line 845
**piwigo version: 2.9.4**
**mysql version: 8.0.11**
|
"rank" becomes a mysql reserved keyword in version 8
|
https://api.github.com/repos/Piwigo/Piwigo/issues/919/comments
| 9 |
2018-08-25T12:07:55Z
|
2019-10-13T11:15:46Z
|
https://github.com/Piwigo/Piwigo/issues/919
| 354,007,605 | 919 |
[
"Piwigo",
"Piwigo"
] |
Following #917 , could it be also possible to create an API with which an external app could change the album photo sort order ?
|
Set album photo sort order with new API
|
https://api.github.com/repos/Piwigo/Piwigo/issues/918/comments
| 1 |
2018-08-20T10:22:57Z
|
2024-07-31T15:16:04Z
|
https://github.com/Piwigo/Piwigo/issues/918
| 352,073,271 | 918 |
[
"Piwigo",
"Piwigo"
] |
The `pwg.categories.getList` method does not return the album photo sort order choosen by the user with the web UI and stored on the server, preventing external apps to adopt it. Could this be implemented as requested [here](https://github.com/Piwigo/Piwigo-Mobile/issues/242) ?
|
Return album photo sort order with API pwg.categories.getList
|
https://api.github.com/repos/Piwigo/Piwigo/issues/917/comments
| 8 |
2018-08-20T10:19:26Z
|
2023-07-05T09:14:36Z
|
https://github.com/Piwigo/Piwigo/issues/917
| 352,072,008 | 917 |
[
"Piwigo",
"Piwigo"
] |
The iOS app downloads images from their URLs and visits are not seen in the stats of the server. Would it be possible to provide an API allowing third party apps to update stats? These data could be sent automatically to the server when the user closes the app.
|
API for updating statistics on server
|
https://api.github.com/repos/Piwigo/Piwigo/issues/916/comments
| 1 |
2018-08-20T07:21:35Z
|
2023-08-03T09:20:37Z
|
https://github.com/Piwigo/Piwigo/issues/916
| 352,013,675 | 916 |
[
"Piwigo",
"Piwigo"
] |
... instead of permissions by photos. With some experience at helping users on Piwigo, I'm confident we should not recommend using permissions by photos until they understand/masterize permissions by albums. Thus we should, at least puth the "permissions by album" on first position on the [Administration > Help me > Permissions] page.
|
[help] put permissions by album first
|
https://api.github.com/repos/Piwigo/Piwigo/issues/915/comments
| 1 |
2018-08-17T15:52:39Z
|
2019-02-01T13:11:29Z
|
https://github.com/Piwigo/Piwigo/issues/915
| 351,647,306 | 915 |
[
"Piwigo",
"Piwigo"
] |
There is a static call to `Smarty_Internal_Debug::display_debug` on `template.class.php` file, line 586.
It rises an error and it prevent showing smarty debug popup when logged in as admin.
|
Calling non-static method `Smarty_Internal_Debug::display_debug`
|
https://api.github.com/repos/Piwigo/Piwigo/issues/912/comments
| 2 |
2018-08-13T14:23:55Z
|
2023-01-03T00:19:59Z
|
https://github.com/Piwigo/Piwigo/issues/912
| 350,052,077 | 912 |
[
"Piwigo",
"Piwigo"
] |
If your default theme is "elegant", and a mobile device browse the gallery, there is no history log for this device, despite the use of "smart pocket" mobile theme.
The solution may be in the answer of "How can we get run add_event_handler('ws_add_methods', 'sp_add_methods'); from themes/smartpocket/themeconf.inc.php **_earlier_** ?"
|
No mobile history log when mobile theme not default
|
https://api.github.com/repos/Piwigo/Piwigo/issues/911/comments
| 1 |
2018-08-10T15:36:43Z
|
2022-08-26T14:58:46Z
|
https://github.com/Piwigo/Piwigo/issues/911
| 349,562,914 | 911 |
[
"Piwigo",
"Piwigo"
] |
I'm new to Piwigo and imagine my confusion when I tried to upload images and it didn't work. I did some extensive debugging before realising that there wasn't ever any issue, just some very unfortunate UX design.
|
Very confusing UX design regarind the progress of uploading images
|
https://api.github.com/repos/Piwigo/Piwigo/issues/909/comments
| 6 |
2018-08-08T22:34:42Z
|
2019-05-21T21:00:34Z
|
https://github.com/Piwigo/Piwigo/issues/909
| 348,916,325 | 909 |
[
"Piwigo",
"Piwigo"
] |
<p>Having difficulty viewing photo album after iOS update to force HTTPS. Cannot view any thumbnails or album title photos - the whole album is visible but the thumbnails are just greyed out broken links.
Have checked whole website and now receive a Secure padlock on all website & piwigo pages when using a web browser. </p>Have also installed Force_HTTPS plugin but receive an error stating 'Your hosting server does not support HTTPS, a SSL certificate is required. Plugin activation is disabled.' even though I have a Secure padlock on the site when I attempt to configure the plugin. The certificate is valid through entire cert chain.<p>
I have spent many evenings trying to resolve the iOS app issue and have reached the end of my knowledge on what to try next. I would be interested to mail some private screenshots or let a moderator look at the site to diagnose the issue if possible.</p> The iOS photo album worked flawlessly before the upgrade to forced https url address.
|
iOS App No Longer Shows Photo Thumbnails or Album Photos after Force HTTPS Upgrade
|
https://api.github.com/repos/Piwigo/Piwigo/issues/908/comments
| 3 |
2018-08-07T22:57:16Z
|
2018-09-07T15:35:01Z
|
https://github.com/Piwigo/Piwigo/issues/908
| 348,515,708 | 908 |
[
"Piwigo",
"Piwigo"
] |
Currently installed version 2.9.4.
Like for other applications, I used to install plugins in external folder.
For example fr the plugin ldap_login, I have something like the following.
A folder where I store all versions for the plugin :
/var/opt/piwigo/common/apps-available/Ldap_Login
I put each version in a sub folder with the version number, like 1.1, 1.2, 2.0, 2.1
Then in the folder /var/opt/piwigo/common/apps-enabled, I put a link to the expected version, like this :
ldap_login -> /var/opt/piwigo/common/apps-available/Ldap_Login/1.2.1/
Then, I just have to set symoblic links in the Piwigo instance to links put in /var/opt/piwigo/common/apps-enabled
But with this structure, the plugin is not detected by Piwigo. I must put the extension physically in the instance.
Could it be possible to mangae symbolic links to load extensions ?
|
Plugins loading failed when installed throw symbolic links
|
https://api.github.com/repos/Piwigo/Piwigo/issues/907/comments
| 2 |
2018-08-06T11:16:01Z
|
2018-08-07T19:30:33Z
|
https://github.com/Piwigo/Piwigo/issues/907
| 347,881,503 | 907 |
[
"Piwigo",
"Piwigo"
] |
Hi,
We're going to use Piwigo for building a big product image library, approx. 800,000 categories (incl. all sub-category), 5,000,000 photos at most.
I wonder if any issue on MySQL or Piwigo itself to limited hosting such in huge categories/photos on self-hosting server, any recommendations on the server hardware? Thanks!
Regards,
Niko Lee
|
How many category & photo can Piwigo hold in maximum?
|
https://api.github.com/repos/Piwigo/Piwigo/issues/906/comments
| 7 |
2018-07-31T06:58:15Z
|
2022-08-19T08:03:31Z
|
https://github.com/Piwigo/Piwigo/issues/906
| 346,058,941 | 906 |
[
"Piwigo",
"Piwigo"
] |
Hi
I want to set up a web photo gallery on my VPS. Then i can access the photos form my mobile phone via APP not webview.
So piwigo have provide APIs for query gallery and photo? I can write app to access.
Thanks!
|
Piwigo have provide APIs for mobile APP?
|
https://api.github.com/repos/Piwigo/Piwigo/issues/905/comments
| 1 |
2018-07-28T14:49:43Z
|
2018-08-14T06:35:51Z
|
https://github.com/Piwigo/Piwigo/issues/905
| 345,454,028 | 905 |
[
"Piwigo",
"Piwigo"
] |
In Piwigo 2.9.4 with PHP 7.2, you get this "deprecated" message:
> Deprecated: __autoload() is deprecated, use spl_autoload_register() instead in include\phpmailer\PHPMailerAutoload.php on line 45
the official answer from PHPMailer devs is on https://github.com/PHPMailer/PHPMailer/issues/981 : don't worry and update to PHPMailer 6.x. Unfortunately, PHPMailer 6 requires PHP 5.5. We can't upgrade this soon to such a PHP version.
We may have to have a specific change in Piwibo embedded PHPMailer 5.2.
|
PHPMailer __autoload() is deprecated
|
https://api.github.com/repos/Piwigo/Piwigo/issues/904/comments
| 1 |
2018-07-26T09:20:20Z
|
2019-06-21T13:03:17Z
|
https://github.com/Piwigo/Piwigo/issues/904
| 344,762,500 | 904 |
[
"Piwigo",
"Piwigo"
] |
On Piwigo 2.9.4, compared to 2.9.3, the users list can no longer be filtered and is not paginated. It always shows the complete list of users. If you have 15 users that's not a big problem. If you 20k users, it makes the user manager unusable.
The problem is due to a235a2e2296e515ac67e4e618d2c2e4a4fa58e19 : the use of "ajax" param instead of "ajaxsource" is the way to go to use the current API of Datatables, but it completely changes the way parameters are sent to admin/user_list_backend.php. Unfortunately, the user list was apparently working fine, I would have prefered it to completely crash: we would have seen the problem before releasing 2.9.4.
|
[2.9.4] users list no longer paginated or filtered
|
https://api.github.com/repos/Piwigo/Piwigo/issues/902/comments
| 1 |
2018-07-24T08:27:30Z
|
2019-04-02T12:22:28Z
|
https://github.com/Piwigo/Piwigo/issues/902
| 343,935,050 | 902 |
[
"Piwigo",
"Piwigo"
] |
If you have "use_exif_mapping" (or "use_iptc_mapping") set in your Piwigo config file, when you use the web interface to upload a file that has metadata already set, the metadata will be mapped into the appropriate image field in Piwigo's database. For example, by default, if you have the EXIF ImageDescription field set, that will become the title field when you upload that file into Piwigo. This is a big timesaver particularly if you are importing photos from some other software, or if you upload them into two places, because it saves you retyping the title.
But it doesn't work if you use the webservice interface. The behavior of the web interface and the webservice interface should be made consistent.
|
FIle upload webservice does not call hook to set title from metadata
|
https://api.github.com/repos/Piwigo/Piwigo/issues/900/comments
| 0 |
2018-07-20T15:01:00Z
|
2018-07-20T15:01:00Z
|
https://github.com/Piwigo/Piwigo/issues/900
| 343,141,281 | 900 |
[
"Piwigo",
"Piwigo"
] |
I may have missed something but I could not find API methods to add an image to favorites and to get the list of favorites. Could this be implemented in a not too far future?
|
Add API to manage Favorites
|
https://api.github.com/repos/Piwigo/Piwigo/issues/899/comments
| 6 |
2018-07-19T20:16:01Z
|
2019-07-17T13:59:01Z
|
https://github.com/Piwigo/Piwigo/issues/899
| 342,873,552 | 899 |
[
"Piwigo",
"Piwigo"
] |
Hi,
I just check changes for PHP7.2 and some code still need be updated. (not only for PHP7.2)
Like using list() when function arguments are array members (check [https://3v4l.org/kCFQC](https://3v4l.org/kCFQC) )
e.g. used [here](https://github.com/Piwigo/Piwigo/blob/843ccb89c1997d551bc1fb5769c5fdaad9655082/include/picture_rate.inc.php#L40)
|
PHP incompatibility changes
|
https://api.github.com/repos/Piwigo/Piwigo/issues/898/comments
| 2 |
2018-07-17T15:59:53Z
|
2018-07-23T13:21:35Z
|
https://github.com/Piwigo/Piwigo/issues/898
| 341,983,520 | 898 |
[
"Piwigo",
"Piwigo"
] |
We have received several user feedback after they update to version 2.9.4
> Parse error: syntax error, unexpected T_FUNCTION in include/dblayer/functions_mysqli.inc.php on line 403
As far as I understand, the problem is the PHP version still on 5.2. Piwigo 2.9.4 needs PHP 5.3 or higher (7.0+ recommended)
|
[2.9.4] unexpected T_FUNCTION in functions_mysqli.inc.php on line 403
|
https://api.github.com/repos/Piwigo/Piwigo/issues/897/comments
| 0 |
2018-07-16T16:59:21Z
|
2019-04-02T10:37:33Z
|
https://github.com/Piwigo/Piwigo/issues/897
| 341,599,038 | 897 |
[
"Piwigo",
"Piwigo"
] |
Hello, I download the zip file from GitHub, deploy it to my windows server, display the successful connection server on the installation page, but can not connect the database, I checked my MySQL is running normally, how do you deal with this problem?
Looking forward to an answer,
harry
|
When installing the system, the installation page shows the problem of not connecting to the database.
|
https://api.github.com/repos/Piwigo/Piwigo/issues/893/comments
| 3 |
2018-07-12T01:27:40Z
|
2019-12-21T09:39:54Z
|
https://github.com/Piwigo/Piwigo/issues/893
| 340,458,365 | 893 |
[
"Piwigo",
"Piwigo"
] |
On my Piwigo installation, I'm having issues with permissions, when creating child albums. Example:
The group "admin" has access permission for the parent album "A". Now, if I create a child album "B" within album A, I'd expect the group "admin" to have access to B. Instead, for both A and B, the admin-group is deleted from the list of permitted groups and all members of the admin-group are listed in the list of permitted users. I have to restore the settings for A and B using the "appley to child-albums" checkbox.
Since group-membership might change, this not a good behaviour.
I'm I doing something wrong/missing some settings or is this ab bug?
Looking forward to an answer,
Bibo
|
Unexpected Behavior Of Permissions On Creating New Child Album
|
https://api.github.com/repos/Piwigo/Piwigo/issues/892/comments
| 6 |
2018-07-11T15:18:25Z
|
2024-04-20T20:44:55Z
|
https://github.com/Piwigo/Piwigo/issues/892
| 340,289,611 | 892 |
[
"Piwigo",
"Piwigo"
] |
HTTPS has been recently added to Piwigo.org, we should have it in Piwigo footer.
|
link to piwigo.org should now be in HTTPS
|
https://api.github.com/repos/Piwigo/Piwigo/issues/891/comments
| 0 |
2018-07-11T13:10:47Z
|
2018-07-12T14:18:18Z
|
https://github.com/Piwigo/Piwigo/issues/891
| 340,235,286 | 891 |
[
"Piwigo",
"Piwigo"
] |
The screenshots on this page are directly loaded from `http://piwigo.org/screenshots/...`
If the Piwigo is using HTTPS, you will get a "mixed content" notice, warning the user the connection is unsecure.
|
http/https mixed content on [Admin > Photos > Add > Applications]
|
https://api.github.com/repos/Piwigo/Piwigo/issues/890/comments
| 0 |
2018-07-11T13:05:48Z
|
2018-07-12T14:18:34Z
|
https://github.com/Piwigo/Piwigo/issues/890
| 340,233,607 | 890 |
[
"Piwigo",
"Piwigo"
] |
On page [Admin > Users > Manage], with PHP 7.2, I get:
> Warning: count(): Parameter must be an array or an object that implements
> Countable in _data/templates_c/xxx.file.user_list.tpl.php on line 1092
|
PHP 7.2, warning on user manager
|
https://api.github.com/repos/Piwigo/Piwigo/issues/887/comments
| 0 |
2018-07-04T15:08:20Z
|
2018-07-04T15:11:20Z
|
https://github.com/Piwigo/Piwigo/issues/887
| 338,310,627 | 887 |
[
"Piwigo",
"Piwigo"
] |
trying to upload images using the piwigo app on ios I recently got those errors after upgrading from php 5.3 to 7.0
The same issue arise with php 5.6, 7.1 ...
Jun 30 05:20:24 www httpd: PHP Notice: Only variables should be passed by reference in /album/html/admin/include/functions_upload.inc.php on line 260
on the piwigo ios app side I got "impossible de lire les données car le format est incorrect"
|
Only variables should be passed by reference
|
https://api.github.com/repos/Piwigo/Piwigo/issues/886/comments
| 1 |
2018-06-30T04:21:11Z
|
2019-03-25T23:56:17Z
|
https://github.com/Piwigo/Piwigo/issues/886
| 337,185,305 | 886 |
[
"Piwigo",
"Piwigo"
] |
I have a lot (!) of orphaned images with no thumbnail and URLs return 404. About 40,000. When I search the file system for the file name in the URL, nothing comes up. I've done the inverse and found files on the file system that does get thumbnails.
Not sure what happened to the images, but I would at least want to remove the invalid file entries from the database. Does piwigo have this functionality, or do I have to do it manually in mysql?
|
Feature for removing db entries with an invalid file path
|
https://api.github.com/repos/Piwigo/Piwigo/issues/885/comments
| 1 |
2018-06-24T21:40:42Z
|
2022-12-16T09:56:53Z
|
https://github.com/Piwigo/Piwigo/issues/885
| 335,213,879 | 885 |
[
"Piwigo",
"Piwigo"
] |
After upgrading Ubuntu to 18.04 and PHP to 7.2 I get these errors/warnings.
Deprecated: Function create_function() is deprecated in /var/www/piwigo/include/functions.inc.php on line 2165
Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /var/www/piwigo/include/template.class.php on line 293.
|
The function create_function() is deprecated
|
https://api.github.com/repos/Piwigo/Piwigo/issues/883/comments
| 3 |
2018-06-16T18:15:01Z
|
2018-07-16T15:14:03Z
|
https://github.com/Piwigo/Piwigo/issues/883
| 333,005,103 | 883 |
[
"Piwigo",
"Piwigo"
] |
Hi,
I've finally done the jump from Piwigo version 2.7.4 to version 2.9.3 with a manual upgrade.
My few users can seen in the album permission settings, in the groups settings, but the user list is empty in the Users/manage with the indication "No data available in table".
If I remember well, even guest and admin users are supposed to be shown there.
The login of the users doesn't seem nevertheless to be a problem.
Interestingly it shows in the same time:
> Showing 0 to 0 of 0 entries
but as well:
> No User Selected out of 13
Piwigo 2.9.3
Système d'exploitation: Linux
PHP: 5.6.8 (Montrer les informations) [2018-06-15 09:55:12]
MySQL: 5.0.83 [2018-06-15 09:55:12]
Bibliothèque graphique: GD bundled (2.1.0 compatible)
Hosted by free.fr with the "preg_split" code modification.
|
No user in Users/manage: "No data available in table"
|
https://api.github.com/repos/Piwigo/Piwigo/issues/882/comments
| 12 |
2018-06-15T07:54:41Z
|
2019-02-05T08:33:56Z
|
https://github.com/Piwigo/Piwigo/issues/882
| 332,679,003 | 882 |
[
"Piwigo",
"Piwigo"
] |
Thought picture_ext and file_ext were changes to be case insensitive it does not appear anywhere in the config file.
Also they are infect have to be written lower cased in the config otherwise the extension wont work.
Probably should mention it in the config file that all extensions should be written lower cased only
|
doc: $conf['picture_ext'] case insensitive
|
https://api.github.com/repos/Piwigo/Piwigo/issues/881/comments
| 2 |
2018-06-12T12:59:07Z
|
2018-06-12T14:18:52Z
|
https://github.com/Piwigo/Piwigo/issues/881
| 331,576,825 | 881 |
[
"Piwigo",
"Piwigo"
] |
"Flat" looking thumbnails
|
https://api.github.com/repos/Piwigo/Piwigo/issues/880/comments
| 0 |
2018-06-11T18:52:45Z
|
2018-07-02T21:29:55Z
|
https://github.com/Piwigo/Piwigo/issues/880
| 331,307,775 | 880 |
|
[
"Piwigo",
"Piwigo"
] |
"Flat
|
https://api.github.com/repos/Piwigo/Piwigo/issues/879/comments
| 0 |
2018-06-11T18:49:45Z
|
2018-06-11T18:50:00Z
|
https://github.com/Piwigo/Piwigo/issues/879
| 331,306,791 | 879 |
|
[
"Piwigo",
"Piwigo"
] |
I cant login while I correctly installed Piwigo.
On all my browsers such as Chrome and Safari will show a message saying that I dont allow Cookies.
But when i check my prefrences, not any cookie is blocked.
So my question is can you fix this or how can i fix this?
|
Cookies are blocked issue
|
https://api.github.com/repos/Piwigo/Piwigo/issues/878/comments
| 7 |
2018-06-11T16:00:17Z
|
2024-01-18T13:42:42Z
|
https://github.com/Piwigo/Piwigo/issues/878
| 331,250,709 | 878 |
[
"Piwigo",
"Piwigo"
] |
The latest version of SMF forum has a "website_url" column in its users table. It breaks the SQL query in `include/picture_comment.inc.php`. The column should be prefixed to avoid any conflict.
|
conflict on website_url column with external user table
|
https://api.github.com/repos/Piwigo/Piwigo/issues/877/comments
| 0 |
2018-06-11T15:39:41Z
|
2018-07-11T09:50:25Z
|
https://github.com/Piwigo/Piwigo/issues/877
| 331,242,770 | 877 |
[
"Piwigo",
"Piwigo"
] |
Hi, I'm using Piwigo 2.9.0,
After uploading a mp4 video, it doesn't automatically generate a representative picture for the video, it just shows the mimetypes mp4 image at `plugins/piwigo-jplayer/mimetypes/mp4.png`
Any idea? Thanks.
|
Not automatically generate a representative picture for videos (mp4)
|
https://api.github.com/repos/Piwigo/Piwigo/issues/876/comments
| 1 |
2018-06-10T10:31:35Z
|
2018-06-11T02:59:49Z
|
https://github.com/Piwigo/Piwigo/issues/876
| 330,957,473 | 876 |
[
"Piwigo",
"Piwigo"
] |
The ws.php file is a target for cross-scripting attacks, I can rename it to hide it from attackers (of course I need to update which I use to access it). However, this breaks the admin interface as there are multiple places Piwigo's code where the ws.php name is hard-coded.
Could you implement an option, which would provide a way for users to rename the script and use a custom name without having to go through a dozen of source files?
|
Customize the name of the API handler (the ws.php script)
|
https://api.github.com/repos/Piwigo/Piwigo/issues/874/comments
| 2 |
2018-06-03T18:19:13Z
|
2018-07-06T12:09:32Z
|
https://github.com/Piwigo/Piwigo/issues/874
| 328,850,050 | 874 |
[
"Piwigo",
"Piwigo"
] |
I recently moved to Piwigo 2.9.2.
I have only enabled the following sizes in the config:
Square | 120 x 120 pixels, crop | edit
Thumbnail | 128 x 96 pixels | edit
M - medium | 1024 x 1024 pixels | edit
And Original.
Most my pictures are 22MP so even the JPEG are quite big.
Using the Mobile Theme for Tablets plugins, I forced the mobile version on my PC and checked what was happening with the FF Web Developer Console + Responsive mode.
It appears that the slideshow mode loads the original picture and not a lower size (even when faking a Galaxy S7 resolution). This means a huge amount of traffic for mobile user.
Clicking on "More Information" displays the -me.jpg file as expected.
Is this the intended behaviour ?
|
SmartPocket displays full resolution pictures in slideshow
|
https://api.github.com/repos/Piwigo/Piwigo/issues/873/comments
| 0 |
2018-06-01T08:01:17Z
|
2018-06-01T08:01:17Z
|
https://github.com/Piwigo/Piwigo/issues/873
| 328,419,016 | 873 |
[
"Piwigo",
"Piwigo"
] |
https://nvd.nist.gov/vuln/detail/CVE-2018-7724
```
The management panel in Piwigo 2.9.3 has stored XSS via the name parameter in a /admin.php?page=photo-${photo_number} request. CSRF exploitation, related to CVE-2017-10681, may be possible.
```
To avoid CSRF vulnerability pwg_token should be added, thanks. When you fix this vulnerability could you mention CVE in commit message, thank you.
|
CVE-2018-7724
|
https://api.github.com/repos/Piwigo/Piwigo/issues/872/comments
| 0 |
2018-05-23T08:47:35Z
|
2018-07-06T12:40:25Z
|
https://github.com/Piwigo/Piwigo/issues/872
| 325,607,398 | 872 |
[
"Piwigo",
"Piwigo"
] |
https://nvd.nist.gov/vuln/detail/CVE-2018-7722
> The management panel in Piwigo 2.9.3 has stored XSS via the name parameter in
> a /ws.php?format=json request. CSRF exploitation, related to CVE-2017-10681,
> may be possible.
From discussion with developer:
> The best one would be to add a required parameter pwg_token, but it would break
> remote apps (like the iOS app) which is more a problem than a solution. So we will
> escape any JS in the "name" parameter.
When you fix this vulnerability could you mention CVE in commit message, thank you.
|
CVE-2018-7722
|
https://api.github.com/repos/Piwigo/Piwigo/issues/871/comments
| 3 |
2018-05-23T08:46:36Z
|
2018-07-06T16:51:05Z
|
https://github.com/Piwigo/Piwigo/issues/871
| 325,607,029 | 871 |
[
"Piwigo",
"Piwigo"
] |
One of our users was surprised to get their password e-mailed to them upon registration, since they had left the default "Send my connection settings by email" checked. They had interpreted it to mean "use this email address to send password reset links."
It would be useful if this were changed (at least in the en_US language) to something like "Email me a copy of my username and password"
|
Improve "Send my connection settings by email" text
|
https://api.github.com/repos/Piwigo/Piwigo/issues/870/comments
| 2 |
2018-05-20T20:36:21Z
|
2022-05-26T09:15:58Z
|
https://github.com/Piwigo/Piwigo/issues/870
| 324,740,578 | 870 |
[
"Piwigo",
"Piwigo"
] |
hi,
i find a issue in my piwigo installation, i have a plugin proctected album (V0.5.b), i set a password for control access for some album.
but when in the right menu, in the special section, i click in to random photo, the piwigo see me (when i m not loged,piwigo see me as a guest) some photo in the protected album.
i don't know if you are the right interlocutor
ps : i french, if it is more easy in french no prob... my english is so bad ^^
|
[BUG] all picture accessible with random photo function with plugin protected album
|
https://api.github.com/repos/Piwigo/Piwigo/issues/869/comments
| 1 |
2018-05-20T20:17:17Z
|
2018-05-20T21:05:17Z
|
https://github.com/Piwigo/Piwigo/issues/869
| 324,738,777 | 869 |
[
"Piwigo",
"Piwigo"
] |
Hello,
Windows uses a rescaling factor (i.e. zoom of 125%) in order to display objects on relative small screen with high resolution.
https://www.thurrott.com/windows/windows-10/4597/windows-10-feature-focus-display-scaling
Due to this feature the people with high resolution screen see piwigo photos blurry.
Are there any chances to implement ` window.devicePixelRatio` to restore right image size?
https://www.jeffersonscher.com/res/resolution.php
|
Blurry photo due to pixel ratio
|
https://api.github.com/repos/Piwigo/Piwigo/issues/868/comments
| 0 |
2018-05-10T18:54:04Z
|
2018-05-10T18:54:19Z
|
https://github.com/Piwigo/Piwigo/issues/868
| 322,042,447 | 868 |
[
"Piwigo",
"Piwigo"
] |
Piwigo 2.9.3 is still marked as compatible with PHP 5.2. Oldest officially maintained branch is PHP 5.6. Wordpress.org statistics https://wordpress.org/about/stats/ currently says that 5.4+ is 89% of users and 5.5+ is 76%.
I think increasing the required version to 5.4 is "nearly painless".
|
increase PHP version required (to 7.0)
|
https://api.github.com/repos/Piwigo/Piwigo/issues/867/comments
| 9 |
2018-05-09T20:51:56Z
|
2021-08-02T17:17:07Z
|
https://github.com/Piwigo/Piwigo/issues/867
| 321,722,165 | 867 |
[
"Piwigo",
"Piwigo"
] |
As far as I understood, derivative pictures are 'encoded' after html upload in order to protect derivatives from being guessed.
It is not possible when the pictures are uploaded through ftp and then synchronised.
Many thanks.
DéHème
|
Derivative pictures encoding when uploaded through ftp
|
https://api.github.com/repos/Piwigo/Piwigo/issues/865/comments
| 0 |
2018-05-06T17:18:16Z
|
2018-05-06T17:18:16Z
|
https://github.com/Piwigo/Piwigo/issues/865
| 320,610,323 | 865 |
[
"Piwigo",
"Piwigo"
] |
As far as there is no private link, keys for automatic authentication is an elegant way to notify people watching a set of pictures/albums.
However management of those links is missing :
- list
- date created
- date expired
- extension ( new date)
- reset
- renew
....
By the way, quasi redundant functions (share picture, share album, collection, event cats, notifications) could be revisited to provide better integration.
Many thanks.
|
Management of keys for automatic authentication
|
https://api.github.com/repos/Piwigo/Piwigo/issues/864/comments
| 0 |
2018-05-06T17:05:15Z
|
2018-05-06T17:05:15Z
|
https://github.com/Piwigo/Piwigo/issues/864
| 320,609,339 | 864 |
[
"Piwigo",
"Piwigo"
] |
When there 0 photos to album who has only sub album
if there's 1 thumbnails has Album thumbnail
if you clic delete > serious error on pwg.categories.deleteRepresentative
and Album thumbnail isn't delete
it's possible to delete on photo page
|
serious error on pwg.categories.deleteRepresentative.
|
https://api.github.com/repos/Piwigo/Piwigo/issues/863/comments
| 0 |
2018-04-26T18:39:49Z
|
2019-02-01T15:38:55Z
|
https://github.com/Piwigo/Piwigo/issues/863
| 318,150,689 | 863 |
[
"Piwigo",
"Piwigo"
] |
It would be good if the albums title, description, comments on albums and photos will be included to the search results
|
Extend search
|
https://api.github.com/repos/Piwigo/Piwigo/issues/862/comments
| 2 |
2018-04-25T20:37:46Z
|
2024-03-17T17:02:09Z
|
https://github.com/Piwigo/Piwigo/issues/862
| 317,784,803 | 862 |
[
"Piwigo",
"Piwigo"
] |
There is an issue to display miniatures and to display the miniatures of a file containing a special character & in its filename
the same issue is visible when trying to display it in mobile apps
also can occure when trying to access the api:
https://album/i.php?/galleries/mariage/pwg_representative/Claire_&_Jean-Philippe_Slideshow-sq.jpg&b=1523873519
Also to note there seems to have few other issue to url encode the strings, we can see the same situation if the filename or the folder containing the file has accentuated characters or spaces.
i.php?\/galleries\/2018\/grossesse 2016-f\u00e9vrier 2017\/1D3A45315-sq.jpg&b=1523671987
I have field a bug against piwigo mobile and some work has been done to check the string for space and accentuaed characters, but the ampersand & is I thing a signal that this all should be done by the main software itself. They should be urlencoded before being sent to API
|
issue to display files with &,space or accentuated in their filename
|
https://api.github.com/repos/Piwigo/Piwigo/issues/861/comments
| 1 |
2018-04-16T15:36:21Z
|
2018-04-16T20:47:40Z
|
https://github.com/Piwigo/Piwigo/issues/861
| 314,709,847 | 861 |
[
"Piwigo",
"Piwigo"
] |
It appears I am allowed to upload duplicate photos. I was hoping Piwigo would check for duplicates, but it seems it does not. I think one way to do this, as Mediawiki does, is to create a hash for the original image. Then for every image put into the upload queue, create a hash and check if that hash exists in the array of existing hashes.
I believe I'm using Piwigo version 2.7.4. Note this is a "one-click install" on a shared Dreamhost server.
|
Use hash of original images to check for duplicate uploads
|
https://api.github.com/repos/Piwigo/Piwigo/issues/860/comments
| 3 |
2018-04-16T02:15:40Z
|
2023-10-15T11:11:18Z
|
https://github.com/Piwigo/Piwigo/issues/860
| 314,478,677 | 860 |
[
"Piwigo",
"Piwigo"
] |
If you upload a TIFF file with exotic color profile, and I simply mean "not sRGB", the JPEG/PNG representative created by upload_file_tiff function will embed the exotic color profile. As usual, we have no idea how the web browser will render colors if you're not on sRGB. It depends on the operating system and web browser.
I've found an sRGB standard color profile + an option for ImageMagick to force the use of a color profile. Let's offer this option.
|
force color profile on TIFF representative
|
https://api.github.com/repos/Piwigo/Piwigo/issues/859/comments
| 0 |
2018-04-11T09:19:07Z
|
2018-04-11T09:19:07Z
|
https://github.com/Piwigo/Piwigo/issues/859
| 313,239,580 | 859 |
[
"Piwigo",
"Piwigo"
] |
Piwigo is an incredible piece of modern-looking brilliantly designed software - but.
Without the right plugins installed it looks a little outdated, and the website showcases the software without these plugins.
If Piwigo doesn't receive a stream of new users it will eventually lose traction - and it must not, because you have a great piece of software here!
Show Piwigo in it's full glory with the Bootstrap theme, with endless scrolling and the Carousel photo view!
|
Piwigo looks amazing but the website doesn't show it
|
https://api.github.com/repos/Piwigo/Piwigo/issues/858/comments
| 2 |
2018-04-09T10:11:13Z
|
2018-10-12T06:59:58Z
|
https://github.com/Piwigo/Piwigo/issues/858
| 312,471,557 | 858 |
[
"Piwigo",
"Piwigo"
] |
thx a lot
|
how to upload psd file ?
|
https://api.github.com/repos/Piwigo/Piwigo/issues/857/comments
| 0 |
2018-04-09T02:20:54Z
|
2018-04-09T04:51:33Z
|
https://github.com/Piwigo/Piwigo/issues/857
| 312,369,838 | 857 |
[
"Piwigo",
"Piwigo"
] |
juste like we have some triggers on {user,photo,album,comment} deletions
|
add trigger on group deletion
|
https://api.github.com/repos/Piwigo/Piwigo/issues/855/comments
| 0 |
2018-03-31T15:29:15Z
|
2019-02-11T13:02:38Z
|
https://github.com/Piwigo/Piwigo/issues/855
| 310,248,739 | 855 |
[
"Piwigo",
"Piwigo"
] |
just like we have triggers for {user,photo,album,comment} deletions
|
add trigger on tag deletion
|
https://api.github.com/repos/Piwigo/Piwigo/issues/854/comments
| 0 |
2018-03-31T15:27:35Z
|
2019-02-01T13:08:05Z
|
https://github.com/Piwigo/Piwigo/issues/854
| 310,248,614 | 854 |
[
"Piwigo",
"Piwigo"
] |
The check_input_parameter on $_POST['selectAction'] introduced in aee8fa1f8dbe7d58118501edd2b6b5be5b184ace was a bit strong :
`check_input_parameter('selectAction', $_POST, false, '/^(edit|merge|duplicate|delete)$/');`
Plugin Colored Tags use the `typetags` value, which is perfectly fine, but does not pass the check:
```
[Hacking attempt] the input parameter "selectAction" is not valid
#1 check_input_parameter admin/tags.php(36)
#2 include admin.php(311)
```
Let's make this check less strict :-)
|
Piwigo 2.9.3 breaks Colored Tags plugin
|
https://api.github.com/repos/Piwigo/Piwigo/issues/853/comments
| 0 |
2018-03-23T09:00:30Z
|
2018-07-12T14:20:30Z
|
https://github.com/Piwigo/Piwigo/issues/853
| 307,947,750 | 853 |
[
"Piwigo",
"Piwigo"
] |
X8al9qHDREqxyA:1620
|
kjii9ip0[
|
https://api.github.com/repos/Piwigo/Piwigo/issues/852/comments
| 0 |
2018-03-21T19:13:23Z
|
2021-05-12T11:15:03Z
|
https://github.com/Piwigo/Piwigo/issues/852
| 307,382,229 | 852 |
[
"Piwigo",
"Piwigo"
] |
Hi,
I'm facing an issue that, my uploaded photo has 640 permission instead of 644, so I can't access the photo by 403 error code.
By checking the code in `functions_upload.inc.php` I see that the function `chmod` is not working properly.
My case, I don't use the Piwigo upload api, but using [an other service](https://tus.io/), and when have the file I use the function `add_uploaded_file` as Piwigo does.
Could someone please suggest me the solution? Thanks.
|
File permission after upload is wrong
|
https://api.github.com/repos/Piwigo/Piwigo/issues/851/comments
| 0 |
2018-03-12T04:59:12Z
|
2018-03-12T04:59:12Z
|
https://github.com/Piwigo/Piwigo/issues/851
| 304,241,481 | 851 |
[
"Piwigo",
"Piwigo"
] |
i have lost password etc but i have admin access to database and files on server. in db i have some like this http://prntscr.com/imsqxc what i should do to restore admin credentials/password?
i tryed generat a new md5 hash by "SELECT MD5('new-password');
typing : "update piwigo_users set password=md5('secret') where id=1; " doesnt work ether. btw sql showing lots of errors in syntax of this query
what i should do?
|
impossible to log on as admin
|
https://api.github.com/repos/Piwigo/Piwigo/issues/850/comments
| 3 |
2018-03-07T13:08:36Z
|
2018-06-06T20:19:02Z
|
https://github.com/Piwigo/Piwigo/issues/850
| 303,091,491 | 850 |
[
"Piwigo",
"Piwigo"
] |
- Open Admin Panel
- Add new Photo(s)
- First Image stuck at 100 %
....
nothing happens (1 Image gets uploaded)
- Ubuntu 16.04.3 Updated
- Php 7 & 5
- Mysql 5.7.21
- Ispconfig 3.1.11
Tried different PHP versions and Processors. Reinstalled on new Server, still not working.
Tried different Browsers, same Error.
Please help, this gets frustrating.
|
Upload stuck @ 100 % on first Image
|
https://api.github.com/repos/Piwigo/Piwigo/issues/849/comments
| 28 |
2018-03-05T13:50:49Z
|
2024-08-06T08:37:11Z
|
https://github.com/Piwigo/Piwigo/issues/849
| 302,307,016 | 849 |
[
"Piwigo",
"Piwigo"
] |
Hi,
Latest Version of piwigo(2.9.3) is vulnerable to cross site scripting vulnerability in the Album Name parameter.Album name can be crafted with malicious payload,which in turn executes while viewing Album.
----------------------------------------------------------------------------------------------------------------------------------
HTTP REQUEST:
----------------------
```
POST /piwigo/piwigo/admin.php?page=cat_list HTTP/1.1
Host: localhost
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-GB,en;q=0.5
Referer: http://10.8.4.2:5880/piwigo/piwigo/admin.php?page=cat_list
Content-Type: application/x-www-form-urlencoded
Content-Length: 127
Cookie: pwg_id=2frjgb4kd5f212cojup43b15c1
DNT: 1
Connection: close
Upgrade-Insecure-Requests: 1
pwg_token=c91f6cca90e3895601750050561b9a4b&virtual_name=**PayloadHere**&submitAdd=
```
Payload Used: `<img src="x" onerror=alert(1);>`
Image Attached:
|
Regarding a Cross Site Scripting Vulnerability.
|
https://api.github.com/repos/Piwigo/Piwigo/issues/848/comments
| 1 |
2018-03-05T08:55:42Z
|
2018-03-05T08:57:40Z
|
https://github.com/Piwigo/Piwigo/issues/848
| 302,216,211 | 848 |
[
"Piwigo",
"Piwigo"
] |
https://nvd.nist.gov/vuln/detail/CVE-2018-5692
> Piwigo v2.8.2 has XSS via the `tab`, `to`, `section`, `mode`, `installstatus`,
> and `display` parameters of the `admin.php` file.
CVE has reference https://www.vulnerability-lab.com/get_content.php?id=2005 which actually lists versions 2.8.2, 2.9.1 and 2.9.2 as vulnerable. Could you tell me versions and commits that fixes this issue, thank you?
|
CVE-2018-5692
|
https://api.github.com/repos/Piwigo/Piwigo/issues/847/comments
| 3 |
2018-03-04T09:19:27Z
|
2018-07-11T09:27:06Z
|
https://github.com/Piwigo/Piwigo/issues/847
| 302,070,336 | 847 |
[
"Piwigo",
"Piwigo"
] |
Issue was described in https://github.com/tkuther/piwigo-bootstrap-darkroom/issues/153 and temporary patched at template level.
I'm making a PR to resolve this problem at core level.
**tldr;**
Function `$template->get_template_vars('TITLE')` for section `recent_cats` returns a HTML string without self anchor tag.
**edit:**
It seems that `favorites` also need a fix.
|
Missing link tag in /recent_cats breadcrumb
|
https://api.github.com/repos/Piwigo/Piwigo/issues/844/comments
| 0 |
2018-03-02T22:28:19Z
|
2018-07-05T13:52:18Z
|
https://github.com/Piwigo/Piwigo/issues/844
| 301,925,377 | 844 |
[
"Piwigo",
"Piwigo"
] |
Hi,
I did love the HTML5 file upload. It was working great until I upgraded to Firefox 58. Now, it doesn't anymore.
Steps to reproduce:
* Open a page like http://$user.piwigo.com/admin.php?page=photos_add&album=$number in firefox 58
* Drag and drop image files from digikam or nautillus to the file upload
Expected behavior: images are added to the queue.
Actual behavior: nothing happens for a while (~10 seconds), and then some images are opened in Firefox in separate tabs (each image in its own tab with a file:// URL pointing to the file).
This still works with Chrome. This is all on Debian stable. I can reproduce the issue with an empty Firefox profile.
Not sure where the bug is (Firefox? Piwigo? Plupload?) :-(.
Is anyone else getting the issue?
Thanks,
|
Picture upload not working since Firefox 58
|
https://api.github.com/repos/Piwigo/Piwigo/issues/843/comments
| 9 |
2018-02-27T20:20:59Z
|
2019-04-27T14:58:13Z
|
https://github.com/Piwigo/Piwigo/issues/843
| 300,778,806 | 843 |
[
"Piwigo",
"Piwigo"
] |
If there is a plus sign "+" in the email address (like in [email protected]), it's not possible to renew a forgotten password. Piwigo tells that user or password is not valid.
|
Impossible to renew a forgotten password with "+" in email address
|
https://api.github.com/repos/Piwigo/Piwigo/issues/842/comments
| 3 |
2018-02-27T11:11:12Z
|
2018-07-17T10:40:26Z
|
https://github.com/Piwigo/Piwigo/issues/842
| 300,588,024 | 842 |
[
"Piwigo",
"Piwigo"
] |
Could you support an SSL=true configuration option in config.inc.php? My host is not SSL, which means that some links (such as straight after login) are 404 broken.
|
Support SSL configuration option
|
https://api.github.com/repos/Piwigo/Piwigo/issues/841/comments
| 4 |
2018-02-22T20:39:10Z
|
2019-01-11T15:28:23Z
|
https://github.com/Piwigo/Piwigo/issues/841
| 299,499,894 | 841 |
[
"Piwigo",
"Piwigo"
] |
Hello,
i have a problem with the "Mobile Theme for Tablets".
We use:
Piwigo 2.9.2
PHP: 7.1.13
MySQL: 5.5.59-0+deb7u1-log
For a test I use only the pure piwigo with the Plugin "Mobile Theme for Tablets" without other plugins.
Here is my selection:
On an iPad (Safari or Chrome or Firefox) I select a photo and click on "More information":
Now the following error appears:
Are there any ideas or solutions to the problem?
John
|
Piwigo 2.9.2 Error: include/derivative.inc.php:311 Stack trace: #0
|
https://api.github.com/repos/Piwigo/Piwigo/issues/840/comments
| 1 |
2018-02-17T09:39:06Z
|
2018-03-03T09:13:13Z
|
https://github.com/Piwigo/Piwigo/issues/840
| 297,992,593 | 840 |
[
"Piwigo",
"Piwigo"
] |
An SQL injection has been discovered in the administration panel of Piwigo v2.9.2. The vulnerability allows remote attackers that are authenticated as administrator to inject SQL code into a query. This could result in full information disclosure.
The SQL injection vulnerability was found in admin/tags.php and is done by injecting SQL code in the 'tags' POST variable. This variable is only sanitized by addslashes() and is not encapsulated by quotes in the concatenated SQL string allowing the injection to work. Furthermore, the result set is part of the page output allowing information disclosure about other tables in the database.
The POST variables 'edit_list' and 'merge_list' are also vulnerable to this attack, however, no exploit exist to disclose information through these variables. A separate vulnerability report was made for 'edit_list' (CVE-2017-16893, issue #804).
The security risk of the vulnerability is estimated as low with a CVSS score of 3.8. Exploitation of the web vulnerability requires the attacker to be authenticated as administrator.
A PoC can be provided. I'm tracking this under CVE-2018-6883
|
Piwigo v2.9.2 - SQL injection in administration panel
|
https://api.github.com/repos/Piwigo/Piwigo/issues/839/comments
| 0 |
2018-02-11T09:25:23Z
|
2018-02-21T16:36:02Z
|
https://github.com/Piwigo/Piwigo/issues/839
| 296,175,351 | 839 |
[
"Piwigo",
"Piwigo"
] |
In the Batch Manager, if you select "all set" and then the delete action, all photos are correctly deleted (AJAX calls to pwg.images.delete) but you end up with a message:
> Select at least one photo
> No photo can be deleted
|
[Batch Manager] delete "all set" produces an incorrect error message
|
https://api.github.com/repos/Piwigo/Piwigo/issues/838/comments
| 0 |
2018-02-08T12:02:22Z
|
2018-02-08T12:04:18Z
|
https://github.com/Piwigo/Piwigo/issues/838
| 295,486,811 | 838 |
[
"Piwigo",
"Piwigo"
] |
Hi all,
I have found an issue after FTP loading.
First step:
- I upload 2 files (one video: aaaa.mp4 and the attached picture: aaaa.jpg).
- I synchronize the uploaded files
- All is right
Second step:
- I want to modify my video and the attached picture so thanks to FTP, I reload again the two new files with the same names (one video: aaaa.mp4 and the attached picture: aaaa.jpg).
- I synchronize again the uploaded files
- Issue:
Within Piwigo / Administration, in "new pictures" menu, I seen the old attached picture and not the new.
Could you tell me please, how can I solve this issue?
BR
Michel
|
Update issue after FTP loading
|
https://api.github.com/repos/Piwigo/Piwigo/issues/837/comments
| 0 |
2018-02-01T10:06:02Z
|
2018-02-01T10:06:02Z
|
https://github.com/Piwigo/Piwigo/issues/837
| 293,470,683 | 837 |
[
"Piwigo",
"Piwigo"
] |
I recently started getting the following on two of my Piwigo installations. If I do a brand new installation into a new directory, I have no problem. So I'm thinking it is one of the plugins (community, perhaps, based on some of the paths) I've activated on the two installations. Is there a way to disable plugins when I can't get to any graphical interfaces?
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 'recursive,
create_subcategories,
nb_photos,
storage
FROM piwi_fp_c' at line 6
SELECT
id,
type,
category_id,
user_album,
recursive,
create_subcategories,
nb_photos,
storage
FROM piwi_fp_community_permissions
WHERE (type = 'any_visitor')
; in /home/[...]/public_html/.[..]/photos/include/dblayer/functions_mysqli.inc.php on line 845
Fatal error: Uncaught Error: Call to a member function fetch_assoc() on boolean in /home/[...]/public_html/[...]/photos/include/dblayer/functions_mysqli.inc.php:226 Stack trace: #0 /home/[...]/public_html/[...]/photos/plugins/community/include/functions_community.inc.php(102): pwg_db_fetch_assoc(false) #1 /home/[...]/public_html/[...]/photos/plugins/community/main.inc.php(48): community_get_user_permissions('2') #2 /home/[...]/public_html/[...]/photos/include/functions_plugins.inc.php(279): community_init() #3 /home/[...]/public_html/[...]/photos/include/common.inc.php(308): trigger_notify('init') #4 /home/[...]/public_html/[...]/photos/index.php(26): include_once('/home/underg10/...') #5 {main} thrown in /home/[...]/public_html/[...]/photos/include/dblayer/functions_mysqli.inc.php on line 226
|
Disable Plugins when unable to access a GUI
|
https://api.github.com/repos/Piwigo/Piwigo/issues/836/comments
| 1 |
2018-01-28T16:34:02Z
|
2018-01-28T18:54:22Z
|
https://github.com/Piwigo/Piwigo/issues/836
| 292,217,979 | 836 |
[
"Piwigo",
"Piwigo"
] |
I, stupidly, changed the password on the database user for my Piwigo database through my web hosting cPanel interface while troubleshooting an issue I was having. Now I get the following error:
Warning: mysqli::__construct(): (HY000/1045): Access denied for user 'dbuser'@'localhost' (using password: YES) in /home/.../public_html/gallery/include/dblayer/functions_mysqli.inc.php on line 67
Is there a way to update the password for the database user to properly reflect the new password I set? I would change the password back, but I changed it in the first place because I wasn't able to remember it and was trying to connect directly to the database. (in retrospect, I should have created a new database user for the direct connection - like I said, stupid!)
|
Reset/Update Database User Password
|
https://api.github.com/repos/Piwigo/Piwigo/issues/835/comments
| 1 |
2018-01-28T16:25:52Z
|
2018-01-29T13:49:32Z
|
https://github.com/Piwigo/Piwigo/issues/835
| 292,217,399 | 835 |
[
"Piwigo",
"Piwigo"
] |
I am using the VideoJS plugin to generate posters for videos in my physical albums. VideoJS successfully generates the thumbnails and puts them in the `pwg_representative` folders for all of my video albums, but Piwigo will not display the thumbnails. Instead it displays the :warning: symbol as if there are no thumbnails.
I don't think that this problem has anything to do with the VideoJS plugin because it creates the posters for the videos just fine. According to the documentation Piwigo should find the .jpg representations in the `pwg_representative`. Am I misunderstanding something?
|
Thumbnails for mp4/m4v's not using image in pwg_representative folder
|
https://api.github.com/repos/Piwigo/Piwigo/issues/833/comments
| 1 |
2018-01-15T22:00:33Z
|
2018-01-15T22:36:56Z
|
https://github.com/Piwigo/Piwigo/issues/833
| 288,727,324 | 833 |
[
"Piwigo",
"Piwigo"
] |
is there a plugin? also im using piwigo embedded videos. when i click the video thumb it opens this white page with the embed instead of like the images.
|
add image vial url
|
https://api.github.com/repos/Piwigo/Piwigo/issues/832/comments
| 0 |
2018-01-12T19:04:02Z
|
2018-01-12T19:04:02Z
|
https://github.com/Piwigo/Piwigo/issues/832
| 288,216,026 | 832 |
[
"Piwigo",
"Piwigo"
] |
When I upload an image from Lightroom to Piwigo I am noticing that all thumbnails and smaller resolution images that were rendered by Piwigo after the upload exhibit a color shift (colors appear warmer and more saturated). But on the full-size image, all colors match what I see in Lightroom.
This may be happening because all Piwigo-rendered images lack color profile information.
Here is a screenshot of image properties from IrfanView of the original JPEG (note the embedded RGB profile):
And this is the same of the medium-size image rendered on Piwigo's side, color profile information is missing:
|
Color balance / color profile issue with reduced images
|
https://api.github.com/repos/Piwigo/Piwigo/issues/831/comments
| 3 |
2018-01-10T04:18:14Z
|
2021-08-16T09:28:57Z
|
https://github.com/Piwigo/Piwigo/issues/831
| 287,310,717 | 831 |
[
"Piwigo",
"Piwigo"
] |
Each year we have to update all source code files in order to match the current year. It has a useless impact on version history of each file. I think we should simply have these dates in a single file, not in every file.
|
remove years from source code headers
|
https://api.github.com/repos/Piwigo/Piwigo/issues/830/comments
| 0 |
2018-01-09T12:50:52Z
|
2019-06-26T14:06:30Z
|
https://github.com/Piwigo/Piwigo/issues/830
| 287,078,009 | 830 |
[
"Piwigo",
"Piwigo"
] |
I have a strange problem similar to this old bug: http://piwigo.org/bugs/view.php?id=2088
Only 7 out of 9 albums are visible as a certain user. When I assign the status "administrator" to that user all albums are visible.
I cannot figure out any differences between those albums. All have permissions based on a group where the user is a member of. I can even see the missing albums in the permission settings of the affected user.
When I try to open an album by ID as this user I get a not authorized error.
I am running piwigo on a VPS with symlinks to the "galleries" folder and the ftp synchronisatin feature.
Piwigo 2.9.2
Operating system: Linux
PHP: 5.6.30-0+deb8u1 (Show info) [2018-01-03 22:44:31]
MySQL: 5.5.58-0+deb8u1 [2018-01-03 22:44:31]
Graphics Library: External ImageMagick 6.8.9-9
Any hint is appreciated!
Thanks
|
Some albums are not visible as user
|
https://api.github.com/repos/Piwigo/Piwigo/issues/829/comments
| 1 |
2018-01-03T21:46:42Z
|
2018-01-04T18:39:51Z
|
https://github.com/Piwigo/Piwigo/issues/829
| 285,818,956 | 829 |
[
"Piwigo",
"Piwigo"
] |
Hi there,
It is not possible to write an emoji in the album name (not tested in other field), it submits without error but erases completely the content of the album name's input field.
A work around is to enter the unicode HTML code.
Here is an example of use : https://leo.lstronic.com/piwigo/index.php?/category/70
Léo
|
Use unicode/emoji symbols in album name
|
https://api.github.com/repos/Piwigo/Piwigo/issues/828/comments
| 2 |
2017-12-28T15:20:59Z
|
2022-03-14T06:33:05Z
|
https://github.com/Piwigo/Piwigo/issues/828
| 284,935,291 | 828 |
[
"Piwigo",
"Piwigo"
] |
We just discovered this : https://agir.april.org/issues/2861
We are not alone : https://www.google.fr/search?q=cialis-5mg-prix-pharmacie+piwigo https://www.google.fr/search?q=viagra+piwigo
_data/settings is pwned, probably for years. We still investigate where does it comes from.
|
Piwigo pwned by viagra resellers
|
https://api.github.com/repos/Piwigo/Piwigo/issues/827/comments
| 14 |
2017-12-21T11:34:30Z
|
2022-08-19T08:06:23Z
|
https://github.com/Piwigo/Piwigo/issues/827
| 283,854,663 | 827 |
[
"Piwigo",
"Piwigo"
] |
The configuration setting "order by" can receive an SQL injection.
This vulnerability is not considered as critical because it requires admin access to be exploited.
Reported by [Sahil Dhar](https://www.linkedin.com/in/sahildhar/)
|
SQL injection in configuration setting
|
https://api.github.com/repos/Piwigo/Piwigo/issues/826/comments
| 0 |
2017-12-18T16:09:04Z
|
2018-02-24T16:10:57Z
|
https://github.com/Piwigo/Piwigo/issues/826
| 282,932,735 | 826 |
[
"Piwigo",
"Piwigo"
] |
The Batch Manager has a SQL injection vulnerability. The bug is not critical because it requires administration access to be exploited, but needs to be fixed anyway.
Reported by [Sahil Dhar](https://www.linkedin.com/in/sahildhar/)
|
SQL injection on Batch Manager, unit mode
|
https://api.github.com/repos/Piwigo/Piwigo/issues/825/comments
| 0 |
2017-12-18T15:43:58Z
|
2018-02-24T16:10:22Z
|
https://github.com/Piwigo/Piwigo/issues/825
| 282,923,834 | 825 |
[
"Piwigo",
"Piwigo"
] |
I'm writing about tools/pwg_rel_create.sh, the line:
`scriptdir=$(dirname $(readlink -e $0))`
does not work on MacOS X (readlink does not work)
|
release builder failing under MacOS X
|
https://api.github.com/repos/Piwigo/Piwigo/issues/824/comments
| 0 |
2017-12-18T13:28:14Z
|
2017-12-18T13:29:49Z
|
https://github.com/Piwigo/Piwigo/issues/824
| 282,878,689 | 824 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.