Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
AlessandroTax Posted February 17, 2022 Posted February 17, 2022 Basically, if I write a content using the Pages app, the Preview button doesn't works, neither in Desktop, Tablet or Mobile Preview. On the other end, if I write content using Blogs, the Preview works. Ideas?
Jim M Posted February 17, 2022 Posted February 17, 2022 Are you writing content in Pages in the ACP or on the front-end? Is this with specific content or any content?
AlessandroTax Posted February 17, 2022 Author Posted February 17, 2022 I am writing in the ACP, it happens with all contents. Now I tryed to do it from the front-end (I never do this) and discovered that something is not working right... like I am missing the space to write the content or the title. If I try to write a content in another Database, everything looks good. Maybe it's something related to my templates?
Jim M Posted February 17, 2022 Posted February 17, 2022 Testing this myself I can confirm that there is a bug with the editor in the ACP with Pages. Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release. Regarding the screenshot you posted, I would check the fields available to your member group and ensure you have a body available. Of course, if you modified your templates, temporarily changing those to unmodified version too would be advised.
AlessandroTax Posted February 17, 2022 Author Posted February 17, 2022 2 minutes ago, Jim M said: Testing this myself I can confirm that there is a bug with the editor in the ACP with Pages. Thank you for bringing this issue to our attention! Woa! So good so far, I'll wait this fix as soon as possible, the Preview feature is so useful. 15 minutes ago, Jim M said: I would check the fields available It seems you solved this. Jim M 1
Marc Posted July 11, 2022 Posted July 11, 2022 This issue has been resolved in 4.7.0 which has recently been released. Please upgrade to that version to resolve this, and of course, let us know if you are still seeing any issues.
Recommended Posts