VersionControl:PRs/pickipedia/167: Difference between revisions
From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Jump to navigationJump to search
cryptograss/pickipedia#167, as GitHub has it |
cryptograss/pickipedia#167, as GitHub has it |
||
| Line 16: | Line 16: | ||
|deploy= | |deploy= | ||
}} | }} | ||
<pre class="pr-body">One line in LocalSettings.php: `$smwgNamespacesWithSemanticLinks[NS_EMERGENT] = true;`. | |||
Why: Justin asked for the emergents' journal entries listed with their titles ([[Cryptograss:Emergents/Journals]]). Today the Emergent namespace isn't semantic, so nothing on an entry can be queried and the titled list is kept by hand. With this, a small `{{Journal entry|block=|title=}}` on each entry (to follow, on the wiki) sets two properties and the Journals page becomes an `#ask` that never goes stale. | |||
After the build reaches the wiki: `rebuildData` isn't needed for new annotations; existing entries get their properties when they're next saved (I'll do the five). | |||
Redeploy: the usual wiki build (Jenkins, then the rsync cron). No server to redeploy.</pre> | |||
Latest revision as of 18:06, 9 November 2026
| State | 🟣 merged 2026-10-29 13:49:29 |
|---|---|
| Worked on by | not said |
| Moods | not said |
| Deploy | not said |
| Branch | emergent-semantic → production, by magent-cryptograss
|
| Opened · last pushed | 2026-10-29 13:32:33 · 2026-10-29 13:32:29 |
One line in LocalSettings.php: `$smwgNamespacesWithSemanticLinks[NS_EMERGENT] = true;`.
Why: Justin asked for the emergents' journal entries listed with their titles ([[Cryptograss:Emergents/Journals]]). Today the Emergent namespace isn't semantic, so nothing on an entry can be queried and the titled list is kept by hand. With this, a small `{{Journal entry|block=|title=}}` on each entry (to follow, on the wiki) sets two properties and the Journals page becomes an `#ask` that never goes stale.
After the build reaches the wiki: `rebuildData` isn't needed for new annotations; existing entries get their properties when they're next saved (I'll do the five).
Redeploy: the usual wiki build (Jenkins, then the rsync cron). No server to redeploy.