coreFORCE - FAQ: Can I upload a custom script file to my coreFORCE site?
If you are familiar with WordPress, you may assume that the only way to accomplish certain tasks, such as putting a file in the root of your web server, is to add a custom PHP file or upload a file via FTP to the web server.*
For security and performance reasons, coreFORCE do not allow any access to upload custom files to the web server. Most clients are on shared servers and so any files uploaded would affect all clients. Even for clients who are on dedicated servers, we still do not permit this for security reasons.
In virtually every case, the reasons for needing to upload a custom file can be more easily done in the coreFORCE backend.
Some common examples:
The robots.txt file already exists in coreFORCE and its contents are dynamically generated.
Sitemaps are automatically generated in coreFORCE based on the pages, taxonomy, and products in your site. You can show or hide products and taxonomy nodes (e.g. category or manufacturer pages) by marking them "cannot sell" or "inactive." The links to the sitemaps are included in the robots.txt file. Every site will have at least 2 sitemaps (one for pages and one or more for products). The first one can be viewed at /xmlsitemap.xml
Putting some text in a file in the root of your domain can be accomplished by creating a page record which will dynamically serve the requested content as a page record that is aliased to the name required. A common use case for this is the ads.txt file used by Google and other ad providers. Screenshots of how to create the ads.txt file are included below.
coreFORCE is a proprietary platform built entirely in-house. It is not based on any open source platform such as WordPress. Thus plugins built for WordPress are not compatible with coreFORCE in any way.
For security and performance reasons, coreFORCE do not allow any access to upload custom files to the web server. Most clients are on shared servers and so any files uploaded would affect all clients. Even for clients who are on dedicated servers, we still do not permit this for security reasons.
In virtually every case, the reasons for needing to upload a custom file can be more easily done in the coreFORCE backend.
Some common examples:
The robots.txt file already exists in coreFORCE and its contents are dynamically generated.
Sitemaps are automatically generated in coreFORCE based on the pages, taxonomy, and products in your site. You can show or hide products and taxonomy nodes (e.g. category or manufacturer pages) by marking them "cannot sell" or "inactive." The links to the sitemaps are included in the robots.txt file. Every site will have at least 2 sitemaps (one for pages and one or more for products). The first one can be viewed at /xmlsitemap.xml
Putting some text in a file in the root of your domain can be accomplished by creating a page record which will dynamically serve the requested content as a page record that is aliased to the name required. A common use case for this is the ads.txt file used by Google and other ad providers. Screenshots of how to create the ads.txt file are included below.
coreFORCE is a proprietary platform built entirely in-house. It is not based on any open source platform such as WordPress. Thus plugins built for WordPress are not compatible with coreFORCE in any way.
Updated on: 06/25/2024
Thank you!