Feature preview
The custom content model adds a new field, which only affects the field level, the text of the old articles will not be unreadable: the new field is empty in the existing documents, the template reads an empty value instead of reporting an error. The real problem is that the template treats empty values as required items, and when importing in bulk, the column names are not aligned with the new fields. Backup before changing, migrate in batches by category, and you can still go back if there is an error.
The custom content model has added a new field, the text of the old article will not be unreadable. The addition of the field affects the field level, not the text storage layer: the new field has no value on existing documents, the template reads the empty value, and the text itself is output as usual. What really makes people think it's unreadable is when this new field is written as a required item in the template, or when the column name is not aligned with the new field during batch import, leading to overwriting, as well as not conducting a thorough check after the field is modified and the entire site is released.
AnQiCMS's custom content model supports flexible content structures. The content model determines which custom fields an article can fill. The addition, renaming, and adjustment of filling requirements, as well as the scope of effect, are all defined by the field definition: whether the list page and detail page display, what input items appear in the background editing interface, and what columns are available for import and export. The main text is stored independently and will not be rewritten or truncated because of an additional field.
Please note the mandatory field setting of the field. Setting a new field as mandatory will only affect newly created and saved documents; existing documents will not be filled in forcibly, but will be required to be filled in the next time they are edited and saved, which may cause the illusion that 'old articles cannot be changed'.
The first type, the template only outputs the text, without looking at the new fields, the behavior does not change. The second type, the template refers to the new field, and the old document is empty in this field, the page outputs a blank position, the structure does not report an error but visually lacks content, this type of problem is most likely to appear in the subtitles of the list page and parameter bars. The third type, the field is renamed or deleted and then rebuilt, and the template refers to the old field name, the value cannot be obtained, and it looks like the content is lost.
The troubleshooting method is very direct: take an old article and view the rendering results with the template before and after the change, and compare the position of the blank to determine whether it is an empty value or the field name does not match.
First define the field and aperture, then move on to the content. It is recommended to: Build fields in the test station or draft status, write clear field usage and value range; choose a category as a pilot, fill in the new fields under the category, and confirm that the template displays normally; then proceed in batches by category. When the quantity is large, use batch import processing, AnQiCMS supports ZIP compressed packages and Excel spreadsheets as two entry methods, the column names of the import table must correspond to the new fields one by one, otherwise there will be a situation where it is filled in but cannot be read.
The unified modification of the old expression should be done through site-wide replacement, batch replacement of keywords or links, which is more labor-saving than manual editing article by article; the replacement range is recommended to be limited to the needed category to avoid mistakenly affecting the same name.
Make a backup before changing the field. Backup and restore cover data and static files, if the adjustment of field structure fails, you can roll back to the previous state. There is a second layer of margin for document-level mistakes: deleting formal documents is moved to the recycle bin instead of physical deletion, which can be restored; changes that are not wanted to be exposed prematurely should be placed in draft status, and those that need to be released at a certain pace should use pending release and scheduled release control, and mistakes will not be directly seen by customers.
Will adding a field trigger a full site regeneration?No, the change in field definition does not equal the change in text; only template changes affect rendering.
Can an empty value be given a default display?In the template, make conditional judgments on empty values, and display the agreed placeholder text if you cannot get it, which is clearer than leaving it blank.
Which trial classification should be selected?Select the category that is moderate in document quantity and the most typical in field usage, where the problem is most likely to be exposed.
Preview
After the manuscript was sent out, it was found that the wording was违规, the problem lies in placing all the compliance checks after publication. The sensitive word filter takes effect when written, content review takes effect before publication, keyword replacement and full-site replacement are used to batch change existing expressions. The three defenses are each set at different steps, in conjunction with the status transition of draft, to be published, recycling station, to ensure that illegal words do not go online, and if they do, they can also be taken back.
Preview
The static site generator itself does not come with an editing entry, content modifications are made in the text files of the code repository, after modification, it must be regenerated and pushed to count as going live. Changes requiring engineering intervention are usually of three types: field structure adjustment, template modification, and batch replacement. A content management system with a backend incorporates these three steps into the interface, custom fields determine which level of editing can be modified, visual template editing and batch import reduce dependency on code, and a draft preview can be used before publication.
Preview
The form without protection has more than 60% of submissions coming from robots, the order to prevent spam is to add hidden fields first and then consider the captcha: hidden fields do not disturb real people, can block a large number of basic robots filling out templates, but cannot block manual replacement services; the captcha improves the interception limit but also increases the probability of real people being mistakenly rejected. Decide whether to add a second layer based on the number of complaints and the ratio of escapees.