The contents of a Smallsite Design site can be archived, and from an archive, overwrite all the current content or import some elements.
Archives of the site are created periodically and during some operations, but are automatically deleted according to a calendar-based schedule.
Archives are a complete .zip file of all the content (not program) files in a site. They can be downloaded, uploaded, used to completely replace the content of a site (overwrite) or selectively import elements from.
Archives are created:
There is no difference between automatic and manual archive internally, but it is for reference when determining if an archive was generated during an operation on the Import page (manual) or routine logins (automatic).
Automatic archives are deleted to leave only the last in each of:
Each time period excludes that time already covered by later time periods, so Current month does not use archives from Current day or Previous day to determine its last archive. For example, if the current day is the 16th of the month, then Current month does not consider any archives after the end of the 14th.
Archive files have a name format of dt.sid.t.algo.hash.zip, where:
- a.dt: date and time saved as yyyy-mm-dd-hh-mm-ss using UTC as a time reference.
- b.sid: Site ID, as specified in the Values section of the Settings page.
- c.t: type of archive, where a is automatic and m is manual.
- d.algo: algorithm used to generate the hash .
- e.hash: hash of the file contents in hex characters.
- f.zip: extension for archive files.
While overwriting a site from an archive is straightforward, importing elements is dependent upon locales and ID conflicts.
The master locale of a site can only have its region changed, so unless the master locale in the archive to be imported from has the same master locale or only differs in region, it cannot be imported. If still eligible, for any other locale in the archive that cannot be renamed to match one in the site, any elements with text for that locale will have that text removed before importing. When expanded, the Files column of the archive's row in the Archive list will show what will happen to each locale.
|Masters match. ar-001 stripped. No de-de in imports||Yes|
|Master renamed to en-001. en-ca renamed to en-gg. No en conflicts as the masters evaluated first, then excluded from following comparisons||Yes|
|en-001*||en-ca renamed to en-001. en-001 stripped because masters already handled, so nothing to rename to||Yes|
|Masters match. en-us match. en-ca stripped. No conflict as exact matches evaluated next after masters, then excluded from following comparisons||Yes|
|Masters match. Conflict because two source locales could be renamed to match the non-master site locale||No|
|Masters match. Conflict because the non-master source locale could be renamed to either of the site ones||No|
In today's internet, people have been getting used to sites using the same language having different spellings and expressions, especially given the dominance of US English content over the early times of the internet. Typically now people will write how they are used to, and let readers accept the spelling and other differences.
Having two or more locales with the same language (and script) is usually to cater for audiences who really want to retain the different idioms and expressions they are used to, and that is why renaming regions is not really a solution. Yes, it may get around the technical issues of importing, but anything imported with renamed regions would have to be carefully checked that all content is consistent with the new locales.
Some elements in the archive might have IDs or internal references that are the same as elements in the site. The ID and Created columns of the Import list will show what their new values will be. Any elements to be imported that reference other imported elements with such changes will have those references updated as well.
Any elements that cannot be imported will need to be recreated in the site and the text individually copied from those elements.
The archive list shows the available archives and the operations that can be done on each.
|1||ID||Archive identifier as its date-time of creation. Currently for the site itself|
|2||Site||Site identifier as specified in the Site ID field of the Values section of the Settings page|
|3||Mode||Loaded for the current site|
Automatic if created at master manager login
Manual if actioned on this page
|4||Files||List of the numbers of all elements in the site or an archive, including any changes required to locales for import. Use to identify possible import issues|
|5||Actions||Actions available for the current site or an archive, followed by any errors that prevent importing|
|Archive||Create an archive of the current site|
|Upload||Upload an archive file to the site|
|Delete||Delete the archive|
|Overwrite||Import the whole archive to replace the current site|
|Import||Import part of the archive. Only shown if no errors that would prevent importation are found|
|Download||Download the archive from the site|
When an archive has been selected for import, a list of any changes to locales required during import are shown. Clicking the Deselect button in the navigation bar re-presents the Select import item drill-down list.
An item in the archive has to be selected.
Drill down to select the one item to be imported. 𝝙 indicates an element that will be renamed to prevent duplicates.
As a result of selection, the result or next action required, by item type, is:
Some descendants of the selected item can be excluded from the import.
Click on which items to exclude. Click again to re-include. Files listed under subsites, categories or articles are a link to their entry under Files, which can be clicked on to exclude them.
For a selected article or category, the new owner element must be selected.
For a selected article or category, the new host in the current site must be clicked on. Drill down to find it. After selection, another item can be selected from the archive for import.
All the items to be imported are listed, including any changes to prevent duplicate identifiers.
|1||Type||The type of item being imported|
|2||ID||Item identifier, if applicable. If to be renamed, the new ID is underneath|
|3||Created||Unique internal item identifier as its creation date. If to be changed, the new identifier is underneath|
|4||Comments||Text for files, else blank|