As LemonSync operates asynchronously, it's possible for local changes to be sync'd before they're ready, or for the changes to pollute/occlude other items in the cache.
Cases:
Copying a page template isn't atomic, and may sync in various states
Copied template sync'd before header is updated, and header URL occludes another page template's URL (i.e., the same URL due to copying or other mistake). New page makes old page inaccessible until cache is cleared.
Page template name and/or filename may occlude files in cache or listing
Certain changes that affect template headers or filenames may result in similar issues
Once the files are corrected and synchronized, clearing the site cache fixes all issues observed.
There may be other side-effects in synchronizing partly-done copies. Ideally, LemonSync should not synchronize files in a few cases:
where file, key, or folder names collide
where headers are incomplete
Additionally, LemonSync should clear the entire cache in these special cases:
new file of any sort
changes to manifest or options
any full sync (e.g., replace upstream)
Metadata changes (manifest and options) may require a special reload beyond clearing the cache.
As LemonSync operates asynchronously, it's possible for local changes to be sync'd before they're ready, or for the changes to pollute/occlude other items in the cache.
Cases:
Once the files are corrected and synchronized, clearing the site cache fixes all issues observed.
There may be other side-effects in synchronizing partly-done copies. Ideally, LemonSync should not synchronize files in a few cases:
Additionally, LemonSync should clear the entire cache in these special cases:
Metadata changes (manifest and options) may require a special reload beyond clearing the cache.