ibes

We ended up using wp webhooks.

There could at least be a hook to deaktivate the REST-API part …

I figured it out.
It’s a problem that Polylang caused while fetching the post-title

I am now in contact with the paid support.

I can do screenshots but I am not sure what part of the screenshot could help?

As the preview works I am 99% sure I do not have a typing error.

The one has a subject line as expected – the other says “Kein Betreff” which is German for “no subject” – I guess my mail client does that?!
If I add something besides the shortcode the prefix ends up in the subject but the shortcode stays blank.

If you can give me instructions on what to focus on in the screenshots I am happy to provide them.

Support gave me following German answer:

Allgemein l?sst sich die Funktion des WooCommerce-Plugins herunterbrechen auf folgende Punkte:

– Das Plugin synchronisiert Empf?nger- und Kaufdaten, sowie den Status des Empf?ngers (Aktiv / Inaktiv) per REST API und dies immer aktuell
– Zudem k?nnen Produkte vie Mycontent direkt in den Newsletter eingebunden werden
– Das Plugin richtet beim Kauf eine Checkbox ein mit der der Newsletter bestellt werden kann

Das Plugin funktioniert auf Basis unserer REST-API
https://rest.cleverreach.com/howto/
https://rest.cleverreach.com/explorer/v3

in Kombination mit der MyContent-Schnittstelle:
https://support.cleverreach.de/hc/de/articles/202373141

@blackboxz
The both plugins do the same job but in different ways.
Both have a ”the_subtitle” function but with different implementations.

I thought about making both compatible but than just solved it for my customer.

All together you are right that there needs to be some modification on the templates.
As far as I remember it did not seem to be possible to just write an ”adapter” eg overwrite the function call of one plugin to act like the other. But as said I did not put big effort in it.

Maybe people who went that way can try to document their process.

@philiparthurmoore
great that you prioritise family.
In reality, that is far more important than subtitles.

If I would already be educated what Gutenberg needs to have Subtitles work with it, I would have given you a hand to make it compatible.

All the best.

Unfortunately my clients didn’t want to wait longer so they too wanted to switch to “WP Subtitle”.

As a exercise I wrote a plugin for the move:
https://github.com/ibes/subtitles-to-wp-subtitle

In the end, it is just a very extensive wrap around:

UPDATE YOUR_PREFIX_postmeta SET meta_key = 'wps_subtitle' WHERE meta_key = '_subtitle'

Hi Sergii – thanks for the hot fix. (Didn’t try it so far, but already thank you for sharing).

That also answers the question: Is it still possible to use the plugin. It seemed to not be possible anymore as Medium seems to close its doors for posting from the outside. But it’s still possible – yeah.

If I happen to use the plugin, I am willing to help fixing stuff.

@pinedev – what about a github for your hotfix?

Oh – is there a way to figure that out?

Maybe I just updated a plugin that should not have been updated …

Awesome

That will boost the usefulness of the plugin a lot.

Let me know if you could need some beta tester

No, there is not update.

I mailed the idea/request again a couple of days ago.

Just the know answer that the request is forwarded.

For my project, that is the missing feature that makes the difference between an unusable plugin and helpful plugin.

To do a single label will at least take 30 seconds to generate and print manually.
For 50 orders a day, that is about half an hour – that is wasted time.

With bulk export that could be done in 1 minute.

Thanks for that review.

So my search goes on.

I am searching for a plugin that helps me motivate my clients to keep their library clean/organized.
And therefore they need to feel the beauty of an organized library when it’s about to insert media.
As this plugin doesn’t come with the insertion in the free version and the preview look like upselling everywhere the search goes on for me.

Yes, unfortunately the buttons look a bit shitty.

But the way the tables collide is solved quite clever.

… ok, done.

not perfect but was a nice exercise. And if the client ends up wanting more features we will go pro.
The code looks very organized so I am sure you guys know what you are doing.

For us it is a breaking error.

Line 51 tries to trim a variable. Some lines later there is a check if the variable is an array (so it seems likely that the variable is an array – some of the times).
I am quite sure that the script breaks if the variable is an array – as trim is not built for arrays.

Quick fix: wrap line 51 in an if-statement.
Replace line 51 with:

if ( is_string( $value ) ) {
      $value = trim( $value );
 }