lausianne

I got in again by searching the settings in the DB. Found here: hh_content_security_policy_value
Then I was able to reset everything and switch on “Report-Only”. Now I can continue. It would be safer if ?“Report-Only”, with a warning that switching it off can break a site with no easy way of recovery.

Reset with this:

a:22:{
s:11:”default-src”;a:2:{s:13:”‘unsafe-eval'”;s:1:”1″;s:6:”source”;s:0:””;}
s:10:”script-src”;a:2:{s:6:”‘‘”;s:1:”1″;s:6:”source”;s:0:””;} s:9:”style-src”;a:2:{s:6:”‘‘”;s:1:”1″;s:6:”source”;s:0:””;}
s:7:”img-src”;a:2:{s:6:”‘‘”;s:1:”1″;s:6:”source”;s:0:””;} s:11:”connect-src”;a:1:{s:6:”source”;s:0:””;} s:8:”font-src”;a:2:{s:6:”‘‘”;s:1:”1″;s:6:”source”;s:0:””;}
s:9:”media-src”;a:2:{s:6:”‘‘”;s:1:”1″;s:6:”source”;s:0:””;} s:10:”report-uri”;a:2:{s:6:”‘‘”;s:1:”1″;s:6:”source”;s:0:””;}
s:9:”child-src”;a:2:{s:6:”‘‘”;s:1:”1″;s:6:”source”;s:0:””;} s:11:”form-action”;a:2:{s:6:”‘‘”;s:1:”1″;s:6:”source”;s:0:””;}
s:15:”frame-ancestors”;a:2:{s:6:”‘‘”;s:1:”1″;s:6:”source”;s:0:””;} s:10:”object-src”;a:2:{s:6:”‘‘”;s:1:”1″;s:6:”source”;s:0:””;}
s:9:”frame-src”;a:2:{s:6:”‘‘”;s:1:”1″;s:6:”source”;s:0:””;} s:10:”worker-src”;a:2:{s:6:”‘‘”;s:1:”1″;s:6:”source”;s:0:””;}
s:12:”manifest-src”;a:3:{s:6:”‘‘”;s:1:”1″;s:15:”‘unsafe-inline'”;s:1:”1″;s:6:”source”;s:0:””;} s:11:”navigate-to”;a:2:{s:1:”“;s:1:”1″;s:6:”source”;s:0:””;}
s:12:”prefetch-src”;a:2:{s:1:”“;s:1:”1″;s:6:”source”;s:0:””;} s:8:”base-uri”;a:2:{s:1:”“;s:1:”1″;s:6:”source”;s:0:””;}
s:12:”plugin-types”;s:0:””;s:9:”report-to”;s:33:”[email protected]”;s:7:”sandbox”;a:2:{s:13:”allow-scripts”;s:1:”1″;s:39:”allow-top-navigation-by-user-activation”;s:1:”1″;}
s:15:”require-sri-for”;a:2:{s:6:”script”;s:1:”1″;s:5:”style”;s:1:”1″;}
}

Now I investigated a bit further and found a pre-publishing check setting in the page preferences:

https://share.zight.com/z8uoY4G9

But in the pattern editor, this is missing.

Thanks Kavya! That is a bit hidden, but at least it is there, for you. I don’t have this, unfortunately:

https://share.zight.com/lluW2n6o

Sure, here you go:

https://share.zight.com/2Nu8y0YJ

Thanks!

Did this again lately. After a lot of back and forth triple checking everything, randomly changing stuff, I eventually got it to work. Unfortunately I still don’t know what the decisive step was. Still waiting for a useful documentation, and an explanation what this error actually means.

Hi Steve,

Thanks for your quick reply. This was for the free version. But now I got the Pro version, no more errors.

That’s what I checked first, there is no spelling difference.

I tested some more and now found this: The error message only appears, when the check mail script is run manually by clicking “Process Email” in the settings. When waiting until the mail is processed automatically, all seems fine.

So the issue apparently is only with the manual checking feature.

In Postie settings, tab “User”, there is this field: “Authorized Addresses”. Below this field is this explanation for the field:

“Posts from emails in this list will be treated as if they came from the admin.”

Into this field I entered an email address that I use to post to the website. Since I entered the address into the field for authorized addresses, it should be authorized, “as if it came from the admin”.

This email address does not belong to a user of the site. So there is no registered user to which the address belongs.

I don’t see which other permissions I could or should set for what is supposed to be considered an admin sender.

Sorry still at a loss. What permissions? The address does not belong to a user.

Ok. Then what else do I need to do than adding the sender address to the Authorized Addresses list?

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 8 months, 3 weeks 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