I downloaded 'SemanticBundle-20140103.zip' but it leads to the error Error: This version of Validator requires MediaWiki 1.16 or above. Despite the fact, that my mediawiki is 1.22.2....
Extension talk:Semantic Bundle/Archive 2
If you don't mind, could you go into the file /extensions/Validator/Validator.php and comment out the line where that error is raised (it should be around line 29)? That may or may not fix the overall problem - please let us know if that worked.
Hi, I am also using mediawiki 1.22.2 and after I downloaded and installed Semantic Bundle I have the same error. After commenting out Validator.php. I get this error: "Error: This version of Semantic MediaWiki requires MediaWiki 1.17 or above; use SMW 1.7.x for MediaWiki 1.16.x."
I commented out the Error message in SemanticMediaWiki extension php and now I have empty pages in my wiki...
It did not originally work. I had to reget the semantic bundle and try a lot of thinks, for it to work again. With Maps/Semantic Maps not in use right now.
I'll try them again, when I have more time...
Found a fix to get semantic features working with mediawiki 1.22.4 and composer. The challenge is that the semantic bundle overwrites the created "semantic extensions" on the initial Semantic Mediawiki, created through "composer" and enableSemantics. The solution
- use composer:
composer require mediawiki/semantic-media-wiki "~1.9" - run maintenance scripts:
php maintenance/update.php
then make a tar of the extension scripts, install the semantic bundle, and extract the previous extensions:
-
tar -cvzf extensions-mediawiki.tgz extensions - install SemanticBundle
-
tar -xvzf extensions-mediawiki.tgz
however: all my types are still of type Page, with message: no type was specified for this property. Assuming type Page for now
I tried that, since I made an new attempt to update, but it only sends errors back
PHP Warning: Class 'SMW\Store' not found in PATH TO WIKI/extensions/SemanticMediaWiki/SemanticMediaWiki.php on line 60
PHP Warning: Class 'SMW\MediaWiki\Jobs\UpdateJob' not found in PATH TO WIKI/extensions/SemanticMediaWiki/SemanticMediaWiki.php on line 61
PHP Warning: Class 'SMW\MediaWiki\Jobs\RefreshJob' not found in PATH TO WIKI/extensions/SemanticMediaWiki/SemanticMediaWiki.php on line 62
PHP Warning: Class 'SMW\SemanticData' not found in PATH TO WIKI/extensions/SemanticMediaWiki/SemanticMediaWiki.php on line 63
PHP Warning: Class 'SMW\DIWikiPage' not found in PATH TO WIKI/extensions/SemanticMediaWiki/SemanticMediaWiki.php on line 64
PHP Warning: Class 'SMW\DIProperty' not found in PATH TO WIKI/extensions/SemanticMediaWiki/SemanticMediaWiki.php on line 65
PHP Warning: Class 'SMW\Serializers\QueryResultSerializer' not found in PATH TO WIKI/extensions/SemanticMediaWiki/SemanticMediaWiki.php on line 66
PHP Warning: Class 'SMW\DataValueFactory' not found in PATH TO WIKI/extensions/SemanticMediaWiki/SemanticMediaWiki.php on line 67
PHP Warning: Class 'SMW\DataItemException' not found in PATH TO WIKI/extensions/SemanticMediaWiki/SemanticMediaWiki.php on line 68
PHP Warning: Class 'SMW\FileExportPrinter' not found in PATH TO WIKI/extensions/SemanticMediaWiki/SemanticMediaWiki.php on line 69
PHP Warning: Class 'SMW\ResultPrinter' not found in PATH TO WIKI/extensions/SemanticMediaWiki/SemanticMediaWiki.php on line 70
PHP Warning: Class 'SMW\SQLStore\TableDefinition' not found in PATH TO WIKI/extensions/SemanticMediaWiki/SemanticMediaWiki.php on line 71
PHP Warning: Class 'SMW\AggregatablePrinter' not found in PATH TO WIKI/extensions/SemanticMediaWiki/SemanticMediaWiki.php on line 72
PHP Warning: Class 'SMW\ListResultPrinter' not found in PATH TO WIKI/extensions/SemanticMediaWiki/SemanticMediaWiki.php on line 73
PHP Warning: Class 'SMW\DIConcept' not found in PATH TO WIKI/extensions/SemanticMediaWiki/SemanticMediaWiki.php on line 74
PHP Fatal error: Class 'SMW\SimpleDependencyBuilder' not found in PATH TO WIKI/extensions/SemanticMediaWiki/SemanticMediaWiki.php on line 112
The PATH TO WIKI being my edit. So, there is something wrong, even if I try to get composer to download the latest version.
I assume you're using the latest Semantic Bundle - but are you using strictly extensions from SB, or are some of the extensions (like SMW itself) coming from elsewhere?
There are other extensions, like Auth_phpBB and MergeUser, NativeSVG and a extension I wrote myself, for instance.
First, I'm not quite sure composer works, like it should. Examples go for composer install ..., but I have to run it with php composer.phar install .... Am I supposed to create a 'composer' shell file myself? Do I need to ?
That said, I seems that composer downloaded everything needed. And yes, I downloaded the latest semanticbundle.
Installation_without_shell_access#Troubleshooting stated, that I have to remove Validator if errors like that occur. I did, but nothing changed.
Heinrich, while others are better informed about this than me, I'm not sure if the two approaches, that is, using SB as well as Composer, are full compatible. In fact, the latest version of SB is a welcome service for people (like myself) who cannot run Composer and need to install a lot of related extensions on top of SMW. Either download the individual extensions yourself (not from SB) and run Composer or use SB and don't run Composer.
Thanks for the input. I now have my wiki back running again. Problem was, that even with a clean installation of mediawiki and semantic bundle it didn't work for some reason. I now use composer and have manually installed some other extensions.
I hope all the other extensions are added to composer soon, for it is really comfortable, if it works.
Hi,
When i try to update or initialize database in smanticmediawiki i get the following error
Notice: Only variables should be passed by reference in C:\xampp\htdocs\mediawiki\extensions\SemanticMediaWiki\includes\Setup.php on line 273.
I am new to it so can anyone help me.
Why is the SemanicBundle offered for download at Special:ExtensionDistributor when the downloaded file contains nothing but a few php setings, but none of the extensions that are shown here on the help page. As always with Mediawiki, the instsallation process and documentation are ABSOLUTELY BULLSHIT.
I agree that Special:ExtensionDistributor is not good for most extensions - or for this bundle. I wish there weren't so many links to it everywhere.
Hi Yaron,
I installed the newest version of MW a few days ago and am now realizing that something in there is messing with at least some of the SMW functionality. For example, I can no longer get a link to properties from the property browser, and the SMW elements are no longer listed in the advanced search. Internet Search tells me that a bunch of things have changed and that with the Bundle I am a full version behind the current SMW. I used the bundle in the first place because we are in a shared hosting environment and I don't have the access to use Composer. So, I was wondering... do you think you will get to updating the Bundle in the next little while?
Thanks!
I too am getting this error, would love to know if there's a fix or a workaround.
I believe a lot of that got fixed when I installed the newest version of SMW manually rather than using the bundle. It was a little tricky but doable.
Did you do a fresh install or did you update SMW? I tried updating to the newest version but saw a ton of errors and had to revert the process. Would love to know what you tried to fix it!
If I remember right I just got rid of all files and reference of the bundle and installed SMW fresh. That (and possibly other steps, can't remember) got rid of the errors. Since all the information is stored in markup in the DB it picked up pretty clean. Possibly after running rebuildData.php. However...
I upgraded MW at the same time, and had to mess with another extension that is no longer supported, and between all of that, our MW seems to no longer update categories etc as promptly as it used to. I have a crontab for both runJobs.php and rebuildData.php (think that's what it was called) running each night and that seems to have things settled the next day, but it's not a satisfying solution.
I don't get the impression that the bundle will receive any more TLC, I'd suggest trying it again.
Thanks, that's definitely a solid pointer, will give it a bash over the coming week. Really appreciate you taking the time to talk through the process you used!
Hi Yaron,
I tried to install SemanticBundle in a MW 1.27.1 via GIT. I know the instructions say "WARNING! This is experimental!", but I keep getting 403-Errors when I do "make" in the console. Is this part of the "experimental" thing? I scrutinized my firewall settings, but they don't seem to be the problem - while phabricator.wikimedia.org looks splendidly up and running to me.
Here's some of the errors during the make process:
HEAD is now at abb1156... Update INSTALL
rm: "." and ".." may not be removed
Cloning into 'SemanticForms'...
fatal: unable to access 'https://phabricator.wikimedia.org/diffusion/MEXT/extensions.git/SemanticForms.git/': The requested URL returned error: 403
Cloning into 'SemanticFormsInputs'...
fatal: unable to access 'https://phabricator.wikimedia.org/diffusion/MEXT/extensions.git/SemanticFormsInputs.git/': The requested URL returned error: 403
Cloning into 'SemanticCompoundQueries'...
fatal: unable to access 'https://phabricator.wikimedia.org/diffusion/MEXT/extensions.git/SemanticCompoundQueries.git/': The requested URL returned error: 403
Cloning into 'SemanticDrilldown'...
Other packages like ParamProcessor, Validator, SemanticExtraSpecialProperties, etc., clone nicely and don't throw errors.
Has that happened to others, too? Any hints?
No hurry, there are alternatives - I was just wondering...
Thanks and all the best, Achim
Hi Yaron,
I'm sure you're busy, but just asking if a new version of semantic bundle will be out soon...
This one is not compatible with the latest MW 1.27 (had issues with semantic forms) :)
Also if I just copy and paste latest SMW and semantic forms over in this semantic bundle will it work?
Thanks so much!
As you know, I haven't upgraded Semantic Bundle in a long time... I do want to do it, but I don't have any immediate plans to. If you can install SMW yourself, I would just install all the extensions that way.
Thanks so much!
I am new in semantic mediawiki, I have installed mediawiki over the wamp, after that I downloaded semantic bundle and it is extracted. I copied the extracted folder to mediawiki pasted inside extension folder.
what to do the rest?
Please add this page to translate
Good day Yaron, reading some of the comments below it appears there is an updated Semantic Bundle that should be out soon? Or is it already out? The downloads at the "Page" appear to be for MW 1.92 ? Any help is greatly appreciate Yaron, and thanks again for your hard work!
Not yet, unfortunately.
Is there any news about this yet?
I'm having a lot of trouble upgrading to 1.25.2 some helped by this page.
What puzzles me about the Semantic Bundle is that it's supposed, at least I thought it was supposed, to be for people who have problems using composer (usually systems hosted on CPANEL [as mine is]), but the documentation now says it relies on validator, and some others, being installed with composer - which defeats the object of the exercise.
What I've tried to do, to work around this, is to use composer to install the required stuff on my own machine, along, then, with the semantic bundle - then copy the whole lot up onto the CPANEL machine. Despite this, I'm still struggling.
Same error here - database error 500 when installing SemanticBundle. Have been trying to do this for months now since I had issues with Composer and basically gave up trying to extend by Wiki install, though I'd really love to work with this if anyone has a solution.
Hi Yaron,
Thanks for all the hard work on this. I was wondering what the correct process would be to remove SB and go back to installing extensions one at a time, using Composer when possible?
Thanks so much.
Just comment out, or remove, the relevant line in LocalSettings.php.
Hey Yaron, back to this thread.
I've been trying to remove the Semantic Bundle settings, transfering all the extensions call onto the LocalSettings.php file. And it all works out except for one setting that I can't comment out without breaking the wiki.
$classMap = require_once( "$IP/extensions/SemanticBundle/SB_AutoloadClassmap.php" );
foreach ( $classMap as $className => $fileName ) {
$wgAutoloadClasses[$className] = $fileName;
}
This was originally in the SemanticBundleSettings.php file. But somehow without it, the wiki breaks. Currently I moved it to the LocalSettings file so I could comment out the call for the SemanticBundleSettings.php all together, but this setting is still calling a SemanticBundle file, which I'm not finding a way around.
Do you know anything about it?
Hi,
I just updated my mediawiki from 1.16.5 to 1.25.2.
To stay up to date I also downloaded the new Semantic-Bundle tarball and unzipped it in my extensions folder.
I enabled it with require_once( "$IP/extensions/Validator/Validator.php" ); in my LocalSettings.php
After this didn't work because of ParamProcessor being missing I downloaded that tarball and unzipped it too.
I also enabled it using require_once( "$IP/extensions/ParamProcessor/src/Processor.php" ); where I'm not sure if this is correct.
Ultimately it gave me more errors than before. I now get lots of these for newly installed ParamProcesser:
PHP Warning: Class 'ParamProcessor\\ParamDefinitionFactory' not found in /var/www/mediawiki-1.25.2/extensions/Validator/Validator.php on line 79
And lots of these which I had before already:
PHP Warning: Class 'SMW\\Store' not found in /var/www/mediawiki-1.25.2/extensions/SemanticMediaWiki/SemanticMediaWiki.php on line 60
Any ideas here?
I would like to avoid using composer.
Since I don't seem to be able to edit my initial post:
I am running Ubuntu 12.04.5 with PHP 5.3.10 and mysql 5.5.44
Well.. okay.
Issue was simply my old config-file which I copied without checking.
Obvously there has been an update to it which makes old config-files invalid.
Took the sample of the new version and made some changes I needed - works.
Which Config file specifically? I am having this same problem.