Merge pull request #664 from humanmade/backport-661-to-v24-branch

mikelittle · web-flow · commit 65c330ecb8db · 2025-09-19T10:37:56.000+01:00
[Backport v24-branch] Fix broken links and formatting.
diff --git a/other-docs/faq/Account/README.md b/other-docs/faq/Account/README.md
@@ -1 +1,3 @@
 # Account FAQs
+
+Awaiting content
diff --git a/other-docs/faq/Account/data-storage-locality.md b/other-docs/faq/Account/data-storage-locality.md
@@ -2,8 +2,12 @@
 
 Your data is distributed among our technology stack. You can find information about the locality of each service as follows.
 
-You can find information about [Database Servers (MySQL)](https://docs.altis-dxp.com/cloud/database/) for content, [S3 Storage](https://docs.altis-dxp.com/cloud/s3-storage/) for assets, and [Backups](https://docs.altis-dxp.com/cloud/backups/) in the documentation.
+You can find information about [Database Servers (MySQL)](docs://cloud/database/) for
+content, [S3 Storage](docs://cloud/s3-storage/) for assets, and [Backups](docs://cloud/backups/) in the documentation.
 
-Information about your [Origin Location](https://docs.altis-dxp.com/cloud/origin-locations/) can be found within the Altis Dashboard; at the top of each environment's details pages, you can find the Region you're located within. All customer data is stored within this region, and is stored in durable, persistent storage across multiple [availability zones](https://docs.altis-dxp.com/cloud/architecture/) (data centres).
+Information about your [Origin Location](docs://cloud/origin-locations/) can be found within the Altis Dashboard; at the top of
+each environment's details pages, you can find the Region you're located within. All customer data is stored within this region, and
+is stored in durable, persistent storage across multiple [availability zones](https://docs.altis-dxp.com/cloud/architecture/) (data
+centres).
 
 All your data is stored isolated from others, with fully dedicated infrastructure for each customer.
diff --git a/other-docs/faq/Common-Errors-and-Issues/README.md b/other-docs/faq/Common-Errors-and-Issues/README.md
@@ -1 +1,3 @@
 # Common Errors and Issues
+
+Awaiting content
diff --git a/other-docs/faq/Common-Errors-and-Issues/build-size.md b/other-docs/faq/Common-Errors-and-Issues/build-size.md
@@ -1,4 +1,4 @@
-# Can't deploy due to build size 
+# Can't deploy due to build size
 
 If your deployment is throwing an error and failing with the message:
 
@@ -13,18 +13,20 @@ You can look at the following areas to reduce build size:
 
 - Add `--prefer-dist` to the composer install command
 - If you are building JS / CSS assets with tools installed via npm or yarn ensure you're removing `node_modules` afterwards.
-- Once the above is done, ensure you clear the build cache in the Altis Dashboard before re-trying the deployment (contact support to clear the build cache)
+- Once the above is done, ensure you clear the build cache in the Altis Dashboard before re-trying the deployment (contact support
+  to clear the build cache)
 
+In some cases, a large file may have been committed to your repository and is being deploy; so check your code repository for large
+files.
 
-In some cases, a large file may have been committed to your repository and is being deploy; so check your code repository for large files.
-
-It can also be the case that your Node modules directory has inflated the build size. These help with build speed, but are not required to be deployed onto your environments and can be safely trimmed as part of your build-script.
+It can also be the case that your Node modules directory has inflated the build size. These help with build speed, but are not
+required to be deployed onto your environments and can be safely trimmed as part of your build-script.
 
 To remove your Node modules directory via your build-script, you can add something like:
 
-```
+```bash
 # Clean up node_modules to reduce the size of the build
 find . -name 'node_modules' -type d -prune -exec rm -rf '{}' +
 ```
 
-You can read more about build script limitations in this article: https://docs.altis-dxp.com/cloud/build-scripts/#limits
+You can read more about build script limitations in [this article](docs://cloud/build-scripts/#limits). 
diff --git a/other-docs/faq/Common-Errors-and-Issues/cant-deploy.md b/other-docs/faq/Common-Errors-and-Issues/cant-deploy.md
@@ -1,7 +1,9 @@
-#  I click deploy, but nothing is happening 
+# I click deploy, but nothing is happening
 
-If you're trying to initiate a deployment, but clicking deploy in the Altis Dashboard is not initiating a deploy, the deploy locks are still engaged.
+If you're trying to initiate a deployment, but clicking deploy in the Altis Dashboard is not initiating a deploy, the deploy locks
+are still engaged.
 
-First ensure another deployment wasn't initiated by another member of the team, or by the Altis Cloud auto-deploy bot. If no other deploy is in-progress, it's possible the deploy locks are stuck.
+First ensure another deployment wasn't initiated by another member of the team, or by the Altis Cloud auto-deploy bot. If no other
+deploy is in-progress, it's possible the deploy locks are stuck.
 
-[Contact us](https://dashboard.altis-dxp.com/support/) so we can manually release deploy locks for you.
+[Contact us](support://new) so we can manually release deploy locks for you.
diff --git a/other-docs/faq/Common-Errors-and-Issues/image-parsing-errors.md b/other-docs/faq/Common-Errors-and-Issues/image-parsing-errors.md
@@ -1,2 +1,3 @@
 # Image parsing errors
 
+Awaiting content
diff --git a/other-docs/faq/Common-Errors-and-Issues/index-occurring.md b/other-docs/faq/Common-Errors-and-Issues/index-occurring.md
@@ -1,6 +1,7 @@
-#  ElasticSearch Index: Error: An index is already occurring. Try again later. 
+# ElasticSearch Index: Error: An index is already occurring. Try again later.
 
-If you receive the error `ElasticSearch Index: Error: An index is already occurring. Try again later. ` when performing an ElasticSearch reindex, it's possible the indexing flag for an in-progress index has got stuck. The resulting error will occur:
+If you receive the error `ElasticSearch Index: Error: An index is already occurring. Try again later. ` when performing an
+ElasticSearch reindex, it's possible the indexing flag for an in-progress index has got stuck. The resulting error will occur:
 
 ```
 Error: An index is already occurring. Try again later.
@@ -12,18 +13,20 @@ In such a case, you can clear the flag by running the following:
 wp elasticpress clear-sync 
 ```
 
-Alternatively, if the above doesn't resolve the issue, it can also be stuck 
-in a [WordPress pransient](https://developer.wordpress.org/apis/transients/). If so, you can try the following:
+Alternatively, if the above doesn't resolve the issue, it can also be stuck
+in a [WordPress transient](https://developer.wordpress.org/apis/transients/). If so, you can try the following:
 
 ```
 wp transient delete ep_wpcli_sync --network
 ```
 
-Occasionally this value can also be stored in the object cache. Flushing the object cache should be performed with caution when working on live environments. 
-You can flush your object cache via a new CLI Session, see: https://docs.altis-dxp.com/cloud/dashboard/cli/ and run the following:
+Occasionally this value can also be stored in the object cache. Flushing the object cache should be performed with caution when
+working on live environments. You can flush your object cache via a [new CLI Session](docs://cloud/dashboard/cli/). Run the
+following:
 
-```
+```bash
 wp cache flush
 ```
 
-**Note that flushing the object cache can have a significant impact on performance, so we recommend you only do this when necessary.** 
+**Note that flushing the object cache can have a significant impact on performance, so we recommend you only do this when necessary.
+** 
diff --git a/other-docs/faq/Common-Errors-and-Issues/integrity-check.md b/other-docs/faq/Common-Errors-and-Issues/integrity-check.md
@@ -35,15 +35,10 @@ Using timestamps for the versions should be OK, but it's possible that this may
 Altis. Because there are multiple servers serving your files, the timestamps for each file could mismatch; this shouldn't normally
 cause an issue.
 
-Our advice is to generate the version string within the build process:
-https://docs.altis-dxp.com/cloud/static-file-caching/
+Our advice is to [generate the version string within the build process](docs://cloud/static-file-caching/).
 
-Read more about integrity checking:
+Read more about integrity checking: with Altis [Subresource Integrity](docs://security/browser/#subresource-integrity) and on
+MDN: https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity
 
-https://docs.altis-dxp.com/security/browser/#subresource-integrity
+Further steps on [debugging](docs://guides/getting-help-with-altis/debugging/)
 
-https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity
-
-Further steps on debugging:
-
-https://docs.altis-dxp.com/guides/getting-help-with-altis/debugging/
diff --git a/other-docs/faq/Common-Errors-and-Issues/node-modules.md b/other-docs/faq/Common-Errors-and-Issues/node-modules.md
@@ -1,7 +1,10 @@
-#  Node modules not updated after deployment
+# Node modules not updated after deployment
 
-Node modules are cached on the build server for faster deployments. It can be the case that your updates to Node modules, or Node versions themselves are not updated after a deployment.
+Node modules are cached on the build server for faster deployments. It can be the case that your updates to Node modules, or Node
+versions themselves are not updated after a deployment.
 
-In this case, you must clear your build cache and redeploy. 
+In this case, you must clear your build cache and redeploy.
 
-To do this, goto the Altis Dashboard release tab, click "advanced" on the deploy menu, and select 'Clear Build Cache'; Then Select "Force Rebuild". This will now rebuild your deployment package, and ensure the proper Node version and Node modules are pulled in as per your build script.
+To do this, goto the Altis Dashboard release tab, click "advanced" on the deploy menu, and select 'Clear Build Cache'; Then Select "
+Force Rebuild". This will now rebuild your deployment package, and ensure the proper Node version and Node modules are pulled in as
+per your build script.
diff --git a/other-docs/faq/Common-Errors-and-Issues/ssl-certificate-common-name.md b/other-docs/faq/Common-Errors-and-Issues/ssl-certificate-common-name.md
@@ -1,3 +1,5 @@
-# My Altis SSL Certificate Common Name uses my Altis domain, and not my main site domain? 
+# My Altis SSL Certificate Common Name uses my Altis domain, and not my main site domain?
 
-This is the standard configuration for Altis. The CN uses the "primary" domain name, which is one controlled by Altis; when domains are added or removed via the Altis Dashboard's domains feature, we then add or remove them from the SAN list and replace the certificates. This should have no impact on your environment's or SEO, as support for SANs is widespread.
+This is the standard configuration for Altis. The CDN uses the "primary" domain name, which is one controlled by Altis; when domains
+are added or removed via the Altis Dashboard's domains feature, we then add or remove them from the SAN list and replace the
+certificates. This should have no impact on your environment's or SEO, as support for SANs is widespread.
diff --git a/other-docs/faq/Common-Errors-and-Issues/stuck-cavalcade.md b/other-docs/faq/Common-Errors-and-Issues/stuck-cavalcade.md
@@ -1,17 +1,25 @@
-#  Cavalcade jobs or stuck, or not running. 
+# Cavalcade jobs or stuck, or not running.
 
-If you've found your Cron/Cavalcade (we use these terms interchangeably) jobs have stopped running, it's likely the job as crashed, and is stuck in a 'running' state in the `wp_cavalcade_jobs` table.
+If you've found your Cron/Cavalcade (we use these terms interchangeably) jobs have stopped running, it's likely the job as crashed,
+and is stuck in a 'running' state in the `wp_cavalcade_jobs` table.
 
 You will need to manually update the status of the job to 'Failed'. This can be done via the Altis CLI.
 
-Once a job has been marked as failed, your code will need to reschedule the job. Typically, this is done by calling wp_schedule_event() conditionally based on wp_next_scheduled().
+Once a job has been marked as failed, your code will need to reschedule the job. Typically, this is done by calling
+wp_schedule_event() conditionally based on wp_next_scheduled().
 
 ## Why does this happen?
 
-Situations where Cavalcade jobs get stuck are challenging to debug. Most commonly, it can occur when the Cavalcade Runner is unable to shut down the job correctly. Unfortunately, these cases are very hard to catch and debug, and while we've eliminated most places where this can occur it does appear to still happen.
+Situations where Cavalcade jobs get stuck are challenging to debug. Most commonly, it can occur when the Cavalcade Runner is unable
+to shut down the job correctly. Unfortunately, these cases are very hard to catch and debug, and while we've eliminated most places
+where this can occur it does appear to still happen.
 
-Usually this happens if the Cavalcade container the job was running in gets killed for over memory consumption, or the container gets scaled in (terminated) by the system. In the latter case, jobs can only be guaranteed to run for 60 minutes. If your job run time exceeds 3,600 seconds, it's likely the container is culled, and the Cavalcade runner cannot shut down.
+Usually this happens if the Cavalcade container the job was running in gets killed for over memory consumption, or the container
+gets scaled in (terminated) by the system. In the latter case, jobs can only be guaranteed to run for 60 minutes. If your job run
+time exceeds 3,600 seconds, it's likely the container is culled, and the Cavalcade runner cannot shut down.
 
 ## Steps to resolve.
 
-If a job or group of jobs are failing consistently, contact Altis Support, and we can assist you isolate the problem. Please provide us with a written architectural overview of the job that is failing. It may be required to create a CLI command to execute the job functions, to help isolate and debug the issue.
+If a job or group of jobs are failing consistently, contact Altis Support, and we can assist you isolate the problem. Please provide
+us with a written architectural overview of the job that is failing. It may be required to create a CLI command to execute the job
+functions, to help isolate and debug the issue.
diff --git a/other-docs/faq/Common-Errors-and-Issues/uploading-files-fails.md b/other-docs/faq/Common-Errors-and-Issues/uploading-files-fails.md
@@ -1,15 +1,14 @@
-#  Uploading files displays 'cannot upload this file type' 
+# Uploading files displays 'cannot upload this file type'
 
-The default WordPress behaviour will only allow files of specified file-types to be uploaded. If a file is uploaded that is not in the list of permitted file types, WordPress will display the error 'Sorry, you are not allowed to upload this file type'.
+The default WordPress behaviour will only allow files of specified file-types to be uploaded. If a file is uploaded that is not in
+the list of permitted file types, WordPress will display the error 'Sorry, you are not allowed to upload this file type'.
 
 What is the default allowed list?
 
 `jpg jpeg png gif mov avi mpg 3gp 3g2 midi mid pdf doc ppt odt pptx docx pps ppsx xls xlsx key mp3 ogg flac m4a wav mp4 m4v webm ogv flv webp`
 
 Can this list be changed?
 
-WordPress allows you to add file types to the above list. To do this, go to
-the Network Admin of your site, then go to 'Settings'. Find the field for
-"Upload file types". Add the file types you wish to upload to the list. Once 
-you save the settings, you'll be able to freely upload files with the
-newly added file extension.
+WordPress allows you to add file types to the above list. To do this, go to the Network Admin of your site, then go to 'Settings'.
+Find the field for "Upload file types". Add the file types you wish to upload to the list. Once you save the settings, you'll be
+able to freely upload files with the newly added file extension.
diff --git a/other-docs/faq/Developing-on-Altis/CORS-s3.md b/other-docs/faq/Developing-on-Altis/CORS-s3.md
@@ -1,3 +1,4 @@
-#  Is it possible to set CORS headers on the S3 bucket? 
+# Is it possible to set CORS headers on the S3 bucket?
 
-No. Assets stored in S3 are served via the CDN (CloudFront). There is no mechanism to set custom headers at all when S3 objects are served via CloudFront.
+No. Assets stored in S3 are served via the CDN (CloudFront). There is no mechanism to set custom headers at all when S3 objects are
+served via CloudFront.
diff --git a/other-docs/faq/Developing-on-Altis/README.md b/other-docs/faq/Developing-on-Altis/README.md
@@ -1 +1,3 @@
 # Developing on Altis
+
+Awaiting content
diff --git a/other-docs/faq/Developing-on-Altis/cross-environment-uploads.md b/other-docs/faq/Developing-on-Altis/cross-environment-uploads.md
@@ -1,5 +1,8 @@
-#  Can I load Production or Non-Production upload assets directly in Local-server?
+# Can I load Production or Non-Production upload assets directly in Local-server?
 
 Yes, but isn't recommended.
 
-While developing an Altis project in Altis Local Server, you maybe tempted to load upload assets from Production or Non-Production Altis Environments directly. This would save time, as you won't have to download assets locally. However, doing so is not recommended for most project. While technically possible, this requires advanced knowledge on NGINX and may cause undesired effects for your local environment. 
+While developing an Altis project in Altis Local Server, you maybe tempted to load upload assets from Production or Non-Production
+Altis Environments directly. This would save time, as you won't have to download assets locally. However, doing so is not
+recommended for most project. While technically possible, this requires advanced knowledge on NGINX and may cause undesired effects
+for your local environment. 
diff --git a/other-docs/faq/Developing-on-Altis/custom-php-extensions.md b/other-docs/faq/Developing-on-Altis/custom-php-extensions.md
@@ -1,5 +1,7 @@
 # I want to implement a feature that requires a PHP Extension, can I install it?
 
-No. It's not possible to customise the PHP extension configuration. 
+No. It's not possible to customise the PHP extension configuration.
 
-We are not accepting requests for PHP Extensions, however, let us know that you're interested in a specific PHP extension. Tell us about your requirements and how you may use the extension. To request a feature, head on over to our roadmap, and submit your ideas - https://dashboard.altis-dxp.com/roadmap   
+We are not accepting requests for PHP Extensions, however, let us know that you're interested in a specific PHP extension. Tell us
+about your requirements and how you may use the extension. To request a feature, head on over to our roadmap, and submit your
+ideas - https://dashboard.altis-dxp.com/roadmap   
diff --git a/other-docs/faq/Developing-on-Altis/download-logs.md b/other-docs/faq/Developing-on-Altis/download-logs.md
@@ -1,7 +1,8 @@
-#  Can I download logs from the Altis Dashboard? 
+# Can I download logs from the Altis Dashboard?
 
-No. It's not possible to download logs from the Altis Dashboard. 
+No. It's not possible to download logs from the Altis Dashboard.
 
-If you need to download logs, or can't find what you're looking for, [contact us](https://docs.altis-dxp.com/guides/getting-help-with-altis/) and we can assist you.
+If you need to download logs, or can't find what you're looking
+for, [contact us](https://docs.altis-dxp.com/guides/getting-help-with-altis/) and we can assist you.
 
-See our article on logs and their retention periods: https://docs.altis-dxp.com/cloud/dashboard/logs/ before requesting logs.
+See our article on [logs and their retention periods](docs://cloud/dashboard/logs/) before requesting logs.
diff --git a/other-docs/faq/Developing-on-Altis/geo-based.restriction.md b/other-docs/faq/Developing-on-Altis/geo-based.restriction.md
@@ -1,5 +1,7 @@
-# Can I restrict access or content for specific countries? 
+# Can I restrict access or content for specific countries?
 
-Altis supports geolocation targeting by default. You can make use of the `Cloudfront-Viewer-Country` HTTP Header to serve content on a per-country basis.
+Altis supports geolocation targeting by default. You can make use of the `Cloudfront-Viewer-Country` HTTP Header to serve content on
+a per-country basis.
 
-More granular regional data is not available via Altis, but third-party geolocation systems may be able to achieve this result instead. See: https://docs.altis-dxp.com/cloud/geo-targeting
+More granular regional data is not available via Altis, but third-party geolocation systems may be able to achieve this result
+instead. See: [Geo targetting](docs://cloud/geo-targeting/)
diff --git a/other-docs/faq/Developing-on-Altis/importing-assets.md b/other-docs/faq/Developing-on-Altis/importing-assets.md
diff --git a/other-docs/faq/Developing-on-Altis/importing-database.md b/other-docs/faq/Developing-on-Altis/importing-database.md
diff --git a/other-docs/faq/Developing-on-Altis/move-bulk-uploads.md b/other-docs/faq/Developing-on-Altis/move-bulk-uploads.md
diff --git a/other-docs/faq/Developing-on-Altis/private-packages.md b/other-docs/faq/Developing-on-Altis/private-packages.md
diff --git a/other-docs/faq/Developing-on-Altis/using-altis-cli.md b/other-docs/faq/Developing-on-Altis/using-altis-cli.md
diff --git a/other-docs/faq/README.md b/other-docs/faq/README.md
diff --git a/other-docs/welcome.md b/other-docs/welcome.md

Original file line number	Diff line number	Diff line change
`@@ -1 +1,3 @@`
`1`	`1`	`# Account FAQs`
	`2`	`+`
	`3`	`+Awaiting content`
Original file line number	Diff line number	Diff line change
`@@ -1 +1,3 @@`
`1`	`1`	`# Common Errors and Issues`
	`2`	`+`
	`3`	`+Awaiting content`
Original file line number	Diff line number	Diff line change
`@@ -1,2 +1,3 @@`
`1`	`1`	`# Image parsing errors`
`2`	`2`
	`3`	`+Awaiting content`