https://bugzilla.wikimedia.org/show_bug.cgi?id=57760
--- Comment #42 from MWJames ---
See [1] for further instructions on how to avoid issues in LocalSettings when
using SMW-NS related configurations.
[1] https://bugzilla.wikimedia.org/show_bug.cgi?id=58182#c4
[2]
http://semantic-mediawiki.org/
https://bugzilla.wikimedia.org/show_bug.cgi?id=57760
MWJames changed:
What|Removed |Added
Blocks||58190
--
You are receiving this mail becaus
https://bugzilla.wikimedia.org/show_bug.cgi?id=57760
--- Comment #41 from MWJames ---
(In reply to comment #39)
> James, modification of things using the namespace consonants still needs to
> be
> delayed. I updated SMW wiki to SMW master just now, and things broke because
> localSettings was usi
https://bugzilla.wikimedia.org/show_bug.cgi?id=57760
--- Comment #40 from Jeroen De Dauw ---
I created a fresh bug for this, else this one will turn into "all things
related to Composer somehow".
https://bugzilla.wikimedia.org/show_bug.cgi?id=58182
--
You are receiving this mail because:
You ar
https://bugzilla.wikimedia.org/show_bug.cgi?id=57760
--- Comment #39 from Jeroen De Dauw ---
James, modification of things using the namespace consonants still needs to be
delayed. I updated SMW wiki to SMW master just now, and things broke because
localSettings was using these constants immediat
https://bugzilla.wikimedia.org/show_bug.cgi?id=57760
MWJames changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugzilla.wikimedia.org/show_bug.cgi?id=57760
--- Comment #38 from MWJames ---
[0] was merged and should resolve reaming issues due to the use of the Composer
install.
Further more, [0] introduces additional tests [1] to verify settings behaviour
for a Composer and non-Composer install.
https://bugzilla.wikimedia.org/show_bug.cgi?id=57760
--- Comment #37 from MWJames ---
(In reply to comment #36)
> > therefore is not recognised by SMW.
>
> Why not? This is still before any SMW logic uses the globals or initializes
> something with them no?
No, the LocalSettings function { ...
https://bugzilla.wikimedia.org/show_bug.cgi?id=57760
--- Comment #36 from Jeroen De Dauw ---
> any behavioral change in LocalSettings that is put into a
> function() { ... } is executed after SMW\setup is run
Yeah, that is the expected behaviour.
> therefore is not recognised by SMW.
Why not?
https://bugzilla.wikimedia.org/show_bug.cgi?id=57760
--- Comment #35 from MWJames ---
Right now I'm unable to provide a false/positive test on Travis-CI
(testExtraNamespacesOnTravisNamespace [1]) because I can't get Travis to behave
as it is does locally but with the above change and the proposed
https://bugzilla.wikimedia.org/show_bug.cgi?id=57760
--- Comment #34 from Jeroen De Dauw ---
Merged my PR into the one adding the extra test. Think the issue has now been
resolved.
https://github.com/SemanticMediaWiki/SemanticMediaWiki/pull/39
--
You are receiving this mail because:
You are on
https://bugzilla.wikimedia.org/show_bug.cgi?id=57760
--- Comment #33 from Jeroen De Dauw ---
The PR now also includes a fix for smwgScriptPath.
--
You are receiving this mail because:
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wik
https://bugzilla.wikimedia.org/show_bug.cgi?id=57760
--- Comment #32 from Jeroen De Dauw ---
For $smwgNamespaceIndex I just submitted a commit that fixes the behaviour at
the cost of smwgNamespacesWithSemanticLinks compatibility.
https://github.com/SemanticMediaWiki/SemanticMediaWiki/pull/40
--
https://bugzilla.wikimedia.org/show_bug.cgi?id=57760
--- Comment #31 from Jeroen De Dauw ---
Ok, the $smwgNamespaceIndex stuff cannot be fixed easily. Looks like we will
need to break compatibility is some way.
$smwgNamespacesWithSemanticLinks is initialized in the settings file, and is
expected
https://bugzilla.wikimedia.org/show_bug.cgi?id=57760
--- Comment #30 from Jeroen De Dauw ---
James: [1] is not needed, and in fact not supported as far as I'm concerned.
The user should not have to care where which entry point is and for which
components they should be included. Perhaps we should
https://bugzilla.wikimedia.org/show_bug.cgi?id=57760
--- Comment #29 from MWJames ---
(In reply to comment #24)
> Ok, great analysis. Just checked the code in WebStart.php, and indeed, LS is
> getting loaded after the Composer autoloader. This means we cannot use config
> yet at the time of entry
https://bugzilla.wikimedia.org/show_bug.cgi?id=57760
--- Comment #28 from James Montalvo ---
Workaround for SMW for now if you're having problems due to non-default
$wgScriptPath is to explicitly set $smwgScriptPath in LocalSettings.php. So I
added the following prior to loading any extensions in
https://bugzilla.wikimedia.org/show_bug.cgi?id=57760
--- Comment #27 from Niklas Laxström ---
Sorry, didn't notice you already have a bug for this.
I'm kind of stuck at translatewiki.net on this issue, as I cannot update some
extensions because they now require composer, but installing them from
https://bugzilla.wikimedia.org/show_bug.cgi?id=57760
MWJames changed:
What|Removed |Added
Summary|Settings settings / |SMW Settings /
|Composer i
19 matches
Mail list logo
