r60328 MediaWiki - Code Review archive

Repository:MediaWiki
Revision:r60327‎ | r60328 | r60329 >
Date:17:27, 23 December 2009
Author:mkroetzsch
Status:deferred
Tags:
Comment:
dynamic extension path (Bug 21832), some new configuration parameters
Modified paths:
  • /trunk/extensions/SemanticMediaWiki/includes/SMW_Settings.php (modified) (history)

Diff [purge]

Index: trunk/extensions/SemanticMediaWiki/includes/SMW_Settings.php
@@ -28,8 +28,11 @@
2929 ###
3030 # This is the path to your installation of Semantic MediaWiki as seen on your
3131 # local filesystem. Used against some PHP file path issues.
 32+# If needed, you can also change this path in LocalSettings.php after including
 33+# this file.
3234 ##
33 -$smwgIP = $IP . '/extensions/SemanticMediaWiki';
 35+$smwgIP = dirname(__FILE__) . '/..';
 36+// $smwgIP = $IP . '/extensions/SemanticMediaWiki';
3437 ##
3538
3639 // load global functions
@@ -79,6 +82,27 @@
8083 ##
8184
8285 ###
 86+# Should SMW consider MediaWiki's subcategory hierarchy in querying? If set to
 87+# true, subcategories will always be interpreted like subclasses. For example,
 88+# if A is a subcategory of B then a query for all elements of B will also yield
 89+# all elements of A. If this setting is disabled, then subclass relationships
 90+# can still be given explicitly by using the property "subcategory of" on some
 91+# category page. Only if the setting is false will such annotations be shown in
 92+# the factbox (if enabled).
 93+##
 94+$smwgUseCategoryHierarchy = true;
 95+##
 96+
 97+###
 98+# Should category pages that use some [[Category:Foo]] statement be treated as
 99+# elements of the category Foo? If disabled, then it is not possible to make
 100+# category pages elements of other catgories. See also the above setting
 101+# $smwgUseCategoryHierarchy.
 102+##
 103+$smwgCategoriesAsInstances = true;
 104+##
 105+
 106+###
83107 # Should SMW accept inputs like [[property::Some [[link]] in value]]? If
84108 # enabled, this may lead to PHP crashes (!) when very long texts are used as
85109 # values. This is due to limitations in the library PCRE that PHP uses for
@@ -104,12 +128,14 @@
105129 # inverses, or shall they be displayed on the other side?
106130 ##
107131 $smwgBrowseShowInverse = false;
 132+##
108133
109134 ###
110135 # Should the browse view always show the incoming links as well, and more of
111136 # the incoming values?
112137 ##
113138 $smwgBrowseShowAll = true;
 139+##
114140
115141 ###
116142 # Should the search by property special page display nearby results when there
@@ -136,12 +162,14 @@
137163
138164 ###
139165 # Settings for inline queries ({{#ask:...}}) and for semantic queries in
140 -# general. This can especially be used to prevent overly high server-load by
141 -# complex queries. The following settings affect all queries, wherever they
 166+# general. This can especially be used to prevent overly high server-load due
 167+# to complex queries. The following settings affect all queries, wherever they
142168 # occur.
143169 ##
144170 $smwgQEnabled = true; // (De)activates all query related features and interfaces
145 -$smwgQMaxLimit = 10000; // Max number of results ever retrieved, even when using special query pages.
 171+$smwgQMaxLimit = 10000; // Max number of results *ever* retrieved, even when using special query pages.
 172+$smwgIgnoreQueryErrors = true; // Should queries be executed even if some errors were detected?
 173+ // A hint that points out errors is shown in any case.
146174
147175 $smwgQSubcategoryDepth = 10; // Restrict level of sub-category inclusion (steps within category hierarchy)
148176 $smwgQSubpropertyDepth = 10; // Restrict level of sub-property inclusion (steps within property hierarchy)

Status & tagging log