Forum Replies Created

Viewing 15 replies - 1 through 15 (of 16 total)
  • Thanks for fixing this. Very puzzling to track down:

    Errors: Edge (Windows), Chrome (Mac)
    OK: Firefox (both), Chrome (Windows)

    Makes me a bit reluctant to do any ES6 stuff just yet. 😉

    Thread Starter maxwelton

    (@maxwelton)

    I’m using the plugin “query monitor” and this is its output to the JS console:

    === PHP Error in AJAX Response === query-monitor.js:198:5
    Object {
       type: "notice"
       message: "Undefined index: show_excerpt"
       file: "\wp-content\plugins\feature-a-page-widget\inc\fpw_widget_class.php"
       line: 224
       stack: Array[4]
          0: FPW_Widget->update()
          1: WP_Widget->update_callback()
          2: wp_ajax_save_widget()
          3: do_action('wp_ajax_save-widget')
    }

    Lines 222 – 224 just need some isset() checks, I think:

    $instance['show_title'] = (bool) $new_instance['show_title'];
    $instance['show_image'] = (bool) $new_instance['show_image'];
    $instance['show_excerpt'] = (bool) $new_instance['show_excerpt'];
    $instance['show_read_more'] = (bool) $new_instance['show_read_more'];

    I get a warning per unchecked option when saving the widget in admin->appearance->widgets.

    Thread Starter maxwelton

    (@maxwelton)

    Just as an update, this notice seems to pop anytime a new menu location is defined and is then a new menu is associated with that location via appearance -> menus.

    Definitely an edge case. Most likely to be seen by someone working on a theme with debug on and showing notices…but a plugin installed after mmm which adds a new menu and theme location might trigger this? Dunno. Anyway, easy enough to solve with an isset() check or whatever.

    Thanks again.

    Thread Starter maxwelton

    (@maxwelton)

    No worries, this is an excellent plugin all the way ’round.

    Thread Starter maxwelton

    (@maxwelton)

    Many thanks for the updates!

    Same.

    Thread Starter maxwelton

    (@maxwelton)

    Thanks. Just found a few more…on the player management admin screen:

    Strict Standards: Declaration of JWP6_Form_Field_Uneditable::validate() should be compatible with JWP6_Form_Field::validate($post_data) in \wp-content\plugins\jw-player-plugin-for-wordpress\jwp6\jwp6-class-form-field.php on line 128 
    
    Strict Standards: Declaration of JWP6_Form_Field_Select::render_field() should be compatible with JWP6_Form_Field::render_field($value = NULL) in \wp-content\plugins\jw-player-plugin-for-wordpress\jwp6\jwp6-class-form-field.php on line 171 
    
    Strict Standards: Declaration of JWP6_Form_Field_Radio::render_field() should be compatible with JWP6_Form_Field::render_field($value = NULL) in \wp-content\plugins\jw-player-plugin-for-wordpress\jwp6\jwp6-class-form-field.php on line 221 
    
    Strict Standards: Declaration of JWP6_Form_Field_Toggle::render_field() should be compatible with JWP6_Form_Field::render_field($value = NULL) in \wp-content\plugins\jw-player-plugin-for-wordpress\jwp6\jwp6-class-form-field.php on line 243 
    
    Strict Standards: Declaration of JWP6_Admin_Page_Players::process_post_data() should be compatible with JWP6_Admin_Page::process_post_data($post_data, $save_to_option = true) in \wp-content\plugins\jw-player-plugin-for-wordpress\jwp6\jwp6-class-admin-page-players.php on line 627

    The fix for this, BTW, is to remove the explode function to its own line:

    // Ajax actions
    $end_url = explode( '/', $_SERVER['PHP_SELF'] );
    if ( is_admin() && 'admin-ajax.php' == end( $end_url ) ) {

    This plugin will not install properly or run in WP debug mode because of this error. Be nice to fix this one, it’s a little ironic (not perfect myself, of course) that a plugin that measures efficiency creates an inefficiency.

    These are not “real” taxonomies or custom post types, unfortunately. Any other plugin installed which modifies custom post types either conflicts with this one (ie, causes types to stop working) or is completely ignored. I like the ease of this plugin, but just today got screwed by this unexpected aspect (I guess I should have looked under the hood to see what was really going on)–so am going to have to take “Types” out of my toolbox. If I write a plugin to convert “Types” custom data to “real” WP data, I’ll post it on WP. (Don’t hold your breath!)

    Does not work on multisite.

    I may have a fix for this. From what I can see, there is a new piece of base site url information that the importer doesn’t know about; or, perhaps, not being a multi-site expert, it may have something to do with how you configure your media storage. In any case, here are the mods that worked for me.

    In the “wordpress importer 0.6.1” plugin, I had to modify two files in the importer plugin:

    In parsers.php:

    After line 92 (look for ‘$base_url’ in line 92), add these two lines:

    $base_blog_url = $xml->xpath('/rss/channel/wp:base_blog_url');
    $base_blog_url = (string) trim( $base_blog_url[0] );

    In wordpress-importer.php:

    After line 50 (“$base_url…”) add a new line:

    var $base_blog_url = '';

    Now, change line 156 (“$this->base_url = esc_url( $import_data[‘base_url’] );”) to:

    $this->base_url = ! empty($import_data['base_blog_url']) ? esc_url( $import_data['base_blog_url'] ) : esc_url( $import_data['base_url'] );

    That allowed me to import my content. Hope this works for you.

    It looks like a few “prepare” calls throughout the plugin need to be modified, not just that one instance.

    If you want to edit the plugin yourself to work as it was before until an update comes out, the following seems to work–no guarantees. I have not added or deleted any icons since making this mod, I just wanted my admin area and public-facing pages to not show the error(s).

    Line 1047, add “,0” right before the final two parens:

    $wpdb->query($wpdb->prepare("CREATE TABLE IF NOT EXISTS$wpdb->ig_caticons(cat_idINT NOT NULL ,priorityINT NOT NULL ,iconTEXT NOT NULL ,small_iconTEXT NOT NULL , PRIMARY KEY (cat_id))",0));

    Line 1338, add “,0” similarly:

    $datas = $wpdb->get_results($wpdb->prepare("SELECT cat_id, priority, icon, small_icon FROM $wpdb->ig_caticons",0));

    I see the same error, just so you know it’s not a one-off thing.

    Thread Starter maxwelton

    (@maxwelton)

    Just some further info: If I pop an alert here (in the flexible-maps.js file, I changed the php file to look to this instead of the minimized version for debugging reasons):

    google.maps.event.addListener(kmlLayer, 'click', function(kmlEvent) {
       alert(kmlEvent.featureData.description);

    I do get the contents of the pop-up. If I do something like this:

    kmlEvent.featureData.description = 'hi';
    alert(kmlEvent.featureData.description);

    I get ‘hi’ as an alert, but the contents of the popup are not changed at all. I get the alert before the pop-up shows up on the map, but, like I say, the content of the pop-up is unchanged.

Viewing 15 replies - 1 through 15 (of 16 total)