How about classic ui? Can you see such folder/files in classic ui ?Can you switch touch ui views (column, card , list) and see if the folder/files appear? If they do, repeat the exercise and see if you get any exception in browser console or error.logUsually this happens when the node structure has ...
Such a value as an href doesn't make sense to me but in the exception says that xss filter can't accept the value so you need to adjust the antisamy configurationSee (1) how can adjust the config per your requirementXSS Filter issue with the target attribute of the a tag
Yes you have to take over the datastore to the standby server and remove the sling id. In summary, below steps should give you an idea. These include the datastore configs :Use the below steps to setup cold standby instance and let me know incase of any issues.Setting up Primary instanceSetup a dire...
You would be able to use AEM as CMS as salesforce allows for rendering content from 3rd party vendors so the content would lay unde AEM (Assets, content) in the form of Content Fragments Models etc. which gives you the json for all the content and this can be consumed by Salesforce community offeri...
Creating a Custom LiveAction and setting a custom rollout config would makes sense as you can control for the livecopies you want/don't want to do this operation and have a bit of flexibility to mix/match things.
I don't think there is an available flag to migrate incremental versions in the version storage. But you can add a custom hook to the tool and make it incremental. See how you can add a custom hook (1). Jackrabbit Oak – Repository migration
OK then it comes to the question, before the inplace upgrade, did you run the version purge, workflow purge, offline compaction and datastore gc ? If there were GBs on indexes( for any reason) they wont be migrated to 6.3
One way to deal with this scenario would be to create a fresh instance running same aem version. Then use crx2oak tool to migrate the Page content using --include-paths=/content/geometrixx argument and the --copy-versions=true flag which would make a backup instance with all versions and pages.You c...
Although you can check why the size is different by checking the Disk usage report but I think there's an issue with indexing on your 6.3 instance post migration if AEM 6.3:- 94 GB AEM 6.0 is 10 GBCheck the jmx console and see index stats on the size of indexes. Also, Do a cycle of compaction and D...