Stephen Rider

Hi — You should wrap the quote in a <span class="pullquote">, not an aside. The plugin looks for the Span and creates the pull-quote in an Aside.

If you still have trouble, give me a specific page on your site where you’ve done it and maybe I’ll be able to see the problem.

See version 2.6

1.3.1 has a fix for themes that don’t call the comment_form_after_fields hook.

Marking this “Resolved”.

Okay, here’s a guess: In the latter photo, you have a different type of nesting with the HTML tags.

If you start with this:

P
..SPAN class=”pullquote”
/P

You get:

ASIDE (pullquote text) /ASIDE
P
..SPAN
/P

That is, the pull-quote is created before the *parent* of the span. Hopefully that will help you adjust the structure of you Theme.

Hi Blair —

I will add an option in the next release that lets you move it to the footer instead of the header. That will solve your problem.

In the meantime, you can fix it by modifying the plugin file. Open graceful-pull-quotes.php and find the following line:

add_action( 'wp_head', array( &$this, 'wp_head' ) );

Change it to:
add_action( 'wp_print_footer_scripts', array( &$this, 'wp_head' ) );

Of course the next plugin update will undo this hack, but then you should be able to go into Settings and click a checkbox to do this.

5against4: My apology for the non-response. I didn’t get a notification of the new topic, and only noticed it today because I was on the page for other reasons.

As I said in the previous comment: I’ll see what I can do about adding a fallback into the system so that older themes work the way they did previously.

Short of hacking the plugin, you would not be able to do it. In terms of code, it appears to simply be a matter of moving the script tags from the header to the footer of the page, which may work fine but may cause problems in certain themes.

That being said, I believe Google is being overly cautious with this warning. Yes, you’re loading a script (from the same server as the rest of your site), but very little actually runs until after the DOM is fully loaded. In fact, all that runs before then is a JS script that tells it to run something after the DOM is loaded. ??

There’s really nothing I can tell from an image. The pull-quotes don’t look bad, but I don’t know what your intent is. Do the built-in pull-quote styles look normal?

If they do then this really is more of a request for help using CSS itself, which is kind of beyond the scope of plugin support.

My best guess is that this happened after the recent plugin update, yes? That would suggest that you’re using an older theme, or one that doesn’t have all the standard WordPress hooks. Look in your theme at the code that draws the comment form. If you’re using WordPress’s built-in comment_form() function, (and WordPress itself is reasonably updated), this should work fine. But if you’re using a custom Comment Form, you need to ensure that the following appears just before the Submit button is output:
do_action( 'comment_form_after_fields' );

This plugin was recently changed to attach the question to the following hook in the theme: comment_form_after_fields

All that being said, I’ll see what I can do about adding a fallback into the system so that older themes work the way they did previously.

I don’t understand the question. You mean you want it to become part of the Jetpack plugin?

You’d have to talk to the Jetpack people for that.

Adding Quiz to user registration is an interesting idea. Thanks — I’ll keep it in mind.

Cool! ??

The link you gave is broken. New link is here: “Top 5 WordPress Plugins for Coders”

What calls are missed? Is there a new type of “deprecated” that the plugin doesn’t know about?

Related: https://www.ads-software.com/support/topic/buddypress-integration-problem