Property/Category setup: Difference between revisions

From Ring of Brodgar
Jump to navigation Jump to search
m (→‎Property vs Category setup: +Boardperlog_sawmill (game/tree))
(ISSUE: Forced updating stopped working.)
 
(2 intermediate revisions by 2 users not shown)
Line 5: Line 5:
:The only successful way so far to force proper data updating across the board seems to be two API-Purged calls on the related property page(s).
:The only successful way so far to force proper data updating across the board seems to be two API-Purged calls on the related property page(s).
:(the second call would be on properties that show up in the unclassified‎ category while they should not.)
:(the second call would be on properties that show up in the unclassified‎ category while they should not.)
:{{error|Currently not working anymore. Unclassified cases can't be forced to there target category anymore. Find fix, and/or alternative simpler solution.}}


:When in source-edit mode the '''[Show Preview]''' prints data on the used, and newly added property, cases.
:When in source-edit mode the '''[Show Preview]''' prints data on the used, and newly added property, cases.
Line 179: Line 180:


{{  Property_cat | 1=Crt-isdeadly | 2=game/kritter
{{  Property_cat | 1=Crt-isdeadly | 2=game/kritter
}}{{Property_cat | 1=Crt-armor | 2=game/kritter
}}{{Property_cat | 1=Crt-basequality | 2=game/kritter
}}{{Property_cat | 1=Crt-basequality | 2=game/kritter
}}{{Property_cat | 1=Crt-basequality-txt | 2=game/kritter
}}{{Property_cat | 1=Crt-hitpoints | 2=game/kritter
}}{{Property_cat | 1=Crt-hitpoints-txt | 2=game/kritter
}}{{Property_cat | 1=Crt-fleeinghitpoints | 2=game/kritter
}}{{Property_cat | 1=Crt-fleeinghitpoints | 2=game/kritter
}}{{Property_cat | 1=Crt-hitpoints | 2=game/kritter
}}{{Property_cat | 1=Crt-fleeinghitpoints-txt | 2=game/kritter
}}{{Property_cat | 1=Crt-armor | 2=game/kritter
}}
}}


Line 241: Line 245:
}}{{Property_cat | 1=Trees_branchtype | 2=game/tree
}}{{Property_cat | 1=Trees_branchtype | 2=game/tree
}}{{Property_cat | 1=Tree_terrains | 2=game/tree
}}{{Property_cat | 1=Tree_terrains | 2=game/tree
}}<!-- alternative(sub-objects) tree/log properties
{{  Property_cat | 1=Tree/name‎ | 2=game/tree
}}{{Property_cat | 1=‎Tree/trv | 2=game/tree
}}{{Property_cat | 1=‎Tree/logs | 2=game/tree
}}{{Property_cat | 1=‎Treelog/stoneaxe | 2=game/tree
}}{{Property_cat | 1=‎Treelog/metalaxe | 2=game/tree
}}{{Property_cat | 1=‎Treelog/bonesaw | 2=game/tree
}}{{Property_cat | 1=‎Treelog/metalsaw | 2=game/tree
}}{{Property_cat | 1=‎Treelog/sawmill | 2=game/tree
}}
}}
{{  Property_cat | 1=Seed_of | 2=game/bush
{{  Property_cat | 1=Seed_of | 2=game/bush
}}{{Property_cat | 1=Grown_from | 2=game/tree
}}{{Property_cat | 1=Grown_from | 2=game/tree

Latest revision as of 09:20, 21 September 2024

info

Notes:

Due to how this work (MW/SMW) Category data changes here don't automatically update the data in the related Category & property pages.
The only successful way so far to force proper data updating across the board seems to be two API-Purged calls on the related property page(s).
(the second call would be on properties that show up in the unclassified‎ category while they should not.)
Currently not working anymore. Unclassified cases can't be forced to there target category anymore. Find fix, and/or alternative simpler solution.
When in source-edit mode the [Show Preview] prints data on the used, and newly added property, cases.

Active cases list (smwtable). (178)
Property category entries: 353
Property pages count(1): 298
Property pages count(2): AllPages(Property)

Property vs Category setup