lausianne

Thank you! But why do I get the “Invalid sender” message in the first place, while the sender is authorized, so he should not be invalid. And I would like to receive the warning mail for actually invalid senders.

Hello @shortpixel,

Thanks for your reply. As I remember, regeneration used to be part of the Image Optimizer. Maybe I’m mistaken, then I apologize.

Still I find the pricing way over the top. Especially since there are several plugins cheaper or even for free, that are good enough. I’d still prefer to get this from you, because I am otherwise happy with your products. For a reasonable price. Or a price based on actual usage, like Image Optimizer credits.

I totally agree with @whistlerdan. Offering an additional plugin is one thing, but removing the feature from the original that we bought is not ok. And the price is totally over the top. Plus it’s even recurring. One reason I got the Image Optimizer was the LTD. If it was and additional $50 for a reGenerate LTD, I would not mind. Or if it cost some of the Optimizer credits for usage, ok. But $50/year and only 20 sites, no way.

Same here, the plugin does not seem to do anything. No error messages in the console.

EDIT: Found it. On another site it worked, so on the first site, where it didn’t, I disabled other plugins and found a conflict with “Admin and Site Enhancements”. This is a very important plugin for me. I hope this conflict can be resolved.

Thanks!

• This reply was modified 1 year ago by lausianne.

Hi Lynn,

Please explain, why for a heading 18px and 20px would work, and 19px would not work?

It is not a matter of decoration or taste. It is a matter of corporate identity. This is absolutely essential for marketing for any organization. I cannot tell a client “Sorry, your CI says 19px, it is 19px on your website, but unfortunately it is not in MailPoet’s dropdown. And also, headings could be bold, but it will be a lot of effort for each newsletter and will cost you extra”.

If I cannot use the required font styles, then I can simply not use MailPoet. I actually wonder who can use it, unless they really don’t care about marketing …

Please, Lynn, we need to find a solution here.

Thank you!

Ralf

Thanks for the reply. That means the message is “hardcoded”, not available in another language and I need to translate ist myself? Not a big deal, just want to be sure this is actually the correct way.

Hi Lynn,

Thanks for your reply. Your link goes to the page that I linked to myself. But the actual style section looks different now. No more input fields, but – sadly – dropdowns.

This is just the problem: The sizes in the given dropdowns are insufficient. I need other sizes. How?

And how can I make headings bold?

Thank you!

No, I did not, good idea. I meant to change them anyway. And indeed, it works now. Thank you!

Thanks for your quick reply.

It’s all on the same multisite, so all subsites are using the same plugins. And also this “problematic” subsite worked fine with WP Armour on the login page, before I changed the domain name.

Versions are 2.1.13?for WP Armour, and 1.26?for extended

Same issue, I believe. I did not try that form yet, but matter what language I set for the site, MailPoet always sends subscription confirmations in English.

Alright. Thanks for the reply, and your work!

I spent another few hours on this, set it up again on another site, went through all of the steps again, everything green and appears to be working, but this issue remains. I still don’t even know what is meant by “main domain” here. I have only one domain set up at the moment.

Always “Main domain not generated yet”
… and “Current Cloud Nodes in Service Redetect – No cloud services currently in use”

What exactly has to be generated where?

Hi,

Thanks for your reply. Yes, you understood correctly. Site language is German, but user language and browser language are English. The error messages appeared in English but were supposed to appear in German.

I tried again, and it is not happening anymore. I don’t know what has changed, but now it is alright. I’ll call again if it happens again.

Cheers!

• This reply was modified 1 year, 5 months ago by lausianne.

How would it work then? Do you have an example? Thanks!

On one child site I switched the theme to 2023. And with 2023, Admin Toolbar indeed does not break the backend. So it does seem to be an incompatibility with Divi.

I’d rather not disable plugins at this point if not absolutely necessary.

There is nothing on the console.

Diagnostic info:

• PHP Version: 8.1.22
• WordPress Version: 6.3.1
• Plugin Version: 7.32
• Current Theme: Divi Agency
• Active Plugins:
• Adminimize
• Divi Coming Soon
• Site Kit by Google
• MainWP Child
• Squirrly SEO (Newton)