Talk:Semantic Bundle/LQT Archive 1

Just thinking...
Nice stuff. How about getting the 'missing' extensions into the MediaWiki SVN also, and possibly stuff all of them in a subfolder 'SemanticMediaWiki' or 'SemanticBundle', instead of having them all at the top level of trunk/extensions/? siebrand 00:33, 13 June 2009 (UTC)


 * Hi, thanks for looking into this. By the 'missing' extensions, do you mean the ones that aren't in SVN at all, or the ones that don't have a tag in SVN, or both? And what's the advantage of grouping them into one place? Yaron Koren 13:34, 14 June 2009 (UTC)
 * By missing I mean the extensions that are not yet in svn.wikimedia.org. The advantage of having them all in that svn repo is that all extensions can be (a) supported by translatewiki.net, so have more than excellent localisation, and (b) there are a lot of MediaWiki developer eyes on that svn, which may have a positive effect on the number of Semantic* developers. Grouping them into one place will give the bundle more profile, IMO - aside from allowing developers to check out the trunk for the bundle at once, instead of having to grab the latest versions from wherever they reside. Last but not least: all developers on the Semantic bundle can join forces and all work on the complete bundle. Cheers! siebrand 17:19, 21 July 2009 (UTC)

Settings not ok
Hi, It seems that the semanticbundlesettings.php is not up-to-date with the bundle. The current version contains Maps and Semantic Maps but it includes good old Semantic Google Maps. --AdSvS 08:15, 6 September 2009 (UTC)

Parser extension version problem?
I just downloaded & installed the semantic bundle zipfile -- it told me that the magic word 'if' could not be found. The ParserFunctions extension downloaded from the bundle is dated 5/25/09. I overlayed the version dated 6/13/09 that I have and the magic word problem went away.--65.117.229.105 06:04, 25 September 2009 (UTC)


 * I have the same problem with the "magic word 'if' not found". I'm using mediawiki 1.15.1 - the documentation for parserfunctions suggests a different version of parserfunctions is required for 1.15.1. It would be helpful to document what version of mediawiki has been tested with the semantic bundle. Bluethorn 01:29, 13 October 2009 (UTC)

typo in folder name
Hi, the folder included in the bundle should be named “SemanticInternalObjects” instead of “SemanticInternalOjbects”. Cheers --kgh 20:21, 15 October 2009 (UTC)


 * Yes, it's been fixed in SVN but not yet released with the fix; but thanks. Yaron Koren 22:22, 15 October 2009 (UTC)


 * No worries, I just wanted to give you a hint in case this was still undiscovered. :-) Apart from that, this hint might save some systemadministrators a bit of time until it is fixed. Cheers --kgh 22:45, 15 October 2009 (UTC)


 * Yeah, that's true; thanks. Yaron Koren 22:50, 15 October 2009 (UTC)

Suggestion for inclusion of further Semantic Extensions
I would vote for inclusion of Extension:Semantic_Graph. Is there a plan to include it? --80.122.147.22 11:38, 19 October 2009 (UTC)


 * Hi - we haven't thought about it, but maybe that's because we don't know anything about it. The 'graph' format in Semantic Result Formats already includes a subset of Semantic Graph's functionality, I believe. Do you know why it's not the whole thing, and whether there's a plan to move more into SRF? Yaron Koren 13:29, 19 October 2009 (UTC)

Undefined property: SMWTimeValue
I'm getting the following problems after installing this new version of Semantic Bundle:

Notice: Undefined property: SMWTimeValue::$m_errors in /srv/www/htdocs/mediawiki/extensions/SemanticMediaWiki/includes/SMW_DV_Time.php on line 384 Warning: implode: Invalid arguments passed in /srv/www/htdocs/mediawiki/extensions/SemanticMediaWiki/includes/SMW_DV_Time.php on line 384 

I have some other extensions installing, but this warning appears even in the main page.


 * This sounds like a bug in SMW - you should post a bug report about it, or ask on the semediawiki-user mailing list. Yaron Koren 16:52, 5 May 2010 (UTC)

MediaWiki Main Page Coming up Blank
After I completed step 4 in the installation steps, I get a blank home page. Commenting out the two entries brings up the home page. What am I doing wrong?


 * See here. Yaron Koren 14:42, 10 October 2010 (UTC)

Don't anderstand the installation
I do the installation of the bundle but I don't anderstand the 3rd step : Copy SemanticBundleSettings.sample.php to SemanticBundleSettings.php

You want us to copy all the code contained in SemanticBundleSettings.sample.php at the end of the code of SemanticBundleSettings.php ? Why not be directly integrated with the code ?

Tks for your job.


 * Hi - the idea is so that users don't directly modify SemanticBundleSettings.sample.php, since that can get changed in later versions of Semantic Bundle - just like users update LocalSettings.php but not DefaultSettings.php. If you already created a file called SemanticBundleSettings.php, then you might not need to do any more work. Yaron Koren 09:43, 19 September 2010 (UTC)

Missing LocalSettings.php in SemanticBundle-20101001.zip?
I am new to semantic mediawiki. Am I to find LocalSettings.php in SemanticBundle-20101001.zip? I am unable to follow step 4 for installaion. Any help would be greatly appreciated.

Thanks,


 * LocalSettings.php isn't part of Semantic Bundle - it's a file that gets created automatically when you first install MediaWiki. If you have a working installation of MediaWiki, it should be right in the main directory. Yaron Koren 14:35, 10 October 2010 (UTC)

Thanks a bunch.

Page security
Hi SB users... I'm wondering which extension you are all using to provide group based page security? The HaloACL extension is the only one I know of that secures semantic data. Are there any others? - Borofkin 05:00, 2 November 2010 (UTC)

Simpler install
A suggestion for improving the install experience for everyone. Add a new file called  to the file package. The file contains: <?php if ( !defined( 'MEDIAWIKI' ) ) { echo "This file is not a valid entry point."; exit( 1 ); }

include_once("$IP/extensions/SemanticMediaWiki/SemanticMediaWiki.php"); enableSemantics($wgServerName);
 * 1) Semantic MediaWiki basic installation.
 * 2) More info: http://semantic-mediawiki.org/wiki/Help:Installation

Then change the install instructions to tell people to copy the  to   and visit the   page. After installation is complete, tell them to replace the  with the file. This way you avoid all the scary looking database errors for everyone that follows the current install instructions.

Versions out of date
Is this still maintained? I thought this was going to be an excellent time saver. Then I checked the version of SemanticMediaWiki. It's not the latest. Of all the extensions in this bundle that one should NEVER be out of date. Now I have to go through and check each extension to be sure I use the latest release. This negates any benefit of using a 'bundle'. Your efforts are reduced to simply being a recommended list of extensions I should check out ONE AT A TIME. Why is there no ReadMe with version numbers in it? Or did I miss it? That should be a MUST HAVE in any bundle like this. ~ 14:20, 8 March 2011 (UTC)


 * Semantic Bundle contains reasonably up to date versions of all key extensions. If there is some critical update, it will be put in and a new version will be released. Semantic Bundle even includes special bugfix releases of SMW, so you often end up having more up to date code then the latest official SMW release. Obviously you MUST HAVE some trust in the developers maintaining the bundle, and also handle your very friendly comments ONE AT A TIME, but are NEVER going to give you up. --Jeroen De Dauw 15:19, 8 March 2011 (UTC)

Need to fix for MediaWiki 1.17
Gives blank pages. Traced to the enableSemantics($wgServerName); line in SemanticBundleSettings.php

$wgServerName has been deprecated in Mediawiki 1.17 and this needs to be hard coded.

Aubrey


 * Thanks for letting us know about that - this will be fixed in the next version. Yaron Koren 19:15, 8 July 2011 (UTC)


 * Thanks for clearing that up. On the support desk, I reported a "Parse error: syntax error, unexpected T_STRING [site name here/]extensions/semantic-bundle/SemanticBundleSettings.php on line 7". I feared it was another symptom of failing to properly upgrade to MW 1.17, but this makes a lot more sense. Exactly what is the line we should use to replace it? Cavila 07:38, 14 July 2011 (UTC)