Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid PDF structure when inside a folder containing a '#' #254

Closed
SystemKeeper opened this issue Oct 24, 2020 · 6 comments · Fixed by #384, #396 or #397
Closed

Invalid PDF structure when inside a folder containing a '#' #254

SystemKeeper opened this issue Oct 24, 2020 · 6 comments · Fixed by #384, #396 or #397

Comments

@SystemKeeper
Copy link

Steps to reproduce

  1. Create a folder starting with a # (hash/hastag) character (like # Publiziert)
  2. Upload / move pdf-file inside the newly created folder
  3. Try to open it with files_pdfviewer

Expected behaviour

PDF file is opened and displayed correctly

Actual behaviour

image

I remember seeing the same issue on a previous version (not sure if it was related to pdf viewer, just that there was a problem with filenames containing a #). Was unable to find it (could also been at the server repo, not sure). This was fixed a while ago.

Server configuration

Nextcloud version: 20.0.0

Client configuration

Browser: Chrome 85

Operating system: Win 10 1909

Logs

Browser log

image

@rgl1234

This comment has been minimized.

@skjnldsv
Copy link
Member

skjnldsv commented Nov 7, 2020

Duplicate of nextcloud/viewer#415

@skjnldsv skjnldsv marked this as a duplicate of nextcloud/viewer#415 Nov 7, 2020
@skjnldsv skjnldsv closed this as completed Nov 7, 2020
@beardhatcode
Copy link
Contributor

beardhatcode commented May 12, 2021

This issue still exists here while it has been fixed in nextcloud/viewer. The error is "file not found" and not invalid structure

@skjnldsv
Copy link
Member

@beardhatcode fixed as well? I assume it was also the double encoding?

@beardhatcode
Copy link
Contributor

beardhatcode commented May 26, 2021

This is fixed by #384 (in combination with the fix in viewer)

@beardhatcode
Copy link
Contributor

beardhatcode commented May 26, 2021

@SystemKeeper , the fix will likely land in Nextcloud 20.0.11 (I see you are running 20.0.0).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants