Does $wgSpamRegex require any Extensions in MediaWiki version 1.23.5 for it to work?
On the one hand, that page in the Manual says it's "built in" to MediaWiki, but then someone on the Talk page mentioned it's not working and another user recommended installing the SpamRegex Extension, which is obsolete but solved that users problem.
So which is it?
The manual seems up to date. $wgSpamRegex is a core function, and does not require any additional extensions.
(The discussion you are referring to is from 2008, and the MW version mentioned there is 1.13.)
The information on the Manual page is correct. $wgSpamRegex is a built-in configuration variable and can be used without any extensions :)
Related
We've MediaWiki 1.31.0 installed, but can't find the feature 'page preview', which is described here: https://www.mediawiki.org/wiki/Page_Previews
On this feature-page there's no hint, in which version of MediaWiki this feature was implemented. Can anybody tell me?
This is not core Mediawiki functionality, but implemented via an extension. See here for more information: https://www.mediawiki.org/wiki/Extension:Popups
PS: 1.31.0 has known security issues, you should at least upgrade to 1.31.7
We're upgrading from Semantic MediaWiki 1.9.2 to version 2.2 and will no longer use the Semantic Bundle.
So we no longer include SemanticBundleSettings.php and SemanticBundle.php in LocalSettings.php but use Composer and the vendor/autoload.php.
The Special:Version page shows the correct version and most things seem to work well but there are some issues.
For example when editing a template this message appears: "This page is not enabled for semantic in-text annotations due to namespace restrictions. Details about how to enable the namespace is described on the configuration help page".
(assuming this has something to do with upgrading)
My question: is there some roadmap to upgrade in a structured way rather then trial-and-error?
I've read Upgrade from SMW 1.9+ for MW 1.22+ and the release notes for SMW 2.0 but this does not give me enough information.
I am busy upgrading SMW 1.9.2 to version 2.2. How do I know which version to use of the accompanying extensions like Semantic Forms or Semantic Extra Special Properties?
As you can see at the SMW docs:
Various MediaWiki extensions are available for further extending
Semantic MediaWiki with additional functionality, and some basic
extensions of MediaWiki are generally useful for employing SMW.
Most extensions are not maintained by the SMW Project. Please see the
extension's main page and installation files to find out whom to
contact for support and where to report bugs. Questions related to
these extensions can be discussed on the mailing list or forum for the
extension (where specified), or on the Semantic MediaWiki user mailing
list.
So, in case that you don't find the relation between your SMW version and the version of each extension in the Semantic MediaWiki user mailing list or the forum for the extension, you should look at the official docs for every extension or contact the developers of each extension, as there is not official reference about the relation you're looking for.
Found a similar question about the difference between QAPlug-FindBugs and FindBugs-IDEA, but not about CheckStyle...
I think (from previous experience) with these plug-ins that one difference is that the QAPlug's CheckStyle version seems to be behind the CheckStyle-IDEA's CheckStyle version (I'm not referring to the versions of the plug-ins, but of the version of CheckStyle that's embedded in them).
Anyone knows of any other differences between those?
Advantages of CheckStyle-IDEA over QAPlug – Checkstyle:
Newer version of Checkstyle used
Community on GitHub
Fast scan before commit
Support for multiple configurations
Support for third-party checks
I haven't noticed any use case when QAPlug is better.
We develop web application and we are going to deploy it on JBoss.
Now we use JSF, Facelets, Webflow, JMX, Spring.
We are going to use JMS(ActiveMQ).
Maybe in the future we will use EJB3. But for near future we will not use it.
What configuration of JBoss would be better to use - web, standard, default?
And why?
Go for the smallest config that does what you need. The "web" configuration seems to have everything you need, including ejb3 support.
Remember, the configurations in the distribution are just examples. It's perfectly acceptable to create custom server configs by copying the deployers and libs around to produce a config that does exactly what you need.
I've never found the need to use anything other than default, sometimes removing some of the config. And that's included JMS, EJB, Spring, Webflow, etc.
I you are using JBoss AS 5.1.X, I recommend this book: http://www.amazon.com/JBoss-AS-Development-Marchioni-Francesco/dp/1847196829
On page 31 there is a detailed explanation about the five provided configurations.