On the Conditional Actions page, I suggest that we rename the "Add a predicate" tab to "New conditional action", because that is what we end up with.

Few people either know what a "predicate" is, let alone know what Ubercart means when it has a tab "Add a predicate". So as soon as people see it, they have no idea what to do, and have to search out what is meant in the documentation.

A Condition Action is defined from a Condition, and an Action, so it seems apt.

Comments

rszrama’s picture

Status: Active » Closed (won't fix)

I appreciate the concern here, but I'd have to see solid proof that "Conditional action" is less confusing than "Predicate." The proposal doesn't take into consideration the fact that there can be multiple conditions and actions and that the predicate also includes meta data like a title, description, class, weight, and trigger. All this data together makes a "Predicate" and is explained at http://www.ubercart.org/docs/user/7657/configuring_conditional_actions. Perhaps the thing to do would be to update the UI to make it explicit that what are listed on the page are in fact the existing predicates.

iantresman’s picture

There is no argument that "predicate" is probably the more appropriate word. But on the "Conditional actions" page, "New Conditional Action" is more understandable and consistent. Let's see whether anyone else comments, but thanks for the feedback.

MBroberg’s picture

I have not used Ubercart yet but I have set up quite a few Drupal sites for myself and customers, so I guess I am a perfect example.
I find both terms confusing, but "Conditional Action" has at least some context for me. I know what an Action is, although I am not familiar with using them in Drupal yet. I also know what a Condition is. So intuitively I can figure out what a Conditional Action must be. A "Predicate" is just the second half of a sentence to me, as I learned in grammar class. Subject/Predicate where predicate contains the verb. So the only thing I have to go on is it most be related to verbs? Or actions?
Drupal has a whole set of vocabulary to learn and it's almost like a foreign language. For instance, I didn't understand "node, module, block" etc. when I started and it was hard for me to set up a site. However, "menu, page, story, site" and similar terms were already in my everyday vocabulary.

I think Conditional Action makes a whole lot more sense to non-programming newbies who are just trying to get a simple site. Ubercart is already confusing enough when you first start, which is always the case with more powerful programs.
The clearer the documentation and terms, the easier it is to get going, which is usually our main goal with a module.

Thank you for the suggestion!

fymbscu’s picture

Status: Closed (won't fix) » Needs review

What is a best practice to troubleshoot when one's conditional action is not producing the desired result? I have actions for shipping quotes for USPS which don't seem to leave the page and the failures are not showing up in my logs. I also have a CA state tax rule that does not seem to be working either.

@MBroberg
You are so right when you say this is a powerful program. The steep learning curve is quite frustrating when apparently "smooth" "streamlined" features fail to work as expected.

I think I've done the due diligence and read any applicable posts I have been able to find, including the documentation. My english grammar is up to snuff. A simple testable example in code would be so helpful.

Any help greatly appreciated.

Regards,

Mark Harrison

tr’s picture

Status: Needs review » Closed (won't fix)

"needs review" is the proper status only when there's a patch to review. There's no patch here.

@fymbscu: As for your other questions, they are unrelated to the subject of this thread. Please open a support request issue here or on ubercart.org if you need help with conditional actions.