roothost

Nobody able to help?

Let’s try again, it’s the code inside the <small> tag that isn’t working via the template.

<li>
          <?php if( get_field('hide_single_page') ) { ?>
          <?php the_post_thumbnail(); ?>
          <?php } else { ?>
          <a href="<?php the_permalink(); ?>"><?php the_post_thumbnail(); ?>
          <?php } ?>  
          <div></div>  
          <span><?php the_title(); ?><br />
          <?php foreach( $posts as $post ): 

        setup_postdata( $post )

        ?>
          <small><?php
$args = [
    'orderby' => 'parent', 
    'order'   => 'DESC' 
];
$terms  = wp_get_object_terms( $post->ID, 'band', $args );
$names  = wp_list_pluck( $terms, 'name' );
$output = implode( ', ', $names );
echo $output; ?></small>
          <?php endforeach; ?>
          </span>
          <?php if( get_field('hide_single_page') ) { ?>
          <?php } else { ?>
          </a>
          <?php } ?>  
        </li>

Hi Craig,

wp_footer has always been there though, that’s the weird thing?

The only change to this site in the last week was upgrading to PHP7, since then the plugin stopped working.

Hi Craig,

I have fixed this by ticking the box that says “Are you using an Ajax powered theme?”.

Regards

Hi, also not working for me. See https://www.premmdesign.co.uk/news/

We recently upgraded to PHP7, but I checked the site after and it seemed to be working fine?

So far I have checked in Chrome, FF, Safari on mac.

Any ideas?

Thanks

Of course, so simple ??

Many thanks!

I also cannot get this to work?

There are no instructions in the plugin, or on this site detailing how exactly to implement this? Unless I’m missing something…

There are no errors in the console.

Strange, has there been an automatic update to Yoast overnight/in the last hour?

It seems to be working as normal now?

See my latest post, it seems to be a conflict with WordFence (on my installs at least).

We tried that earlier, and just tried again. The problem persists all the while WordFence is activated…

I swear, when testing this plugin a few weeks ago, it worked? Installing on a live site yesterday alerted me to the fact that something is broken.

When is a fix likely on this? Still getting the error here…

Jenny has pretty much covered everything above, but one thing I will say is that you should never edit a file within a plugin.

Whilst it may work, and achieve what you intended, what happens when you update that plugin to the latest version? That’s right, it overwrites any custom edits you may have made.

There are always various hooks you can use to override plugin functions, which can be called via functions.php and the link above gives you all you need to know to copy the templates files over in to your theme.

Please see screenshot at https://drive.google.com/file/d/0B4oBv3qcwOmRenBuUjVQeUhYQWc/edit?usp=sharing you will notice the grey circle just underneath media library that keeps spinning.

If I deactivate the slider plugin, it works straight away.

Thanks

Simon

Hi Tom,

Thanks for your reply, this is what I get when clicking console, nothing else gets added when i click add featured image.

Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi) post.php?post=271&action=edit:1
Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi) post.php?post=271&action=edit:114
Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi) post.php?post=271&action=edit:533
2
Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi)