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"
] |
Although there is all information available, sync does not create the "rotation" field in the image table in the database.
This is actually not "harmfull", if piwigo itself generates the thumbnails (except that the first thumb rendering might be mistaken).
But I'm creating the thumbnails offline, because my piwigo server is a raspi which does not have enough computing power to create the thumbnails in acceptable time.
(PR available)
|
[sync] does not create "rotation"
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1761/comments
| 1 |
2022-10-20T11:32:20Z
|
2022-10-21T04:29:51Z
|
https://github.com/Piwigo/Piwigo/issues/1761
| 1,416,454,927 | 1,761 |
[
"Piwigo",
"Piwigo"
] |
I have old images which have 720 for longitude/latitude which correctly is rejected on database sync. Unfortunately the sync aborts at this point.
sync should check the limits before sending the SQL statement to mysql.
(PR available)
|
[sync] images with ill longitude/latitude crashes sync
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1760/comments
| 2 |
2022-10-20T11:28:14Z
|
2024-06-19T13:38:25Z
|
https://github.com/Piwigo/Piwigo/issues/1760
| 1,416,449,681 | 1,760 |
[
"Piwigo",
"Piwigo"
] |
On page [admin > configuration > option], I get:
> <b>Fatal error</b>: Uncaught TypeError: array_merge(): Argument #1 must be of type array, null given in local/config/config.inc.php:16
>
> Stack trace:
> #0 local/config/config.inc.php(16): array_merge()
> #1 admin/configuration.php(332): include('...')
> #2 admin/configuration.php(341): order_by_is_local()
> #3 admin.php(320): include('...')
>#4 {main}
> thrown in <b>local/config/config.inc.php</b> on line <b>16</b><br />
On line 15 of `local/config/config.inc.php` I have:
```
$conf['file_ext'] = array_merge(
// isset($conf['picture_ext']) ? $conf['picture_ext'] : array(),
$conf['picture_ext'],
array('pdf', 'tiff', 'tif', 'psd', 'eps', 'ai', 'svg')
);
```
That's because `$conf['picture_ext']` is not set and PHP 8.1 does not like that.
|
[PHP 8.1] fatal error on configuration page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1759/comments
| 0 |
2022-10-19T12:41:48Z
|
2022-10-19T12:46:40Z
|
https://github.com/Piwigo/Piwigo/issues/1759
| 1,414,904,795 | 1,759 |
[
"Piwigo",
"Piwigo"
] |
After we check for update on the maintenance > env page, there is no link to the update page, so we don't really know were to go after we know that an update is available.
We should add a link to the update page.
|
[Check update] No link to the update page after update check
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1758/comments
| 0 |
2022-10-19T12:21:20Z
|
2022-10-21T08:34:22Z
|
https://github.com/Piwigo/Piwigo/issues/1758
| 1,414,874,385 | 1,758 |
[
"Piwigo",
"Piwigo"
] |
After creating an album, if you edit it rigth after we get the message on the page :
```<b>Deprecated</b>: explode(): Passing null to parameter #2 ($string) of type string is deprecated in <b>/var/www/html/piwigo/admin/include/functions.php</b> on line <b>2377</b>```
It disappears when we refresh the page, but still needs a fix.
|
php8 warning on album edit right after album creation.
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1757/comments
| 1 |
2022-10-19T10:33:06Z
|
2023-06-26T09:33:28Z
|
https://github.com/Piwigo/Piwigo/issues/1757
| 1,414,720,656 | 1,757 |
[
"Piwigo",
"Piwigo"
] |
There are some issues with php8 and the comments system.
Warnigns are triggered with the trim() function
There are also some problems concerning the input escape of single cotes.
|
Comments on pictures issues with php8
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1756/comments
| 0 |
2022-10-18T08:42:00Z
|
2022-10-21T08:36:36Z
|
https://github.com/Piwigo/Piwigo/issues/1756
| 1,412,811,497 | 1,756 |
[
"Piwigo",
"Piwigo"
] |
Add check conditions for php8 warnings
|
Php8 Warnings on related albums
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1755/comments
| 0 |
2022-10-17T14:06:08Z
|
2022-10-21T08:33:43Z
|
https://github.com/Piwigo/Piwigo/issues/1755
| 1,411,648,832 | 1,755 |
[
"Piwigo",
"Piwigo"
] |
https://github.com/Piwigo/Piwigo/blob/ba08bffcb2768fb773c27d9b7ddb0f1d7645750b/include/ws_functions/pwg.php#L832
and
https://github.com/Piwigo/Piwigo/blob/ba08bffcb2768fb773c27d9b7ddb0f1d7645750b/include/ws_functions/pwg.php#L838
have an invalid trailing comma.
They generate the following error when trying to connect with the remote sync client
```
2022/10/16 15:50:49 [error] 1167#1167: *320 FastCGI sent in stderr: "PHP message: PHP Parse error: syntax error, unexpected ')' in /var/www/***/include/ws_functions/pwg.php on line 833" while reading response header from upstream, client: 172.70.110.35, server:*** request: "POST /ws.php HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.2-fpm.sock:", host: "***"
```
|
syntax error, unexpected ')' in include/ws_functions/pwg.php caused by trailing commas
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1753/comments
| 0 |
2022-10-16T14:00:46Z
|
2022-10-21T08:34:45Z
|
https://github.com/Piwigo/Piwigo/issues/1753
| 1,410,498,151 | 1,753 |
[
"Piwigo",
"Piwigo"
] |
Piwigo 13.0.0
Linux (debian)
PHP: 8.1.11
MySQL: 10.5.15-MariaDB-0
php error when uploading a photo with digikam when I have a special character (here the apostrophe) in the title of my photo : "Beauté d'automne (TEST)"
I specify that with the web form there is no problem.
`[Fri Oct 14 09:23:00.827306 2022] [php:error] [pid 710552] [client CLIENT_IP:60431] PHP Fatal error: Uncaught mysqli_sql_exception: 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 'automne (TEST)',\n `date_creation` = '2022-10-14 07:53:27'\n WHERE `id` = '...' at line 2 in /PIWIGO_DIR/include/dblayer/functions_mysqli.inc.php:132\nStack trace:\n#0 /PIWIGO_DIR/include/dblayer/functions_mysqli.inc.php(132): mysqli->query()\n#1 /PIWIGO_DIR/include/dblayer/functions_mysqli.inc.php(478): pwg_query()\n#2 /PIWIGO_DIR/include/ws_functions/pwg.images.php(1102): single_update()\n#3 /PIWIGO_DIR/include/ws_core.inc.php(600): ws_images_add()\n#4 /PIWIGO_DIR/include/ws_protocols/rest_handler.php(41): PwgServer->invoke()\n#5 /PIWIGO_DIR/include/ws_core.inc.php(281): PwgRestRequestHandler->handleRequest()\n#6 /PIWIGO_DIR/ws.php(22): PwgServer->run()\n#7 {main}\n thrown in /PIWIGO_DIR/include/dblayer/functions_mysqli.inc.php on line 132`
Here is an example of a photo that I can't upload : https://share.heraut.eu/f.php?h=1gGeSHGY&d=1:
Thank you and have a nice day.
|
Uncaught mysqli_sql_exception (UPLOAD WITH DIGIKAM)
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1752/comments
| 0 |
2022-10-14T07:33:09Z
|
2022-10-14T07:33:09Z
|
https://github.com/Piwigo/Piwigo/issues/1752
| 1,408,905,743 | 1,752 |
[
"Piwigo",
"Piwigo"
] |
I got this error after upgrade version 13
Fatal error: Uncaught Error: Call to undefined function userprefs_get_param() in /admin/include/themes.class.php:423 Stack trace: #0 /admin/include/themes.class.php(50): themes->get_fs_themes() #1 /admin/include/updates.class.php(38): themes->__construct() #2 /admin/updates_pwg.php(29): updates->__construct() #3 /admin/updates.php(28): include('/var/www/client...') #4 //admin.php(320): include('/var/www/client...') #5 {main} thrown in /admin/include/themes.class.php on line 423
|
Fatal error: Uncaught Error: Call to undefined function userprefs_get_param() - themes.class.php:423
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1751/comments
| 12 |
2022-10-13T07:58:09Z
|
2022-10-21T08:18:31Z
|
https://github.com/Piwigo/Piwigo/issues/1751
| 1,407,326,931 | 1,751 |
[
"Piwigo",
"Piwigo"
] |
As can be seen with
https://demo1.piwigo.com/index?/best_rated/created-weekly-list-any
that leads to
```
Piwigo encountered an unrecoverable error
bad chronology field (date)
#1 parse_well_known_params_url /var/www/piwigo_master_12/include/section_init.inc.php(152)
#2 include /var/www/piwigo_master_12/index.php(12)
```
In fact that happens with the start of any of the possible tokens, like
https://demo1.piwigo.com/index?/best_rated/created-
https://demo1.piwigo.com/index?/best_rated/posted-
|
best_rated/created- leads to "Piwigo encountered an unrecoverable error"
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1750/comments
| 0 |
2022-10-12T15:30:33Z
|
2022-10-14T09:11:25Z
|
https://github.com/Piwigo/Piwigo/issues/1750
| 1,406,412,588 | 1,750 |
[
"Piwigo",
"Piwigo"
] |
Remove the details with {icon} Tags and just put the actual tags with the icon.
|
[History page] Remove the {icon} Tags in details.
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1747/comments
| 0 |
2022-10-12T14:20:17Z
|
2022-10-21T08:50:46Z
|
https://github.com/Piwigo/Piwigo/issues/1747
| 1,406,304,925 | 1,747 |
[
"Piwigo",
"Piwigo"
] |
I'm getting the above warning when trying to download an image in Piwigo 13.0.0. This corrupts the download.
Could be related to dd44d0e40999632fb1d80f313f51b6decbfa937c, as I think headers can't be sent after calling `flush()`
|
Warning: Cannot modify header information - headers already sent in /var/www/piwigo/action.php on line 228
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1746/comments
| 5 |
2022-10-12T05:29:38Z
|
2022-10-19T13:04:23Z
|
https://github.com/Piwigo/Piwigo/issues/1746
| 1,405,590,343 | 1,746 |
[
"Piwigo",
"Piwigo"
] |
|
Missing translation on update page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1745/comments
| 0 |
2022-10-11T14:18:59Z
|
2022-10-21T08:51:06Z
|
https://github.com/Piwigo/Piwigo/issues/1745
| 1,404,728,484 | 1,745 |
[
"Piwigo",
"Piwigo"
] |
See #1544 or #1276 or #1063 or #658 or #423
|
upgrade script to 13
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1744/comments
| 0 |
2022-10-10T13:21:51Z
|
2022-10-10T14:17:39Z
|
https://github.com/Piwigo/Piwigo/issues/1744
| 1,403,171,230 | 1,744 |
[
"Piwigo",
"Piwigo"
] |
- [x] : Better details : https://sandbox.piwigo.com/picture?/2532/category/448-v2
- [x] : Details translation in french needs a 'é'
- [x] : Album name in details must be clickable + tiptip
- [x] : Album name in object must be clickable (only the first parent must be shown)
- [x] : Add images id when we visit them by another way than through the gallery
- [x] : Change default names in databases (EX : most_visited ou categories)
|
[History page] Updates for 13
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1743/comments
| 0 |
2022-10-05T14:27:50Z
|
2022-10-10T14:09:34Z
|
https://github.com/Piwigo/Piwigo/issues/1743
| 1,397,886,601 | 1,743 |
[
"Piwigo",
"Piwigo"
] |
In the history page, you can have unmodified lines like this :
This occurs when a plugin adds a page in the gallery and you visit it. We should add a default case so it doesn't happen.
|
[History page] Unhandled case for plugins in gallerie
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1742/comments
| 0 |
2022-10-04T09:34:25Z
|
2022-10-04T09:37:03Z
|
https://github.com/Piwigo/Piwigo/issues/1742
| 1,395,950,220 | 1,742 |
[
"Piwigo",
"Piwigo"
] |
Hello, I have the same problem in a fresh install (piwigo version 12.3.0 - php7.3).
The downloaded file is corrupted (incomplete, I get a .part file) with Firefox (v100.0), but not in Chrome nor Edge).
The problem seems to be solved when I comment ob_clean() in action.php even if I assume that this is not the best way to proceed.
_Originally posted by @vilnus in https://github.com/Piwigo/Piwigo/issues/1297#issuecomment-1266606502_
|
[12.3] ob_clean() - corrupted downloads
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1741/comments
| 3 |
2022-10-04T08:45:36Z
|
2022-10-15T11:41:19Z
|
https://github.com/Piwigo/Piwigo/issues/1741
| 1,395,887,772 | 1,741 |
[
"Piwigo",
"Piwigo"
] |
When you try to edit an image from the history that has been deleted. You get a sql error.
We add a better UI for it.
|
[History page] Edit deleted image causes error.
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1740/comments
| 0 |
2022-10-03T12:42:54Z
|
2022-10-03T12:43:37Z
|
https://github.com/Piwigo/Piwigo/issues/1740
| 1,394,670,928 | 1,740 |
[
"Piwigo",
"Piwigo"
] |
Between the filters and the first line of plugins, the margin is too small. It is:
before commit fd82502 it was:
|
[13.0.0RC4] broken margin on plugin page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1739/comments
| 0 |
2022-09-30T14:20:09Z
|
2022-10-04T10:34:34Z
|
https://github.com/Piwigo/Piwigo/issues/1739
| 1,392,517,590 | 1,739 |
[
"Piwigo",
"Piwigo"
] |
Reported on French forum https://fr.piwigo.org/forum/viewtopic.php?pid=235785#p235785
> file_get_contents(./_data/cache/piwigo_news-fr.cache.php): failed to open stream: No such file or directory in ../admin/include/functions.php on line 3508
|
[13.0.0RC4] dashboard, latest news not loading
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1738/comments
| 0 |
2022-09-30T13:58:29Z
|
2022-09-30T13:59:44Z
|
https://github.com/Piwigo/Piwigo/issues/1738
| 1,392,487,524 | 1,738 |
[
"Piwigo",
"Piwigo"
] |
The alerts are displayed under the first album creation form. If you don't see the scroll bar on the side you can't notice the alert.
Those alerts are supposed to be placed at the top of the page.
|
Error and warning alerts are displayed under the page on first album creation (fresh install)
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1737/comments
| 0 |
2022-09-27T14:38:30Z
|
2022-09-27T14:41:56Z
|
https://github.com/Piwigo/Piwigo/issues/1737
| 1,387,880,351 | 1,737 |
[
"Piwigo",
"Piwigo"
] |
Error on the page be cause of some single quote escape problems.
|
[Album permissions] Single quote escape problem
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1736/comments
| 0 |
2022-09-26T14:38:27Z
|
2022-09-26T14:43:13Z
|
https://github.com/Piwigo/Piwigo/issues/1736
| 1,386,201,021 | 1,736 |
[
"Piwigo",
"Piwigo"
] |
As described on https://github.com/Piwigo/Piwigo/issues/802#issuecomment-944392667 we would need a dedicated API method to associate/dissociate/move photos and albums... instead of multiple calls to `pwg.images.setInfo`
cc @EddyLB @remi-martin
|
pwg.images.setCategory to associate/dissociate/move photos to albums
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1735/comments
| 2 |
2022-09-26T12:34:37Z
|
2024-06-19T20:17:20Z
|
https://github.com/Piwigo/Piwigo/issues/1735
| 1,386,005,047 | 1,735 |
[
"Piwigo",
"Piwigo"
] |
if a photo has a 90 or 270 degrees rotation (`images.rotation` equals 1 or 3), we should take that into account to switch width and height.
See also https://github.com/Piwigo/Piwigo/commit/099d1f3b186f14833df6e34dd294d57cbdf800a7
|
[Batch Manager] filter by orientation does not take rotation into account
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1734/comments
| 1 |
2022-09-26T10:31:02Z
|
2024-07-01T13:18:14Z
|
https://github.com/Piwigo/Piwigo/issues/1734
| 1,385,826,488 | 1,734 |
[
"Piwigo",
"Piwigo"
] |
|
[config, FR] invalid character for confirmation popin
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1733/comments
| 0 |
2022-09-21T12:28:02Z
|
2022-09-21T12:31:52Z
|
https://github.com/Piwigo/Piwigo/issues/1733
| 1,380,849,935 | 1,733 |
[
"Piwigo",
"Piwigo"
] |
Search used to add linked album to a picture is broken in php8.1, looks like there are php warning that causes the result of the request to be unreadable.
|
[Picture Modify] Linked album search is broken in php8.1
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1732/comments
| 0 |
2022-09-19T14:40:27Z
|
2022-09-19T14:41:47Z
|
https://github.com/Piwigo/Piwigo/issues/1732
| 1,378,070,558 | 1,732 |
[
"Piwigo",
"Piwigo"
] |
Is it possible to show empty album ? Even if it's not from GUI config but from a custom conf line
|
Show empty album
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1731/comments
| 0 |
2022-09-17T13:24:22Z
|
2022-09-17T13:24:22Z
|
https://github.com/Piwigo/Piwigo/issues/1731
| 1,376,772,018 | 1,731 |
[
"Piwigo",
"Piwigo"
] |
When opening the calendar on a specific year, for example `index.php?/categories/created-weekly-list-2021` we get:
> Notice: Undefined property: Smarty_Internal_Undefined::$objMap in include/smarty/libs/sysplugins/smarty_internal_extension_handler.php on line 132
>
> Fatal error: Uncaught --> Smarty: undefined extension class 'Smarty_Internal_Method_GetVariable' <-- thrown in include/smarty/libs/sysplugins/smarty_internal_undefined.php on line 62
This is due to this line in `include/calendar_base.class.php`:
```
$existing = $template->smarty->getVariable('chronology_navigation_bars');
```
Indeed, the Smarty version (3.1.39) embedded in Piwigo 12 says about `getVariable`:
> @deprecated since 3.1.28 please use Smarty_Internal_Data::getTemplateVars() instead.
And this function no longer exists in Smarty 4.1. So, let's replace it!
|
[13.0.0RC3] calendar, undefined extension class Smarty_Internal_Method_GetVariable
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1730/comments
| 0 |
2022-09-16T08:00:25Z
|
2022-09-16T08:05:50Z
|
https://github.com/Piwigo/Piwigo/issues/1730
| 1,375,574,121 | 1,730 |
[
"Piwigo",
"Piwigo"
] |
Link to the forum for the error -> https://piwigo.org/forum/viewtopic.php?id=32196
The fix proposed works fine, so we add it.
|
AMM Php error reported on the forum
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1729/comments
| 0 |
2022-09-14T14:34:51Z
|
2022-09-14T14:36:11Z
|
https://github.com/Piwigo/Piwigo/issues/1729
| 1,373,098,362 | 1,729 |
[
"Piwigo",
"Piwigo"
] |
If a description is too long it becomes cut at the end and we can't read it properly.
Add a tiptip so it can be fully read
|
[Plugin Manager] Long desciptions are not readable
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1728/comments
| 1 |
2022-09-13T13:46:03Z
|
2022-09-21T13:52:57Z
|
https://github.com/Piwigo/Piwigo/issues/1728
| 1,371,486,163 | 1,728 |
[
"Piwigo",
"Piwigo"
] |
Emails in user manager are unreadable when they are too long.
2 solutions :
- Add "..." at the end of the email but it becomes incomplete so can't be copied to clipboard
- Add a scroll so you can still select the email
|
[User Manager] Unreadable emails when they are too long
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1727/comments
| 1 |
2022-09-13T10:05:42Z
|
2022-09-21T14:50:27Z
|
https://github.com/Piwigo/Piwigo/issues/1727
| 1,371,192,571 | 1,727 |
[
"Piwigo",
"Piwigo"
] |
Inherited from a glorious past (kidding), we have this nearly hidden feature "Display only recently posted photos". When this feature is enabled, in old themes, you see an icon in the "albums" block, to only display the recently updated content.
1) only a few old themes show the icon. Elegant (released in June 2012, that's 10 years ago) doesn't show this icon. I took the above screenshot on dark, older than Elegant
2) you can perfectly find the recent content by going to the "recent photos" or "recent albums" section
3) it adds some code in several places that no one still understand
|
remove feature "Display only recently posted photos"
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1726/comments
| 1 |
2022-09-12T13:25:54Z
|
2024-07-31T15:16:06Z
|
https://github.com/Piwigo/Piwigo/issues/1726
| 1,369,910,048 | 1,726 |
[
"Piwigo",
"Piwigo"
] |
Add a tiptip on the restore action to explain what it really does.
|
[Plugin Manager] Explain "restore" action
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1725/comments
| 0 |
2022-09-12T11:54:10Z
|
2022-09-12T14:06:12Z
|
https://github.com/Piwigo/Piwigo/issues/1725
| 1,369,755,050 | 1,725 |
[
"Piwigo",
"Piwigo"
] |
On SVG files, the edit page in the adminstration has margins broken compared to JPEG files.
|
[13.0.0RC3] edit photo, incorrect margins on SVG files
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1724/comments
| 0 |
2022-09-12T10:58:23Z
|
2022-09-14T10:12:51Z
|
https://github.com/Piwigo/Piwigo/issues/1724
| 1,369,683,581 | 1,724 |
[
"Piwigo",
"Piwigo"
] |
We want to change the Eye icon to an icon more representative of a curve like this one :
|
[Activity page] Change activity icon
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1723/comments
| 0 |
2022-09-12T10:32:46Z
|
2022-09-12T11:37:59Z
|
https://github.com/Piwigo/Piwigo/issues/1723
| 1,369,651,232 | 1,723 |
[
"Piwigo",
"Piwigo"
] |
Upon completely installing a fresh copy of 13RC3, I cannot load the admin page. It returns the following:
```
Deprecated: number_format(): Passing null to parameter #1 ($num) of type float is deprecated in /mnt/2tb_usb2/html/admin/include/functions.php on line 3381
Warning: file_get_contents(./_data/cache/piwigo_news-en.cache.php): Failed to open stream: No such file or directory in /mnt/2tb_usb2/html/admin/include/functions.php on line 3507
Fatal error: Uncaught TypeError: array_slice(): Argument #1 ($array) must be of type array, bool given in /mnt/2tb_usb2/html/admin/include/functions.php:3510 Stack trace: #0 /mnt/2tb_usb2/html/admin/include/functions.php(3510): array_slice() #1 /mnt/2tb_usb2/html/admin/intro.php(177): get_piwigo_news() #2 /mnt/2tb_usb2/html/admin.php(320): include('...') #3 {main} thrown in /mnt/2tb_usb2/html/admin/include/functions.php on line 3510
```
I am using PHP 8.1.2 (cli) (built: Aug 17 2022 13:08:39) (NTS).
Thanks for any help!
|
Admin page not loading
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1722/comments
| 4 |
2022-09-12T07:04:27Z
|
2022-12-22T16:39:57Z
|
https://github.com/Piwigo/Piwigo/issues/1722
| 1,369,381,660 | 1,722 |
[
"Piwigo",
"Piwigo"
] |
When I'm logged in and in any category page, eg. https://example.com/piwigo/index.php?/category/3, I get the following warning:
<b>Warning</b>: Undefined array key "IS_IN_CADDIE" in <b>/srv/html/piwigo/_data/templates_c/1oivm68^b28a8459f5c203fb0f2c820e9728d5e1488fa528_0.file.public_controller.tpl.php</b> on line <b>174</b>
Server: Ubuntu 20.04, PHP 8.1 and Piwigo 13.0.0RC3
|
PHP Warning
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1721/comments
| 5 |
2022-09-11T20:32:49Z
|
2022-09-20T16:54:45Z
|
https://github.com/Piwigo/Piwigo/issues/1721
| 1,369,056,373 | 1,721 |
[
"Piwigo",
"Piwigo"
] |
Good morning.
I just increased those values on php.ini:
post_max_size => 10240M => 10240M
upload_max_filesize => 2048M => 2048M
post_max_size => 10240M => 10240M
From the default 100MB limit just to allow upload my DSLR pics (which are too big) and upload some videos vía videojs plugin but those seems to have no effect:
That's a 1,4GB vídeo:
¿Where are those vars ignored? Using nginx with max_body_size on 0; (unlimited)
Thanks in advance.
|
How to increase max file size correctly.
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1720/comments
| 6 |
2022-09-09T11:15:23Z
|
2022-10-16T06:02:26Z
|
https://github.com/Piwigo/Piwigo/issues/1720
| 1,367,679,149 | 1,720 |
[
"Piwigo",
"Piwigo"
] |
When we do a research to link an album to a picture, the button is super small, it would be better if we could click on the whole line to add the searched album to linked album list.
|
[Photo Edit] button to add a linked album is too small
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1719/comments
| 0 |
2022-09-07T14:43:21Z
|
2022-09-07T14:43:56Z
|
https://github.com/Piwigo/Piwigo/issues/1719
| 1,364,776,686 | 1,719 |
[
"Piwigo",
"Piwigo"
] |
The search for linked albums start when we type at least 3 characters, but it seems like not working when you don't know that. So we start the search at the first char.
|
[Photo Edit] Linked album search start at char 3, should be 1
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1718/comments
| 0 |
2022-09-07T14:06:45Z
|
2022-09-07T14:09:34Z
|
https://github.com/Piwigo/Piwigo/issues/1718
| 1,364,724,003 | 1,718 |
[
"Piwigo",
"Piwigo"
] |
UI must be se same no matter the file extension of the picture
|
[Edit picture] Margins are not the same when picture is SVG and other type
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1717/comments
| 1 |
2022-09-07T11:58:56Z
|
2022-09-14T10:13:41Z
|
https://github.com/Piwigo/Piwigo/issues/1717
| 1,364,555,144 | 1,717 |
[
"Piwigo",
"Piwigo"
] |
Was getting the following error when trying to update my extensions:
`[Tue Sep 06 11:33:23.152166 2022] [php:info] [pid 2466] [client 192.168.1.250:64629] PHP Deprecated: Implicit conversion from float 1662482003.152163 to int loses precision in /data/photos/software/piwigo/include/Logger.class.php on line 367
`
I patched this on my system, fix below:
```
--- piwigo/include/Logger.class.php.orig 2022-09-06 11:35:08.660271896 -0500
+++ piwigo/include/Logger.class.php 2022-09-06 11:34:18.356824710 -0500
@@ -364,7 +364,7 @@
{
$originalTime = microtime(true);
$micro = sprintf('%06d', ($originalTime - floor($originalTime)) * 1000000);
- $date = new DateTime(date('Y-m-d H:i:s.'.$micro, $originalTime));
+ $date = new DateTime(date('Y-m-d H:i:s.'.$micro, intval($originalTime)));
return $date->format($this->options['dateFormat']);
}
```
|
Can't update extensions in 13.0.0RC3
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1715/comments
| 0 |
2022-09-06T16:37:39Z
|
2022-09-21T14:57:51Z
|
https://github.com/Piwigo/Piwigo/issues/1715
| 1,363,548,792 | 1,715 |
[
"Piwigo",
"Piwigo"
] |
When uploading an svg, either they are too big or they are invisible.
|
Svg in resumé of uploaded photos are not sized properly
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1714/comments
| 0 |
2022-09-06T09:47:07Z
|
2022-09-06T09:54:37Z
|
https://github.com/Piwigo/Piwigo/issues/1714
| 1,363,012,115 | 1,714 |
[
"Piwigo",
"Piwigo"
] |
A huge white space pushed the form down under the page.
|
[Photo add form] Add photo form disapeared on 13RC3
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1713/comments
| 0 |
2022-09-05T11:15:33Z
|
2022-09-05T11:28:49Z
|
https://github.com/Piwigo/Piwigo/issues/1713
| 1,361,777,363 | 1,713 |
[
"Piwigo",
"Piwigo"
] |
See https://fr.piwigo.org/forum/viewtopic.php?id=29785 (related to #28)
Let's fallback to the approved `fetchRemote` function.
|
[dashboard] error on Piwigo latest news behind proxy
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1712/comments
| 0 |
2022-08-27T15:25:35Z
|
2022-08-27T15:27:10Z
|
https://github.com/Piwigo/Piwigo/issues/1712
| 1,353,073,116 | 1,712 |
[
"Piwigo",
"Piwigo"
] |
When I remove the start date, I'm supposed to get more results "at the end" of the list. The first line should not change. In my case, it changes and it seems to hide the most results.
|
[13] visits history, incoherent results when removing start date
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1711/comments
| 0 |
2022-08-26T14:48:49Z
|
2022-09-28T10:52:48Z
|
https://github.com/Piwigo/Piwigo/issues/1711
| 1,352,374,574 | 1,711 |
[
"Piwigo",
"Piwigo"
] |
When I see the "other" section on the storage bar, I really wonder what it's hiding. Piwigo knows it, so I think it would be good to provide the details.
with details:
|
[dashboard] storage bar, provide details about "other"
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1710/comments
| 1 |
2022-08-26T06:35:04Z
|
2023-11-08T14:02:17Z
|
https://github.com/Piwigo/Piwigo/issues/1710
| 1,351,818,172 | 1,710 |
[
"Piwigo",
"Piwigo"
] |
1) check number of custom size files
```
~/git/Piwigo/_data/i$ find . -name "*-cu_*" | wc -l
66
```
2) use action [Administration > Tools > Maintenance > Actions > Delete multiple size images > Custom]
3) check number of custom size files
```
~/git/Piwigo/_data/i$ find . -name "*-cu_*" | wc -l
66
```
|
[maintenance] deleting custom sizes does not work
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1709/comments
| 0 |
2022-08-22T13:03:09Z
|
2022-09-09T10:42:41Z
|
https://github.com/Piwigo/Piwigo/issues/1709
| 1,346,389,814 | 1,709 |
[
"Piwigo",
"Piwigo"
] |
In the current Piwigo 12, we display the age of the first photo added in Piwigo. On the dashboard.
The problems are:
- you might delete this first photo and the "age" of your Piwigo will change...
- I don't think this information is relevant on the dashboard
I propose we display the age of the Piwigo on the Maintenance page instead and we base the age on the `user_infos.registration_date` of the guest user (id=2) instead.
|
display age of Piwigo on the maintenance page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1707/comments
| 0 |
2022-08-19T08:17:19Z
|
2022-08-19T09:20:23Z
|
https://github.com/Piwigo/Piwigo/issues/1707
| 1,344,110,425 | 1,707 |
[
"Piwigo",
"Piwigo"
] |
Admin -> Configuration -> Multiple sizes
Deselecting one or more sizes / editing the size parameters are not saved after clicking the "Save Settings" button
Operating system: Linux
PHP: 7.4.30
MySQL: 5.7.39-0ubuntu0.18.04.2
Graphics Library: GD 2.3.3
|
13.0.0RC2 Photo size configurations are not saved
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1705/comments
| 2 |
2022-08-09T23:00:09Z
|
2022-09-21T14:37:23Z
|
https://github.com/Piwigo/Piwigo/issues/1705
| 1,333,870,812 | 1,705 |
[
"Piwigo",
"Piwigo"
] |
Redesign of the properties tab on the album edition page, according to the following design (created by Alice).
|
Album edition page redesign
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1704/comments
| 1 |
2022-08-05T13:13:30Z
|
2023-06-26T09:31:18Z
|
https://github.com/Piwigo/Piwigo/issues/1704
| 1,329,925,367 | 1,704 |
[
"Piwigo",
"Piwigo"
] |
In ws.htm the pwg.history.search method takes 0 param so we can't use the method here.
We need to add the params in ws.php and make the method work on the history page and in ws.htm.
|
[History search] pwg.history.search method has 0 params
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1703/comments
| 0 |
2022-08-03T14:27:28Z
|
2023-07-04T14:59:36Z
|
https://github.com/Piwigo/Piwigo/issues/1703
| 1,327,308,111 | 1,703 |
[
"Piwigo",
"Piwigo"
] |
HI,
I have a Piwigo installed on my server for many years now, and it works like a charm, I love this soft, thanks for all the hard work ! :heart:
I open this issue to report a new error that I did not have when using Piwigo on PHP 7.x, and seems to have appeared when updating to PHP 8.1: when creating or renaming an album, if the name contains an apostrophe, I get the following error (when trying for example to create an album "vacances d'été 2022"):
``
Fatal error: Uncaught mysqli\_sql\_exception: 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 'été 2022', `comment` = NULL, `commentable` = 'true' WHERE `id` = ...' at line 3 in /photos/piwigo/include/dblayer/functions\_mysqli.inc.php:132 Stack trace: #0 //piwigo/include/dblayer/functions\_mysqli.inc.php(132): mysqli->query() #1 /photos/piwigo/include/dblayer/functions\_mysqli.inc.php(478): pwg\_query() #2 /photos/piwigo/admin/cat\_modify.php(118): single\_update() #3 /photos/piwigo/admin/album.php(60): include('...') #4 //photos/piwigo/admin.php(320): include('...') #5 {main} thrown in /photos/piwigo/include/dblayer/functions\_mysqli.inc.php on line 132
``
As I am French, I have many existing albums with apostrophe, and there was no issue in the past. So I guess this is an issue with PHP 8 ? Note that when using `Vacances d\'été 2022` for example, escaping the apostrophe with a `\` the issue does not occur.
I am afraid this might also be a security issue, if the content of the SQL requests are not parsed to make sure unwanted characters are not interpreted ?
Thanks for your time !
|
Album creation / renaming failed if containing apostrophe with PHP 8.1
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1701/comments
| 1 |
2022-08-02T16:11:08Z
|
2022-09-26T12:47:59Z
|
https://github.com/Piwigo/Piwigo/issues/1701
| 1,326,079,738 | 1,701 |
[
"Piwigo",
"Piwigo"
] |
As we did with the user manager, we stop using cookies and we use user_prefs for the view selector in plugin manager.
|
[Plugin Manager] Change view selector so we use user_prefs
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1700/comments
| 0 |
2022-08-01T15:07:21Z
|
2022-08-01T15:11:33Z
|
https://github.com/Piwigo/Piwigo/issues/1700
| 1,324,571,858 | 1,700 |
[
"Piwigo",
"Piwigo"
] |
We implemented the view selector with the use of cookies, but now that we have user_prefs we change it for the greater good.
|
[User Manager] Change view selector so we use user_prefs
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1699/comments
| 0 |
2022-08-01T13:57:21Z
|
2022-08-01T13:58:07Z
|
https://github.com/Piwigo/Piwigo/issues/1699
| 1,324,472,016 | 1,699 |
[
"Piwigo",
"Piwigo"
] |
Hi,
- Users -> Activity -> User Activity logs
- Dashboard -> Users -> activity
These two options do not give the same results, see the two screen shots.
Piwigo 12.3.0
Linux : raspberry / Raspbian GNU/Linux 11 (bullseye)
PHP: 7.4.30
MySQL: 5.5.5-10.5.15-MariaDB-0+deb11u1
External ImageMagick 6.9.11-60
Thank you
|
User activity not coherent
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1698/comments
| 2 |
2022-07-30T12:35:31Z
|
2022-09-28T14:35:49Z
|
https://github.com/Piwigo/Piwigo/issues/1698
| 1,323,011,719 | 1,698 |
[
"Piwigo",
"Piwigo"
] |
## Hello,
- - - Go and fix this stupid thing!
## Description:
The value of the /search/1940/created-monthly-list request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks.
## Payload:
```java
GET /piwigo/index.php?/search/4863/created-monthly-list%22%3Ehttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcomhttps:\pornhubdotcom%3CYZxWX%3E HTTP/1.1
Host: pwned_host.com
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Firefox/102.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
DNT: 1
Connection: close
Cookie: pwg_id=hctfqtab45adhogo2suhq2mr0c; ssc_phoneSwap=0
Upgrade-Insecure-Requests: 1
```
PoC:
[href](https://github.com/nu11secur1ty/CVE-nu11secur1ty/blob/main/vendors/Piwigo/2022/12.3.0/Docs/Pwigo-XSS-Reflected.gif)
|
XSS-Reflected
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1697/comments
| 0 |
2022-07-28T11:54:41Z
|
2022-09-16T08:38:43Z
|
https://github.com/Piwigo/Piwigo/issues/1697
| 1,320,820,385 | 1,697 |
[
"Piwigo",
"Piwigo"
] |
|
[Album Manager] Green badge icon is too close to number
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1696/comments
| 0 |
2022-07-27T12:51:24Z
|
2022-07-27T12:55:36Z
|
https://github.com/Piwigo/Piwigo/issues/1696
| 1,319,519,909 | 1,696 |
[
"Piwigo",
"Piwigo"
] |
The javascript has errors when the piwigo url as some "-" in it which is not so uncommon. Review the way you get the catId in url with the split.
|
[Album move] Can't open nodes on piwigo with certain urls
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1695/comments
| 0 |
2022-07-25T10:53:41Z
|
2022-07-25T10:57:30Z
|
https://github.com/Piwigo/Piwigo/issues/1695
| 1,316,640,425 | 1,695 |
[
"Piwigo",
"Piwigo"
] |
I don't know if it is a Piwigo bug, or a Shotwell's Piwigo plugin problem, I've also opened a bug on Shotwell side:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1982564
Trying to upload photo to Piwigo via Shotwell plugin I got and error like "URL not valid" (I got it in Italian).
Looking at Piwigo side I found this php error:
[22-Jul-2022 11:06:39 Europe/Berlin] PHP Deprecated: substr(): Passing null to parameter #1 ($string) of type string is deprecated in /var/www/piwigo/include/functions_user.inc.php on line 804
[22-Jul-2022 11:06:39 Europe/Berlin] PHP Fatal error: Uncaught TypeError: get_class(): Argument #1 ($object) must be of type object, bool given in /var/www/piwigo/include/ws_protocols/rest_encoder.php:145
Stack trace:
#0 /var/www/piwigo/include/ws_core.inc.php(289): PwgRestEncoder->encodeResponse()
#1 /var/www/piwigo/include/ws_protocols/rest_handler.php(42): PwgServer->sendResponse()
#2 /var/www/piwigo/include/ws_core.inc.php(281): PwgRestRequestHandler->handleRequest()
#3 /var/www/piwigo/ws.php(22): PwgServer->run()
#4 {main}
thrown in /var/www/piwigo/include/ws_protocols/rest_encoder.php on line 145
[22-Jul-2022 11:06:40 Europe/Berlin] PHP Deprecated: substr(): Passing null to parameter #1 ($string) of type string is deprecated in /var/www/piwigo/include/functions_user.inc.php on line 804
[22-Jul-2022 11:06:40 Europe/Berlin] PHP Fatal error: Uncaught TypeError: get_class(): Argument #1 ($object) must be of type object, bool given in /var/www/piwigo/include/ws_protocols/rest_encoder.php:145
Stack trace:
#0 /var/www/piwigo/include/ws_core.inc.php(289): PwgRestEncoder->encodeResponse()
#1 /var/www/piwigo/include/ws_protocols/rest_handler.php(42): PwgServer->sendResponse()
#2 /var/www/piwigo/include/ws_core.inc.php(281): PwgRestRequestHandler->handleRequest()
#3 /var/www/piwigo/ws.php(22): PwgServer->run()
#4 {main}
thrown in /var/www/piwigo/include/ws_protocols/rest_encoder.php on line 145
I think both Shotwell and Piwigo are updated to latest version:
Shotwell: 0.30.14 – “Celle”
Piwigo 12.3.0
Operating System: Linux
PHP: 8.1.2
MySQL: 5.5.5-10.6.7-MariaDB-2ubuntu1.1
Grafic Lib: GD 2.3.0
Thanks
Giulio
|
[PHP 8.1] Shotwell cannot upload anymore
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1694/comments
| 3 |
2022-07-22T09:30:37Z
|
2022-07-22T10:05:49Z
|
https://github.com/Piwigo/Piwigo/issues/1694
| 1,314,764,421 | 1,694 |
[
"Piwigo",
"Piwigo"
] |
With php 8.0 and 8.1, warnings appear in piwigo, we need to fix them so Piwigo becomes compatible with php 8.1 and 8.0.
|
Compatibility with php 8.0 and php 8.1
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1693/comments
| 1 |
2022-07-19T09:53:33Z
|
2022-07-28T14:17:41Z
|
https://github.com/Piwigo/Piwigo/issues/1693
| 1,309,271,668 | 1,693 |
[
"Piwigo",
"Piwigo"
] |
I updated Chrome today which seems to have switched to HTTP2 by default. When viewing a photo via `i.php` the image is broken and there is an error in the console :
```
GET https://galerie.strangeplanet.fr/i.php?/upload/2022/07/16/20220716130608-9f2835c1-sq.jpg net::ERR_HTTP2_PROTOCOL_ERROR 200
```
You can test it here by clicking on any blue pin https://galerie.strangeplanet.fr/osmmap.php?/categories&v=2
Or here https://galerie.strangeplanet.fr/picture.php?/6993/category/231 by switching to the XS resolution (assuming the image has not been generated and cached, so it will only be broken once per image/resolution).
I did some search and found this discussion : https://stackoverflow.com/questions/58215104/whats-the-neterr-http2-protocol-error-about
It _may_ be related to the `Content-Length` header which is more striclty checked in HTTP2, and the size is obviously wrong when gzip is enabled on the server.
|
Error loading images over HTTP2
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1692/comments
| 1 |
2022-07-18T09:52:31Z
|
2022-08-22T13:09:30Z
|
https://github.com/Piwigo/Piwigo/issues/1692
| 1,307,695,694 | 1,692 |
[
"Piwigo",
"Piwigo"
] |
while uploading photos, there will be thumbs created below the upload section. New photos are added to the left, so all thumbs jump to the right which makes this pretty choppy. Better ad new images to the right so already added image thumbs stay in their place
|
when adding new photos, add the thumbs to the right not to the left
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1691/comments
| 2 |
2022-07-17T11:59:24Z
|
2022-09-23T13:07:52Z
|
https://github.com/Piwigo/Piwigo/issues/1691
| 1,307,076,545 | 1,691 |
[
"Piwigo",
"Piwigo"
] |
Ex : 'test+' name cause error "Name in empty"
|
[Group Manager] '+' symbol group name end causes error
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1690/comments
| 0 |
2022-07-11T10:58:46Z
|
2022-07-14T16:33:15Z
|
https://github.com/Piwigo/Piwigo/issues/1690
| 1,300,545,049 | 1,690 |
[
"Piwigo",
"Piwigo"
] |
When we add a group, the group list shuffle like crazy and we lose sight of the add button and the group we just added.
|
[Group Manager] Group list shuffles after adding a group
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1689/comments
| 0 |
2022-07-11T10:09:41Z
|
2022-07-14T16:33:53Z
|
https://github.com/Piwigo/Piwigo/issues/1689
| 1,300,492,133 | 1,689 |
[
"Piwigo",
"Piwigo"
] |
I'm currently trying to extend quicksearch to search contents of private fields. For this i use the eventHandler
"qsearch_results" wich allows me to add the so found items to $search_results['items'].
This works, as long as there is no match on the core fields. If there is such a match, then the content of $search_results['items'] wil be overwritten by later code during permission checks.
IMO the handler for qsearch_results should receive a copy of the $ids array, an return a new $ids array (changed or not)
$ids = trigger_change('qsearch_results', $ids, $expression, $qsr);
|
impossible to change search_results during handling of event "qsearch_results"
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1686/comments
| 2 |
2022-07-11T07:38:33Z
|
2022-07-20T09:29:42Z
|
https://github.com/Piwigo/Piwigo/issues/1686
| 1,300,328,423 | 1,686 |
[
"Piwigo",
"Piwigo"
] |
We previously added SVG support for Piwigo but we found out that there was problem when using php8.
|
SVG support compatibility with php 8.0 and 8.1
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1684/comments
| 2 |
2022-07-06T14:46:57Z
|
2022-07-14T16:33:00Z
|
https://github.com/Piwigo/Piwigo/issues/1684
| 1,295,953,361 | 1,684 |
[
"Piwigo",
"Piwigo"
] |
When the user agent in "details" is too long it becomes impossible for the php to unserialize it because mysql just cuts when the varchar is too long, so we moved the user agent in a dedicated column.
|
[Activity Page] The page is broken when user agent is too long
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1683/comments
| 2 |
2022-07-05T15:33:34Z
|
2022-07-14T16:38:42Z
|
https://github.com/Piwigo/Piwigo/issues/1683
| 1,294,459,706 | 1,683 |
[
"Piwigo",
"Piwigo"
] |
I'm using python 3.9 and the requests package to upload images to my Piwigo gallery. I want to associate multiple tags with an image when I upload. My request code looks much like the following:
```
tags = ["some text", "more text"]
headers = {'Accept': 'application/json'}
params = {'format' : 'json', 'method' : 'pwg.images.addSimple', 'Content-Type' : 'form-data'}
files = {
'image' : open(filename, "rb")
}
data = {
'pwg_token' : pwg_token,
'tags' : json.dumps(tags)
}
requests.post(piwigo_url, headers=headers, params=params, data = data, files=files)
```
Doing this leads to erroneous square brackets and quotation marks in the uploaded tag names. See the following image for an example of the incorrect tag names. The tag containing no quotation marks or square brackets is the format I am expecting for all the tags.
<img width="1194" alt="Screen Shot 2022-06-30 at 11 55 04 AM" src="https://user-images.githubusercontent.com/108487316/176749619-9f4c48cd-53d1-4c96-accc-a92c62dc9f10.png">
|
[API] pwg.images.addSimple endpoint incorrectly parses request JSON array
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1680/comments
| 1 |
2022-06-30T18:20:05Z
|
2022-07-06T14:19:19Z
|
https://github.com/Piwigo/Piwigo/issues/1680
| 1,290,489,725 | 1,680 |
[
"Piwigo",
"Piwigo"
] |
We add more sense to piwigo tabs through the administration by uniformizing their titles.
|
Titles uniformisation in admin
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1679/comments
| 0 |
2022-06-27T09:21:53Z
|
2022-07-14T16:35:00Z
|
https://github.com/Piwigo/Piwigo/issues/1679
| 1,285,507,025 | 1,679 |
[
"Piwigo",
"Piwigo"
] |
I have the following configuration:
`browser ->(https)-> apache reverse proxy ->(http)-> nginx reverse proxy ->(http)-> piwigo`
In this case, the variable `$_SERVER['HTTP_X_FORWARDED_HOST']` on Piwigo does not hold the hostname currently expected in Piwigo code (see https://github.com/Piwigo/Piwigo/blob/master/include/functions_url.inc.php#L52), but a comma-separated list of hostnames. In my case it was twice the right one: `myhostname, myhostname`
The result was a broken batch resize feature, because the API returned invalid URLs like:
`https://myhostname, myhostname/i.php?...`
where it should be:
`https://myhostname/i.php?...`
I managed to workaround that by adding the following lines in `local/config/config.inc.php`. When there is a comma in this variable, it keeps only the first value (the one before the first comma):
```
if ($_SERVER['HTTP_X_FORWARDED_HOST'] && strpos($_SERVER['HTTP_X_FORWARDED_HOST'], ',') !== FALSE){
$_SERVER['HTTP_X_FORWARDED_HOST'] = explode(',',$_SERVER['HTTP_X_FORWARDED_HOST'])[0];
}
```
I think that this logic should be in https://github.com/Piwigo/Piwigo/blob/master/include/functions_url.inc.php#L52
That's how some other projects implemented it. See https://github.com/xp-framework/xp-framework/issues/162 , https://github.com/RicoSuter/NSwag/issues/2370 , https://github.com/pallets/werkzeug/issues/371 or https://bz.apache.org/bugzilla/show_bug.cgi?id=57665#c14
I can create a PR if you want.
|
X-Forwarded-Host header with a comma-separated list should be supported
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1678/comments
| 0 |
2022-06-26T16:05:41Z
|
2022-06-26T16:05:41Z
|
https://github.com/Piwigo/Piwigo/issues/1678
| 1,284,963,928 | 1,678 |
[
"Piwigo",
"Piwigo"
] |
Support for iOS Live Photos would be a very welcome feature.
|
iOS Live Photos
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1677/comments
| 6 |
2022-06-26T03:08:07Z
|
2023-12-21T21:53:35Z
|
https://github.com/Piwigo/Piwigo/issues/1677
| 1,284,784,312 | 1,677 |
[
"Piwigo",
"Piwigo"
] |
All the statistics (Hour, day, month, year) can be displayed when it is not in compare mode. However, the statistics of "Hour" and "Day" cannot be shown when it is in compare mode.
|
[Tools - History] "Hour" and " Day" charts cannot be selected when it is in compare mode
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1676/comments
| 1 |
2022-06-23T18:29:36Z
|
2022-07-15T16:41:50Z
|
https://github.com/Piwigo/Piwigo/issues/1676
| 1,282,787,486 | 1,676 |
[
"Piwigo",
"Piwigo"
] |
When the plugin is deactivated, the system shows an error message.
|
[Plugin] Deactivation of plugin shows error messages
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1675/comments
| 1 |
2022-06-23T18:08:54Z
|
2022-09-23T13:10:38Z
|
https://github.com/Piwigo/Piwigo/issues/1675
| 1,282,766,097 | 1,675 |
[
"Piwigo",
"Piwigo"
] |
Verify the creation and changes of the album name
i) Validate the changing of the existing album name into null
-When an administrator intends to change the name of an existing album to empty, the album information can still be updated
successfully.
ii) The same existing album name is used to create a new album
- Admins can still add new albums using existing album names.
iii) Check the edit icon of album
-After clicking the edit album icon on the right end side of each album, it will navigate to the "Dashboard" page.
|
[Album] Verify the creation and changes of the album name
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1674/comments
| 0 |
2022-06-23T18:01:24Z
|
2022-06-23T18:01:24Z
|
https://github.com/Piwigo/Piwigo/issues/1674
| 1,282,758,846 | 1,674 |
[
"Piwigo",
"Piwigo"
] |
Some emails don't fit in the email field which is limited to 40 characters
|
forgotten password email field is too short
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1673/comments
| 0 |
2022-06-22T13:43:51Z
|
2022-06-22T14:30:57Z
|
https://github.com/Piwigo/Piwigo/issues/1673
| 1,280,167,931 | 1,673 |
[
"Piwigo",
"Piwigo"
] |
On a very few piwigo acccount we got reported that the activity page wasn't loading properly. After some investigations we found out that the detail column in the activity table was a varchar(255) and it was used to store some serialized php. The detail column is used to store the user agent and it happened that if the user agent was too long, the serialized php went over 255 characters and so the serialized php could not be unserialized and that caused some errors.
For Piwigo 12 we can do a quick fix but in Piwigo 13 we plan to move the user agent from the $details to a separate column in the activity table.
|
[Activity page] Unserializing $details breaks sometimes
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1672/comments
| 0 |
2022-06-20T12:47:42Z
|
2022-07-05T15:48:09Z
|
https://github.com/Piwigo/Piwigo/issues/1672
| 1,276,877,534 | 1,672 |
[
"Piwigo",
"Piwigo"
] |
Namespaces have been included in PHP since version 5.3, they are vital to preventing conflicts that may arise from having two codebases interacting. Currently I am attempting to write an integration between Piwigo and phpBB, but unfortunately several functions share the same name. It is my understanding that this can be solved by adding the following code to the various source files:
```php
<?php
namespace Piwigo;
```
This will make all functions and classes accessible from within Piwigo and if using from a different codebase, the functions can be accessed by appending _\Piwigo_ to any function or class declaration. It also allows Piwigo to integrate other pre-written libraries without conflicts in the code.
|
Add a Piwigo Namespace
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1671/comments
| 1 |
2022-06-16T02:31:39Z
|
2022-09-23T13:12:04Z
|
https://github.com/Piwigo/Piwigo/issues/1671
| 1,272,966,179 | 1,671 |
[
"Piwigo",
"Piwigo"
] |
Hello,As part of a testing project under a software testing course at University Malaya we are currently testing piwigo.We have found a PHP mailer exception when the admin tries to move the user to the subscribed group.We hope you will look into this matter further.
|
Php mailer exception
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1670/comments
| 1 |
2022-06-11T16:13:52Z
|
2022-07-06T09:35:18Z
|
https://github.com/Piwigo/Piwigo/issues/1670
| 1,268,315,205 | 1,670 |
[
"Piwigo",
"Piwigo"
] |
> [mysql error 1264] Out of range value for column 'height' at row 1 UPDATE piwigo_images SET width=8192, height=122880 WHERE id=95 in /opt/piwigo/include/dblayer/functions_mysqli.inc.php on line 864
The above error occurs when Large size images is uploaded
This error maybe fixed by editting maximum heght size of mysql.
But I am newer.
Could you answer the following question?
1. Which file I should edid to edit maximum heght size of mysql?
2. Side effect of editting maximum heght size
|
Out of range value for image height
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1669/comments
| 1 |
2022-06-09T08:08:38Z
|
2022-07-21T08:00:11Z
|
https://github.com/Piwigo/Piwigo/issues/1669
| 1,265,757,087 | 1,669 |
[
"Piwigo",
"Piwigo"
] |
When going to the activity page the menu on the left closes. We need the user section of the menu to be open.
|
[Activity page] Menu is closed when going on activity page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1668/comments
| 0 |
2022-06-08T12:57:26Z
|
2022-07-14T16:39:00Z
|
https://github.com/Piwigo/Piwigo/issues/1668
| 1,264,704,109 | 1,668 |
[
"Piwigo",
"Piwigo"
] |
Hi,
Piwigo -> Photos > Batch management -> filter on one album -> Edit one photo -> delete this photo
Then the next page displayed is "homepage"
and it is needed to go back to "admin" > Photos > and so on
Done several times, identical behaviour each time.
Piwigo 12.2.0
OS: Linux / Rapsberry pi / 11 (bullseye)
PHP: 7.4.28
MySQL: 5.5.5-10.5.15-MariaDB-0+deb11u1
Graphics library: External ImageMagick 6.9.11-60
|
Incorrect return path after deleting a photo
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1667/comments
| 2 |
2022-06-07T14:58:26Z
|
2022-09-28T16:48:39Z
|
https://github.com/Piwigo/Piwigo/issues/1667
| 1,263,440,735 | 1,667 |
[
"Piwigo",
"Piwigo"
] |
For the new album manager we added a "last modified" badge that indicate when was the albums "last modified" but it appears that moving some albums next to it triggers the "last modified" parameter which makes it less relevant. So we choose to hide it and instead add the number of pictures contained in all the sub-albums of the current album (As we had in the previous album manager)
|
[Album Manager] Change lastmodified badge
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1666/comments
| 0 |
2022-06-07T13:02:26Z
|
2022-07-14T16:37:32Z
|
https://github.com/Piwigo/Piwigo/issues/1666
| 1,263,264,980 | 1,666 |
[
"Piwigo",
"Piwigo"
] |
Tiptip tooltips are not centered, we need to fix that
|
[Album Manager] Tiptip tooltips are not centered with the action icons
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1665/comments
| 0 |
2022-06-07T12:46:35Z
|
2022-07-14T16:37:52Z
|
https://github.com/Piwigo/Piwigo/issues/1665
| 1,263,239,189 | 1,665 |
[
"Piwigo",
"Piwigo"
] |
In Piwigo 13 we implemented SVG support, but we still use raw SVG in gallery and administration pages which can cause some latency if the uploaded SVGs are too big. As SVGs are mostly used for Icons and drawings with not a lot of details, this should not be felt by the users but for the worst case scenarios we will add a size limit for SVGs.
If the SVG is too big we will create a representative for it so the page loading time is shortened. We still have to decide what the limit is.
|
SVG size threshold for direct display
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1664/comments
| 0 |
2022-06-06T10:13:43Z
|
2024-07-31T15:16:06Z
|
https://github.com/Piwigo/Piwigo/issues/1664
| 1,261,639,915 | 1,664 |
[
"Piwigo",
"Piwigo"
] |
Attempts to login using digikam export plugin fails.
The login actually succeeds but piwigo throws an exception and doesn't respond to the request.
` PHP Fatal error: Uncaught
TypeError: get_class(): Argument #1 ($object) must be of type object, bool given in /var/www/domainname/piwigo/include/ws_protocols/rest_encoder.php:145`
Analysis shows login handler returns the bool whereas the function encodeResponse($response) is conditionallly expecting an PwgError object.
I will raise a pull request to fix this.
|
[API] pwg.session.login fails from digikam export plugin
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1662/comments
| 1 |
2022-06-02T00:05:15Z
|
2022-07-19T17:14:12Z
|
https://github.com/Piwigo/Piwigo/issues/1662
| 1,257,334,429 | 1,662 |
[
"Piwigo",
"Piwigo"
] |
Hello,As part of a testing project under a software testing course at University Malaya we are currently testing piwigo.We have found several deprecated warnings when piwigo is used with PHP version 8.1.6 or higher. We hope you will look into this matter further
|
Deprecated warnings appear when used with php 8.1.6
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1661/comments
| 9 |
2022-05-25T15:21:56Z
|
2023-12-17T11:24:22Z
|
https://github.com/Piwigo/Piwigo/issues/1661
| 1,248,265,281 | 1,661 |
[
"Piwigo",
"Piwigo"
] |
I run Piwigo 13.0.0 beta 2, upgraded from 11 to 12 to 13. Visiting `/admin.php?page=updates&tab=ext` won't let me come through - alongside with a bunch of deprecation warnings, I get one fatal error:
```
Fatal error: Type of SmartyCompilerException::$line must be int (as in class Exception) in /(REDACTED)/include/smarty/libs/sysplugins/smartycompilerexception.php on line 8
```
I could imagine that this is just another PHP 8.1 problem...?
Environment:
```
$ php --version
PHP 8.1.5 (cli) (built: Apr 12 2022 16:19:58) (NTS gcc x86_64)
Copyright (c) The PHP Group
Zend Engine v4.1.5, Copyright (c) Zend Technologies
with Zend OPcache v8.1.5, Copyright (c), by Zend Technologies
```
|
[PHP 8.1] Can't update my extensions
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1660/comments
| 5 |
2022-05-16T22:07:42Z
|
2022-09-28T17:43:56Z
|
https://github.com/Piwigo/Piwigo/issues/1660
| 1,237,784,209 | 1,660 |
[
"Piwigo",
"Piwigo"
] |
I'm not sure if this is PHP8 related but I got this message:
Fatal error: Uncaught TypeError: strip_tags(): Argument #1 ($string) must be of type string, array given in /xxx/include/functions_metadata.inc.php:190 Stack trace: #0 /xxx/include/functions_metadata.inc.php(190): strip_tags() #1 /xxx/include/picture_metadata.inc.php(24): get_exif_data() #2 /xxx/picture.php(1017): include('...') #3 {main} thrown in /xxx/include/functions_metadata.inc.php on line 190
In the functions_metadata.inc.php on line 190 (as mentioned above) I disabled the strip_tags($value); and I do not get the error message anymore. The error prevents the page to be displayed, especially with reading Exif (like in Bootstrap Darkroom etc) for the picture/photo page.
if (!$conf['allow_html_in_metadata'])
{
foreach ($result as $key => $value)
{
// in case the origin of the photo is unsecure (user upload), we remove
// HTML tags to avoid XSS (malicious execution of javascript)
**//$result[$key] = strip_tags($value);**
}
}
See also on the forum -> https://piwigo.org/forum/viewtopic.php?pid=183718#p183718
BTW ... PHP says about strip_tags(): This function should not be used to try to prevent XSS attacks. Use more appropriate functions like htmlspecialchars() or other means depending on the context of the output.
Environment:
Piwigo 12.2.0
Operating system: Linux
PHP: 8.0.8 (Show info) [2022-05-12 13:00:07]
MySQL: 8.0.29-0ubuntu0.21.10.2 [2022-05-12 13:00:07]
Graphics Library: ImageMagick 6.9.11-60
|
[PHP8?] functions_metadata.inc.php Fatal error strip_tags()
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1659/comments
| 0 |
2022-05-12T11:09:39Z
|
2022-05-12T11:11:04Z
|
https://github.com/Piwigo/Piwigo/issues/1659
| 1,233,823,348 | 1,659 |
[
"Piwigo",
"Piwigo"
] |
Uploading .png is successful.
png image couldn't be displayed on galleries page.
According to /var/log/apache2/error.log, PHP may cause this error.
_PHP Warning: imagesy() expects parameter 1 to be resource, bool given in ***/piwigo/admin/include/image.class.php on line 689,_
Similar problem is found in https://piwigo.org/forum/viewtopic.php?id=22731.
But this doesn't say how to fix it by ccs coding
Could you tell how to fix it.
Environment
OS: Ubuntu 18.04
PHP: 7.4.3
MySQL: Ver 15.1 Distrib 10.3.34-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
|
Display .png return error
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1658/comments
| 1 |
2022-05-12T02:20:34Z
|
2022-05-13T02:40:11Z
|
https://github.com/Piwigo/Piwigo/issues/1658
| 1,233,362,790 | 1,658 |
[
"Piwigo",
"Piwigo"
] |
We chosed to implement support of svg files for piwigo, this takes into account the thumbnail on the edit picture page.
|
SVG support for piwigo
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1657/comments
| 3 |
2022-04-27T13:06:01Z
|
2022-07-14T16:39:43Z
|
https://github.com/Piwigo/Piwigo/issues/1657
| 1,217,332,989 | 1,657 |
[
"Piwigo",
"Piwigo"
] |
For those pages, we decided to simplify their titles with : "Obect" + Badge.
Ex: Albums 120.
|
[Tags/Groups/Users] Page title uniformisation
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1656/comments
| 0 |
2022-04-26T10:15:11Z
|
2022-04-26T10:24:34Z
|
https://github.com/Piwigo/Piwigo/issues/1656
| 1,215,726,637 | 1,656 |
[
"Piwigo",
"Piwigo"
] |
As this section is a bit confused for the user, we decided to remove it. Plus we can also delete custom sizes in the Maintenance page.
|
[Options page] Removing custom sizes in configuration section
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1655/comments
| 1 |
2022-04-26T08:31:45Z
|
2022-09-12T14:18:59Z
|
https://github.com/Piwigo/Piwigo/issues/1655
| 1,215,598,930 | 1,655 |
[
"Piwigo",
"Piwigo"
] |
Differents files of the _data folder, I don't know what files generate them. create on my navbar some php errors:
Piwigo : 12.2.0
php: 8.0
example :
`Warning: Undefined array key "count_categories" in piwigo\_data\templates_c\jbliys^b6e599d81599c8c06e88fc7c914623696fa9e298_0.file.menubar_related_categories.tpl.php on line 56`
It's the case for count_categories here, but also for "title" in the same file, or "level" in the tags file. for the moment, not finding where it come from, I desactivated php errors. (second solution, before I did "$_smarty_tpl->tpl_vars['...']->value['...']??'' " but I thought it's not a good idea to modified these files.
|
unknow array key in $_smarty_tpl->tpl_vars['...']->value['...']
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1654/comments
| 3 |
2022-04-24T20:12:02Z
|
2022-10-13T18:07:55Z
|
https://github.com/Piwigo/Piwigo/issues/1654
| 1,213,756,182 | 1,654 |
[
"Piwigo",
"Piwigo"
] |
`Deprecated: Function strftime() is deprecated in / ... /include/smarty/libs/sysplugins/smarty_internal_runtime_codeframe.php on line 48`
[https://www.php.net/manual/en/function.strftime.php](url)
`Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in / ... /include/template.class.php on line 911`
|
strftime deprecated in PHP 8.1
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1653/comments
| 2 |
2022-04-22T10:30:29Z
|
2023-04-10T21:48:30Z
|
https://github.com/Piwigo/Piwigo/issues/1653
| 1,212,171,113 | 1,653 |
[
"Piwigo",
"Piwigo"
] |
When the option `$conf['original_url_protection'] = 'images';` is set, Piwigo replaces the URLs of images with URLs of the type `…/action.php?id=9712&part=e`.
When this configuration is set, the `pwg.images.getInfo` method returns an URL of the type `…/action.php?id=9712&part=e` where the ampersand symbol was replaced with `&` i.e. HTML encoded (see https://github.com/Piwigo/Piwigo-Mobile/issues/503).
This is not a valid URL and this prevents third party apps to exploit the image (to share it for example). A quick fix would be highly appreciated.
|
[API] pwg.images.getInfo returns HTML encoded URLs
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1652/comments
| 0 |
2022-04-14T06:31:29Z
|
2022-04-14T06:31:29Z
|
https://github.com/Piwigo/Piwigo/issues/1652
| 1,204,096,109 | 1,652 |
[
"Piwigo",
"Piwigo"
] |
In the plugin installer, after installing a plugin, the activate link redirects to the plugin manager page but with the "Activated" filter selected. So we can't activate the plugin directly.
|
[Plugins Manager] After installing a plugin, activate action wrong redirect
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1651/comments
| 2 |
2022-04-12T14:00:05Z
|
2022-07-14T16:32:44Z
|
https://github.com/Piwigo/Piwigo/issues/1651
| 1,201,897,756 | 1,651 |
[
"Piwigo",
"Piwigo"
] |
Since version 12.2.0, the `pwg.getInfos` method returns the following array:
```
{
"stat":"ok",
"result":{
"infos": [{"name":"version","value":"11.5.0"},
{"name":"nb_elements","value":"339"},
{"name":"nb_categories","value":"28"},
{"name":"nb_virtual","value":"28"},
{"name":"nb_physical","value":"0"},
{"name":"nb_image_category","value":"348"},
{"name":"nb_tags","value":"11"},
{"name":"nb_image_tag","value":"33"},
{"name":"nb_users","value":"7"},
{"name":"nb_groups","value":"1"},
{"name":"nb_comments","value":"0"},
{"name":"first_date","value":"2017-08-31 22:44:11"}
{"name":"cache_size","value":4242}
]
}
}
```
The added `name` and `value` pair (last of the list) contains a `value` of type Integer instead of String. This has broken the simple JSON decoding job in third party apps.
This new JSON data requires a much more complex decoder able to manage two different types for the same `value` key. It would have been much simpler to adopt the same String type. Can this be corrected?
|
[API] pwg.getInfos returns a key "value" as Integer instead of String
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1650/comments
| 0 |
2022-04-10T11:08:28Z
|
2022-04-10T11:08:28Z
|
https://github.com/Piwigo/Piwigo/issues/1650
| 1,198,987,779 | 1,650 |
[
"Piwigo",
"Piwigo"
] |
I'm having issues with 12.2.0, not sure if it's a bug or if I misconfigured it.
I used the videojs plugin to support video, but when I use my phone to upload a lot of videos, the phone occasionally goes to sleep, when I reactivate the phone the webpage resumes the upload and at the end it says the upload was successful.
It looks perfect, but when I play the video, I will find that some videos are damaged and cannot be played, I am sure this is a piwigo problem, because reuploading the same video can be played, and the local player can't play it after downloading the damaged video.
I suspect that the data block was not uploaded completely when the phone went to sleep, which may have caused some bugs, but piwigo directly returned success without verifying the integrity of the uploaded data. This has already cost me (because I thought the upload was successful and I deleted the original video but in fact the server has a corrupted video).
I have a large number of videos that need to be uploaded, I can't imagine how to use piwigo safely if I have to manually compare the hash and watch to verify whether the video is intact for each uploaded video. I don't know php, so I can't find the problem and fix it myself, can anyone give me a good idea, thanks a lot.
The specific environment I use is this self-created docker image: [king011/piwigo:12.0.2](https://hub.docker.com/repository/docker/king011/piwigo)
Here is my "config_default.inc.php" local/config/config.inc.php
```
<?php
// +-----------------------------------------------------------------------+
// | This file is part of Piwigo. |
// | |
// | For copyright and license information, please view the COPYING.txt |
// | file that was distributed with this source code. |
// +-----------------------------------------------------------------------+
/**
* configuration page
*
* Set configuration parameters that are not in the table config. In the
* application, configuration parameters are considered in the same way
* coming from config table or config_default.inc.php.
*
* It is recommended to let config_default.inc.php as provided and to
* overwrite configuration in your local configuration file
* local/config/config.inc.php. See tools/config.inc.php as an example.
*
* Why having some parameters in config table and others in
* config_*.inc.php? Modifying config_*.inc.php is a "hard" task for low
* skilled users, they need a GUI for this : admin/configuration. But only
* parameters that might be modified by low skilled users are in config
* table, other parameters are in config_*.inc.php
*/
// +-----------------------------------------------------------------------+
// | misc |
// +-----------------------------------------------------------------------+
// order_by_custom and order_by_inside_category_custom : for non common pattern
// you can define special ORDER configuration
//
// $conf['order_by_custom'] = ' ORDER BY date_available DESC, file ASC, id ASC';
// order_by_inside_category : inside a category, images can also be ordered
// by rank. A manually defined rank on each image for the category.
//
// $conf['order_by_inside_category_custom'] = $conf['order_by_custom'];
// picture_ext : file extensions for picture file, must be a subset of
// file_ext
$conf['picture_ext'] = array('jpg','jpeg','png','gif');
// file_ext : file extensions (case sensitive) authorized
$conf['file_ext'] = array_merge(
$conf['picture_ext']
#array('tiff', 'tif', 'mpg','zip','avi','mp3','ogg','pdf')
);
// enable_formats: should Piwigo search for multiple formats?
$conf['enable_formats'] = false;
// format_ext : file extensions for formats, ie additional versions of a
// photo (or nay other file). Formats are in sub-directory pwg_format.
$conf['format_ext'] = array('cr2', 'tif', 'tiff', 'nef', 'dng', 'ai', 'psd');
// top_number : number of element to display for "best rated" and "most
// visited" categories
$conf['top_number'] = 15;
// anti-flood_time : number of seconds between 2 comments : 0 to disable
$conf['anti-flood_time'] = 60;
// qualified spam comments are not registered (false will register them
// but they will require admin validation)
$conf['comment_spam_reject'] = true;
// maximum number of links in a comment before it is qualified spam
$conf['comment_spam_max_links'] = 3;
// calendar_datefield : date field of table "images" used for calendar
// catgory
$conf['calendar_datefield'] = 'date_creation';
// calendar_show_any : the calendar shows an additional 'any' button in the
// year/month/week/day navigation bars
$conf['calendar_show_any'] = true;
// calendar_show_empty : the calendar shows month/weeks/days even if there are
//no elements for these
$conf['calendar_show_empty'] = true;
// newcat_default_commentable : at creation, must a category be commentable
// or not ?
$conf['newcat_default_commentable'] = true;
// newcat_default_visible : at creation, must a category be visible or not ?
// Warning : if the parent category is invisible, the category is
// automatically create invisible. (invisible = locked)
$conf['newcat_default_visible'] = true;
// 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'] = 'public';
// newcat_default_position : at creation, should the album appear at the first or last position ?
$conf['newcat_default_position'] = 'first';
// level_separator : character string used for separating a category level
// to the sub level. Suggestions : ' / ', ' » ', ' → ', ' - ',
// ' >'
$conf['level_separator'] = ' / ';
// paginate_pages_around : on paginate navigation bar, how many pages
// display before and after the current page ?
$conf['paginate_pages_around'] = 2;
// show_version : shall the version of Piwigo be displayed at the
// bottom of each page ?
$conf['show_version'] = false;
// meta_ref to reference multiple sets of incorporated pages or elements
// Set it false to avoid referencing in Google, and other search engines.
$conf['meta_ref'] = true;
// links : list of external links to add in the menu. An example is the best
// than a long explanation :
//
// Simple use:
// for each link is associated a label
// $conf['links'] = array(
// 'http://piwigo.org' => 'PWG website',
// 'http://piwigo.org/forum' => 'PWG forum',
// );
//
// Advanced use:
// You can also used special options. Instead to pass a string like parameter value
// you can pass a array with different optional parameter values
// $conf['links'] = array(
// 'http://piwigo.org' => array('label' => 'PWG website', 'new_window' => false, 'eval_visible' => 'return true;'),
// 'http://piwigo.org/forum' => array('label' => 'For ADMIN', 'new_window' => true, 'eval_visible' => 'return is_admin();'),
// 'http://piwigo.org/ext' => array('label' => 'For Guest', 'new_window' => true, 'eval_visible' => 'return is_a_guest();'),
// 'http://piwigo.org/downloads' =>
// array('label' => 'PopUp', 'new_window' => true,
// 'nw_name' => 'PopUp', 'nw_features' => 'width=800,height=450,location=no,status=no,toolbar=no,scrollbars=no,menubar=no'),
// );
// Parameters:
// 'label':
// Label to display for the link, must be defined
// 'new_window':
// If true open link on tab/window
// [Default value is true if it's not defined]
// 'nw_name':
// Name use when new_window is true
// [Default value is '' if it's not defined]
// 'nw_features':
// features use when new_window is true
// [Default value is '' if it's not defined]
// 'eval_visible':
// It's php code witch must return if the link is visible or not
// [Default value is true if it's not defined]
//
// Equivalence:
// $conf['links'] = array(
// 'http://piwigo.org' => 'PWG website',
// );
// $conf['links'] = array(
// 'http://piwigo.org' => array('label' => 'PWG website', 'new_window' => false, 'visible' => 'return true;'),
// );
//
// If the array is empty, the "Links" box won't be displayed on the main
// page.
$conf['links'] = array();
// random_index_redirect: list of 'internal' links to use when no section is defined on index.php.
// An example is the best than a long explanation :
//
// for each link is associated a php condition
// '' condition is equivalent to 'return true;'
// $conf['random_index_redirect'] = array(
// PHPWG_ROOT_PATH.'index.php?/best_rated' => 'return true;',
// PHPWG_ROOT_PATH.'index.php?/recent_pics' => 'return is_a_guest();',
// PHPWG_ROOT_PATH.'random.php' => '',
// PHPWG_ROOT_PATH.'index.php?/categories' => '',
// );
$conf['random_index_redirect'] = array();
// List of notes to display on all header page
// example $conf['header_notes'] = array('Test', 'Hello');
$conf['header_notes'] = array();
// show_thumbnail_caption : on thumbnails page, show thumbnail captions ?
$conf['show_thumbnail_caption'] = true;
// allow_random_representative : do you wish Piwigo to search among
// categories elements a new representative at each reload ?
//
// If false, an element is randomly or manually chosen to represent its
// category and remains the representative as long as an admin does not
// change it.
//
// Warning : setting this parameter to true is CPU consuming. Each time you
// change the value of this parameter from false to true, an administrator
// must update categories informations in screen [Admin > General >
// Maintenance].
$conf['allow_random_representative'] = false;
// representative_cache_on_level: if a thumbnail is chosen as representative
// but has higher privacy level than current user, Piwigo randomly selects
// another thumbnail. Should be store this thumbnail in cache to avoid
// another consuming SQL query on next page refresh?
$conf['representative_cache_on_level'] = true;
// representative_cache_on_subcats: if a category (= album) only contains
// sub-categories, Piwigo randomly selects a thumbnail among sub-categories
// representative. Should we store this thumbnail in cache to avoid another
// "slightly" consuming SQL query on next page refresh?
$conf['representative_cache_on_subcats'] = true;
// allow_html_descriptions : authorize administrators to use HTML in
// category and element description.
$conf['allow_html_descriptions'] = true;
// image level permissions available in the admin interface
$conf['available_permission_levels'] = array(0,1,2,4,8);
// check_upgrade_feed: check if there are database upgrade required. Set to
// true, a message will strongly encourage you to upgrade your database if
// needed.
//
// This configuration parameter is set to true in BSF branch and to false
// elsewhere.
$conf['check_upgrade_feed'] = false;
// rate_items: available rates for a picture
$conf['rate_items'] = array(0,1,2,3,4,5);
// Define default method to use ('http' or 'html' in order to do redirect)
$conf['default_redirect_method'] = 'http';
// Define using double password type in admin's users management panel
$conf['double_password_type_in_admin'] = false;
// Define if logins must be case sensitive or not of user's registration. ie :
// If set true, the login "user" will equal "User" or "USER" or "user",
// etc. ... And it will be impossible to use such login variation to create a
// new user account.
$conf['insensitive_case_logon'] = false;
// how should we check for unicity when adding a photo. Can be 'md5sum' or
// 'filename'
$conf['uniqueness_mode'] = 'md5sum';
// Library used for image resizing. Value could be 'auto', 'imagick',
// 'ext_imagick' or 'gd'. If value is 'auto', library will be chosen in this
// order. If chosen library is not available, another one will be picked up.
$conf['graphics_library'] = 'auto';
// If library used is external installation of ImageMagick ('ext_imagick'),
// you can define imagemagick directory.
$conf['ext_imagick_dir'] = '';
// how many user comments to display by default on comments.php. Use 'all'
// to display all user comments without pagination. Default available values
// are array(5,10,20,50,'all') but you can set any other numeric value.
$conf['comments_page_nb_comments'] = 10;
// how often should we check for new versions of Piwigo on piwigo.org? In
// seconds. The check is made only if there are visits on Piwigo.
// 0 to disable.
$conf['update_notify_check_period'] = 24*60*60;
// how often should be remind of new versions available? For example a first
// notification was sent on May 5th 2017 for 2.9.1, after how many seconds
// we send it again? 0 to disable.
$conf['update_notify_reminder_period'] = 7*24*60*60;
// should the album description be displayed on all pages (value=true) or
// only the first page (value=false)
$conf['album_description_on_all_pages'] = false;
// Number of years displayed in the history compare mode (for the years chart)
$conf['stat_compare_year_displayed'] = 5;
// +-----------------------------------------------------------------------+
// | email |
// +-----------------------------------------------------------------------+
// send_bcc_mail_webmaster: send bcc mail to webmaster. Set true for debug
// or test.
$conf['send_bcc_mail_webmaster'] = false;
// define the name of sender mail: if value is empty, gallery title is used
$conf['mail_sender_name'] = '';
// define the email of sender mail: if value is empty, webmaster email is used
$conf['mail_sender_email'] = '';
// set true to allow text/html emails
$conf['mail_allow_html'] = true;
// smtp configuration (work if fsockopen function is allowed for smtp port)
// smtp_host: smtp server host
// if null, regular mail function is used
// format: hoststring[:port]
// exemple: smtp.pwg.net:21
// smtp_user/smtp_password: user & password for smtp authentication
$conf['smtp_host'] = '';
$conf['smtp_user'] = '';
$conf['smtp_password'] = '';
// 'ssl' or 'tls'
$conf['smtp_secure'] = null;
// +-----------------------------------------------------------------------+
// | metadata |
// +-----------------------------------------------------------------------+
// show_iptc: Show IPTC metadata on picture.php if asked by user
$conf['show_iptc'] = false;
// show_iptc_mapping : is used for showing IPTC metadata on picture.php
// page. For each key of the array, you need to have the same key in the
// $lang array. For example, if my first key is 'iptc_keywords' (associated
// to '2#025') then you need to have $lang['iptc_keywords'] set in
// language/$user['language']/common.lang.php. If you don't have the lang
// var set, the key will be simply displayed
//
// To know how to associated iptc_field with their meaning, use
// tools/metadata.php
$conf['show_iptc_mapping'] = array(
'iptc_keywords' => '2#025',
'iptc_caption_writer' => '2#122',
'iptc_byline_title' => '2#085',
'iptc_caption' => '2#120'
);
// use_iptc: Use IPTC data during database synchronization with files
// metadata
$conf['use_iptc'] = false;
// use_iptc_mapping : in which IPTC fields will Piwigo find image
// information ? This setting is used during metadata synchronisation. It
// associates a piwigo_images column name to a IPTC key
$conf['use_iptc_mapping'] = array(
'keywords' => '2#025',
'date_creation' => '2#055',
'author' => '2#122',
'name' => '2#005',
'comment' => '2#120'
);
// show_exif: Show EXIF metadata on picture.php (table or line presentation
// available)
$conf['show_exif'] = true;
// show_exif_fields : in EXIF fields, you can choose to display fields in
// sub-arrays, for example ['COMPUTED']['ApertureFNumber']. for this, add
// 'COMPUTED;ApertureFNumber' in $conf['show_exif_fields']
//
// The key displayed in picture.php will be $lang['exif_field_Make'] for
// example and if it exists. For compound fields, only take into account the
// last part : for key 'COMPUTED;ApertureFNumber', you need
// $lang['exif_field_ApertureFNumber']
//
// for PHP version newer than 4.1.2 :
// $conf['show_exif_fields'] = array('CameraMake','CameraModel','DateTime');
//
$conf['show_exif_fields'] = array(
'Make',
'Model',
'DateTimeOriginal',
'COMPUTED;ApertureFNumber',
'ExifVersion',
'Software',
'FNumber',
'ExposureBiasValue',
'FILE;FileSize',
'ExposureTime',
'Flash',
'ISOSpeedRatings',
'FocalLength',
'FocalLengthIn35mmFilm',
'WhiteBalance',
'ExposureMode',
'MeteringMode',
'ExposureProgram',
'LightSource',
'Contrast',
'Saturation',
'Sharpness',
'bitrate',
'channel',
'date_creation',
'display_aspect_ratio',
'duration',
'filesize',
'format',
'formatprofile',
'codecid',
'frame_rate',
'latitude',
'longitude',
'make',
'model',
'playtime_seconds',
'sampling_rate',
'type',
'resolution',
'rotation',
);
// use_exif: Use EXIF data during database synchronization with files
// metadata
$conf['use_exif'] = true;
// use_exif_mapping: same behaviour as use_iptc_mapping
$conf['use_exif_mapping'] = array(
'date_creation' => 'DateTimeOriginal'
);
// allow_html_in_metadata: in case the origin of the photo is unsecure (user
// upload), we remove HTML tags to avoid XSS (malicious execution of
// javascript)
$conf['allow_html_in_metadata'] = false;
// decide which characters can be used as keyword separators (works in EXIF
// and IPTC). Coma "," cannot be removed from this list.
$conf['metadata_keyword_separator_regex'] = '/[.,;]/';
// +-----------------------------------------------------------------------+
// | sessions |
// +-----------------------------------------------------------------------+
// session_use_cookies: specifies to use cookie to store
// the session id on client side
$conf['session_use_cookies'] = true;
// session_use_only_cookies: specifies to only use cookie to store
// the session id on client side
$conf['session_use_only_cookies'] = true;
// session_use_trans_sid: do not use transparent session id support
$conf['session_use_trans_sid'] = false;
// session_name: specifies the name of the session which is used as cookie name
$conf['session_name'] = 'pwg_id';
// session_save_handler: comment the line below
// to use file handler for sessions.
$conf['session_save_handler'] = 'db';
// authorize_remembering : permits user to stay logged for a long time. It
// creates a cookie on client side.
$conf['authorize_remembering'] = true;
// remember_me_name: specifies the name of the cookie used to stay logged
$conf['remember_me_name'] = 'pwg_remember';
// remember_me_length : time of validity for "remember me" cookies, in
// seconds.
$conf['remember_me_length'] = 5184000;
// session_length : time of validity for normal session, in seconds.
$conf['session_length'] = 3600;
// session_use_ip_address: avoid session hijacking by using a part of the IP
// address
$conf['session_use_ip_address'] = true;
// Probability, on each page generated, to launch session garbage
// collector. Integer value between 1 and 100, in %. 0 to disable and let
// the system default behavior (on Debian-like, it's "never delete
// session").
$conf['session_gc_probability'] = 1;
// +-----------------------------------------------------------------------+
// | debug/performance |
// +-----------------------------------------------------------------------+
// number of photos beyond which individual photos are added in the
// lounge, a temporary zone where photos wait before being "launched".
// 50k photos by default.
$conf['lounge_activate_threshold'] = 1;
// Lounge is automatically emptied (photos are being pushed to their
// albums) when the oldest one reaches this duration. Lounge can be emptied
// before, either manually or at the end of the upload. In seconds.
// 5 minutes by default.
$conf['lounge_max_duration'] = 5*60;
// show_queries : for debug purpose, show queries and execution times
$conf['show_queries'] = false;
// show_gt : display generation time at the bottom of each page
$conf['show_gt'] = false;
// debug_l10n : display a warning message each time an unset language key is
// accessed
$conf['debug_l10n'] = false;
// activate template debugging - a new window will appear
$conf['debug_template'] = false;
// save copies of sent mails into local data dir
$conf['debug_mail'] = false;
// die_on_sql_error: if an SQL query fails, should everything stop?
$conf['die_on_sql_error'] = false;
// if true, some language strings are replaced during template compilation
// (instead of template output). this results in better performance. however
// any change in the language file will not be propagated until you purge
// the compiled templates from the admin / maintenance menu
$conf['compiled_template_cache_language'] = false;
// This tells Smarty whether to check for recompiling or not. Recompiling
// does not need to happen unless a template is changed. false results in
// better performance.
$conf['template_compile_check'] = true;
// This forces Smarty to (re)compile templates on every invocation. This is
// handy for development and debugging. It should never be used in a
// production environment.
$conf['template_force_compile'] = false;
// activate merging of javascript / css files
$conf['template_combine_files'] = true;
// this permit to show the php errors reporting (see INI 'error_reporting'
// for possible values)
// gives an empty value '' to deactivate
$conf['show_php_errors'] = E_ALL;
// +-----------------------------------------------------------------------+
// | authentication |
// +-----------------------------------------------------------------------+
// apache_authentication : use Apache authentication as reference instead of
// users table ?
$conf['apache_authentication'] = false;
// users_table: which table is the reference for users? Can be a different
// table than Piwigo table
//
// If you decide to use another table than the default one, you need to
// prepare your database by deleting some datas :
//
// delete from piwigo_user_access;
// delete from piwigo_user_cache;
// delete from piwigo_user_feed;
// delete from piwigo_user_group;
// delete from piwigo_user_infos;
// delete from piwigo_sessions;
// delete from piwigo_rate;
// update piwigo_images set rating_score = null, added_by = <webmaster_id>;
// delete from piwigo_caddie;
// delete from piwigo_favorites;
//
// All informations contained in these tables and column are related to
// piwigo_users table.
$conf['users_table'] = null;
// If you decide to use external authentication
// change conf below by $conf['external_authentification'] = true;
$conf['external_authentification'] = false;
// Other tables can be changed, if you define associated constants
// Example:
// define('USER_INFOS_TABLE', 'pwg_main'.'user_infos');
// user_fields : mapping between generic field names and table specific
// field names. For example, in PWG, the mail address is names
// "mail_address" and in punbb, it's called "email".
$conf['user_fields'] = array(
'id' => 'id',
'username' => 'username',
'password' => 'password',
'email' => 'mail_address'
);
// password_hash: function hash the clear user password to store it in the
// database. The function takes only one parameter: the clear password.
$conf['password_hash'] = 'pwg_password_hash';
// password_verify: function that checks the password against its hash. The
// function takes 2 mandatory parameter : clear password, hashed password +
// an optional parameter user_id. The user_id is used to update the password
// with the new hash introduced in Piwigo 2.5. See function
// pwg_password_verify in include/functions_user.inc.php
$conf['password_verify'] = 'pwg_password_verify';
// guest_id : id of the anonymous user
$conf['guest_id'] = 2;
// default_user_id : id of user used for default value
$conf['default_user_id'] = $conf['guest_id'];
// Registering process and guest/generic members get language from the browser
// if language isn't available PHPWG_DEFAULT_LANGUAGE is used as previously
$conf['browser_language'] = true;
// webmaster_id : webmaster'id.
$conf['webmaster_id'] = 1;
// does the guest have access ?
// (not a security feature, set your categories "private" too)
// If false it'll be redirected from index.php to identification.php
$conf['guest_access'] = true;
// +-----------------------------------------------------------------------+
// | history |
// +-----------------------------------------------------------------------+
// nb_logs_page : how many logs to display on a page
$conf['nb_logs_page'] = 300;
// Every X new line in history, perform an automatic purge. The more often,
// the fewer lines to delete. 0 to disable.
$conf['history_autopurge_every'] = 1021;
// How many lines to keep in history on autopurge? 0 to disable.
$conf['history_autopurge_keep_lines'] = 1000000;
// On history autopurge, how many lines should to deleted at once, maximum?
$conf['history_autopurge_blocksize'] = 50000;
// +-----------------------------------------------------------------------+
// | urls |
// +-----------------------------------------------------------------------+
// gallery_url : you can set a specific URL for the home page of your
// gallery. This is for very specific use and you don't need to change this
// setting when move your gallery to a new directory or a new domain name.
$conf['gallery_url'] = null;
// question_mark_in_urls : the generated urls contain a ? sign. This can be
// changed to false only if the server translates PATH_INFO variable
// (depends on the server AcceptPathInfo directive configuration)
$conf['question_mark_in_urls'] = true;
// php_extension_in_urls : if true, the urls generated for picture and
// category will not contain the .php extension. This will work only if
// .htaccess defines Options +MultiViews parameter or url rewriting rules
// are active.
$conf['php_extension_in_urls'] = true;
// category_url_style : one of 'id' (default) or 'id-name'. 'id-name'
// means that an simplified ascii representation of the category name will
// appear in the url
$conf['category_url_style'] = 'id';
// picture_url_style : one of 'id' (default), 'id-file' or 'file'. 'id-file'
// or 'file' mean that the file name (without extension will appear in the
// url). Note that one additional sql query will occur if 'file' is chosen.
// Note that you might experience navigation issues if you choose 'file'
// and your file names are not unique
$conf['picture_url_style'] = 'id';
// tag_url_style : one of 'id-tag' (default), 'id' or 'tag'.
// Note that if you choose 'tag' and the url (ascii) representation of your
// tags is not unique, all tags with the same url representation will be shown
$conf['tag_url_style'] = 'id-tag';
// +-----------------------------------------------------------------------+
// | tags |
// +-----------------------------------------------------------------------+
// full_tag_cloud_items_number: number of tags to show in the full tag
// cloud. Only the most represented tags will be shown
$conf['full_tag_cloud_items_number'] = 200;
// menubar_tag_cloud_items_number: number of tags to show in the tag
// cloud in the menubar. Only the most represented tags will be shown
$conf['menubar_tag_cloud_items_number'] = 20;
// menubar_tag_cloud_content: 'always_all', 'current_only' or 'all_or_current'
// For the tag cloud in the menubar.
// 'always_all': tag cloud always displays all tags available to the user
// 'current_only': tag cloud always displays the tags from the current pictures
// 'all_or_current': when pictures are displayed, tag cloud shows their tags, but
// when none are displayed, all the tags available to the user are shown.
$conf['menubar_tag_cloud_content'] = 'all_or_current';
// content_tag_cloud_items_number: number of related tags to show in the tag
// cloud on the content page, when the current section is not a set of
// tags. Only the most represented tags will be shown
$conf['content_tag_cloud_items_number'] = 12;
// tags_levels: number of levels to use for display. Each level is bind to a
// CSS class tagLevelX.
$conf['tags_levels'] = 5;
// tags_default_display_mode: group tags by letter or display a tag cloud by
// default? 'letters' or 'cloud'.
$conf['tags_default_display_mode'] = 'cloud';
// tag_letters_column_number: how many columns to display tags by letter
$conf['tag_letters_column_number'] = 4;
// +-----------------------------------------------------------------------+
// | Related albums |
// +-----------------------------------------------------------------------+
// beyond this limit, do not try to find related albums. If there are too
// many items, the SQL query will be slow and the results irrelevant,
// because showing too many related albums.
$conf['related_albums_maximum_items_to_compute'] = 1000;
// once found the related albums, how many to show in the menubar? We take
// the heaviest (with more relations).
$conf['related_albums_display_limit'] = 20;
// +-----------------------------------------------------------------------+
// | Notification by mail |
// +-----------------------------------------------------------------------+
// Default Value for nbm user
$conf['nbm_default_value_user_enabled'] = false;
// Search list user to send quickly (List all without to check news)
// More quickly but less fun to use
$conf['nbm_list_all_enabled_users_to_send'] = false;
// Max time used on one pass in order to send mails.
// Timeout delay ratio.
$conf['nbm_max_treatment_timeout_percent'] = 0.8;
// If timeout cannot be combined with nbm_max_treatment_timeout_percent,
// nbm_treatment_timeout_default is used by default
$conf['nbm_treatment_timeout_default'] = 20;
// Parameters used in get_recent_post_dates for the 2 kind of notification
$conf['recent_post_dates'] = array(
'RSS' => array('max_dates' => 5, 'max_elements' => 6, 'max_cats' => 6),
'NBM' => array('max_dates' => 7, 'max_elements' => 3, 'max_cats' => 9)
);
// the author shown in the RSS feed <author> element
$conf['rss_feed_author'] = 'Piwigo notifier';
// how long does the authentication key stays valid, in seconds. 3 days by
// default. 0 to disable.
$conf['auth_key_duration'] = 3*24*60*60;
// +-----------------------------------------------------------------------+
// | Set admin layout |
// +-----------------------------------------------------------------------+
$conf['admin_theme'] = 'clear';
// should we load the active plugins ? true=Yes, false=No
$conf['enable_plugins']=true;
// Web services are allowed (true) or completely forbidden (false)
$conf['allow_web_services'] = true;
// Maximum number of images to be returned foreach call to the web service
$conf['ws_max_images_per_page'] = 500;
// Maximum number of users to be returned foreach call to the web service
$conf['ws_max_users_per_page'] = 1000;
// Display a link to subscribe to Piwigo Announcements Newsletter
$conf['show_newsletter_subscription'] = true;
// Check for available updates on Piwigo or extensions, performed each time
// the dashboard is displayed
$conf['dashboard_check_for_updates'] = true;
// Number Weeks displayed on activity chart on the dashboard
$conf['dashboard_activity_nb_weeks'] = 4;
// On album mover page, number of seconds before auto openning album when
// dragging an album. In milliseconds. 3 seconds by default.
$conf['album_move_delay_before_auto_opening'] = 3*1000;
// This variable is used to show or hide the template tab in the side menu
$conf['show_template_in_side_menu'] = false;
// +-----------------------------------------------------------------------+
// | Filter |
// +-----------------------------------------------------------------------+
// $conf['filter_pages'] contains configuration for each pages
// o If values are not defined for a specific page, default value are used
// o Array is composed by the basename of each page without extension
// o List of value names:
// - used: filter function are used
// (if false nothing is done [start, cancel, stop, ...]
// - cancel: cancel current started filter
// - add_notes: add notes about current started filter on the header
// o Empty configuration in order to disable completely filter functions
// No filter, No icon,...
// $conf['filter_pages'] = array();
$conf['filter_pages'] = array
(
// Default page
'default' => array(
'used' => true, 'cancel' => false, 'add_notes' => false),
// Real pages
'index' => array('add_notes' => true),
'tags' => array('add_notes' => true),
'search' => array('add_notes' => true),
'comments' => array('add_notes' => true),
'admin' => array('used' => false),
'feed' => array('used' => false),
'notification' => array('used' => false),
'nbm' => array('used' => false),
'popuphelp' => array('used' => false),
'profile' => array('used' => false),
'ws' => array('used' => false),
'identification' => array('cancel' => true),
'install' => array('cancel' => true),
'password' => array('cancel' => true),
'register' => array('cancel' => true),
);
// +-----------------------------------------------------------------------+
// | Slideshow |
// +-----------------------------------------------------------------------+
// slideshow_period : waiting time in seconds before loading a new page
// during automated slideshow
// slideshow_period_min, slideshow_period_max are bounds of slideshow_period
// slideshow_period_step is the step of navigation between min and max
$conf['slideshow_period_min'] = 1;
$conf['slideshow_period_max'] = 10;
$conf['slideshow_period_step'] = 1;
$conf['slideshow_period'] = 4;
// slideshow_repeat : slideshow loops on pictures
$conf['slideshow_repeat'] = true;
// $conf['light_slideshow'] indicates to use slideshow.tpl in state of
// picture.tpl for slideshow
// Take care to have slideshow.tpl in all available templates
// Or set it false.
// Check if Picture's plugins are compliant with it
// Every plugin from 1.7 would be design to manage light_slideshow case.
$conf['light_slideshow'] = true;
// the local data directory is used to store data such as compiled templates,
// plugin variables, combined css/javascript or resized images. Beware of
// mandatory trailing slash.
$conf['data_location'] = '_data/';
// where should the API/UploadForm add photos? This path must be relative to
// the Piwigo installation directory (but can be outside, as long as it's
// reachable from your webserver).
$conf['upload_dir'] = './upload';
// where should the user be guided when there is no photo in his gallery yet?
$conf['no_photo_yet_url'] = 'admin.php?page=photos_add';
// directory with themes inside
$conf['themes_dir'] = PHPWG_ROOT_PATH.'themes';
// enable the synchronization method for adding photos
$conf['enable_synchronization'] = true;
// permitted characters for files/directories during synchronization
$conf['sync_chars_regex'] = '/^[a-zA-Z0-9-_.]+$/';
// folders name excluded during synchronization
$conf['sync_exclude_folders'] = array();
// PEM url (default is http://piwigo.org/ext)
$conf['alternative_pem_url'] = '';
// categories ID on PEM
$conf['pem_plugins_category'] = 12;
$conf['pem_themes_category'] = 10;
$conf['pem_languages_category'] = 8;
// based on the EXIF "orientation" tag, should we rotate photos added in the
// upload form or through pwg.images.addSimple web API method?
$conf['upload_form_automatic_rotation'] = true;
// 0-'auto', 1-'derivative' 2-'script'
$conf['derivative_url_style']=0;
$conf['chmod_value']= substr_compare(PHP_SAPI, 'apa', 0, 3)==0 ? 0777 : 0755;
// 'small', 'medium' or 'large'
$conf['derivative_default_size'] = 'medium';
// below which size (in pixels, ie width*height) do we remove metadata
// EXIF/IPTC... from derivative?
$conf['derivatives_strip_metadata_threshold'] = 256000;
//Maximum Ajax requests at once, for thumbnails on-the-fly generation
$conf['max_requests']=3;
// one of '', 'images', 'all'
//TODO: Put this in admin and also manage .htaccess in #sites and upload folders
$conf['original_url_protection'] = '';
// Default behaviour when a new album is created: should the new album inherit the group/user
// permissions from its parent? Note that config is only used for Ftp synchro,
// and if that option is not explicitly transmit when the album is created.
$conf['inheritance_by_default'] = false;
// 'png' or 'jpg': your uploaded TIF photos will have a representative in
// JPEG or PNG file format
$conf['tiff_representative_ext'] = 'png';
// in the upload form, let users upload only picture_exts or all file_exts?
// for some file types, Piwigo will try to generate a pwg_representative
// (TIFF, videos, PDF)
$conf['upload_form_all_types'] = true;
// Size of chunks, in kilobytes. Fast connections will have better
// performances with high values, such as 5000.
$conf['upload_form_chunk_size'] = 500;
// If we try to generate a pwg_representative for a video we use ffmpeg. If
// "ffmpeg" is not visible by the web user, you can define the full path of
// the directory where "ffmpeg" executable is.
$conf['ffmpeg_dir'] = '';
// batch manager: how many images should Piwigo display by default on the
// global mode. Must be among values {20,50,100}
$conf['batch_manager_images_per_page_global'] = 20;
// batch manager: how many images should Piwigo display by default on the
// unit mode. Must be among values {5, 10, 50}
$conf['batch_manager_images_per_page_unit'] = 5;
// how many missing md5sum should Piwigo compute at once.
$conf['checksum_compute_blocksize'] = 50;
// quicksearch engine: include all photos from sub-albums of any matching
// album. For example, if search is "bear", then we display photos from
// "bear/grizzly". When value changed, delete database cache files in
// _data/cache directory
$conf['quick_search_include_sub_albums'] = false;
// +-----------------------------------------------------------------------+
// | log |
// +-----------------------------------------------------------------------+
// Logs directory, relative to $conf['data_location']
$conf['log_dir'] = '/logs';
// Log level (OFF, CRITICAL, ERROR, WARNING, NOTICE, INFO, DEBUG)
// development = DEBUG, production = ERROR
$conf['log_level'] = 'DEBUG';
// Keep logs file during X days
$conf['log_archive_days'] = 30;
// +-----------------------------------------------------------------------+
// | Proxy Settings |
// +-----------------------------------------------------------------------+
// If piwigo needs a http-proxy to connect to the internet, set this to true
$conf['use_proxy'] = false;
// Connection string of the proxy
$conf['proxy_server'] = 'proxy.domain.org:port';
// If the http-proxy requires authentication, set username and password here
// e.g. username:password
$conf['proxy_auth'] = '';
?>
```
|
Upload integrity check？
|
https://api.github.com/repos/Piwigo/Piwigo/issues/1649/comments
| 2 |
2022-04-10T01:14:31Z
|
2022-07-21T08:02:35Z
|
https://github.com/Piwigo/Piwigo/issues/1649
| 1,198,828,270 | 1,649 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.