In the middle of working on a new newbb block system I stuck in a simple obstacle:
I need to add a js statement to onsubmit event of blockform.
I try to add something like this:
$statusEleName = $statusEle->getName();
$statusEle->customValidationCode[] = "if ( myform.{$statusEleName}.value == '' ) { myform.{$statusEleName}.value = 'all';}";
but it never rendered.
there is a new blockform class in 2.6 but it failed to render js codes too.
see in XOOPS26/class/xoopsform/blockform.php

If i use a separate nest form inside blockform it show codes but it seems it is useless in a nested form.
see:


It seems there is no easy way to add js in a block form.

I found that it is a serious bug in both xoops core and modules multi-select elements in forms.
There is not any validation to prevent the form return on submit when user dont select any option (the value is null).
The issue is in XoopsFormSelect class when multiple selections is allowed.
Also i find it in some recent modules like publisher blocks in category select box element.
It is a serious issue.
Anybody have the best solution for it?

ok I end up with a js solution.



It will prevent user to select nothing.
IMO this solution is good right now.

But what we can do for a "XoopsFormCheckBox"? I mean when user dont select any option.

I enhance this solution and used it in newbb.

but it need to be addressed iby the core team in 2.6

The main issue is:
we cannot add customValidationCode to xoopsFormValidate_blockform

Also we need to enhance the xoopsform class to accept all properties.

eg we need this function for set and get in selectbox form.

set function:

get function:


then in render function we have this:


then we can use it like this:

Quote:
Can you please add it to Bugs or Feature Requests in SourceForge, so we can keep track of this?

As always, please post there the link to this post, and then post the link to the request here, so it's easier to follow-up.

Quote:

Yes. It was my intention too. but I always prefer to discuss here first because it will bright up the issue more.
actually there is one bug and at least one feature to add.
The bug is serious.
XoopsForm classes cannot add anything to blockform
It means a module developer cannot add anything to blockform.

also the feature request.
More set and get functions in XoopsForm Classes

maybe we can have another feature request for accepting more functionality and pre-defined js codes in XoopsForm for validation? anybody have any suggestion?

@irmtfan

could you test the following modification in your configuration ?

Just add the 2 lines starting with @


then it would be possible to use for each element added to blockform either customValidationCode[] or either isRequired()

the root of this problem is we cannot add any element to $form defined in system module.
see in
xoops26\modules\system\class\form\block.php
and
xoops255\modules\system\class\block.php
in function getForm around line 138 ( in xoops255)


so it used getOptions function and a nested form is created.
i still cannot find any good solution to access to $form

I don't think it is the final solution, but at the moment, in 2.6.0 alpha2 there is a file named modules/system/blocks/system_blocks.php
Inside there are 2 kind of specific functions b_xxx_show and b_xxx_edit. The former is for display specific content of a block and the later is for editing.

I have modified the b_system_info_edit

which is the code found in main.php block


As You see we can add specific elements and with the parameter 'true' in addElement we can set Rquired to true.

Then with my modification in the render method in blockform.php. The specific fields are displayed and in the html file there are javascript scripts to check if the fields are empty and display an erreur message, in the option part of the form.

I hope this could help.

Sorry my bad.
I didnt test "is required" in 2.6 because my main problem was adding some js codes as customValidationCode.

Now i see you are right and required is working in 2.6
I still cannot find why it is working in 2.6 but not in 2.5.5
for example see publisher
In 2.6 "is required" in publisher blocks worked
In 2.5.5 publisher module by using the same form for blocks "is required" is not working.

but it is not important for me.
the main bug still remain.
adding a customValidationCode to xoopsFormValidate_blockform is not possible.
try to change your code by this:


js codes will not add to function xoopsFormValidate_blockform()

edit:
search function xoopsFormValidate in the source code page and you can see these codes will be added to
function xoopsFormValidate_() which is the main bug because this is the nested form.(another form inside the blockform)
I hope you understand me.