Please log a ticket with Brightcove support. If they find anything wrong with core AEM functionality(Which I highly doubt), update here and we can further debug the issue.

You could try manually overlaying the StyleTextEditor.js file under /apps. More details at [1] [1] https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/configuring-rte-plugin-for-content-fragment-editor/qaq-p/230868 

Check if you have allowed the host making the POST call in the "Apache Sling Referrer Filter" If still an issue, check the log files on AEM side when you make a request from the dispatcher to see what's going on. Also, might be a good idea to change dispatcher log level to DEBUG and see if there are...

You can use this AEM page exporter[1] for this use case which exports AEM pages as a package [1] https://experienceleague.adobe.com/docs/experience-manager-65/administering/contentmanagement/page-exporter.html?lang=en#exporting-a-page 

When a inheritance is cancelled, AEM bascially updates the jcr:mixinTypes with cq:LiveSyncCancelled. Permissions for this cannot be managed OOTB unless you take the edit permissions which will cause users to not able to add any content to the pages as well. I believe you need to write custom code us...

Login to the publish instance with the admin user and check if the right version of content is available there. Most probably it is missing. Another issue can be dispatcher flush not getting triggered which causes the dispatcher to show the old content.

- Check if you get the same behavior when logging in as "admin"- Check if the token configuration is set too low. IT should be 12 hours by default[1]- If you are using a third-party login(SAML/LDAP), try using a local AEM account and see if you get the same issue. [1] https://helpx.adobe.com/ca/expe...

You can use rep:glob for this requirement.  See below for more details:  Example: If you set rep:glob="" then it will only apply the permissions to the current node and not on the child nodes. [1] https://jackrabbit.apache.org/oak/docs/security/authorization/restriction.html 

You can compare the oak version with the already upgraded instance to make sure if the instance is upgraded successfully. Other ways to check if the upgrade was triggered: - Instance should be started in the "UPGRADE" mode. You can check that from the upgrade.log file- Check the upgrade.log for "cod...

Please do not increase the traversal limit. That limit is there to protect against OOM issues which means increasing the limit will use more memory and in some case, cause outofmemoryStart by creating an index and you can use the oakutils[1] tool to generate the definition. If this is still an issue...