Foswiki on GitHub is open for business! Next release meeting: Monday Dec. 1, 1300Z

Item8669: Move MAINWEB definition to Site Prefs so people can disable the compatibility plugin

Priority: CurrentState: AppliesTo: Component: WaitingFor:
Urgent Closed Engine   Main.KennethLavrsen
Just upgraded a client's wiki to 1o9 and their content broke as %MAINWEB% doesn't expand anymore. Did we mention it on the release notes or somewhere which deprecate features were finially removed in 1o9?

A quick workaround was to define MAINWEB in the SitePreferences.

-- MichaelDaum - 05 Mar 2010

quick test:
  • MAINWEB == Main

and I can't see any definition of MAINWEB in DefaultPreferences or SitePreferences

I wonder what is up with this.

-- SvenDowideit - 05 Mar 2010

LocalSite.cfg?

-- PaulHarvey - 05 Mar 2010

wbniv@wbniv-laptop:~/foswiki/Release01x00/TWikiCompatibilityPlugin$ grep -R MAINWEB . | grep -v '.svn'
./lib/Foswiki/Plugins/TWikiCompatibilityPlugin.pm:    #Map TWIKIWEB to SYSTEMWEB and MAINWEB to USERSWEB
./lib/Foswiki/Plugins/TWikiCompatibilityPlugin.pm:    Foswiki::Func::setPreferencesValue('MAINWEB', '%USERSWEB%');
./data/System/TWikiCompatibilityPlugin.txt:Map TWIKIWEB to SYSTEMWEB and MAINWEB to USERSWEB - no Preference settings required.
./TWikiCompatibilityPlugin.txt:Map TWIKIWEB to SYSTEMWEB and MAINWEB to USERSWEB - no Preference settings required.

-- WillNorris - 06 Mar 2010

I don't use anything TWikixxxPlugin anymore and I think MAINWEB should not be implemented in TWikiCompatibilityPlugin.

-- MichaelDaum - 06 Mar 2010

i'd have to agree - it seems an odd thing for us to have done.

-- SvenDowideit - 07 Mar 2010

Foswiki is maturing.

A year ago we all were upgrading and we were all running with TWikiCompatibilityPlugin enabled. And this also translated MAINWEB and TWIKIWEB.

Now a year later more and more of us have the plugins we need in Foswiki name space and TCP becomes something we disable. However these MAINWEB tags are still everywhere in our old webs.

So maybe it is the right time to move the definition from TCP to System.DefaultPreferences starting from 1.1.

Maybe even from 1.0.10 (if we release such a thing). And then remove it from TCP so we do not define it two places.

This is what I suggest we do. And this is what I have done in my own production sites. I disabled TCP and defined these two macros in Site Prefs.

I will take this action. It is a bit below the bar for a feature proposal. I will check it in and revert if someone disagrees. It is few lines and easy to revert.

-- KennethLavrsen - 07 Mar 2010

sold. to the man in the green t-shirt.

-- SvenDowideit - 07 Mar 2010

I have done it in trunk only.

There is no reason to also do this in 1.0.10. It is good to do these steps in minor/major releases.

-- KennethLavrsen - 24 Mar 2010
 

ItemTemplate edit

Summary Move MAINWEB definition to Site Prefs so people can disable the compatibility plugin
ReportedBy MichaelDaum
Codebase trunk
SVN Range
AppliesTo Engine
Component
Priority Urgent
CurrentState Closed
WaitingFor KennethLavrsen
Checkins distro:6f6e61b5f703 distro:514da7e46f21
TargetRelease minor
ReleasedIn 1.1.0
Topic revision: r13 - 04 Oct 2010, KennethLavrsen
 
The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. see CopyrightStatement. Creative Commons License