Curbuntu

@cartpauj, thanks for the quick response. I don’t see a “Save” option there. (I would upload a screenshot, but I don’t see an option to do that here.)

And even if something were saved under PrettyLink | Options, how would that allow me to edit an existing link?

Thanks for your patience.

Purchase made. Will follow up with installation question via e-mail.

So I need to purchase the Pro version? Fair enough. That’s how the “freemium” model is supposed to work.

Two quick questions about the purchase:

1. If I buy a “single” license now, can I upgrade to “multisite” (or even “unlimited”) by paying the difference (e.g., paying US$23.00 more to upgrade from single-site [US$21.99] to multisite [US$44.99])?
2. How do you define “multisite”?

Whatever your answers, I will make the purchase as soon as I hear back from you.

I’ve been digging through the documentation while I’ve been waiting for a reply. I’m guessing as a solution here, so tell me if I’m getting warm:

If I knew what variable/code WP or POM uses for the post title (I’m assuming that such a variable exists, though I don’t know what it is), then I could put that variable in the “Print Page Top HTML”, and I could style it as well.

The name of the page/post-title variable is unknown. Also unknown is whether or not I would have to upgrade to POM Pro to accomplish this. Given how well POM works, POM Pro would be worth it if it allowed what I’m trying to do.

I was just about to reply to my own posting by saying that [print-me pause_before_print="3000"] is one of the examples given in your documentation. But what you said about almost everything being cache makes sense. I’ll keep experimenting.

“Top” and “Bottom” (or “wherever”) [print-me] entries are good news indeed! Thanks.

After several failed tries with three other print plug-ins, I think Print-o-Matic is going to be the ticket for our websites. Kudos for a great product.

Many thanks for your continued quick responses.

On your documentation page, the “/” only appears in one example (Multiple Targets). I missed it there, but you used a closing-slash in replying to someone else on the forum a while ago; that mention made me curious enough to give it a try.

Is this slash-ending something that needs to appear in all the examples, or are there only certain themes which require it? Perhaps a mention of it could be made in the documentation page. And, just to make life more interesting, the “/” is not needed in the Default Target Attribute.

As for the Pause Before Print of 1500 ms (1.5 seconds) — that doesn’t seem too unreasonable. But that was for a very short test page, so I’m wondering what it will need to be for printing much longer posts. Pardon the pun, but “time will tell.”

I have a few more partially related questions, but it seems like they’d be better grouped in a separate thread.

Now that I have the PoM basics working (at least, I hope they’re still working this morning!), I’ll do some more experimentation (e.g., alt= or title=, headers, footers, etc.) before committing to PoM. It will mean adding code to upwards of 500 posts and ~20 pages. But if PoM is as solid as it appears, at a minimum, I’ll do a review, and perhaps even upgrade to PPM.

I had success with the following:

1) Putting a slash after the target command, i.e. [print-me target=".post_content"/]; along with…
2) Increasing “Pause before print” to 1500.

Why the slash?

Typo: In the previous message, I omitted the necessary “.” in the target=".post_content" examples. Sorry.

Thanks for the quick reply! I’ve tried both target='post_content' and target="post_content" to no avail.

I’ve created this page — https://finestofthewheat.org/print-o-matic-test-page-temp/ — which manifests the same problem.