Como se mencionó anteriormente, este componente solo funcionará en escritorio. Hay muy poco beneficio en mostrar las vistas previas en dispositivos móviles, ya que todo será tan pequeño y muy difícil de leer.
Este componente utiliza la implementación nativa del navegador para renderizar los PDF, por lo que los resultados se verán diferentes en distintos navegadores.
Además, tenga en cuenta que las cargas de PDF no están permitidas de forma predeterminada en Discourse. Si desea permitir que sus usuarios carguen archivos PDF, deberá agregar esa extensión a authorized_extensions si desea que todos sus usuarios puedan cargar PDF, o a authorized_extensions_for_staff si desea limitar eso a los miembros del personal.
Access to fetch at 'https://travelmassive-discourse-cdn.s3.dualstack.us-west-1.amazonaws.com/original/2X/b/b578f6364592121964e6a2fd4969e5c1222bd909.pdf' (redirected from 'https://lounge.travelmassive.com/uploads/short-url/pTnA3r043WfhDK8HSdPQrtNn8Lf.pdf') from origin 'https://lounge.travelmassive.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
Update
I was able to fix this by adding the following CORS policy in my S3 bucket configuration.
It’s necessary to add, that if you see this text in the error message from origin 'https://lounge.travelmassive.com' has been where your domain is without slash / at the end, then in the CORS configuration you should also add your domain without slash at the end like this: https://mydiscourse.url
I noticed that your uploads are on AWS so, the issue is probably CORS related (the component is not active on your site for me to confirm). See the post below yours.
thanks for sharing that!
Please note that this issue will only affect self-hosters that have set up something like S3. Self-hosters that are not using S3 will not run into this issue. Customers hosted by CDCK will also not need to worry about that since they already have that set up.
That said, CORS configuration is a bit outside of the scope of this topic. If your uploads bucket does not allow your own domain access, then that needs to be fixed regardless since there might be some other issues caused by that.
I’m a little bit unsure what happened here. Both cases seem to be working for me everytime I try. We can just chalk it up to a transitory network issue but please let me know if you see it again
I pushed a tiny update to this component that should improve the loading perception, there’s now a theme-color based placeholder instead of the default browser Iframe styles. It only shows up while the file is loading so 99% of the time, you won’t even notice it.
Would it be possible to make PDF Preview suppressable by prepending a space before the upload link, like with oneboxing? Sometimes you want a list of documents and not previews. Sometimes you want a preview.
I’m on Safari on MacOS Catalina, and I don’t have anything disabling in-browser PDF display—for instance, http://www.orimi.com/pdf-test.pdf displays fine. But I’m still getting the “Blocked Plug-in” window/message when I view the preview in theme-creator.
Site-specific settings in Safari prefs aren’t any different than other websites.
Still not working for me on Safari in MacOS Big Sur. No special settings to blog plugins, and other PDFs display in the browser.
Safari Web Inspector has the following complaints when loading the preview page in theme-creator: Unrecognized Content-Security-Policy directive 'worker-src'. Refused to load blob:https://theme-creator.discourse.org/7b9b62c7-e782-4080-a521-04e3b06aa142 because it does not appear in the object-src directive of the Content Security Policy.
my links in the messages are in the form of domain/secure-media-uploads/original/...
but in the console/network I can see that the actual downloads come from the bucket
Do you see the amz credential ?
if not maybe this coud help ?
I also remember that something weird was happening when I tried to move a post from categories (or was it a copy/paste?) it finally worked when I re-uploaded the file.
So I’m stumped - especially as to why it works in two forums I run and not the other - S3 being the only difference. And that you have it working with S3. I’m really confused.
It may be a conflict with another component or theme. It’s working as expected for me. Start by disabling other components and try using the default theme if yours is different. Same with plugins.
Ok - I’ve made progress. Disabling S3 uploads fixes it for new uploads. But I’m left with a S3 / local mess if I go down that road!
If could be that I am not using the CDN thingo (CloudFront) which throws up the annoying errors on the admin page. I’ll have a crack setting that up and see if that works.
Estoy buscando un plugin que permita abrir el PDF en una nueva pestaña.
El comportamiento actual de mi Discourse es permitir solo la descarga.
¿Sería posible lograrlo con un tema similar?
Si utiliza S3, es posible que también necesite actualizar su política CORS. Consulte la publicación a continuación: Inline PDF Previews - #106 by JammyDodger
¿Alojado por nosotros? Los componentes de tema están disponibles para usar en nuestros planes Estándar, Empresarial y Corporativo.
