enableSemantics no longer needed

It's now optional, see https://gerrit.wikimedia.org/r/#/c/44620/

Can you update the docs? :)

Jeroen De Dauw (talk)

Yep, thank you for the info. I will update as soon as SMW 1.9 is out. Hmm, that was the best part of it. No only just invoking SMW but also enabling semantics. It was like a tiny celebration during setup. I will miss it. ;)

[[kgh]] (talk)

You will still be able to call it. We can't get rid of it in the next 10000 years or so anyway, so no point in even deprecating it :)

Jeroen De Dauw (talk)

Cool. So I can continue to have my little semantic sensations during install. :D

[[kgh]] (talk)

You can always

function inizializeAllTheSemanticAwesome() {
    // include statement here
    // enable semantics here

    // more semantic includes here
}

inizializeAllTheSemanticAwesome();

Jeroen De Dauw (talk)

I just deployed this awesomeness.

[[kgh]] (talk)

Due to changes in how SMW is installed and initialized (now using Composer), enableSemantics() will still be used to ensure that NS related settings in LocalSettings still work the same as prior to SMW 1.9+Composer. For more information, see [1] and [2].

[1] https://bugzilla.wikimedia.org/show_bug.cgi?id=58182

[2] https://bugzilla.wikimedia.org/show_bug.cgi?id=57760

James Hong Kong (talk)

Pooh, things were indeed getting ugly here. :| I believe this should be included into the "INSTALL.md" before we embed this files content into this wiki. Thank you for keeping me in the loop on this!

[[kgh]] (talk)

James, can you please update the INSTALL.md file? You know best what the deal with the settings invocation is now.

Jeroen De Dauw (talk)

I believe that indeed nothing has really changed except that SMW does not have to be invoked as before and that the $smwgNamespaceIndex parameter has to be set prior to enabling semantics as Daniel stated.

[[kgh]] (talk)