Feature Proposal: The rename web operation to cope with a large site and read-only/mirror webs
not to search all webs if NoInAllPublicWebs is set
Motivation
When you move a web, unlike when you move a topic, you are not asked whether or not to search all public webs.
On a large site having thousands of webs, that surely times out.
The operation tries to modify topics on read-only or slave webs (c.f.
ReadOnlyAndMirrorWebs), which may lead to an error.
Description and Documentation
If
{NoInAllPublicWebs}
configuration parameter (c.f.
NoInAllPublicWebsOption) is true, when the
rename
script moves a web, topics of the other webs are not scanned for link remediation.
Regardless of
{NoInAllPublicWebs}
, when a web is moved, backlinks and on read-only and slave webs are not scanned and fixed.
Examples
Impact
Implementation
--
Contributors: HideyoImazu - 2012-11-08
Discussion
I think we discussed this elsewhere. Looks OK.
--
PeterThoeny - 2012-11-14
BTW, I almost missed this feature proposal and
RenameTopicWithNoWebPrefix because the
ProposedFor target release field was not set. If not set it will not show in the Jerusalem feature list in
TWikiFeatureProposals.
--
PeterThoeny - 2012-11-14
Renamed this topic because the topic name was very long.
--
HideyoImazu - 2012-11-15
Read-only and slave web support is added.
--
HideyoImazu - 2012-12-25