@kgroneman - I had a look at the case, we were referring to the form I mentioned previously. While technically still true that multiple discussion styles share the form I'm not sure we need to do anything with it to do what you've described - as long as you're OK with the component being above or below the editor form. In this case, you'd just need to create a custom page to override the PostPage, e.g. PostPage.ideas, and set it at the Node level admin of the idea exchange you'd like to change. This is an example of what I mean from my test environment: For reference, the documentation on this lives here: https://community.khoros.com/t5/Pages-and-layouts/Override-a-default-page/ta-p/108961 Please let me know if that helps or if you have any questions. ... View more

No problem, glad that worked. I've got this scheduled to deploy during the maintenance window tomorrow evening. ... View more

@StanGromer - Can you please check your stage environment now? I've made an adjustment that will allow you to set a custom page to TkbArticleEditorPage. Note that my change will block Studio Publishing, but you can revert it in Studio -> Versions if you need to publish in the meantime. If the change looks good, I can deploy it or you can submit a support ticket asking for it to be deployed. I believe every page should be available by default so I'll look into getting it updated in a future release.  @kgroneman - I'm not 100% sure without seeing the exact request/ticket, but based on what you described it sounds like we (Support) were referring to the message editor form that lives on the PostPage, e.g.: <component id="editor"/> Our services team can add custom fields to the editor form, but since Forums/Ideas/Blogs share the same editor it would persist across discussion styles. You might be able to utilize the same method Stan is and create a custom PostPage in Studio and set it in the Node level admin for the discussion styles of your choosing. Any component that is added to the page would appear above or below the "editor" form, I'm not sure if that fits your desired use case. Hope this helps! ... View more

Hi @m4ttyb0y , I'm not aware of any changes that would cause a break like this off the top of my head, but there are a lot of reasons an error like this could occur. I haven't seen other reports of this behavior from other customers yet either. Have you submitted a case with our Support team yet? If you have, I wasn't able to locate it so it'd be great if you could send me the ticket number. If not, I would recommend doing that as a next step. It would be helpful to have an example of where you encountered the error on your community (along with a date/timestamp) and any specific steps you're taking to reproduce it so we can try on our side. Best, ... View more