Universal Module Input Rules

[xison]

Hi there,

 

I'm attempting to make-shift an order form for Dedicated Servers utilizing the Universal Module.

 

So far I have it working the way I want, however the input rules do not appear to be working. I am betting I am simply doing it wrong, but it may be a bug, I'm not sure.

 

Anyway, I've created a product under the Universal Module called "Dedicated Server", with the following Service Options:

1) Hostname - Name 'hostname' - Regular Input Box - Required: Yes - Encrypt: No

2) Operating System - Name 'operating_system' - Select Box - Required: Yes - Encrypt: No

3) Special Instructions - Name 'instructions' - Textarea - Required: No - Encrypt: No

 

In the input rules, I have the following, based on the example in the documentation here: http://docs.blesta.com/display/user/Universal+Module

{"hostname":{
    "valid":{
        "rule":"isEmpty",
        "negate":true,
        "message":"You must enter a Hostname."
    }
}}

According to the documentation, it should not allow the 'hostname' parameter to go through if it is empty, but it does on it's merry little way.

 

Am I doing something wrong?

 

Thanks.

[xison]

... anyone?

[Michael]

Hi there,

 

I'm attempting to make-shift an order form for Dedicated Servers utilizing the Universal Module.

 

So far I have it working the way I want, however the input rules do not appear to be working. I am betting I am simply doing it wrong, but it may be a bug, I'm not sure.

 

Anyway, I've created a product under the Universal Module called "Dedicated Server", with the following Service Options:

1) Hostname - Name 'hostname' - Regular Input Box - Required: Yes - Encrypt: No

2) Operating System - Name 'operating_system' - Select Box - Required: Yes - Encrypt: No

3) Special Instructions - Name 'instructions' - Textarea - Required: No - Encrypt: No

 

In the input rules, I have the following, based on the example in the documentation here: http://docs.blesta.com/display/user/Universal+Module

{"hostname":{
    "valid":{
        "rule":"isEmpty",
        "negate":true,
        "message":"You must enter a Hostname."
    }
}}

According to the documentation, it should not allow the 'hostname' parameter to go through if it is empty, but it does on it's merry little way.

 

Am I doing something wrong?

 

Thanks.

 

I'm not familiar with this, however try changing hostname to: service_field_1

[xison]

That has no effect.

Paul? Cody? Tyson?

[Ken]

In the input rules, I have the following, based on the example in the documentation here: http://docs.blesta.com/display/user/Universal+Module

The documentation for it is still being worked on but is coming last time I've heard.

[Paul]

I don't see anything inherently wrong with the way you've configured this. I think we will need to try to duplicate the issue, to see if we can confirm this as being a bug or not. Has anyone else been able to confirm?

[m0hamedessam]

I don't see anything inherently wrong with the way you've configured this. I think we will need to try to duplicate the issue, to see if we can confirm this as being a bug or not. Has anyone else been able to confirm?

i do

http://www.blesta.com/forums/index.php?/topic/856-universal-module-after-upgrading-to-v301-not-work/

[xison]

I don't see anything inherently wrong with the way you've configured this. I think we will need to try to duplicate the issue, to see if we can confirm this as being a bug or not. Has anyone else been able to confirm?

I will do some digging and provide some more info later. I'm not at my desk for a while (almost dinner time, and then family time).

I can tell you I installed the trial on v3.0.0 then upgraded using the v3.0.1 patch.

[Alex]

Has anyone else been able to confirm?

 

Yep, I can confirm that the issue persists...

 

https://fullambit.net/portal/plugin/order/main/configure/Dedicated%20Server/?pricing_id=69&group_id=6

 

{"Hostname":{
    "valid":{
        "rule":"isEmpty",
        "negate":true,
        "message":"You must enter a Hostname."
    }
}}

[Cody]

Error validation was only happening immediately before provisioning the service. We've updated the Universal module to do this validation when the form is initially submitted as well.

CORE-765 fixed for 3.0.3.

[mitsos]

This bug has not been fixed in 3.0.3. I've encountered it today while adding a product.

 

Universal module service options:

 

Label: Enter your domain

Name: cliententerdomain

Type: text

Required: Yes

Encrypt: Yes

Values: empty

 

Input rule validation:

 

{"cliententerdomain":{
                     "valid":{
                             "rule":"isEmpty","negate":true,"message":"Domain cannot be empty. We wouldn't know how to set up your product correctly."
                             }
                     }
}

 

Additional info:

tried changing the field name (see documentation) to service_field_1, uni_cliententerdomain, uni_service_field_1. (uni_ comes from viewing the source of the page. That's the actual name given to the variable)

 

Did not check this before manually applying the patch for the empty order page (as documented in http://www.blesta.com/forums/index.php?/topic/1086-oh-noes-universal-module/#entry8899). Universal module came up with an upgrade button after applying the patch, clicked upgrade then went on with configuring the product.

 

Input validation should happen as soon as you hit the Continue button, after selecting the package required, to prevent the client having to redo this step at the end of checkout.

 

"Proper" ordering flow: Select package, click select, forget to input domain, click continue, message that the domain is required pops up, client enters domain, click continue, enter customer/payment info.

 

Setting the options as the package options instead of the service options (need to change the text on the page to admin options, client options, it's too confusing as it is now) works OK. The validation happens correctly when trying it from the admin site.

[Cody]

What version of the universal module are you using?

[mitsos]

Version 1.0.8

[Michael]

Version 1.0.8

 

Your outdated.

 

• Universal Module (ver 1.0.9)
• Author: Phillips Data, Inc.

[Tyson]

Setting the options as the package options instead of the service options (need to change the text on the page to admin options, client options, it's too confusing as it is now) works OK. The validation happens correctly when trying it from the admin site.

 

Are you saying your input error rule is being validated when adding a service in the admin area, but not when adding a service via an order form?

[mitsos]

Your outdated.

 

• Universal Module (ver 1.0.9)
• Author: Phillips Data, Inc.

Not my fault:

Blesta © 2007-2013, Phillips Data, Inc.

Licensed to X

Installed Version 3.0.3

 

Universal module has been upgraded through the web gui (the upgrade button came up instead of the manage button, see my post above). Thought that was supposed to upgrade it.

 

Are you saying your input error rule is being validated when adding a service in the admin area, but not when adding a service via an order form?

Exactly. Adding a rule in the package section, with the input validation, requires me as the admin logged in to enter the hostname when manually editing the package. When "ordering" the product as a client, no validation happens.

[Michael]

Weird maybe you'll have to reinstall it to see the new version number because mine says 1.0.9. However you clicked on upgrade on the module to edit it :s

[mitsos]

Does uninstalling and reinstalling remove any packages/services or is it safe to uninstall and reinstall to test if it upgrades correctly?

[Michael]

Does uninstalling and reinstalling remove any packages/services or is it safe to uninstall and reinstall to test if it upgrades correctly?

 

Only products you made on the universal module, not the packages you made.

[Tyson]

I don't think reinstalling is necessary. It may just be a bug specific to the order form, but we'll need to try to reproduce it first. I've reopened CORE-765 to take a look into this issue.

[mitsos]

Uninstalled the universal module, and when going to modules > available, the version listed is 1.0.8. I think the validation bug is irrelevant, since I cannot upgrade to the latest module version to verify if the bug is fixed or not. As a reminder, my blesta version shows up as 3.0.3

 

 

EDIT:

Manually uploaded public_html/components/modules/universal_module overwritting the files on the server. Version 1.0.9 showed up correctly. Installed, will test and report back.

[Tyson]

I believe the latest version of the module is 1.0.8 for v3.0.3. There is a 1.0.9 for v3.0.4 of Blesta, but CubicWebs may have downloaded an update to 1.0.9 posted on the forums sometime afterward (I'm not sure).

[Michael]

I believe the latest version of the module is 1.0.8 for v3.0.3. There is a 1.0.9 for v3.0.4 of Blesta, but CubicWebs may have downloaded an update to 1.0.9 posted on the forums sometime afterward (I'm not sure).

That's weird lol. Not released but I have it :s

[mitsos]

Nope, 1.0.9 comes with 3.0.3. Taken directly from the unzipped 3.0.3.

 

Success!!! bug is fixed. The domain field is correctly validated, and a message pops up if it is empty. If a domain is written into the box, then it shows up on the next step.

 

Thank you all for your time. Another small step for man, a giant leap for mankind

 

EDIT: (trigger happy post)

 

For those in the same situation as me, don't forget to go back to packages>browse and edit all your packages to point to the correct module "thingy" (service). Otherwise nothing happens when you click select on the order form. Assuming this is due to the module being uninstalled. Easy fix.

[Tyson]

Glad you got it fixed. I guess the universal module will be v1.0.10 for v3.0.4 of Blesta then.