Validator 1.0.0.1 gives me
Fatal error: Uncaught exception 'Exception' with message 'Validator depends on the ParamProcessor library.' in C:\xampp\htdocs\wiki\extensions\Validator\Validator.php on line 31
on MediaWiki 1.23wmf2
Topic on Extension talk:Validator/Flow
It looks like you did not install the ParamProcessor library. The sanest way to install this extension including dependencies is to use Composer.
I'm getting the same error message (MW 1.19.7, SMW 1.9). How does one go about installing the ParamProcessor library without shell access (without Composer)? It is included in the Validator 'wrapper', but there are no installation instructions for the library specifically as far as I can see.
I've got this error too.
Fatal error: Uncaught exception 'Exception' with message 'Validator depends on the ParamProcessor library.' in /var/www/wiki/extensions/Validator/Validator.php:31 Stack trace: #0 /var/www/wiki/LocalSettings.php(151): require_once() #1 /var/www/wiki/includes/WebStart.php(136): require_once('/var/www/wiki/L...') #2 /var/www/wiki/index.php(46): require('/var/www/wiki/i...') #3 {main} thrown in /var/www/wiki/extensions/Validator/Validator.php on line 31
Is there a simple way to install ans setup ParamProcessor library?
bkb
If you do not have shell access, you are restricted to using the tarball for now. I hope will will soon have an extension installation GUI...
Why to be obliged to have shell access, in my case I am hosted by a 3rd party service. I will never have a shell access. How configure manually ParamProcessor Library?
Thank in advance, Marco
Same thing... Trying to set this up on WAMP and it's free for all. No way to get this working. :(
Hello. I'm using 1.20.x and I have shell access but sorry, I can't find the information about how to install ParamProcessor with or without Composer...
Also, after using composer I had to recover from a backup because this error. (That was an attempt to update Maps to 3.0, for use with Semantic Maps).
Please, some guide to solve this?
Thanks.
I was also trying to use Maps. So in order to install Validator without having access to shell, do the following:
Download the stable version of both ParamProcessor and Validator. Extact the content in extensions/ParamProcessor (create the map ParamProcessor) and for Validator in extensions/Validator (create the map Validator).
After you have the files in place, change the file called: LocalSettings.php (in the root folder). And add this line to the end for ParamProcessor:
# ParamProcessor
require_once( "$IP/extensions/ParamProcessor/Processor.php" );
After this line you can add the next line for Validator:
# Validator
require_once( "$IP/extensions/Validator/Validator.php" );
Finally you can continue to setup other extensions after this lines.
The problem is that Validator spits out "Validator depends on the ParamProcessor library." so one navigates to Extension:ParamProcessor which redirects back to Extension:Validator. So we start going on the assumption that ParamProcessor was renamed to Validator with Validator trying to require itself through ParamProcessor.php in the Validator folder that just includes Validator.php which goes back to spitting out the error message "Validator depends on the ParamProcessor library." which-*segfault*.
There is some logic issues with the page and extension naming that causes confusion. Anyone who reads the Extension:Validator page then uses Mediawiki's extension distributor will be left clueless since ParamProcessor is not listed as a dependency on the extension page. There are also no installation instructions noting how to install ParamProcessor outside of Composer.
Thanks for pointing this out. I've updated the Extension:ParamProcessor page to point to where it should.
What I don't get is why this is not included in the semantic bundle. Validator is there, but ParamProcessor is not. That is inherently broken. Even if following the link to ParamProcessor listed above, there are no instructions how to install that in Mediawiki. Yes I know there is a thing called composer, yes I know that is the preferred way to install Validator, but here is the thing. The point of semantic bundle is if composer is not a viable option. What is the point of having a bundle if one has to download a handful of other extensions to get it working.
According to the docu this should already be part of the currentSemantic Bundle.