Hello,
on two projects, entering data into the form, it throws the error "jqv: custom rule not found". Reading in the forum I found several solutions, but none work in my case. In particular, I tried deleting fields upload images and files (the ones that give error) and make the switch from jquery to mootools to recreate the fields, to redo the switch from mootools to jquery. I tried to do is to try the case without the project in sendbox, is trying it at each step and the errors still occur. One of the two projects also presents the error of several tens of fields, then delete and rebuild it would be pretty hard. Suggestions?

thanks
Akasha

Which version are you in?

Could you post your entire config please?

I'm having the same problem. Tried a brand new project, 1 table, 1 file upload wizard field. I get the "custom rule not found..." error when i run it on the sandbox, as well as download/install on J2.5. I'm using the "CMS" version of Cook, not the beta.

Hi there
just thought i would help clear this one up a little
audibleid asked which version of Cook are your using

on your projects page in the builder
look at the joomla compatibility its either
- Cook 1.5 compatible with (Joomla 1.6/1.7/2.5),
- Cook 2.0 beta => compatible with joomla 2.5 only
- which one is selected?

Also on your projects page the config details that will help are located on the config tab
- it helps if we know ALL settings listed on the config tab such as Framework => MooTools

@ Akasha
I am only guessing at present but perhaps you are building under Cook 1.5?
Try Cook 2.0
tell us a little bit more about your settings / properties on the image and file uploads
- i have seen the default settings not be maintained if you view the properties

@ gdpodesta "brand new project" default build is Cook 1.5 (CMS Version)
-> did you try the build under Cook 2.0
-> result under 2.0 build
-> did you define any of the options for file upload

Biting my nails waiting for the "beta" part of the newer version to be gone before I invest my time in the generated code, so in the meantime i'm using "Cook 1.5 compatible with (Joomla 1.6/1.7/2.5),"

JS Frame Work: jQuery, tried Mootools as well
Form Style :Condensed
Features: Reduced
TODO: No

DB automatisms: Model
Timeout loading: 20 Seconds.

In and admin form, the error popped up immediately after focus left the file select box when clicking on the string input field. I tried quite a variety of options, beginning with none at all, and progressively adding some to see if that would help.

Thanks @BTB300!

Indeed,

BTB3000 wrote: @gdpodesta "brand new project" default build is Cook 1.5

// audibleid - "K+ for this @BTB300"
Also, (@gdpodesta) if you left the config as default, the JS framework would have been set to MooTools...

I've seen this very behaviour caused by the same thing while creating a new project today with a colleaugue.

If however, this is not the case and the JS is set to use jQuery, try switching COOK versions as suggested by @BTB300.

NOTE: I'm not 100% sure of the ill-effect 'rolling-back' a project from CK2.0b to CK1.5... It can cause issues with projects containing access and publishing fields that will result in you having to remove the fields from tables & layouts then re-add them... Again, not 100% sure why but, a shot in the dark tells me that, because the access and publishing fields have been updated in v2.0, - for instance, publishing is now an int, previously a bool in 1.5 - and the JS form validator for mootools has probably not been updated to account for these changes. Hence it throws the JQV error message as it's expecting to be validated by jQuery since jQuery is Cook's preferred JS.

Anyway, this is speculation but it would perfectly explain the behaviour you describe and that I experienced earlier.

Hope this helps and thanks once again @BTB3000!

Gez

Also, have you looked in the script panael of dev tools... If I remember correctly, you'll be getting a console error stating that jQuery.[Something] is not function.

DB automatisms: Model
Timeout loading: 20 Seconds.

I don't think these options are applicable in V1.5 in any case - they are V2.0 features.

BTW, other fields may have been updated in the new version too, not just the publishing and access.

Hope this helps!

Gez

You're right about Mootools being the default, which is where i'd originally been getting the errors, so tried jQuery with the same outcome..

I'm using CK1.5 because I've got a fair amount of customizing to do, and won't be able to easily upgrade the code to 2.0 when it's ready, so wanted to avoid any unknown issues that are still part of the beta.

If I understand you correctly, youre suggesting to build it in 2.0 once, then roll back to 2.5? i have no problem reinstalling numerous times at this point because I haven't started the customization on my end yet.

I'd give some serious consideration to building your component with CK2.0b - @admin is baking his heart out under the hood of the framework at the moment to make what I believe to be the last few tweaks and you'll notice that the tickets concerning version 2.0b are very few and far between these days. All of the new features in 2.0b, far outweigh the very slight changes required now to fix some minor issues (IMHO).

If I understand you correctly, youre suggesting to build it in 2.0 once, then roll back to 2.5? i have no problem reinstalling numerous times at this point because I haven't started the customization on my end yet.

I meant, once in cook 2.0b, try not to rollback to Cook 1.5 as it can result in having to rebuild certain fields because of quite drastic core changes in how certain fields work.

Hope it helps,

Gez

audibleid wrote: Also, have you looked in the script panel of dev tools...? If I remember correctly, you'll be getting a console error stating that jQuery.[Something] is not function.

Hi there as for the publish and access field differences I removed the old publish field from the wizard ONLY not the table
Then drag the publish field back to wizard and it changes it to published

Never have had to remove and rebuild a field from my data base when changing between Cook versions

I had to roll back to 1.5 Cook for some reason and never seen issues with published and access after completing the above and didn't have to rebuild fields again

Thanks @BTB3000!

As for your error I see you posted similar issue about. Config images or uploads from my experience I have seen this error when there is an image or file upload in the layout (1.5 build)

Is your other post related to the same problem we are working on?

Do you have this error on any other layouts without an image or file upload

I would not recommend this for all issues but I recently fixed two issues by flushing the sandbox data set worth a try... But Can't say it will fix it for you

Are you defining the rename properties using the guides in the properties type them exactly as they are listed such as {ALIAS}.{EXT}

If you define it as {MYFIELDNAME}.{DOC} it will not work

DB automatisms: Model

even though they are Cook 2.0+ specific
DB automatisms??? In Cook 1.5 aren't they in table

Found this -> www.j-cook.pro/forum/18-closed-tickets/3...mit=10&start=10#5187
Admin says Move to Cook V2.0 it Supports j 1.6, 1.7 as well and closed similar ticket as validator now uses j-query