Arjan Olsder

For now I think you have to downgrade PHP for the quick solution. The developer who was handling this code has left our company. We are sourcing a new one. Since this is a non-commercial side project we don’t have many resources. I expect we will be updating the code end of Q3 at latest with PHP 8.2 compatibility.

Ah so. I thought you tried to input logic into the form field, but you are discussing the code here. Interesting. We will test this.

Our developer will look at this in the second half of this week.

@dbase66 what are you trying to ask here? The URL input field is not developed to use other logic than handling URL/keyword combinations in the order they are listed.

We don’t support custom post types at this moment. It’s on the roadmap for development.

Just to be sure. Are you trying to run YouTube embeds through our plugin? It’s not intended for that. We are planning updates on the plugin next month. Since it’s a non-commercial project, our time can be limited now and then.

Hi. You are Dutch. Please submit your problem to [email protected] and our developers will take a look with you. That’s much faster than the support forums here.

Hi. Can you tell me a bit more about the WordPress and PHP versions you are running? Does it also blank out when all plugins / themes are deactivated?

Can you try to set the plugin to ignore headings?

Can you list the non-latin characters you are using in a post that disappears? I also have many reports now that 1.5.2 solved this issue.

Happy to hear that ??

Please give 1.5.2 a go.

@devrekli, perhaps your e-mail didn’t pass my spamfilter. Sorry. Please try again.

@asisrodriguez thanks for the offer on the Spanish translations. Looking forward to that, but first we want to make sure the code is solid.

@riga75 please revert back to v1.3 untill 1.5.2 is available. I hope today otherwise tomorrow.

We have the feeling it might have to do with symbols like (c) (r) ™ in texts. So we are updating the regex for that at the moment. In 1.3 this wasn’t a problem. This bug is introduced to the changes we made to support non-latin characters.

@asisrodriguez can you contact me at [email protected]? I’d like to connect you with my lead developer on this plugin so we can see where the problems come from and provide a fix in the next minor release.

@mirksen can you contact me at [email protected]? I’d like to connect you with my lead developer on this plugin so we can see where the problems come from and provide a fix in the next minor release.