Hello,
on the validation of a field "image" (of type "image picker" or "file uploader"), there is the following problem in javascript: "jqv: custom rule not found". Reading the various topics, say it is a problem of regex, but nothing more. Someone can give me more information? Someone managed to solve this problem?

thanks

Migrate to 2.0 if you can.

This issues will not be anymore fixed on 1.5

Workaround: remove the validation for this field :

Remove the class on the field :
validate[custom[file]]

I will continue to use version 1.5, because I want the component to remain compatible with versions 1.6, 1.7 and 2.5 of joomla and also because in version 2.0 I have other problems. I think your solution is just a bypass of the problem, I would try to solve it at all.
Thank you very much.

V2.0 is also compatible 1.6 and 1.7.

It is not written, but it works because it is the same 11.x Plateform.

ah! thanks for the information, I did not know!

in version 2.0 have the same problem: "jqv: custom rule not found - file_5278" more gives me a problem with the validation of a decimal field: "Validation Rule missing: decimal_10_2", the decimal value of the field is "22.44"

Is this a custom rule you've created? If so...

You should rename the handler without the underscores... Joomla/cook conventions strip them out.

rename it to something like decimal10to2

Also, see some posts that I made here for advice on validating with custom regex in COOK ...

Gez

Audibleid Thank you, your support is important. With regard to the following problem "jqv: custom rule not found - file_5278" did not find any solution?

+1 Karma

however, I concluded not to make mandatory field and set a default value (an image) and then remove the validation as the administrator said. In this way does not come out the annoying javascript error!

Hi there,

Your error

jqv: custom rule not found - file_5278

Is this a custom rule?

I also experienced similar errors last night with fields that were working previously and they had not changed since the day before.

@admin - have you changed anything?

Previously, whenever I've experienced the jqv custom rule errors, it's been due to a badly named handler or a malformed regex.

Gez

I think it is not a custom rule.

Now, to handle different possibles extensions types in same page, there is something new.

When you use underscore, it keeps only the first part, but the whole name is used as JS handler name.

ex :
file_5278

Rule : file
Instance name (Rand number) : 5278
JS validator handler : file_5278

It looks tricky, but it is only for particular cases to share a unique rule file when :
- The regex is dynamic depending on the field
- The messages errors can be dynamically changed.

Please check your javascript and tell me if you can see theses file validations.

Even if you do not personalize, if you look at the code seems to do a custom validation 'domClass' => 'validate [custom [file_2200]]'. However, just remove the validation 'domClass' =>'', make the field not required and set a default image, doing it this way no longer uses the validation js but uses validation php and everything works fine.

Yes, because the validation is called this way :

validate => 'file'
Means the rule 'file' will be loaded (both JS and PHP), we speak about the physical rule file class

This rule will instance a Javascript code with a name for handling it : file_2200

domClass => validate[custom[file_2200]]
Is calling this javascript snipplet written throught the rule class (As many snipplets are wrote as there are different validation behaviors, because it is not possible to keep the same)

ruleInstance => file_2200
Is the value sent to the rule in order to know this name. It make double use, but for the moment I must leave this. My problem is that de fields and the rules cannot call each others (Totally separated code in static, so it is difficult to play with it)

All this is not really easy. I promise you it is difficult and I do not understand why Joomla is so painfull to reallize JS front validation.

I work on that, and will fix all these annoying issues soon.
The way to make it working can change a little bit, it is not stable and not 100% clean for the moment.
When I find a better way, I will update the source.

Anyway, the PHP validation works like a charm (when regex is good of course), so the validation can be skipped for those reading here and cannot solve their problems.

Remember : to avoid the validation of a particular field, you only have to remove the class name (validate[...])
If you remove the 'validate' property, you will avoid validation both sides (JS + PHP) No validation at all.

You are absolutely right. if I can fix it I'll tell you, thanks again.

@smarano :

Do you still have this issue when you generate ?
Can I close this topic ?

If you still have it, can you tell me wich Projet / Table ?