So Outside Technology Security CMS
AnQiCMS
Online Demonstration

How to see the default switch of a new site placed in a back-end system?

📅 2026-11-01 👁️ 0

How to verify the default switch of a newly created site when multiple sites are managed in one backend? It can be understood as 'the initial configuration layer inherited from the template by the new site': first confirm the default value of the site status is open access or temporarily closed, and then confirm whether this switch controls the entire site or a single module under the site. AnQiCMS's multi-site management supports managing multiple independent sites in one backend, often used in scenarios with multiple brands and themes. The switch seen when creating a new site determines whether the site is visible to the outside world, but does not determine whether the content has been written into the database.

The default value affects which batch of sites

The default value only affects sites created after this point. Existing sites will not be filled in. This is an easy misjudgment in the multi-site backend: changing the default status to off, the old sites will still be online; changing the default status to open, the sites manually closed in the old sites will not automatically go online. Check according to two lines, one is the default value at the template or configuration level, and the other is the actual status of the site instance.

To confirm which category you belong to, you can perform a small-scale verification: create a test site, do not manually change any switches, and directly check its external status, whether the back-end entry is accessible, and whether all modules under the site are enabled. The result obtained from the test site is the current default value of this back-end.

The three configurations to be checked when creating a new site

After creating a site, it is necessary to check three configurations, usually the access status, the binding of the access entry, and the basic content structure bound to the site. The order of the three should not be reversed: the access status determines whether the site is open to the outside, the entry binding determines where users come from, and the content structure determines whether this site can carry articles, pages, and categories.

In configuration sites (such as corporate websites, government portals, and marketing sites), the third place also includes language and site type. The configuration of multi-language sites and the site's own switch are two separate things: turning off the site does not affect the language configuration remaining on the template, and incomplete language configuration will not automatically turn off the site. Checking them separately can avoid the situation of 'thinking it has been turned on, but only half of the configuration has been done'.

What is the difference between closing a site and deleting a site?

The site is offline by closing it, the data still stays in the database and can be restored to external access by re-opening; deleting the site is a different process. In AnQiCMS, document deletion is handled by moving it to the recycle bin instead of physical deletion, the content in the recycle bin can be restored, which is also important for multiple sites: when shutting down a batch of sites in bulk, if the deletion is mistakenly treated as closing, the cost of rollback will significantly increase.

The safe approach is to separate three types of actions: first disable access, then keep them in the recycle bin for a while, and only do physical cleaning after confirming they are no longer needed. Make a full backup before performing any batch actions, including data and static files, so that if the site is mistakenly deleted, you can also recover static resources like images and attachments.

What is shared and isolated between multiple sites?

The shared is usually the program itself, the runtime environment, and some global settings; the isolated is the content data of the site, the site-level configuration items, and the access entry of the site. Understanding this boundary is essential to determine whether 'changing one place will affect all sites'. For example, configuring a pseudo-static rule or site map for a single site, the scope of effect is only in that site; while program upgrades, authentication methods, and such will affect all sites simultaneously.

When troubleshooting online issues, you can first narrow down the scope according to this boundary: if only a single site is abnormal, look for site-level configuration and content data; if all sites are abnormal at the same time, look for the program itself and the runtime environment.

The check order before going live

When launching a new site, a reusable order is to: first confirm the status of the site and access entry, then confirm whether the content structure and categories are set up, then confirm that the backup task covers this new site, and then perform a verification of external and backend access, after which the content can be released. This order puts the risk of 'turning off and then turning on' in front of the processing, to avoid finding out that the status is wrong after a large amount of content has been entered.

Common questions

Will the default closed new site have been indexed by the search engine?The site is inaccessible to the outside when it is closed, and crawling will fail; it is recommended to confirm the access entry and language configuration again before officially releasing to avoid large-scale jumps or blank pages after release.

Can you still find the content in the recycle bin after closing the site?Closing and deleting are two different processes. Closing means it is offline, and the content is still in the site's own data; only the content that has been deleted will enter the recycle bin, and the documents in the recycle bin can be restored.

A single backend manages multiple sites, do you need to back up them separately by site?The more stable approach is to back up the entire data and static files, and then select the range by site when restoring. Backing up only a single site is prone to missing cross-site shared configurations, and there may be a mismatch between configurations and content when restoring.

Related articles

How to queue for site upgrades when the security minor version is released on the same day and the major version is scheduled for December?

The short-cycle security minor version and the end-of-year major version should be queued in two channels: the security version enters the maintenance window on the same day, and the major version is first verified in the test environment for templates and data, and then灰度切量并可回退。This article provides the queuing rules, steps within the window, and observation indicators for the gray period for the two types of versions.

2026-11-01

Which item should be inspected first for backup and recovery before merging multiple sites into a batch of domain names?

Before merging multiple sites into a new domain batch, backup and recovery must be accepted first to ensure clean recovery: Confirm that the backup covers the database and static files, and then perform a real recovery drill in an isolated environment before discussing address switching, 301 redirects, and site map reconstruction.

2026-11-01

The security patches and system upgrades for the operating environment are due at the same time, which step should be done first?

When the environment security patch and the content system upgrade coincide with the same maintenance window, first patch the high-risk operating environment patches, and then schedule the content system upgrade, and first verify compatibility on the copy. This article explains the differences in nature of the two updates, the reasons for sorting, and the minimum operational steps and rollback preparation within the window.

2026-11-01

The contact form is flooded with spam submissions, should you add honey trap fields first or implement captcha verification first.

When a form is flooded with spam submissions, first add hidden honey pot fields, and then decide whether to implement CAPTCHA based on the remaining spam volume. Honey pots are effective against script submissions that do not parse styles and do not disturb real visitors; CAPTCHA has a cost, as it will block a portion of real users. In the statistics checked that day, robots accounted for forty-five percent of global network traffic, and more than half of the form submissions without protection were spam. The two layers should be implemented sequentially rather than simultaneously.

2026-11-01

After the translation of the multilingual site is completed, should the page address of each language be generated separately?

After the full-page translation of a multilingual site is completed, each language should have a stable and accessible independent page address, and a sitemap should be generated separately by language for easy verification. Language tags solve the problem of displaying the correct version of search and AI retrieval, but do not improve ranking. This article gives the verification sequence and common mistakes after going online.

2026-11-01

For articles sent at scheduled times, should the page cache be refreshed again?

Set the article for timed publishing to be released on time, and check whether the main content page, list and home page cache, and sitemap are in sync. Static generation and state transition are two steps, the cache of the list page is often behind the detail page, and the new address also needs to enter the sitemap and cooperate with link push, so that the timed publishing can truly be seen.

2026-11-01

How to import articles from the old station table once, if the fields do not match

The order of handling the mismatch of fields when importing the exported table of the old station to the new system is: first select the channel and then discuss mapping, the three columns of fixed title, alias, and category must be mapped, then determine the default value strategy for custom fields, and finally use title search to check if it already exists to avoid repeated imports and sample check the import results

2026-11-01

Can deleted articles be retrieved, and how are drafts, pending publication, and recycling stations divided?

Deleted articles can usually be retrieved: In the AnQiCMS backend, deleting formal documents is not a physical deletion, but moving them to the recycle bin, from which they can be restored. Each of the four document statuses has its own boundaries - formal documents are visible to the public, drafts are only in the background and preview links contain the preview tag, pending publication waits for the set time to take effect, and the recycle bin accommodates deleted content. This article explains the appropriate operations for each and the safe sequence for bulk cleaning.

2026-11-01