このコンポーネントは PDF をレンダリングするためにネイティブのブラウザ実装を使用するため、ブラウザによって表示結果が異なります。
また、Discourse ではデフォルトで PDF のアップロードが許可されていません。ユーザーに PDF ファイルのアップロードを許可したい場合は、すべてのユーザーが PDF をアップロードできるようにするには authorized_extensions に、スタッフメンバーに限定するには authorized_extensions_for_staff にその拡張子を追加する必要があります。
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.
MacOS Big SurのSafariではまだ動作しません。ブログプラグインに特別な設定はなく、他のPDFはブラウザで表示されます。
theme-creatorでプレビューページを読み込む際、Safari Web Inspectorから以下のエラーが報告されています。 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.