We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
描述bug kukasawa主题时,页面内嵌入tweet,前端 post 显示错误。
期望的正常结果 使用其他主题,嵌入tweet的内容都显示正常。 升级到最新版本4.6.0问题依旧。
复现步骤 设置成kukasawa主题,100%复现
环境
补充说明
issue中发现别人发tweet卡片问题的时候,不用notion config设置皮肤,改成环境变量和blog.config.js设置就好了。 我也去试了一下,修改部署后,只有第一个帖子突然嵌入的tweet是正常的,后面再重新发布问题依旧。 所以这个主题应该还是有问题的。
The text was updated successfully, but these errors were encountered:
我刚刚尝试一下,是可以在fukasawa中嵌入twitter
你可以实现再更新到4.6.1版本,如果还存在问题,请留下访问网址,我需要在页面上调试一下
Sorry, something went wrong.
tangly1024
No branches or pull requests
描述bug
![WX20240625-122549@2x](https://private-user-images.githubusercontent.com/55296/342696032-8773ee86-56b6-4284-ad9c-cb243ca55e91.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjExMzQzMjIsIm5iZiI6MTcyMTEzNDAyMiwicGF0aCI6Ii81NTI5Ni8zNDI2OTYwMzItODc3M2VlODYtNTZiNi00Mjg0LWFkOWMtY2IyNDNjYTU1ZTkxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MTYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzE2VDEyNDcwMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWNiMzk5OGM3MWUzYjI4ZGM1NGM5NjFjZDNhNDJlYWY5NTNkYjI4MDRjNzAzN2M3MGE4ZGQxZmFjZTM5NTI0YjkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.6sztHJe8zWWkt81aKcv1yG0P7xBnM1MXiYwHFH95khI)
kukasawa主题时,页面内嵌入tweet,前端 post 显示错误。
期望的正常结果
使用其他主题,嵌入tweet的内容都显示正常。
升级到最新版本4.6.0问题依旧。
复现步骤
设置成kukasawa主题,100%复现
环境
补充说明
issue中发现别人发tweet卡片问题的时候,不用notion config设置皮肤,改成环境变量和blog.config.js设置就好了。
我也去试了一下,修改部署后,只有第一个帖子突然嵌入的tweet是正常的,后面再重新发布问题依旧。
所以这个主题应该还是有问题的。
The text was updated successfully, but these errors were encountered: