• First impression: Wow! These guys made something impressive! Even the free version looks great. Let’s test a bit and go get the pro!

    But then, right after the first click:

    Notice: Undefined index: custom_style in plugins\formidable\classes\views\frm-entries\form.php on line 4

    Notice: Undefined index: before_html in plugins\formidable\classes\views\frm-entries\form.php on line 11

    Notice: Undefined index: after_html in plugins\formidable\classes\views\frm-entries\form.php on line 55

    and then I look in the code…. what a mess…

    Gentlemen, you just lost a client.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Steph Wells


    Try as I may, I’m not able to replicate. Which version are you using, and what did you do to cause this?

    Would you like to provide more detail about why you feel the code is a mess?

    Which version? The only you have here. Just installed yesterday.
    Cannot reproduce? Turn debug output on. Or just look at those lines in your code, and you will see that you do not check if the values exist.

    About the “mess”:

    You write things like
    return self::display_forms_list($params, ”, false, false, $errors);
    having void display_forms_list. So, what are you returning exactly?

    Even worse example of the same:
    __FRMSAVED=”<?php esc_attr(_e(‘Saved’, ‘formidable’)) ?>”;
    What esc_attr? _e() does not return anything. It prints.

    setup_edit_vars($record, $table, $fields=”
    $fields is array. Why default value is string?

    And so on. That in my eyes is a mess.

    In addition to that, you infest the global space with your variables and defines. I do not want to use a plugin that has so many globals. Especially, with such simple prefix, ‘frm_’. Defines must be replaced with class constants. All globals must be replaced with only one, if you really need it.


    Plugin Author Steph Wells


    self::display_forms_list() returns the list of forms. I’m not seeing the problem there.

    You’re right that esc_attr(_e( is bad and incorrect. This is a simple bug that has already been fixed in v1.07.02. We have removed a lot of the globals and defines as well in v1.07.02.

    We are continually working to improve this plugin, both what you see and what you don’t. We appreciate your suggestion of combining the globals into one, and move defines to constants. We don’t profess to know everything, and pointers on improvement are appreciated. Thanks!

    Plugin Author Steph Wells


    By the way, the undefined index messages look like a plugin conflict. We’d appreciate it if you would go through your plugins and tell us which one is causing the problem. You’re right that there isn’t a check there to see if the value exists, but it is checked upstream when the $values array is set.

    Plugin Author Steph Wells


    We found your list of notices by the way. You were trying to add an entry to a form with no fields.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Very strange…’ is closed to new replies.