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
|
|---|---|---|---|---|---|---|---|---|---|
[
"hwchase17",
"langchain"
] |
Currently is as below, which is way too ugly
```
335 Create a new model by parsing and validating input data from keyword arguments.
336
337 Raises ValidationError if the input data cannot be parsed to form a valid model.
338 """
339 # Uses something other than `self` the first arg to allow "self" as a settable attribute
--> 340 values, fields_set, validation_error = validate_model(__pydantic_self__.__class__, data)
341 if validation_error:
342 raise validation_error
...
---> 53 input_variables = values["input_variables"]
54 template = values["template"]
55 template_format = values["template_format"]
KeyError: 'input_variables'
```
|
improve error messages for missing keys in pydantic classes
|
https://api.github.com/repos/langchain-ai/langchain/issues/109/comments
| 3 |
2022-11-10T05:03:46Z
|
2023-10-12T16:11:25Z
|
https://github.com/langchain-ai/langchain/issues/109
| 1,443,260,377 | 109 |
[
"hwchase17",
"langchain"
] |
per https://github.com/hwchase17/langchain/issues/104 needed to start skipping unit tests due to a segfault - look into this more and figure out what fixes are needed https://github.com/hwchase17/langchain/blob/95dd2f140e19d29bdb62d4dae2048e3edf0ee147/tests/integration_tests/embeddings/test_huggingface.py#L7
|
fix sentence_transformers segfault in integration tests
|
https://api.github.com/repos/langchain-ai/langchain/issues/108/comments
| 1 |
2022-11-09T21:29:43Z
|
2023-09-12T21:29:58Z
|
https://github.com/langchain-ai/langchain/issues/108
| 1,442,768,284 | 108 |
[
"hwchase17",
"langchain"
] |
```
pytest tests/integration_tests
============================= test session starts ==============================
platform darwin -- Python 3.9.12, pytest-7.1.1, pluggy-1.0.0
rootdir: /Users/delip/workspace/langchain
plugins: anyio-3.5.0, dotenv-0.5.2
collected 14 items / 1 error
==================================== ERRORS ====================================
____________ ERROR collecting tests/integration_tests/test_faiss.py ____________
ImportError while importing test module '/Users/delip/workspace/langchain/tests/integration_tests/test_faiss.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
../../opt/anaconda3/lib/python3.9/importlib/__init__.py:127: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
tests/integration_tests/test_faiss.py:9: in <module>
from langchain.faiss import FAISS
E ModuleNotFoundError: No module named 'langchain.faiss'
```
|
make integration_tests fails currently
|
https://api.github.com/repos/langchain-ai/langchain/issues/104/comments
| 3 |
2022-11-09T19:42:36Z
|
2022-11-09T21:28:18Z
|
https://github.com/langchain-ai/langchain/issues/104
| 1,442,648,768 | 104 |
[
"hwchase17",
"langchain"
] |
I get this error when I run `pip install -r requirements.txt`
```
ERROR: Could not find a version that satisfies the requirement faiss (from versions: none)
ERROR: No matching distribution found for faiss
```
As per [this issue](https://github.com/facebookresearch/faiss/issues/984), requirements.txt should be updated to faiss-cpu.
|
pip install requirements.txt fails on conda on mac
|
https://api.github.com/repos/langchain-ai/langchain/issues/101/comments
| 1 |
2022-11-09T18:17:26Z
|
2022-11-09T23:47:48Z
|
https://github.com/langchain-ai/langchain/issues/101
| 1,442,545,258 | 101 |
[
"hwchase17",
"langchain"
] |
add llm extra dependencies
add all extra dependencies
|
improve pip install
|
https://api.github.com/repos/langchain-ai/langchain/issues/96/comments
| 0 |
2022-11-09T05:21:12Z
|
2022-11-14T16:34:36Z
|
https://github.com/langchain-ai/langchain/issues/96
| 1,441,400,288 | 96 |
[
"hwchase17",
"langchain"
] |
to make sure they are up to date
|
add tests for notebooks
|
https://api.github.com/repos/langchain-ai/langchain/issues/94/comments
| 7 |
2022-11-09T02:20:03Z
|
2023-09-10T16:47:31Z
|
https://github.com/langchain-ai/langchain/issues/94
| 1,441,238,396 | 94 |
[
"hwchase17",
"langchain"
] |
First, when I load them I get a warning:
```python
hf = HuggingFaceHub(repo_id="google/flan-t5-xl")
You're using a different task than the one specified in the repository. Be sure to know what you're doing :)
```
Then, when I use it in inference, I get gibberish.
```python
hf("The capital of New York is")
'ew York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is The capital of the world New York is'
```
If I run the API via `requests`, I get the expected answer
```python
import requests
API_URL = "https://api-inference.huggingface.co/models/google/flan-t5-xl"
headers = {"Authorization": "Bearer api_org_xxxxxxxxxxxxxxxxxxxxxxxxxxx"}
def query(payload):
response = requests.post(API_URL, headers=headers, json=payload)
return response.json()
output = query({
"inputs": "The capital of New York is",
})
print(output)
[{'generated_text': 'Albany'}]
```
Any suggestions?
|
google/flan-t5-xxl and google/flan-t5-xl don't seem to work with HuggingFaceHub
|
https://api.github.com/repos/langchain-ai/langchain/issues/90/comments
| 2 |
2022-11-08T21:15:39Z
|
2022-11-09T17:39:24Z
|
https://github.com/langchain-ai/langchain/issues/90
| 1,440,914,516 | 90 |
[
"hwchase17",
"langchain"
] | null |
get data from a particular url
|
https://api.github.com/repos/langchain-ai/langchain/issues/89/comments
| 0 |
2022-11-08T19:20:04Z
|
2022-12-11T22:25:02Z
|
https://github.com/langchain-ai/langchain/issues/89
| 1,440,772,447 | 89 |
[
"hwchase17",
"langchain"
] |
https://github.com/hwchase17/langchain/blob/master/langchain/text_splitter.py
|
Add NLTK support for splitting text
|
https://api.github.com/repos/langchain-ai/langchain/issues/88/comments
| 0 |
2022-11-08T14:14:54Z
|
2022-11-10T04:46:57Z
|
https://github.com/langchain-ai/langchain/issues/88
| 1,440,287,738 | 88 |
[
"hwchase17",
"langchain"
] | null |
Add support for pinecone vector DB
|
https://api.github.com/repos/langchain-ai/langchain/issues/87/comments
| 4 |
2022-11-08T14:13:06Z
|
2023-09-10T16:47:36Z
|
https://github.com/langchain-ai/langchain/issues/87
| 1,440,284,398 | 87 |
[
"hwchase17",
"langchain"
] | null |
Add HuggingFace Hub embeddings support
|
https://api.github.com/repos/langchain-ai/langchain/issues/86/comments
| 2 |
2022-11-08T14:11:12Z
|
2022-11-27T08:25:01Z
|
https://github.com/langchain-ai/langchain/issues/86
| 1,440,280,293 | 86 |
[
"hwchase17",
"langchain"
] | null |
Add AI21 Embeddings support
|
https://api.github.com/repos/langchain-ai/langchain/issues/85/comments
| 8 |
2022-11-08T14:10:45Z
|
2023-09-27T13:45:46Z
|
https://github.com/langchain-ai/langchain/issues/85
| 1,440,279,263 | 85 |
[
"hwchase17",
"langchain"
] | null |
Add AI21 text generation support
|
https://api.github.com/repos/langchain-ai/langchain/issues/84/comments
| 0 |
2022-11-08T14:10:33Z
|
2022-11-10T16:12:30Z
|
https://github.com/langchain-ai/langchain/issues/84
| 1,440,278,806 | 84 |
[
"hwchase17",
"langchain"
] | null |
Add Cohere Embeddings support
|
https://api.github.com/repos/langchain-ai/langchain/issues/83/comments
| 1 |
2022-11-08T14:10:14Z
|
2022-11-10T04:46:27Z
|
https://github.com/langchain-ai/langchain/issues/83
| 1,440,278,031 | 83 |
[
"hwchase17",
"langchain"
] |
It's just a bit annoying, I want to use this library in production and I currently store credentials not in the environment.
I think the ideal API is like all the AWS SDKs where you can either stick them in the environment OR pass them as params to the llm constructor.
I can do a PR for this if you're accepting PRs?
|
Should be able to pass API keys as params rather than requiring them to be in the environment
|
https://api.github.com/repos/langchain-ai/langchain/issues/76/comments
| 3 |
2022-11-07T09:48:42Z
|
2022-11-07T21:35:03Z
|
https://github.com/langchain-ai/langchain/issues/76
| 1,438,065,793 | 76 |
[
"hwchase17",
"langchain"
] |
I have just updated to version 0.0.7
1- When running a simple question like: "What is the capital of Idaho?" , the result is OK
2- When running a question like: "What is the hometown of the reigning men's U.S. Open champion?"
I got the following error:
What is the hometown of the reigning men's U.S. Open champion?
Are follow up questions needed here: Yes.
Follow up: Who is the reigning men's U.S. Open champion?
(.......)
File ~/anaconda3/envs/nlp/lib/python3.10/site-packages/langchain/chains/self_ask_with_search/base.py:166, in SelfAskWithSearchChain.run(self, question)
152 def run(self, question: str) -> str:
153 """Run self ask with search chain.
154
155 Args:
(...)
...
--> 107 elif "snippet" in res["organic_results"][0].keys():
108 toret = res["organic_results"][0]["snippet"]
109 else:
KeyError: 'organic_results'
|
SelfAskWithSearchChain error when followup required
|
https://api.github.com/repos/langchain-ai/langchain/issues/58/comments
| 7 |
2022-11-03T13:35:03Z
|
2022-11-07T13:52:16Z
|
https://github.com/langchain-ai/langchain/issues/58
| 1,434,674,823 | 58 |
[
"hwchase17",
"langchain"
] |
https://github.com/deepset-ai/haystack
|
add support for haystack
|
https://api.github.com/repos/langchain-ai/langchain/issues/55/comments
| 21 |
2022-11-02T04:58:18Z
|
2023-11-04T16:07:26Z
|
https://github.com/langchain-ai/langchain/issues/55
| 1,432,498,748 | 55 |
[
"hwchase17",
"langchain"
] |
elasticsearch, pinecone
|
add support for more vector databases
|
https://api.github.com/repos/langchain-ai/langchain/issues/54/comments
| 3 |
2022-11-02T04:57:58Z
|
2022-11-08T14:12:46Z
|
https://github.com/langchain-ai/langchain/issues/54
| 1,432,498,499 | 54 |
[
"hwchase17",
"langchain"
] |
cohere, huggingface, ai21
|
Add support for more embedding models
|
https://api.github.com/repos/langchain-ai/langchain/issues/53/comments
| 10 |
2022-11-02T04:57:41Z
|
2022-11-08T14:09:57Z
|
https://github.com/langchain-ai/langchain/issues/53
| 1,432,498,294 | 53 |
[
"hwchase17",
"langchain"
] |
maybe not the ones that require $$
|
Run integration tests on GHA
|
https://api.github.com/repos/langchain-ai/langchain/issues/52/comments
| 1 |
2022-11-02T04:20:00Z
|
2023-09-12T21:29:57Z
|
https://github.com/langchain-ai/langchain/issues/52
| 1,432,464,453 | 52 |
[
"hwchase17",
"langchain"
] |
Would be good to have some methods that split on tokens as in the OpenAI example
https://github.com/openai/openai-cookbook/blob/459afa7d9bf026c4434f54458dc7d9e7d9f9f5fe/examples/Obtain_dataset.ipynb
|
Add huggingface tokenizer support for splitting text
|
https://api.github.com/repos/langchain-ai/langchain/issues/45/comments
| 1 |
2022-11-01T03:54:31Z
|
2022-11-13T17:37:45Z
|
https://github.com/langchain-ai/langchain/issues/45
| 1,430,824,058 | 45 |
[
"hwchase17",
"langchain"
] | null |
Add vector database semantic search chain
|
https://api.github.com/repos/langchain-ai/langchain/issues/40/comments
| 2 |
2022-10-28T06:52:33Z
|
2022-11-12T15:24:50Z
|
https://github.com/langchain-ai/langchain/issues/40
| 1,426,777,906 | 40 |
[
"hwchase17",
"langchain"
] | null |
add vector database (FAISS) integration
|
https://api.github.com/repos/langchain-ai/langchain/issues/39/comments
| 0 |
2022-10-28T06:52:15Z
|
2022-11-04T18:18:10Z
|
https://github.com/langchain-ai/langchain/issues/39
| 1,426,777,633 | 39 |
[
"hwchase17",
"langchain"
] |
right now, some chains print out intermediate steps, some dont. lets standardize it so that they all have the same flag which turns it on/off, and things are printed out in a standard way. Ideally colorized
|
more consistent printing of intermediate steps
|
https://api.github.com/repos/langchain-ai/langchain/issues/38/comments
| 0 |
2022-10-28T06:51:51Z
|
2022-11-04T18:18:01Z
|
https://github.com/langchain-ai/langchain/issues/38
| 1,426,777,279 | 38 |
[
"hwchase17",
"langchain"
] | null |
create github action to auto publish new pypi package when version changes
|
https://api.github.com/repos/langchain-ai/langchain/issues/26/comments
| 3 |
2022-10-26T04:46:07Z
|
2023-08-24T16:22:21Z
|
https://github.com/langchain-ai/langchain/issues/26
| 1,423,431,400 | 26 |
[
"Piwigo",
"Piwigo"
] |
Directory `_data/cache` contains many `*.cache` files, generated by the `persistent_cache` system. It is not often purged. Considering it is often related to user cache, we should purge it each time we `invalidate_user_cache`
|
limit increase of _data/cache directory
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2203/comments
| 0 |
2024-08-07T20:14:09Z
|
2024-08-07T20:15:26Z
|
https://github.com/Piwigo/Piwigo/issues/2203
| 2,454,264,856 | 2,203 |
[
"Piwigo",
"Piwigo"
] |
Let's take an example. You're in the gallery search, with filters `{added_by=plegall, filetypes=jpg, date_posted:y2023}`. With version 14, the list of values for filter `added_by` will be only "plegall", because the list of `added_by` values is based on the current list of search results. Of course it will only find photos added by "plegall". But this is not smart. If you want to filter on another user, you have to clear this filter, validate, open the filter again. Bad UX.
The list of values for `added_by` filter should be computed from the photos filtered by `{filetypes=jpg, date_posted:y2023}`. The list of values for `filetypes` filter should be computed from the photos filtered by `{added_by=plegall, date_posted:y2023}`... ie the "other" filters.
|
[search] smarter dynamic filters
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2202/comments
| 0 |
2024-08-06T14:31:29Z
|
2024-08-06T15:05:11Z
|
https://github.com/Piwigo/Piwigo/issues/2202
| 2,451,042,419 | 2,202 |
[
"Piwigo",
"Piwigo"
] |
for status, privacy level and group advanced filters
|
[users] display the number of occurrences for each item
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2201/comments
| 0 |
2024-08-05T15:26:20Z
|
2024-08-05T15:50:15Z
|
https://github.com/Piwigo/Piwigo/issues/2201
| 2,448,837,436 | 2,201 |
[
"Piwigo",
"Piwigo"
] |
Yesterday, August 3, when I logged into my own photo album site using Piwigo version 14.4, the site redirected to other pornographic urls.
I checked the site later and found that malicious people had written malicious HTML code to some fields in my piwigo database.
However, I am not a professional in this field, I do not understand how the attacker wrote my database, I deleted the original site information after the attack, resulting in the imperfect preservation of the attacked information, only leaving these two pictures and the malicious HTML code that the attacker wrote to the SQL database.
The following line is malicious HTML code that the attacker injected into the field values of my SQL database:
` '"\><meta http-equiv="refresh" content="0;url=https://www.highratecpm.com/zjf065d3?key=7d12071e2113ba80d9395f1c5a19b3cf"> `
I am from China, using the translation software to write this paragraph, there may be some parts of the expression is not correct.
I am sure that I am using piwigo version 14.4, but I did not find any security updates in version 14.5, so I hope to get a reply, whether this problem has been fixed or no one has found or encountered it.
|
I used piwigo14.4 to create a website site that was attacked,SQL database is injected with malicious HTML code
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2200/comments
| 1 |
2024-08-03T16:27:30Z
|
2024-08-08T15:09:00Z
|
https://github.com/Piwigo/Piwigo/issues/2200
| 2,446,449,996 | 2,200 |
[
"Piwigo",
"Piwigo"
] |
Hello,
It would be extremely practical to be able to add a tag to an album and have this tag automatically applied to all the sub-albums and photos contained in it.
|
Feature request : Add a tag to an album
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2199/comments
| 0 |
2024-08-03T15:30:03Z
|
2024-08-03T15:30:03Z
|
https://github.com/Piwigo/Piwigo/issues/2199
| 2,446,410,736 | 2,199 |
[
"Piwigo",
"Piwigo"
] |
This is properly impossible, in theory. The bounds must be wrong at some point.
<img width="1067" alt="Screenshot 2024-08-02 at 17 45 29" src="https://github.com/user-attachments/assets/ee518b7b-5deb-4999-bbd3-41dbeab14739">
|
[15.0.0beta2][search] filter by filesize might lead to empty results
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2198/comments
| 0 |
2024-08-02T15:46:15Z
|
2024-08-02T15:47:52Z
|
https://github.com/Piwigo/Piwigo/issues/2198
| 2,445,265,729 | 2,198 |
[
"Piwigo",
"Piwigo"
] |
Me and @inesmarcal discover a new vulnerability never before reported in "HOST/admin.php?page=user_list" link, where based on filters should be possible to see the users list, but some of the parameters from these filters are SQL injectable:
Following the request sent through Firefox, we can see that exists several parameters:
If we manipulate the parameters 'max_level' and 'min_register' in order to include a quote and then resend the request, a MYSQL error will appear, which proves the existence of a SQL Injection vulnerability in both fields.
'max_level'
'min_register'
Looking at the source code it's possible to observe that these parameters are grouped in a variable that will use them in the execution of a SQL query:
This could lead to several consequences like "Code Execution" and "Information Disclosure" by manipulate the SQL queries, so these parameters must sanitized before used in any SQL queries. This affect version 12.2.0 and might affect future versions, since there is a reported vulnerability similar to this in version 13.8.0.
PS: please assign this issue to me (@joaosilva21) and my collegue @inesmarcal
PS II: this issue was created in order to have a reference link in the future for the CVE being submitted. When confirmed, the name of this issue will change in order to include the CVE ID in it.
|
SQL Injection in User List visualization via Admin > Manage
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2197/comments
| 3 |
2024-08-02T00:55:38Z
|
2024-08-02T23:29:53Z
|
https://github.com/Piwigo/Piwigo/issues/2197
| 2,443,760,486 | 2,197 |
[
"Piwigo",
"Piwigo"
] |
test
|
test
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2196/comments
| 0 |
2024-08-02T00:04:39Z
|
2024-08-02T00:08:26Z
|
https://github.com/Piwigo/Piwigo/issues/2196
| 2,443,717,198 | 2,196 |
[
"Piwigo",
"Piwigo"
] |
When ratings are disabled (which is the default configuration), Piwigo should not list the filter by ratings in the gallery search.
|
[search] filter by rating should be hidden when feature is disabled
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2195/comments
| 3 |
2024-07-31T15:20:01Z
|
2024-08-01T10:31:12Z
|
https://github.com/Piwigo/Piwigo/issues/2195
| 2,440,319,502 | 2,195 |
[
"Piwigo",
"Piwigo"
] |
Following #2166 we would need to know:
* how files are added, ie sync or API or both. We have no idea how important the "add by sync" still is in 2024. I would say "less than 5% of Piwigo installs use it" but I might be very wrong.
* which kind of files are hosted. Is Piwigo used 98% for JPEG files? Are MP4 videos used on more than 50% of Piwigo installs? We have no idea for now.
|
anonymous statistics to piwigo.org, details on files
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2194/comments
| 0 |
2024-07-29T21:35:26Z
|
2024-07-29T21:41:46Z
|
https://github.com/Piwigo/Piwigo/issues/2194
| 2,436,422,356 | 2,194 |
[
"Piwigo",
"Piwigo"
] |
These are the planned new widgets
- Rating
- File size
- Ratio
- height
- width
|
[search] Add new search filter widgets
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2193/comments
| 0 |
2024-07-25T09:30:50Z
|
2024-07-25T14:11:11Z
|
https://github.com/Piwigo/Piwigo/issues/2193
| 2,429,490,031 | 2,193 |
[
"Piwigo",
"Piwigo"
] |
Due to the fixed height of the widget some options disappear
|
[search] Added by list gets cut off
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2192/comments
| 0 |
2024-07-24T06:56:46Z
|
2024-07-24T07:42:14Z
|
https://github.com/Piwigo/Piwigo/issues/2192
| 2,426,750,783 | 2,192 |
[
"Piwigo",
"Piwigo"
] |
hello, there is this page https://siteweb.com/galerie/index.php?/add_photos allowing users non admin to upload photos, but there is also a warning message about a value of a variable _quota_details_ missing
_Warning: Undefined array key "quota_details" in /var/www/html/galerie/data/templates_c/1879avm^8abcc0ffac9f32fe22e3e7c3293d8801f9072dfe_0.file.add_photos.tpl.php on line 692
_Warning: Attempt to read property "value" on null in /var/www/html/galerie/data/templates_c/1879avm^8abcc0ffac9f32fe22e3e7c3293d8801f9072dfe_0.file.add_photos.tpl.php on line 692
I guess there should be some fields in administration to set the max weight of a file uploadable ?
Piwigo14.4.0/ Community 14.a
PHP: 8.2.7
MySQL: 10.11.6-MariaDB-0+deb12u1
Bibliothèque graphique: GD 2.3.3
|
Warning message about quota_details on the uploading page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2191/comments
| 0 |
2024-07-22T08:11:28Z
|
2024-07-22T08:11:28Z
|
https://github.com/Piwigo/Piwigo/issues/2191
| 2,422,235,798 | 2,191 |
[
"Piwigo",
"Piwigo"
] |
Because after discussion we raised the issue that having the input text when the email is sent could be confusing for the user. Instead we put a more explicit message and allow the user to generate a new link in modal user > password. But we leave the text input for all other cases.
Old:
New:
with email
without email
with error when sending email
|
[users] add new user message and text input can be confusing
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2189/comments
| 0 |
2024-07-16T08:09:47Z
|
2024-07-16T08:16:04Z
|
https://github.com/Piwigo/Piwigo/issues/2189
| 2,410,505,353 | 2,189 |
[
"Piwigo",
"Piwigo"
] |
Hello, i've an issue when i've too many files in the cache (/var/www/_data/upload/xxxx).
Directory rights are ok. I've 13900 thumbnails files in the directory.
When i go to a new image without thumbnail, it tries to generate it, but fails.
The image link gives a code 200 but it contains a message begining with:
"Undefined constant "MKGETDIR_DEFAULT" in /var/www/include/Logger.class.php ...."
If I a clear the cache, i can immediately after, generate the thumbnail.
My filesystem is btrfs (shouldn't be a limitation).
|
Can't generate thumbnail when too many files in a directory
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2188/comments
| 0 |
2024-07-15T21:13:54Z
|
2024-07-15T21:14:19Z
|
https://github.com/Piwigo/Piwigo/issues/2188
| 2,409,654,252 | 2,188 |
[
"Piwigo",
"Piwigo"
] |
Thank's to : https://piwigo.org/forum/viewtopic.php?id=33738
|
[dashboard] activity tooltips pop out of the screen
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2187/comments
| 0 |
2024-07-15T10:35:32Z
|
2024-07-15T15:41:49Z
|
https://github.com/Piwigo/Piwigo/issues/2187
| 2,408,405,695 | 2,187 |
[
"Piwigo",
"Piwigo"
] |
When the main user is set, the delete icon should disappear. It's only on the UX side, in the API (backend side) it's already impossible to delete the main user.
|
[Users] Delete icon is present when a main user is set
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2186/comments
| 0 |
2024-07-15T10:20:28Z
|
2024-07-29T15:32:00Z
|
https://github.com/Piwigo/Piwigo/issues/2186
| 2,408,377,940 | 2,186 |
[
"Piwigo",
"Piwigo"
] |
and an underline to remove
|
[Users] Wrong text color on hover buttons in the user modal
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2185/comments
| 0 |
2024-07-15T10:08:52Z
|
2024-07-15T10:22:58Z
|
https://github.com/Piwigo/Piwigo/issues/2185
| 2,408,356,049 | 2,185 |
[
"Piwigo",
"Piwigo"
] |
So I wanted to try and customize my piwigo installation, perhaps contribute some features back upstream, but I can't get the current head to run.
Process I took:
- fresh install of 14.4 for a dev server
- added some content
- `git clone ...`, switch directories from 14.4 to git, merge `local/` and `_data`
Page is broken:
So is it currently possible to upgrade from the main release to git-head?
|
Upgrading from 14.4 to git-head
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2182/comments
| 1 |
2024-07-07T18:39:02Z
|
2024-07-11T07:51:27Z
|
https://github.com/Piwigo/Piwigo/issues/2182
| 2,394,169,707 | 2,182 |
[
"Piwigo",
"Piwigo"
] |
Hi, the following error has occur when I click my username(admin) at the top right corner in the piwigo page:
```
Fatal error: Uncaught DivisionByZeroError: Division by zero in /config/www/_data/templates_c/p6jhns^97fe272ea0e342f147a8d8650c738e329e4c10f1_0.file.intro.tpl.php:504
Stack trace:
#0 /app/www/public/include/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_667533c8cb4a47_52699291()
#1 /app/www/public/include/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode()
#2 /app/www/public/include/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render()
#3 /app/www/public/include/smarty/libs/sysplugins/smarty_internal_templatebase.php(238): Smarty_Internal_Template->render()
#4 /app/www/public/include/smarty/libs/sysplugins/smarty_internal_templatebase.php(116): Smarty_Internal_TemplateBase->_execute()
#5 /app/www/public/include/template.class.php(483): Smarty_Internal_TemplateBase->fetch()
#6 /app/www/public/include/template.class.php(406): Template->parse()
#7 /app/www/public/admin/intro.php(497): Template->assign_var_from_handle()
#8 /app/www/public/admin.php(346): include('...')
#9 {main} thrown in /config/www/_data/templates_c/p6jhns^97fe272ea0e342f147a8d8650c738e329e4c10f1_0.file.intro.tpl.php on line 504
```
before this, I modify the configure file show as following to solve chinese fold name problem:
```
$conf['sync_chars_regex'] = '/^[\x{2e80}-\x{fe4f}a-zA-Z0-9-_.\(\)\[\]\!@#×\s]+$/u';
```
but when I restore this configure and restart the container, the error remains.
My piwigo deploy by docker with image linuxserver/piwigo:latest which use 14.4.0 version of this repository. Is anyone some help?
|
Fatal error: Uncaught DivisionByZeroError
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2181/comments
| 1 |
2024-07-07T14:07:38Z
|
2024-08-03T12:00:50Z
|
https://github.com/Piwigo/Piwigo/issues/2181
| 2,394,071,205 | 2,181 |
[
"Piwigo",
"Piwigo"
] |
This does not appear to be the same issue as https://github.com/Piwigo/Piwigo/issues/1305
Installing piwigo and am receiving the following error message when submitting the netinstall.php form:
`[Fri Jul 05 15:09:50.433252 2024] [fcgid:warn] [pid 269936:tid 129046465349376] [remote 96.74.78.141:49566] mod_fcgid: stderr: PHP Fatal error: Uncaught Error: Call to undefined function __() in /[...]/pwg_unzip.php:209, referer: [...]/piwigo-netinstall.php`
```
$ grep "__(" img.stevarino.com/*.php
pwg_files.php: throw new Exception(__('Unable to open directory.'));
pwg_files.php: throw new Exception(__('Unable to create directory.'));
pwg_files.php: throw new Exception(__('File is not writable.'));
pwg_files.php: throw new Exception(__('Unable to open file.'));
pwg_files.php: throw new Exception(__('Not an uploaded file.'));
pwg_files.php: throw new Exception(__('The uploaded file exceeds the maximum file size allowed.'));
pwg_files.php: throw new Exception(__('The uploaded file was only partially uploaded.'));
pwg_files.php: throw new Exception(__('No file was uploaded.'));
pwg_files.php: throw new Exception(__('Missing a temporary folder.'));
pwg_files.php: throw new Exception(__('Failed to write file to disk.'));
pwg_files.php: throw new Exception(sprintf(__('%s is not a directory.'),$dirName));
pwg_files.php: throw new Exception(__('Unable to open directory.'));
pwg_unzip.php: throw new Exception(sprintf(__('File %s is not compressed in the zip.'),$file_name));
pwg_unzip.php: throw new Exception(sprintf(__('Trying to unzip a folder name %s'),$file_name));
pwg_unzip.php: throw new Exception(__('Unable to write destination file.'));
pwg_unzip.php: throw new Exception(__('Unable to write in target directory, permission denied.'));
pwg_unzip.php: throw new Exception(__('Not enough memory to open file.'));
```
I can confirm that these function calls are in the source, but I don't know where those would exist in source control (does not appear to be in this repo): https://piwigo.org/download/netinstall/class.unzip.txt
Installed modules:
```
$ php -m | tr '\n' ' '
[PHP Modules] bcmath bz2 calendar Core ctype curl date dom exif fileinfo filter ftp gd gettext hash iconv imagick imap intl json libxml mbstring mysqli mysqlnd openssl pcntl pcre PDO pdo_mysql pdo_sqlite Phar posix pspell random Reflection session SimpleXML soap sockets sodium SPL sqlite3 standard tokenizer xml xmlreader xmlwriter xsl Zend OPcache zip zlib [Zend Modules] Zend OPcache
```
Sanity check:
```
$ php -r "__('foo');"
PHP Fatal error: Uncaught Error: Call to undefined function __() in Command line code:1
Stack trace:
#0 {main}
thrown in Command line code on line 1
```
Thanks in advance!
|
PHP 8.2: Call to undefined function __() during netinstall.php
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2180/comments
| 3 |
2024-07-05T22:42:40Z
|
2024-07-06T01:59:40Z
|
https://github.com/Piwigo/Piwigo/issues/2180
| 2,393,208,485 | 2,180 |
[
"Piwigo",
"Piwigo"
] |
There is no primary action, one needs to be a secondary action for better UX
|
no hierarchy between buttons after upload
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2178/comments
| 0 |
2024-07-02T08:03:18Z
|
2024-07-02T08:37:54Z
|
https://github.com/Piwigo/Piwigo/issues/2178
| 2,385,537,036 | 2,178 |
[
"Piwigo",
"Piwigo"
] |
Hello,
I'm working with Piwigo v13.8.
I noticed, that in the admin page I was notified of some "Orphans" on my setup.
And I tried to delete them, but allthough Piwigo said the batch action completed succesfully, still the pictures were mentioned as Orphans and they were still there.
Diving into the code I saw that in "batch_manager_global.php" the line that is doing the job is commented out:
When I enabled the line by removing the comment sign, I was able to perform the deletion of the Orphans succesfully.
Is there a reason that it's not enabled by default?
Regards,
|
Delete orphans failes
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2177/comments
| 0 |
2024-06-25T14:05:49Z
|
2024-06-25T14:05:49Z
|
https://github.com/Piwigo/Piwigo/issues/2177
| 2,372,794,294 | 2,177 |
[
"Piwigo",
"Piwigo"
] |
Hi,
for a while now, under some circumstances like mine, creating a user fails. No error, the submit button seems asleep.
I have not dug to find why, but I suspect some problem with Firefox in strict mode. Sorry for being so loose.
This problem reminds me that hard time I had with https://github.com/Piwigo/Piwigo/issues/1296#issuecomment-772222380
|
Creating new user fails / Firefox - Strict mode
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2176/comments
| 2 |
2024-06-21T18:42:06Z
|
2024-07-18T16:37:37Z
|
https://github.com/Piwigo/Piwigo/issues/2176
| 2,367,072,833 | 2,176 |
[
"Piwigo",
"Piwigo"
] |
## Problem
I am running Piwigo using the Linuxserver provided docker image ( https://hub.docker.com/r/linuxserver/piwigo ) on my raspberry PI and am having trouble uploading images. Everything else runs perfectly fine.
## Details
I managed to successfully set up my Piwigo container, and am able to register, log in, create galleries & tags, view galleries and their contents, adjust configurations, install plugins etc.
Everything works perfectly fine, but when I try to upload an image, the image gets successfully uploaded (and can be viewed in the gallery), but the server fails to respond to the upload POST request, until a timeout error is thrown.
The following line can be found in the nginx log after the 504 was received by the browser:
`[error] 255#255: *48 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 192.168.178.43, server: _, request: "POST /ws.php?method=pwg.images.upload&format=json HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.178.30:8081", referrer: "http://192.168.178.30:8081/admin.php?page=photos_add"`
I access the website directly via IPv4 address.
The error persists no matter on which browser or platform i try to upload. Tested on:
- Desktop, Chrome
- Desktop, Edge
- Mobile, Chrome
I already tried reaching out to the LinuxServer.io team, but they did not find the cause either, saying that this may be a Piwigo issue, and not a docker issue.
### System details
`Linux Justin-RASPI 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux`
### Docker setup
Piwigo container:
```yaml
piwigo:
image: lscr.io/linuxserver/piwigo
restart: unless-stopped
depends_on:
- database
networks:
mainnet:
ipv4_address: 172.20.1.5
ports:
- 8081:80
- 8082:443
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/Berlin
volumes:
- /srv/piwigo/config:/config
- /mnt/ssd/server/piwigo:/gallery
```
Database container (for reference, if necessary)
```yaml
database:
image: mariadb:lts
restart: unless-stopped
environment:
- MARIADB_RANDOM_ROOT_PASSWORD=yes
networks:
mainnet:
ipv4_address: 172.20.0.2
ports:
- "3306:3306"
volumes:
- /srv/database/backup:/backup
- /srv/database/config:/etc/mysql
- /srv/database/logs:/var/log/mysql
- /srv/database/data:/var/lib/mysql
```
---
I am unfortunately not too knowledgeable with PHP, so I didn't try any debugging yet.
I'm thankful for every bit of help!
|
Uploading image results in timeout (504)
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2175/comments
| 0 |
2024-06-21T15:36:16Z
|
2024-06-21T15:37:39Z
|
https://github.com/Piwigo/Piwigo/issues/2175
| 2,366,787,772 | 2,175 |
[
"Piwigo",
"Piwigo"
] |
The "sync metadata" action generates several AJAX requests to `pwg.images.syncMetadata`. Unfortunately, they are sent in parallel, all at once. That is a nonsense to me. Piwigo frontend shoud send them one by one. With the use of `queuedManager` just like it's done with `pwg.images.delete`.
|
[batch manager, sync metadata] use AJAX requests in sequence instead of parallel
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2174/comments
| 0 |
2024-06-21T14:48:31Z
|
2024-07-09T18:04:56Z
|
https://github.com/Piwigo/Piwigo/issues/2174
| 2,366,703,463 | 2,174 |
[
"Piwigo",
"Piwigo"
] |
As described in #2169 :
> When sending a request to Piwigo API, method pwg.images.syncMetadata, the list of image_ids is provided as an array. While this is certainly the "cleaner", here is what is sent: ws.php?format=json&method=pwg.images.syncMetadata&image_id[]=1&image_id[]=2&image_id[]=3
>
> I think it would be more efficient to send image_id=1,2,3
... without breaking the way it currently works.
|
[pwg.images.syncMetadata] accept image_ids as comma separated list
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2173/comments
| 2 |
2024-06-21T14:38:06Z
|
2024-07-09T13:42:47Z
|
https://github.com/Piwigo/Piwigo/issues/2173
| 2,366,684,803 | 2,173 |
[
"Piwigo",
"Piwigo"
] |
Hi,
Duplicate finder is good but we don't know from which album is the photo without editing it.
It should be nice to add this information in the popin or perhaps under the photo
Regards
|
Feature Request : Batch Duplicate Finder, Display from which album(s) are the photo
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2172/comments
| 0 |
2024-06-21T09:42:03Z
|
2024-06-21T09:42:03Z
|
https://github.com/Piwigo/Piwigo/issues/2172
| 2,366,150,463 | 2,172 |
[
"Piwigo",
"Piwigo"
] |
Browsers have a built in PDF reader why do we not use this to display PDFs rather than a preview
|
[picture page] PDF integration
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2170/comments
| 1 |
2024-06-20T09:04:16Z
|
2024-06-20T11:37:52Z
|
https://github.com/Piwigo/Piwigo/issues/2170
| 2,363,922,970 | 2,170 |
[
"Piwigo",
"Piwigo"
] |
> PHP message: PHP Warning: Unknown: Input variables exceeded 1000. To increase the limit change max_input_vars in php.ini ... "POST ws.php?format=json&method=pwg.images.syncMetadata , referrer: "http://.../admin.php?page=batch_manager"
When sending a request to Piwigo API, method `pwg.images.syncMetadata`, the list of `image_ids` is provided as an array. While this is certainly the "cleaner", here is what is sent: ws.php?format=json&method=pwg.images.syncMetadata&image_id[]=1&image_id[]=2&image_id[]=3
1. I think it would be more efficient to send image_id=1,2,3
2. instead of single HTTP variable, we send 3. There is a limit (to 1000 by default). If you have 1000 photos, you send 1000 `image_id[]` + `pwg_token` and it exceeds the limit !
The most immediate way to fix this problem is to ask javascript in batch manager to group image_ids by 500 instead of 1000. This is what we're going to do for now. I would be happy that later we have a list of image_id seperated by commas.
|
[batch manager, sync metadata] Input variables exceeded 1000
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2169/comments
| 0 |
2024-06-19T12:58:31Z
|
2024-06-19T12:59:48Z
|
https://github.com/Piwigo/Piwigo/issues/2169
| 2,362,326,193 | 2,169 |
[
"Piwigo",
"Piwigo"
] |
Hi
I want to say that I am very happy with using Piwigo. The author of the app deserves great **Applause**.
**Reason:**
Nowadays, security is playing an increasingly important role. The computing power used to crack passwords has gained significant efficiency. For this reason, a strong password **isn't as secure as it used to be**. Sorry for adding another topic, but I think I started an important problem. I guess that many users would like their private photos, videos to be well protected. Piwigo has a mobile app that is great for this feature 👏
**Suggestion for marking the topic:**
Type: Feature
Type: Enhancement
Section: Users & Groups
Priority: High
Milestone: Yes
**Main part:**
Does the Product Owner plan to consider my request to create a 2FA (two-factor authentication) or MFA for the Piwigo app based on an event in a **trusted device**. A plugin for Piwigo doesn't seem like a good solution for anyone (I saw that one plugin exists in beta), but it is such a basic and integral feature that it shouldn't be implemented as an add-on.
**Proposed scenario for Product Owner:**
1. In the application, the Piwigo webapp Administrator can select an option (I treat the solution I propose as an option - the Administrator has the right not to decide on protection): "Login only with authorization in the Piwigo mobile app." for themselves or for a specific user/group.
2. The Administrator is shown the Token key in case of loss of the device where the mobile app was used for authorization.
3. Warning about data backup:
- Token Key
- Media (photos, videos, etc.) in case of server failure, loss of the token and the device with the mobile app.
4. The Administrator logs into the Piwigo mobile app and receives a message about adding the device to trusted. Even if someone steals the password, logging in to the new mobile app won't nothing. Trusted devices can be managed only via the Piwigo webapp (website sends requests to new devices - adding them to trusted). At this point, the captured password won't allow you to log in to the Piwigo application website, because it already verifies it through a trusted device with the Piwigo mobile app.
5. The User account created by the Administrator receives the following information upon login: "Request for secure login to <Piwigo instance name>. Install the mobile app and follow the steps given in the guide" - from now on, the user has 7 days to complete authorization. If they don't do it in this specified time, their account will be blocked. After blocking, they must write a message to the Administrator asking for unblocking.
Summary:
There are already 2 applications (webapp and mobile). All that remains is:
1. Creating a **push token mechanism (encrypted)** to the mobile application from the server <Piwigo instance name>.
2. Encryption with a salt of token keys in the DataBase
I'd appreciate a full answer. Please don't treat my message as a demand - it is a request.
Best regards
Luke
|
Authorization Token from Mobile App
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2168/comments
| 2 |
2024-06-18T16:32:40Z
|
2024-07-05T01:11:43Z
|
https://github.com/Piwigo/Piwigo/issues/2168
| 2,360,266,821 | 2,168 |
[
"Piwigo",
"Piwigo"
] |
related to #1710
When we have too many elements in the tooltips, the tooltip is too large, which creates a border effect (the small arrow is offset).
|
[dashboard] storage bar details too large
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2167/comments
| 0 |
2024-06-11T15:20:09Z
|
2024-06-11T15:23:44Z
|
https://github.com/Piwigo/Piwigo/issues/2167
| 2,346,705,553 | 2,167 |
[
"Piwigo",
"Piwigo"
] |
We don't want any private data. We (Piwigo developers) need some technicals information (Piwigo version, PHP version, MySQL/MariaDB flavor, graphics library...) and also some general stats (number of photos, albums, users, administrators, tags, activities) as well as list of "public" extensions used (only the ones available on piwigo.org/ext).
Of course, we keep everything anonymous. We don't even know the origin url of the Piwigo sending its statistics.
With such statitstics, we (Piwigo developers) would be able to know the number of Piwigo installations (is it 10k, 100k or 1 million ?), the way Piwigo is used (single or multiple administrators), the average number of photos and albums... We would also be able to know if some features are used (user comments, ratings, history...).
Statistics about extensions would make it possible to show, on piwigo.org/ext how many active users each extension has, which version is used... Wordpress.org has that and it's crazy useful (in my opinion).
Let's say "once a week" send statistics to piwigo.org. This feature would be deactivable, but active by default. Here is an example of what would be sent:
```
Array
(
[origin_hash] => 5b699b5db056156e0198154ee8f7c559d42e561b
[technical] => Array
(
[php_version] => 8.1.2-1ubuntu2.17
[piwigo_version] => 14.4.0
[os_version] => Linux
[db_version] => 5.5.5-10.6.16-MariaDB-0ubuntu0.22.04.1
[php_datetime] => 2024-06-10 21:21:27
[db_datetime] => 2024-06-10 21:21:27
[graphics_library] => ext_imagick/6.9.11-60
)
[general_stats] => Array
(
[nb_photos] => 149
[nb_categories] => 344
[nb_tags] => 47
[nb_image_tag] => 314
[nb_users] => 7
[nb_admins] => 1
[nb_groups] => 5
[nb_rates] => 1
[nb_views] => 3054
[disk_usage] => 533
[nb_formats] => 0
[formats_disk_usage] =>
[installed_on] => 2022-10-19 10:24:09
[nb_private_plugins] => 1
[nb_plugins] => 9
[nb_private_themes] => 1
[nb_themes] => 10
[default_theme] => modus
[default_language] => en_US
[nb_activities] => 2068
)
[plugins] => Array
(
[0] => #303/community/auto
[1] => #199/GrumPluginClasses/3.5.15
[2] => #304/ContactForm/auto
[3] => #610/piwigo-videojs/2.9.b
[4] => #140/bbcode_bar/auto
[5] => #530/batch_manager_prefilters/auto
[6] => #972/editorplus/auto
[7] => #535/CryptograPHP/auto
)
[themes] => Array
(
[0] => #599/smartpocket/auto
[1] => #728/modus/auto
[2] => #383/Pure_clear_blue/auto
[3] => #9/clear/12.a
[4] => #831/bootstrap_darkroom/auto
[5] => #685/elegant/auto
[6] => #308/simple/auto
[7] => #602/simpleng/3.2.7
[8] => #773/stripped_responsive/auto
)
[themes_usage] => Array
(
[bootstrap_darkroom] => 5
[modus] => 2
)
[languages_usage] => Array
(
[en_US] => 6
[fr_FR] => 1
)
[activities] => Array
(
[album] => Array
(
[add] => 404
[delete] => 61
[edit] => 106
[move] => 7
)
[group] => Array
(
[add] => 13
[delete] => 8
[edit] => 17
)
[photo] => Array
(
[add] => 175
[delete] => 26
[edit] => 979
)
[tag] => Array
(
[add] => 12
[delete] => 1
[edit] => 12
)
[user] => Array
(
[add] => 7
[delete] => 5
[edit] => 81
[login] => 119
[logout] => 35
)
[system] => Array
(
[core] => Array
(
[autoupdate] => 21
[config] => 52
[maintenance] => 34
)
[plugin] => Array
(
[activate] => 68
[autoupdate] => 17
[deactivate] => 38
[delete] => 6
[install] => 5
[restore] => 4
[uninstall] => 3
[update] => 9
)
[theme] => Array
(
[activate] => 11
[deactivate] => 3
[delete] => 5
[install] => 1
[set_default] => 24
[update] => 8
)
)
)
[features] => Array
(
[use_watermark] => no
[activate_comments] => yes
[rate] => yes
[log] => yes
[history_guest] => yes
[history_admin] => no
)
)
```
|
send statistics to piwigo.org, anonymously
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2166/comments
| 0 |
2024-06-10T19:23:20Z
|
2024-06-10T19:32:16Z
|
https://github.com/Piwigo/Piwigo/issues/2166
| 2,344,668,434 | 2,166 |
[
"Piwigo",
"Piwigo"
] |
A new interface for creating a user. Overhaul of the password system (when a user is created) and new interface for a user's first login.
|
[Users] New add user pop in
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2165/comments
| 0 |
2024-06-10T10:04:58Z
|
2024-07-01T13:06:52Z
|
https://github.com/Piwigo/Piwigo/issues/2165
| 2,343,488,116 | 2,165 |
[
"Piwigo",
"Piwigo"
] |
Update Batch Manager Unit Mode according to web design (see below).
|
Batch Manager Unit Mode redesign
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2164/comments
| 0 |
2024-05-30T09:56:31Z
|
2024-07-02T09:20:18Z
|
https://github.com/Piwigo/Piwigo/issues/2164
| 2,325,251,421 | 2,164 |
[
"Piwigo",
"Piwigo"
] |
When the configuration to allow download is active but the download permission for the specific guest user is revoked, the download link still appears for the guest users on non picture formats (IE mp4, PDF, ...)
|
Download link appears for guest user when download is not allowed
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2163/comments
| 0 |
2024-05-29T09:20:49Z
|
2024-05-29T14:41:24Z
|
https://github.com/Piwigo/Piwigo/issues/2163
| 2,322,812,251 | 2,163 |
[
"Piwigo",
"Piwigo"
] |
In `admin.php?page=photos_add§ion=applications`, clicking on "Learn more" in the Shotwell panel leads to [http://yorba.org/shotwell/](http://yorba.org/shotwell/), which appears to be a nonexistent domain.
|
Shotwell link is bad
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2162/comments
| 0 |
2024-05-22T00:18:11Z
|
2024-08-02T14:18:47Z
|
https://github.com/Piwigo/Piwigo/issues/2162
| 2,309,323,011 | 2,162 |
[
"Piwigo",
"Piwigo"
] |
Some user name their photos/albums/tags with custom identifiers. These identifiers may include dots. For example, naming an album `BB.G5483.04509`. The search will split in 3 words `BB` + `G5483` + `04509` because `.` is considered as a word spliter.
The `.` should indeed be removed in examples like `first. second. third` or `two words.` but not in `BB.G5483.04509` or `PO.45579`.
|
[search] do not always split word on dot
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2161/comments
| 0 |
2024-05-17T10:25:10Z
|
2024-05-17T10:28:52Z
|
https://github.com/Piwigo/Piwigo/issues/2161
| 2,302,358,005 | 2,161 |
[
"Piwigo",
"Piwigo"
] |
After updating to Piwigo 14.4.0, I get this error synchronising:
Fatal error: Cannot redeclare strip_html_in_metadata() (previously declared in /var/www/piwigo/include/functions_metadata.inc.php:186) in /var/www/piwigo/include/functions_metadata.inc.php on line 186
|
Fatal error: Cannot redeclare strip_html_in_metadata()
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2160/comments
| 1 |
2024-05-16T07:20:51Z
|
2024-07-06T15:42:18Z
|
https://github.com/Piwigo/Piwigo/issues/2160
| 2,299,559,302 | 2,160 |
[
"Piwigo",
"Piwigo"
] |
Piwigo 14.4.0 (Truechart on TrueNAS SCALE)
When I sync thousands of photos, the sync page errors to repeating this message over and over:
`Deprecated: addslashes(): Passing null to parameter #1 ($string) of type string is deprecated in /app/www/public/admin/include/functions_metadata.php on line 107`
Until it stops this this message:
`Fatal error: Maximum execution time of 30 seconds exceeded in /app/www/public/admin/include/functions_metadata.php on line 185`
|
"Deprecated: addslashes()...." when syncing gallery
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2159/comments
| 1 |
2024-05-13T14:06:04Z
|
2024-08-02T07:01:49Z
|
https://github.com/Piwigo/Piwigo/issues/2159
| 2,292,935,237 | 2,159 |
[
"Piwigo",
"Piwigo"
] |
We are currently updating the interface for the user edit pop-in to enhance usability and integrate additional features.
|
[Users] New user edit pop in
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2158/comments
| 2 |
2024-05-10T16:07:09Z
|
2024-07-01T13:05:46Z
|
https://github.com/Piwigo/Piwigo/issues/2158
| 2,290,006,831 | 2,158 |
[
"Piwigo",
"Piwigo"
] |
Hello, I encountered an issue with RSS email notifications when bulk-adding images to a virtual album in Piwigo 14.4.0 via the "Pictures - Add" feature in the admin backend. The logic should be that the email shows the number of new images added to the album in this update, such as:
74 new pictures (April 6), 295 new pictures (April 5), 155 new pictures (April 5)
However, what actually happened was that the email repeatedly stated that only 1 new image was added to the album, such as:
1 new picture (April 26), 1 new picture (April 26), 1 new picture (April 26)
While this issue does not occur when synchronizing physical albums with Piwigo, there are times when adding physical albums is not convenient. We hope that this problem can be resolved.
|
Adding images to virtual albums causes RSS email issues
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2157/comments
| 0 |
2024-04-25T17:34:19Z
|
2024-04-26T03:16:17Z
|
https://github.com/Piwigo/Piwigo/issues/2157
| 2,264,138,280 | 2,157 |
[
"Piwigo",
"Piwigo"
] |
Some plugin might unset template variable `PAGE_BANNER`, resulting in a warning:
```
Undefined array key "PAGE_BANNER"
```
|
[PHP 8.2] Undefined array key "PAGE_BANNER"
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2156/comments
| 0 |
2024-04-24T14:39:51Z
|
2024-04-24T14:43:19Z
|
https://github.com/Piwigo/Piwigo/issues/2156
| 2,261,468,377 | 2,156 |
[
"Piwigo",
"Piwigo"
] |
Following #1938 there are still missing PHP functions for templates. Indeed some plugins use PHP functions in templates that Piwigo core does not.
|
PHP 8.2 and Deprecated: Creation of dynamic property
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2155/comments
| 0 |
2024-04-24T14:27:11Z
|
2024-04-24T14:27:37Z
|
https://github.com/Piwigo/Piwigo/issues/2155
| 2,261,439,922 | 2,155 |
[
"Piwigo",
"Piwigo"
] |
I've been chasing an issue which appears persistent from PiwiGo version 13.x through the current 14.4
When I upload photos through the web interface, I can see that all steps but one seem to complete:
1. Photos make it into the uploads/ directory with correct permissions
2. Thumbnails are generated in the _data folder correctly
However, two SQL database updates seem not to occur:
1. In piwigo_images, the field storage_category_id remains NULL rather than being set to the appropriate album (category).
2. In piwigo_image_category, no new entry is created.
When I manually fix the storage_category_id in piwigo_images, AND manually create the correct entry linking the image_id and category_id fields in the piwigo_image_category table, everything works as it should.
Finally, bulk uploaing photos via FTP and manually synchronizing through the Administration interface all works perfectly. The photos uploaded through the web interface are not picked up by this synchronization.
Would love to know what the issue might be, or what I may try to patch and submit this! Or I can start going through the code myself, though if a friendly human index out there could point me towards some of the right files that would be a big timesaver. Thank you!!!
|
Web Uploaded Photos Fail To Enter SQL Database at piwigo_image_category, but FTP Upload and Synchronization Works
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2154/comments
| 3 |
2024-04-22T13:48:57Z
|
2024-05-02T13:19:16Z
|
https://github.com/Piwigo/Piwigo/issues/2154
| 2,256,591,864 | 2,154 |
[
"Piwigo",
"Piwigo"
] |
Noticed on 12.2.0 - I'll check whether later versions are similarly affected
I'm running in a set of Docker containers (one for the database, one for php_fpm and one for nginx) and I've noticed that if you map the port on the nginx container to a different published port in docker-compose (e.g. with --ports 9081:8081) the element_URL returned by pwg.images.getInfo contains both ports e.g. https://hostname:9081:8081/photos/....
The workaround is to ensure that nginx is configured to listen on the published port and set --ports so that the two numbers are the same. I'm hoping to make a couple of small enhancements to the APIs I'm working with in the next few weeks so I'll see if I can work out a fix for this at the same time.
|
pwg.images.getInfo API call can return malformed URLs when running in a Docker container
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2153/comments
| 0 |
2024-04-21T09:29:31Z
|
2024-04-21T09:29:31Z
|
https://github.com/Piwigo/Piwigo/issues/2153
| 2,254,986,277 | 2,153 |
[
"Piwigo",
"Piwigo"
] |
Hi,
after update to the latest version (from 14.3.0 to 14.4.0) when I try to sync or only a dir or a full album album, I get this error
Fatal error: Cannot redeclare strip_html_in_metadata() (previously declared in /home/user/public_html/photo/include/functions_metadata.inc.php:186) in /home/user/public_html/photo/include/functions_metadata.inc.php on line 186
But the library, subfolders and photo are published.
BR,
Angelo
|
Error during update of library or album
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2152/comments
| 2 |
2024-04-20T17:30:20Z
|
2024-04-24T14:19:27Z
|
https://github.com/Piwigo/Piwigo/issues/2152
| 2,254,645,986 | 2,152 |
[
"Piwigo",
"Piwigo"
] |
The `pwg.image.rotate` API method deletes representatives and updates their URLs in the database so that the server knows that it should recreate them. In principle, URLs of the type: `https://…/_data/i/upload/2024/02/17…` are replaced with `https://…/i.php?/upload/2024/02/17…`. But is this always the case?
When called, `pwg.image.rotate` returns the JSON {"stat":"ok","result":true} after successfully rotating a photo. This JSON does not contain the modified sizes, nor the new URLs.
A third party app calling `pwg.image.rotate` obviously knows how the width and height have been changed and how to rotate thumbnails already in cache. But it may not know the URL of thumbnails not yet in cache unless it reloads all image data by calling `pwg.images.getInfo` to retrieve all addresses.
To reduce network accesses (battery consumption) and speed up third party apps, I would like that `pwg.image.rotate` also returns the width, height and URL of all thumbnails.
|
[API] pwg.image.rotate not returning sizes and thumbnail URLs
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2151/comments
| 2 |
2024-04-19T09:47:40Z
|
2024-04-21T16:53:25Z
|
https://github.com/Piwigo/Piwigo/issues/2151
| 2,252,559,318 | 2,151 |
[
"Piwigo",
"Piwigo"
] |
Introduced in Piwigo 14.4.0, new bug on synchronization:
> Fatal error: Cannot redeclare strip_html_in_metadata() (previously declared in include/functions_metadata.inc.php:186) in include/functions_metadata.inc.php on line 186
That is because the function `strip_html_in_metadata` is declared inside the function `get_exif_data` which can be called more than once.
|
[14.4.0, synchronization] Cannot redeclare strip_html_in_metadata()
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2150/comments
| 3 |
2024-04-18T12:20:16Z
|
2024-05-14T04:21:31Z
|
https://github.com/Piwigo/Piwigo/issues/2150
| 2,250,553,311 | 2,150 |
[
"Piwigo",
"Piwigo"
] |
When you rename an album, you can no longer create a sub-album.
|
[album manager] unable to create sub-album after rename
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2149/comments
| 0 |
2024-04-17T09:44:21Z
|
2024-04-17T10:00:10Z
|
https://github.com/Piwigo/Piwigo/issues/2149
| 2,247,857,457 | 2,149 |
[
"Piwigo",
"Piwigo"
] |
When a fatal error occurs (function `fatal_error`), Piwigo will apparently always display an error page with an error message and a backtrace.
(The php configuration options `display_errors` and) the local config options `show_php_errors_on_frontend` / `show_php_errors` seem to be ignored in this case.
This is apparently because the function signature is `function fatal_error($msg, $title=null, $show_trace=true)`, and all (?) callers only pass the first argument.
This could be a security concern (I guess?), a lot of web hosting guides recommend to switch off displaying PHP errors on the frontend. I would prefer to just have a generic "Internal Server Error" be displayed (especially with the config options set as they are).
I encountered this when I set up a separate PHP pool, running it as a separate user, after I already set up Piwigo. As a result, the `_data` directory contents were not writable, and Piwigo was complaining about this.
Piwigo version: 14.3.0
|
fatal_error always shows error / backtrace, no matter how show_php_errors_on_frontend / show_php_errors are set
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2148/comments
| 0 |
2024-04-15T19:31:55Z
|
2024-04-15T19:32:24Z
|
https://github.com/Piwigo/Piwigo/issues/2148
| 2,244,456,830 | 2,148 |
[
"Piwigo",
"Piwigo"
] |
|
[access denied] Page has no styling elements and needs a redesign
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2147/comments
| 0 |
2024-04-12T13:42:58Z
|
2024-04-12T13:49:51Z
|
https://github.com/Piwigo/Piwigo/issues/2147
| 2,240,188,615 | 2,147 |
[
"Piwigo",
"Piwigo"
] |
If you search for " word" or "word ", Piwigo will search for the space character as a word. This is not the expected behavior.
|
[search] leading or trailing spaces alter search results
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2146/comments
| 0 |
2024-04-12T07:49:18Z
|
2024-04-12T07:50:23Z
|
https://github.com/Piwigo/Piwigo/issues/2146
| 2,239,324,353 | 2,146 |
[
"Piwigo",
"Piwigo"
] |
When you have `ModeArray` in your list of EXIF fields to extract from the photo:
```
$conf['show_exif_fields'] = array(
'exif_field_Make' => 'Make',
'exif_field_Model' => 'Model',
'exif_field_ExposureTime' => 'ExposureTime',
'exif_field_FocalLength' => 'FocalLength',
'exif_field_FNumber' => 'FNumber',
'exif_field_ModeArray' => 'ModeArray',
);
```
The `ModeArray` is an array, obviously, and it breaks PHP code because `strip_tags` breaks on an array with PHP 8:
> Fatal error: Uncaught TypeError: strip_tags(): Argument #1 ($string) must be of type string, array given in include/functions_metadata.inc.php:190
>
> Stack trace:
> #0 include/functions_metadata.inc.php(190): strip_tags()
> #1 include/picture_metadata.inc.php(24): get_exif_data()
> #2 picture.php(1014): include('...')
> #3 {main}
> thrown in include/functions_metadata.inc.php on line 190
|
[PHP 8.x] exif ModeArray field breaks picture page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2145/comments
| 0 |
2024-04-10T10:22:37Z
|
2024-04-10T10:24:44Z
|
https://github.com/Piwigo/Piwigo/issues/2145
| 2,235,247,961 | 2,145 |
[
"Piwigo",
"Piwigo"
] |
Button colors does not match current graphic identity.
|
Button colors were not harmonized in web form and applications page
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2144/comments
| 0 |
2024-04-05T14:40:40Z
|
2024-04-05T15:13:15Z
|
https://github.com/Piwigo/Piwigo/issues/2144
| 2,228,196,426 | 2,144 |
[
"Piwigo",
"Piwigo"
] |
If I change album permissions for a user group, e.g. make a sub-album private, I can do that via the admin panel -> Users -> Groups -> Manage permissions. The issue is that the album doesn't actually become private. It is still visible to users from that group. However, it will be private to newly registered users that by default belong to that group. So you end up with users belonging to the same user group seeing different things, maybe even albums that you want to be private. This is a bit of a serious security issue.
The workaround is moving the whole album to the 'Forbidden' section and then moving the ones that you want to make public back to the 'Authorized' section. This is not clear at all that this is how it works and now I wonder how many albums in my gallery are public to certain user groups when they should be private....
|
Changing album group permissions doesn't work properly
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2143/comments
| 2 |
2024-04-03T15:18:04Z
|
2024-06-14T07:55:54Z
|
https://github.com/Piwigo/Piwigo/issues/2143
| 2,223,215,499 | 2,143 |
[
"Piwigo",
"Piwigo"
] |
When browsing a combination of tags, if the list of tag ids (separated by comma) is longer than 50 chars, a recent version of MariaDB will throw an error.
|
Data too long for column 'tag_ids'
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2142/comments
| 0 |
2024-03-31T15:07:39Z
|
2024-03-31T15:09:02Z
|
https://github.com/Piwigo/Piwigo/issues/2142
| 2,217,037,532 | 2,142 |
[
"Piwigo",
"Piwigo"
] |
The field IP in the piwigo_history table is too small (varchar(15)) and cannot save IPv6 completely. Those are truncated.
Should be at least 39 characters long to allow IPv6 addresses to be saved.
|
IP field in History table is too small
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2141/comments
| 1 |
2024-03-27T16:57:43Z
|
2024-07-03T12:13:59Z
|
https://github.com/Piwigo/Piwigo/issues/2141
| 2,211,313,714 | 2,141 |
[
"Piwigo",
"Piwigo"
] |
Still some `undefined array key` and private class attribute.
|
[PHP 8.x] errors on menu
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2140/comments
| 0 |
2024-03-27T13:59:17Z
|
2024-03-27T14:00:31Z
|
https://github.com/Piwigo/Piwigo/issues/2140
| 2,210,885,580 | 2,140 |
[
"Piwigo",
"Piwigo"
] |
Dear all,
My piwigo batch manager has gone bananas lately. Especially, I'm seeing the following message at the top of the page : "Warning: A non-numeric value encountered in /var/www/photos/admin/batch_manager.php on line 790".
I don't know if this is a consequence of the message above but the batch manager is not usable at all now (for example I can't select filters or photos anymore).
Any idea what is causing the problem?
After I got this issue I tried to make a fresh install of piwigo (kept the mysql database and moved my saved upload folder back into the fresh install folder): the issue is still there, which makes me wonder whether the issue could be linked to the content of the mysql database or the upload folder?
Thanks in advance for your help!
|
Non-numeric value encountered in batch_manager.php on line 790
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2139/comments
| 1 |
2024-03-25T21:27:43Z
|
2024-04-30T12:58:11Z
|
https://github.com/Piwigo/Piwigo/issues/2139
| 2,206,753,131 | 2,139 |
[
"Piwigo",
"Piwigo"
] |
This icon isn't explicit enough, seen as this link takes us to the batch manager it seems only logicial to use the same icon as in the menu ( this is the class used : "icon-th")
|
[edit album] manage album photos icon not ovious to its use
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2138/comments
| 0 |
2024-03-25T13:05:21Z
|
2024-03-27T14:04:39Z
|
https://github.com/Piwigo/Piwigo/issues/2138
| 2,205,725,380 | 2,138 |
[
"Piwigo",
"Piwigo"
] |
Hello,
I am getting this error:
Fatal error: Uncaught mysqli_sql_exception: Out of range value for column 'category_id' at row 1 in /srv/hfr-internal/include/dblayer/functions_mysqli.inc.php:132 Stack trace: #0 /srv/hfr-internal/include/dblayer/functions_mysqli.inc.php(132): mysqli->query() #1 /srv/hfr-internal/include/functions.inc.php(533): pwg_query() #2 /srv/hfr-internal/index.php(723): pwg_log() #3 {main} thrown in /srv/hfr-internal/include/dblayer/functions_mysqli.inc.php on line 132
The problem is that the category_id type table is SMALLINT(5) SIGNED. That gives me a range of -32768 to 32767. My max category id value is 38738, so above that range.
If I am logged in as an admin I get no message, probably because pwg_log() doesn't record admin activity to the piwigo_history table? However, if I am logged in as a normal user I see the error at the bottom of the page. In addition, the thumbnail doesn't show up and I can't open the image (while everything works if I am an admin).
The solution seems somewhat simple - I just changed the attribute to UNSIGNED. I am not sure having it SIGNED confers any benefits given that half of that range is not usable for us (we don't have categories with negative category_ids). But not sure it is the optimal solution.
|
SQL error - category_id out of SMALLINT(5) range
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2137/comments
| 0 |
2024-03-18T15:46:47Z
|
2024-03-18T15:46:47Z
|
https://github.com/Piwigo/Piwigo/issues/2137
| 2,192,583,181 | 2,137 |
[
"Piwigo",
"Piwigo"
] |
If a photo is tagged "party" and "friend", if you search "party friend" the photo won't be in the results.
|
[search 14.x] search by word on 2 words matching tags gives no result
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2136/comments
| 0 |
2024-03-17T17:21:23Z
|
2024-04-10T15:13:01Z
|
https://github.com/Piwigo/Piwigo/issues/2136
| 2,190,772,570 | 2,136 |
[
"Piwigo",
"Piwigo"
] |
First, Piwigo 14.3.0 is unable to rotate HEIC photos by default and the method `pwg.image.rotate` reports the string `[Image] unsupported file extension` which is not a JSON data. It should either manage HEIC photos or report a JSON including an error message because this is problematic for third party apps like the iOS and Android apps (another issue).
Here are the steps to reproduce the issue from the UI:
1. Add `'heic'` to `$conf['picture_ext']` with the LocalFiles Editor plugin for enabling HEIC photos rotations,
2. Choose a HEIC photo from the web UI,
3. Request a rotation, e.g. 90° clockwise,
4. Check the corresponding files in the `_data` and `upload` folders.
The original HEIC image located in the _upload_ folder is rotated as expected. But the thumbnail files located in __data_ are not deleted as the plugin does when dealing with JPEG files. The thumbnail shown on the web UI does not present the image rotated as expected. Force reloading the web page does nothing.
|
rotateImage plugin does not update thumbnails after rotating HEIC photo
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2135/comments
| 0 |
2024-03-15T20:45:54Z
|
2024-04-19T09:07:25Z
|
https://github.com/Piwigo/Piwigo/issues/2135
| 2,189,444,169 | 2,135 |
[
"Piwigo",
"Piwigo"
] |
Every `$conf['update_notify_check_period']` (default = 24 hours) Piwigo sends a requests to piwigo.org to list the versions of Piwigo currently available. If the current Piwigo is behind the latest version available on piwigo.org, Piwigo sends an email notification to the webmasters. To make sure Piwigo does not check piwigo.org too often (and sends an email to webmasters), it relies on the configuration parameter `update_notify_last_check` which is written by function `notify_piwigo_new_versions`:
```
conf_update_param('update_notify_last_check', date('c'));
```
If, for any reason, Piwigo fails to write this line in the database, Piwigo may not crash and continue to execute remaining code, thus notifiying webmasters... Even with a read-only database, I haven't been able to fully reproduce this bug, because my Piwigo stops as soon as the `insert/update` in the config table fails. Some users report that it does not crash for them and that they get dozens, or even thousands emails "a new version of Piwigo is available". Perfectly annoying!
https://fr.piwigo.org/forum/viewtopic.php?id=30404
https://piwigo.org/forum/viewtopic.php?id=33511
|
more than one email notification on new Piwigo version available
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2134/comments
| 1 |
2024-03-13T10:09:37Z
|
2024-03-13T10:13:24Z
|
https://github.com/Piwigo/Piwigo/issues/2134
| 2,183,600,561 | 2,134 |
[
"Piwigo",
"Piwigo"
] |
Self-hosted albums uploaded via FTP are not movable into virtual albums in the album manager.
more detail:
When I upload files via FTP to the Galleries folder and sync, it creates the albums and sub-albums if they are there, but in the album manager, those albums can't be moved.
However, if I use the Java uploader, and it works, uploads the albums and all the images and doesn't error out (thats another issue), I can move those albums into other albums with no issue
EDIT: Updating this with a thread form the piwigo forums on troubleshoot and reproducing the issues on another machine: https://piwigo.org/forum/viewtopic.php?pid=189488
Still having the issue.
|
Cannot move albums in Galleries folder in the Album Manager
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2133/comments
| 0 |
2024-03-09T04:40:29Z
|
2024-03-11T14:40:10Z
|
https://github.com/Piwigo/Piwigo/issues/2133
| 2,177,048,976 | 2,133 |
[
"Piwigo",
"Piwigo"
] |
|
[Album Selector] albums full hierarchy
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2132/comments
| 2 |
2024-03-08T14:46:14Z
|
2024-07-31T09:50:28Z
|
https://github.com/Piwigo/Piwigo/issues/2132
| 2,176,180,706 | 2,132 |
[
"Piwigo",
"Piwigo"
] |
|
[Search 14.2+] Missing icon in album selector
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2131/comments
| 0 |
2024-03-08T14:38:05Z
|
2024-03-08T14:41:05Z
|
https://github.com/Piwigo/Piwigo/issues/2131
| 2,176,166,548 | 2,131 |
[
"Piwigo",
"Piwigo"
] |
Does this software support docker installation?
|
docker support？
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2130/comments
| 1 |
2024-03-06T17:07:15Z
|
2024-05-01T10:13:45Z
|
https://github.com/Piwigo/Piwigo/issues/2130
| 2,172,026,153 | 2,130 |
[
"Piwigo",
"Piwigo"
] |
<img width="487" alt="Screenshot 2024-03-06 at 12 33 53" src="https://github.com/Piwigo/Piwigo/assets/9326959/eb740c25-2bf0-4074-b730-ac3c6aa97363">
This is due to https://github.com/Piwigo/Piwigo/commit/e57b8b8449750eece0b091a554e85d07eee56810 change which has unwanted side effects.
|
[user activity] user filter box exceeds container size
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2129/comments
| 0 |
2024-03-06T11:35:55Z
|
2024-03-06T11:38:33Z
|
https://github.com/Piwigo/Piwigo/issues/2129
| 2,171,297,978 | 2,129 |
[
"Piwigo",
"Piwigo"
] |
Piwigo version 14.2.0 but this was happening with earlier versions too.
In mobile view, if only sub-albums / sub-folders are visible only the first 20 of them are shown, and I don't see any way to see any more: there is no "next" link or numbers at the bottom of the page, like the desktop view or a page with only images has.
I see this same behavior in both Firefox and Chrome.
|
mobile view has no link to get past the first 20 sub-albums / sub-folders
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2128/comments
| 0 |
2024-03-03T23:39:17Z
|
2024-03-03T23:40:37Z
|
https://github.com/Piwigo/Piwigo/issues/2128
| 2,165,624,872 | 2,128 |
[
"Piwigo",
"Piwigo"
] |
Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Additionally, a 503 Service Unavailable error was encountered while trying to use an ErrorDocument to handle the request.
|
Upgrading ONLY dir, I got this error:
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2127/comments
| 0 |
2024-03-03T22:36:40Z
|
2024-03-03T22:36:40Z
|
https://github.com/Piwigo/Piwigo/issues/2127
| 2,165,601,415 | 2,127 |
[
"Piwigo",
"Piwigo"
] |
While the second is sort order Z-A
|
Typo: When you want to sort your albums there is twice the ability to sort A-Z
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2124/comments
| 1 |
2024-03-01T12:33:23Z
|
2024-03-01T13:01:49Z
|
https://github.com/Piwigo/Piwigo/issues/2124
| 2,163,307,982 | 2,124 |
[
"Piwigo",
"Piwigo"
] |
When you edit images in an album (not individual images) you can search for the new album. This list isn't sorted, so it gives you the idea that you find the correct album, while it maybe a lower, or higher in the list.
|
In admin mode move to album isn't sorted
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2123/comments
| 0 |
2024-03-01T12:31:55Z
|
2024-03-01T12:31:55Z
|
https://github.com/Piwigo/Piwigo/issues/2123
| 2,163,305,606 | 2,123 |
[
"Piwigo",
"Piwigo"
] |
On the new search engine user interface, when the filter "added_by" is enabled, if you have some users who had added some photos, but the user was deleted afterwards, you get:
> Notice : Undefined offset: <user_id> in index.php on line 397
|
[search] undefined offset when missing added_by user
|
https://api.github.com/repos/Piwigo/Piwigo/issues/2122/comments
| 0 |
2024-03-01T10:19:57Z
|
2024-03-01T10:25:08Z
|
https://github.com/Piwigo/Piwigo/issues/2122
| 2,163,078,113 | 2,122 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.