cornhustlah

thank you, @topitoconnectey

looks like i was incorrectly told to use $form.wpcf7InitForm() when it’s really wpcf7.initForm( $form )

did this function change in recent times, though? because it seems like wpcf7InitForm() was once the correct function…?

i’ve been looking into this today.. i’ll report back if i find anything.

yea, your count would get messed up, but i think you could keep it in check with every skipped attachment like so:

if (get_post_type($post->ID) == 'attachment'){
  $results_count--; continue;
}

as for it working in general with your loop, i couldnt be sure what might be causing it fail unless i had a look at all of your code.. can you post your full loop here for me to view?

I ran into this problem today..

I am not using an attachment template and search results are coming up with attachment posts due to matching results in the attachment titles, so I get results that pointlessly takes the user to a page with nothing but the attachment image and the header and footer. To work around this issue, i simply added a line to my loop in search.php:

<?php while ( have_posts() ) : the_post();
if (get_post_type($post->ID) == 'attachment' || $post->post_status == 'private'){continue;}?>
...

<?php endwhile; ?>

I also noticed that private pages were also getting returned, so that’s what that post_status condition in my if statement is all about.

i just set up a new, vanilla install of WP on a different web host and have run into the same exact issue. on this new server i have also made sure safe_mode is set to “Off” before install and use of the plugin. backups work fine but restore process fails at the DB restoration function.

same here, but i get “3” .. doesnt matter which method:

https://thesite.com/wp-complete-backup/api-xxxxxxxxxxxxx/type-both
https://thesite.com/wp-complete-backup/api-xxxxxxxxxxxxx/database
https://thesite.com/wp-complete-backup/api-xxxxxxxxxxxxx/type-filesystem

AWSM.

yea i gotta say this is pretty stupid

bump.

i am also experiencing this problem .. any new news?

im experiencing this problem but not because im switching tabs .. it seems that if i have a blank post (editor content) the Visual Editor refuses to show the cursor jump to the next line on pressing “Return” after any anchor has been added. once the post is updated with some content, the number of times i tried hitting the return key will show up as new paragraphs and the cursor/return key regain their normal behavior.

i noticed this before after entering some images and brushed it off as a random inconvenience, but now i realize those pics must’ve had had anchors on them. am pretty sure it’s an actual bug, too, as i tested a couple older versions of WordPress installs and found no issue. i also tried deactivating all plugins (the only one installed, ironically, is TinyMCE Advanced) and i tried deleting my functions file (figured worth a shot since i have some random TinyMCE related functions in there), both to no avail.

this is REALLY annoying and i’d like to know if there’s a fix somewhere..

i found this solution to work easier/better:

wordpress.stackexchange.com/questions/3014/highlighting-wp-nav-menu-ancestor-class-w-o-children-in-nav-structure

i should also mention that next_posts_link(), previous_posts_link() and posts_nav_link() all pull up a faulty URL and i had to catch this custom setup for pagination:

<?php // OK, custom tax's dont work nice with query_posts (i think) but they DEF dont work nice with next_posts(), previous_posts() and  posts_nav_link()
              // SO, got the custom page nav from here:
              // https://www.ads-software.com/support/topic/adding-pagination-to-a-wp_query-loop?replies=16
        if($taxquery->max_num_pages>1){
          if ($paged > 1) { ?>
            <a href="<?php echo '?page=' . ($paged -1); //prev link ?>"><</a>
          <?php
          }
          for($i=1;$i<=$taxquery->max_num_pages;$i++){?>
            <a href="<?php echo '?page=' . $i; ?>" <?php echo ($paged==$i)? 'class="selected"':'';?>><?php echo $i;?></a>
          <?php
          }
          if($paged < $taxquery->max_num_pages){?>
            <a href="<?php echo '?page=' . ($paged + 1); //next link ?>">></a>
          <?php
          }
        }?>

which i based off this semi-related support topic:
https://www.ads-software.com/support/topic/adding-pagination-to-a-wp_query-loop?replies=16

??

i should also mention that next_posts_link(), previous_posts_link() and posts_nav_link() all pull up a faulty URL and i had to catch this custom setup for pagination:

<?php // OK, custom tax's dont work nice with query_posts (i think) but they DEF dont work nice with next_posts(), previous_posts() and  posts_nav_link()
              // SO, got the custom page nav from here:
              // https://www.ads-software.com/support/topic/adding-pagination-to-a-wp_query-loop?replies=16
        if($taxquery->max_num_pages>1){
          if ($paged > 1) { ?>
            <a href="<?php echo '?page=' . ($paged -1); //prev link ?>"><</a>
          <?php
          }
          for($i=1;$i<=$taxquery->max_num_pages;$i++){?>
            <a href="<?php echo '?page=' . $i; ?>" <?php echo ($paged==$i)? 'class="selected"':'';?>><?php echo $i;?></a>
          <?php
          }
          if($paged < $taxquery->max_num_pages){?>
            <a href="<?php echo '?page=' . ($paged + 1); //next link ?>">></a>
          <?php
          }
        }?>

which i based off this semi-related support topic:
https://www.ads-software.com/support/topic/adding-pagination-to-a-wp_query-loop?replies=16

??

OK :::

$paged = (get_query_var('paged')) ? get_query_var('paged') : 1;

should actually be:

$paged = (get_query_var('page')) ? get_query_var('page') : 1;

see here:
https://wordpress.stackexchange.com/questions/16353/custom-taxonomy-not-working-with-posts-per-page-in-new-wp-query-pagination-probl

OK :::

$paged = (get_query_var('paged')) ? get_query_var('paged') : 1;

should actually be:

$paged = (get_query_var('page')) ? get_query_var('page') : 1;

see here:
https://wordpress.stackexchange.com/questions/16353/custom-taxonomy-not-working-with-posts-per-page-in-new-wp-query-pagination-probl