gulliver

For anyone else it might help, I’ll add Brandon’s solution here:

If you're using jQuery to load content via Ajax, I have found this to be a pretty simple solution:

$(document).ajaxComplete(function() {
//creates the share icons
stButtons.locateElements();
});

This will fire after every ajax call. You can also call this function in the 'complete' function of jQuery.ajax() settings.

Thanks.
It’s part of core code, with no specific css selector and so trying to remove it is probably as easy as trying to hide.

Thanks got the link. It’s useful for removing an entire meta box, but not parts thereof. No worries, thanks anyway.

The menu order seems to be legacy code, of little use in modern versions with more flexible menu options.

Thanks, Gino.

As mentioned in our email contact, it works better than it did, but still has errors.

On submit, it correctly adds an item to the cart and loads a new PayPal tab.
But it also displays the error message of ‘Failed to submit!’, which vanishes from screen within a few seconds.

In browsers where focus switches to the new tab that error message probably isn’t seen, because by the time the user has switched back to the original tab the message has gone.

In the absence of any other suggestions, I’m tempted to change the timing of that message so it’s removed more quickly.

@girlieworks… Thanks.

@staartmees… Also, thanks – and, more importantly, I apologize for doubting you.

Somewhere between ‘old age, stupidity, dust on screen and glasses’ I’d incorrectly pasted a quicktag with just a single (rather than double) dash. Hence it didn’t work.

And being totally honest, I’d forgotten that <!–nextpage–> worked on pages and thought it just for posts. Clearly I must have once known it, because my custom theme has the necessary code, appropriately tweaked, and which I must have added years ago.

Duh me!

Anyway, thanks to you both for saving me from myself. 😉

Thanks, but…

<!–more–> defines the pre-‘read more’ break-point in places where the whole post isn’t shown.

<!–nextpage–> will split a post into multiple pages.

UPDATE…

With a clearer head, I think I now understand.

Create cpt for ‘host’.
Create cpt for ‘shows’.
Register custom taxonomy for ‘show’.

So when I ‘add new show’ the edit screen will list the hosts so that I can select the appropriate one and assign the show to that host.
Maybe I’m wrong, but it’s time to experiment.

UPDATE: I’ll answer my own post in case it helps somebody else later.

I’ve used this (much of which somebody elsewhere supplied):

<?php if(get_post_type() == 'page'): // If a page. ?>
<p><a href="<?php the_permalink(); ?>" title="permalink">Permalink</a>.</p>

<?php elseif(get_post_type() == 'post'): // If a post. ?>
<p><a href="<?php the_permalink(); ?>" title="permalink">Added</a> <?php the_time('F j, Y') ?>.</p>
<?php endif; ?>

An option is to replace ‘Permalink’ (for page) with <?php echo get_the_title(); ?>, or leave blank.