When calling pwg.images.setInfo with an image_id and a name parameter with value Bateau, the method sets the title as expected but it also replaces the original filename of the image with Bateau (seen on the web GUI and the mobile app). The call also returns a non JSON response leading to an error (checked with both JPEG and PNG formats).
If I add the file parameter with the value image.jpg to the above request, the method does the same, i.e. set the original filename to Bateau.jpg, but does not return a non JSON response (tested with both PNG and JPEG files). If the name value contains spaces, the original filename looses its extension.
When calling pwg.images.setInfo with an image_id and a file parameter with value e.g. image.jpg, the method sets the original filename even if the parameter single_value_mode is not provided with the replace value (as expected).
This is really annoying, in particular when the original filename lost its extension. The workaround is to call the method twice to change the title. Could this be fixed?
- When calling `pwg.images.setInfo` with an `image_id` and a `name` parameter with value `Bateau`, the method sets the title as expected but it also replaces the original filename of the image with `Bateau` (seen on the web GUI and the mobile app). The call also returns a non JSON response leading to an error (checked with both JPEG and PNG formats).
- If I add the `file` parameter with the value `image.jpg` to the above request, the method does the same, i.e. set the original filename to `Bateau.jpg`, but does not return a non JSON response (tested with both PNG and JPEG files). If the `name` value contains spaces, the original filename looses its extension.
- When calling `pwg.images.setInfo` with an `image_id` and a `file` parameter with value e.g. `image.jpg`, the method sets the original filename even if the parameter `single_value_mode` is not provided with the `replace` value (as expected).
This is really annoying, in particular when the original filename lost its extension. The workaround is to call the method twice to change the title. Could this be fixed?
<!-- github-sync-id:493969095 -->
When calling pwg.images.setInfo with an image_id and a name
parameter with value Bateau, the method sets the title as expected
but it also replaces the original filename of the image with Bateau
I can't reproduce that. I have tried with tools/ws.htm and it works as expected :-/
If I add the file parameter with the value image.jpg to the above
request, the method does the same, i.e. set the original filename to Bateau.jpg
Can't reproduce that either :-/ And no problem to set a "file" to "a file name with spaces.jpg".
When calling pwg.images.setInfo with an image_id and a file
parameter with value e.g. image.jpg, the method sets the original
filename even if the parameter single_value_mode is not provided
with the replace value (as expected).
I reproduce that. The update of the file property does not take the single_value_mode into account. It can be fixed.
Hi @EddyLB
> When calling `pwg.images.setInfo` with an `image_id` and a `name`
> parameter with value `Bateau`, the method sets the title as expected
> but it also replaces the original filename of the image with `Bateau`
I can't reproduce that. I have tried with `tools/ws.htm` and it works as expected :-/
> If I add the `file` parameter with the value `image.jpg` to the above
> request, the method does the same, i.e. set the original filename to
> `Bateau.jpg`
Can't reproduce that either :-/ And no problem to set a "file" to "a file name with spaces.jpg".
> When calling `pwg.images.setInfo` with an `image_id` and a `file`
> parameter with value e.g. `image.jpg`, the method sets the original
> filename even if the parameter `single_value_mode` is not provided
> with the `replace` value (as expected).
I reproduce that. The update of the `file` property does not take the `single_value_mode` into account. It can be fixed.
<!-- github-comment-id:533598794 -->
Thanks for your reply. I did not know I could use tools/ws.htm which simplifies life a lot (was typing URLs directly). That means that I must now investigate the library I use to prepare the JSON block sent to the server. First time I encounter such a problem with it :=(
Thanks for your reply. I did not know I could use tools/ws.htm which simplifies life a lot (was typing URLs directly). That means that I must now investigate the library I use to prepare the JSON block sent to the server. First time I encounter such a problem with it :=(
<!-- github-comment-id:533628456 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
pwg.images.setInfowith animage_idand anameparameter with valueBateau, the method sets the title as expected but it also replaces the original filename of the image withBateau(seen on the web GUI and the mobile app). The call also returns a non JSON response leading to an error (checked with both JPEG and PNG formats).fileparameter with the valueimage.jpgto the above request, the method does the same, i.e. set the original filename toBateau.jpg, but does not return a non JSON response (tested with both PNG and JPEG files). If thenamevalue contains spaces, the original filename looses its extension.pwg.images.setInfowith animage_idand afileparameter with value e.g.image.jpg, the method sets the original filename even if the parametersingle_value_modeis not provided with thereplacevalue (as expected).This is really annoying, in particular when the original filename lost its extension. The workaround is to call the method twice to change the title. Could this be fixed?
Hi @EddyLB
I can't reproduce that. I have tried with
tools/ws.htmand it works as expected :-/Can't reproduce that either :-/ And no problem to set a "file" to "a file name with spaces.jpg".
I reproduce that. The update of the
fileproperty does not take thesingle_value_modeinto account. It can be fixed.Thanks for your reply. I did not know I could use tools/ws.htm which simplifies life a lot (was typing URLs directly). That means that I must now investigate the library I use to prepare the JSON block sent to the server. First time I encounter such a problem with it :=(
Solved. The problem was caused by the Autocorrect Filename plugin. Once deactivated, no more issue ;-)