• Just updated to Magic Fields 2.1 and now get this error message

    Notice: Undefined index: quantity in /var/www/html2/wp-content/plugins/magic-fields-2/mf_register.php on line 74 Notice: Undefined index: quantity in /var/www/html2/wp-content/plugins/magic-fields-2/mf_register.php on line 74

    Anybody explain how to fix this?

    http://wordpress.org/extend/plugins/magic-fields-2/

Viewing 8 replies - 1 through 8 (of 8 total)
  • Did you find a solution to this?

    Thread Starter blakeyman

    (@blakeyman)

    No
    🙁

    Plugin Author hunk

    (@hunk)

    Hi, save again the custom post types

    Thread Starter blakeyman

    (@blakeyman)

    Hunk

    Can you please explain how I “save again”?

    Thread Starter blakeyman

    (@blakeyman)

    Hunk

    Can you please explain how I “save again”?

    Thread Starter blakeyman

    (@blakeyman)

    Upgraded to WP 3.8.1 and also get the (additional) errors too.

    [nb: WP “works”, this is just with this set: define(‘WP_DEBUG’, true);]

    Strict standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method mf_menu::unique_post_type() should not be called statically in /var/www/bbr.zapto.org/public_html/wp-includes/plugin.php on line 429

    Strict standards: Non-static method mf_settings::get() should not be called statically in /var/www/bbr.zapto.org/public_html/wp-content/plugins/magic-fields-2/main.php on line 135

    Strict standards: Non-static method mf_settings::get() should not be called statically in /var/www/bbr.zapto.org/public_html/wp-content/plugins/magic-fields-2/main.php on line 139

    Strict standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method mf_install::folders() should not be called statically in /var/www/bbr.zapto.org/public_html/wp-includes/plugin.php on line 429

    Thread Starter blakeyman

    (@blakeyman)

    hunk

    OK – from Magic Fields panel I “saved again”.
    That stopped error from mf_register.php on line 74

    Still getting the 4 errors from last post though.

    Thread Starter blakeyman

    (@blakeyman)

    I can send you Apache error log for more detail too…
    😉

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Error after upgrade to 2.1’ is closed to new replies.