Extension talk:ParamProcessor
- [History↑]
Contents
| Thread title | Replies | Last modified |
|---|---|---|
| Class RangeValidator not found | 4 | 06:05, 12 February 2013 |
| Download doesn't work | 1 | 17:35, 17 January 2013 |
| Validator and graph result format | 2 | 16:54, 20 October 2012 |
| SMW setMessage problem in v1.14 Validator | 0 | 09:07, 27 September 2012 |
| Short description of this extension please | 1 | 19:00, 22 May 2012 |
| Parameter manipulation | 6 | 22:26, 21 March 2012 |
| Undefined index error | 5 | 20:22, 29 February 2012 |
| Describe lists parsemag as alias | 3 | 13:54, 2 October 2011 |
| 4.10? | 1 | 11:31, 24 August 2011 |
Hi,
a fatal error comes up when I execute a simple ask query such as {{#ask: [[Category:Publication]] }}:
Fatal error: Class '\ValueValidators\RangeValidator' not found in ...\extensions\Validator\includes\ParamDefinitionFactory.php on line 176
The following extensions are installed:
- MediaWiki 1.19.3
- PHP 5.3.0 (apache2handler)
- Semantic MediaWiki (Version 1.9 alpha)
- DataTypes (Version 0.1 alpha)
- DataValues (Version 0.1 alpha)
- ValueFormatters (Version 0.1 alpha)
- ValueParsers (Version 0.1 alpha)
- ValueValidators (Version 0.1 alpha)
- Validator (ParamProcessor) (Version 1.0 alpha)
Cheers, Basil
I suspect you are running incompatible alpha versions. Since you just list them as being alpha I can't tell. The latest alphas are working fine with each other and so are the latest releases. The error you are running into suggests you have either an outdated Validator or and outdated DataValues extension bundle.
Hi Jeroen,
just now I deleted the extension folders for Validator and DataValues and did a fresh checkout. The version numbers are still the same and the fatal error did not disappear.
Any idea what I could try?
Cheers, Basil
I fixed the problem for now in extensions/DataValues/ValueValidators/ValueValidators.classes.php. It seems like the validators are not correctly registered. I added some backslashes at the beginning:
'\ValueValidators\RangeValidator' => 'includes/validators/RangeValidator.php', '\ValueValidators\StringValidator' => 'includes/validators/StringValidator.php',
Cheers, Basil
Uh oh... that is not good...
That should not be needed and is caused by MW 1.19.x not having decent namespace support in its autoloader. This is going to cause problems elsewhere as well, so we'll need to take care of this before the next SMW release.
I created bug 44892 to keep track of this
Version 0.5 seems to break parts of the graph output for Semantic Result Formats (or vice versa). It will not show the labels, colors or legend. I was able to fix this by downgrading to version 0.4.14. --Dgennaro 17:19, 18 October 2012 (UTC)
Version 1.13 of Validator works fine for me. When I installed 1.14 I got the bug below. Going back to 1.13 fixed it. So I have a workaround, but this may be a bug in 1.14.
The problem is that any Semantic MediaWiki {{#ask}} call results in the following message:
PHP Fatal error: Call to undefined method Parameter::setMessage() in C:\Program Files (x86)\Apache Software Foundation\Apache2.2\htdocs\mediawiki\extensions\SemanticMediaWiki\includes\SMW_QueryProcessor.php on line 512
Here is my version info:
MediaWiki 1.18.1 PHP 5.2.13 (apache2handler) MySQL 5.1.58-community Semantic Forms (Version 2.5) Semantic MediaWiki (Version 1.7.1) Semantic Result Formats (Version 1.7.1) Character Escapes (Version 0.9.1) LinkedWiki (Version 0.1.0.2222) Validator (Version 0.4.13)
Indeed, I have yet not beta-ed over to the latest SMW 1.8, but that is not yet officially released. And Validator 1.14 came out just after SMW 1.7.1.
Hope this helps, Lloyd Rutledge
Hello,
would somebody please tell me the functionality of this extension in a few words? The extension description doesn't make sense for me. Maybe I'm too silly for that. But many extensions require validator, so it has to be important. Thanks for your help.
Cheers
The reason for manipulating data is to enter "yes" instead of "true"? Please remind that we don't want change any sense! You know that all here is text and you also know that this is not about converting or encoding. Drop it!
Validator allows a bunch of values for boolean parameters, for example yes/no, on/off, but not true/false actually, might make sense to include this as well. Perhaps also show/hide while we're at it.
Yeah, we can add those. The boolean type was never fully implemented so far anyway - if you have on/off, you ought to consider internationalizing these as well :)
One more todo for 0.5.
I want to suggest to keep it simple! The attribute can be named SwitchOn the values are true/false.
| SwitchOn=true}}
Furthermore you could handle it with 1 and 0 but than there were no new datatype - Ooh
Anyway you can implement what you want, but if there is no additional benefit it is just absurd...
I'm getting the following error on my form pages "Notice: Undefined index: original-value in /extensions/Validator/includes/Validator.php on line 168" Any hints on how I can resolve this? Thanks!
What version are you using? I suspect this issue has already been fixed. When are you getting it? Using Semantic Forms?
Hi Jeroen,
I'm getting this notice when using sparql inline query e.g.
{{#sparql: SELECT ?person ?income WHERE { ?person <http://mywiki/property/Income> ?income . } }}
I have:
MediaWiki 1.17.0
Semantic Forms (Version 2.3.2)
Semantic MediaWiki (Version 1.7.0.2)
Any ideas?
Where is this #sparql parser function coming from? It's not part of SMW AFAIK. Also, what version of Validator are you using?
I have a parserfunction that has 1 alias. The describe parserfunction says: Aliases: parsemag
The error is in line 173 of Validator_Describe.php in Validator 0.4.11:
$description .= $this->msg( 'validator-describe-aliases', 'parsemag', $wgLang->listToText( $aliases ), count( $aliases ) );
Changing $this->msg to wfMsgExt fixes the problem.
Thanks for pointing this out. I just removed the parsemag argument. Using wfMsgExt might fix the issue, but will break the behavior of the language parameter.
