s

Some more details about the use-case:

I set up Easy Watermark to apply the watermark only to full sizes images, I don’t want it to be applied to any other size.

But for example if I upload a small image of 900×900, and my ‘largest’ image size is 1024×1024, the original is used for both the ‘largest’ size and ‘full’ size, making the ‘largest’ image appear with a watermark too (which I don’t want).

I am not sure if I was able to explain myself in a clear way ??

Thank you @mikeschinkel, you gave me some nice and useful insights! ??

As I develop websites from scratch optimized for the client’s needs, not just install and configure themes and plugins, I need to keep up with new technologies in order to provide a fast, efficient and secure websites with all the custom features needed by the client.

So every website is unique and it requires a lot of development.

Honestly there are WordPress developers who are light-years ahead of me, and I wanted to reduce the distance. ??

I completely agree with you!

@otto42 thank you also from me!

@emilysparkle I thought the same… :/

The update sill shows up and this is not right!!

From 2.3 to 3.0 is NOT an update, but an UPGRADE (from a free version to a paid version). This should be optional and not be shown in the update page as a regular update, since it isn’t…

Is also shows up in tools like Manage WP as a regular update, but every time it throws an error because it can’t update it.

The point is: if you can’t UPDATE a FREE plugin for FREE , it should NOT appear as an update in WordPress!

@bedas
No, this is not right!!

From 2.3 to 3.0 is NOT an update, but an UPGRADE (from a free version to a paid version). This should be optional and not be shown in the update page as a regular update, since it isn’t…

Is also shows up in tools like Manage WP as a regular update, but every time it throws an error because it can’t update it.

The point is: if you can’t UPDATE a FREE plugin for FREE , it should NOT appear as an update in WordPress!

@bedas
Same for me. I just updated to 2.3.1, but again it shows me the update to 3.0 (which I can’t do).

??

@bedas
I followed your instructions, (delete typeset 2.3, and installed it again) but I keep getting the notification update.
Can’t you release a 2.3.1 to permanently fix the issue?
It’s very annoying, and it doesn’t looks good on my client side for whom I’m keeping the website up-to-date

• This reply was modified 6 years, 9 months ago by s.

Same problem here… I followed the instructions in the link but I keep getting the “You must have a valid subscription in order to get upgrades or support for this plugin.” message

Yes, I think that this might be the easiest solution. Thanks a lot ??
I hoped there was a plugin for this (a sort of internal IFTTT for WordPress ?? – but now I have an idea for something to develop when I’ll have time).

I’ll go with PHP, since writing SQL queries for me is probably slower and more difficult, I will surely miss something important and spend days to find out what it is.

@lebaux can you confirm if SEO Data Transporter is able to transfer all the custom post SEO description and titles from Yoast SEO to The SEO Framework following the guide linked by @barnez

That’s great! Thanks a lot! ??

I get the same errors. Has anybody found a solution?

( ! ) Notice: Trying to get property of non-object in D:\www\STEFANO\woptimize.io\wp-includes\post.php on line 6080
( ! ) Notice: Trying to get property of non-object in D:\www\STEFANO\woptimize.io\wp-includes\post.php on line 6081

• This reply was modified 7 years, 9 months ago by s.
• This reply was modified 7 years, 9 months ago by s.
• This reply was modified 7 years, 9 months ago by s.