Stephen Rider

To be clear: I don’t mind the “freemium” model for plugins, but I dislike that a) the developer actively conceals this fact until after you install it, and b) there are no fewer than three LARGE “upgrade” buttons on the plugin’s small admin page.

Not only laughably aggressive promotion of the PRO VERSION, but laughably aggressive policing of reviews. Note the reviewer above at best said “it works”, which the developer restates as “you admitted that our plugin [is] pretty awesome”. Um… no he didn’t. He said nothing of the sort. ::smh::

Not really an issue report, so marking “Resolved”.

Nice tip! Thanks!

Sorry for the delay — not sure why, but WP.org doesn’t inform me of new issues on this site. :-\

Anyway… could you show me a page where you’re having the problem? I’m not sure why it wouldn’t work, but the most common culprit is that the wp-header hook is missing, so the JavaScript doesn’t load (or something else preventing the JavaScript from loading).

Do you know what update (version) caused the problem?

Another possibility is that you’re not doing the span correctly; but if it WAS working before and then stopped, that’s probably not the problem.

I’m on PHP 5.3 — That the highest my host provides at the moment. Too bad.

You might consider adding a version test to the plugin itself so that it gives the user an informative error message, rather than the fatal error I got.

The Jetpack plugin by Automattic has a module that handles subscriptions in a similar manner. But that’s a “does everything” style plugin and may not be suitable for all sites; so this one may still be useful for some.

Hey it’s open source, right? Why not fork it and create your own updated version and share it?

If it was working before and then suddenly stopped, I can only imagine that there was an update to the theme that did this. Most likely the theme contains CSS that styles objects with a class of “pullquote”.

The first thing you might try is to change the “HTML Container” setting. If you’re currently using <blockquote>, change it to <aside>, for example.

If that doesn’t work, try changing the “Class selector for default pull-quote” setting. Use something other than “pullquote”. If you do this, you will also have to alter the CSS on your site. (If you have Automattic’s “Jetpack” plugin installed, it has a “Custom CSS” module that will allow you to do this easily. To do this, create your own custom Pullquote CSS and then activate the “Do not link CSS” setting in Pull-Quotes settings to turn off the built-in CSS.)

Marking this resolved. Straightforward issue.

Okay, found the problem — or at least narrowed it down.

I have an unusual setup in one aspect — I run multiple sites off of a single codebase that is symlinked to multiple sites. That is, the “wp” folder in the above-described setup is actually a symlink.

Works great in all other ways that I’ve observed, but triggers the “cheating” message for some reason. If I can figure out a fix I may submit to trac as a bugfix.

A bug was unfortunately introduced in a recent update which affected some older themes. It has since been fixed.

Thanks for the comments!

marking Resolved

It does duplicate content, and it is supposed to. This is the nature of pull-quotes.

Where it does NOT duplicate content is in RSS feeds and similar, where the unformatted repeated text would read very strangely. The Pull-Quote is created with JavaScript, which does no run within the context of RSS.

There are a couple things to check. First off, switch to a different theme and see if it works there. If it does, then your theme is part of the issue. If it’s still wrong in a different theme, then the plugin should probably be reinstalled.

I’ve tried to put in some good “reset” styles in the CSS, but it’s possible that you have styles set for Blockquotes or Asides that are bleeding into the pull-quote formatting.

I suppose the real question is: What did you change between yesterday (when it worked) and today?