BernWoz

I have a similar problem – the welcome email is sent and received, but the user is signed up without having to confirm the double opt in.

OK, got this to work with a short code – thanks for the tip.
It also sends the email, so I will stick with using the shortcode for now.

Is this bug specific to version 3.60.1 or is it also in earlier versions?
Also please be more specific about how to use the “mailpoet subscription shortcode” or direct me to the documentation.
Thanks.

AFAIK I’m using the MailPoet sending service. I think the problem was, I didn’t have a SSL certificate, so the email service wouldn’t talk to my web site as it considered it risky. I have since installed a SSL cert (its hosted on GoDaddy) but I now have a new problem!
I upgraded WordPress to 5.6.2 and upgraded MailPoet to the latest release. I now cannot add to the email list. I’m using a MailPoet form to enter name and email, but it gives me the error “This value seems to be invalid”.

That worked nicely – thanks.
Are there any more tricks/tips on how to manage the header? Adding logos or positioning them in the header?

I have been trying to resolve this issue of block opacity.
The example site is here;
https://catherinemcgreevy.com/books/

In this cast I can get the block opacity by editing the block paragraphs as HTML and adding this to the HTML;
p style=”background-color:rgba(236, 246, 250, .5);”

However I have to do this in every block which is not the correct or efficient method.
If I try to add to Appearance->Customize->Additional CSS, this has no effect.
I have also tried at the Page level in Block->Advanced->Additional CSS, but this also has no effect. And yes, update/publish and refresh of the intended page.

Can someone advise how to correctly manage the block background opacity?

None of the above suggestions worked. I tried setting the opacity in Appearance->Customize->CSS. I also tried to select each block and add the code(s) in Advanced->CSS, but these did not work with any of the options. I am also using the plugin Twentig but for other settings, it does not control opacity.

To fix my issue I displayed the paragraph as HTML in the block options and changed the following;
orig: “background-color:#ecf6fa”

My edit: “background-color:rgba(236, 246, 250, .5);”

This works well but is tedious as I have to do it in each paragraph block.
I also found that my blocks (the ones I edited as HTML) continue to display as HTML in my dashboard. I can preview as text but the regular block settings seem to disappear. I sometimes think that WordPress is Sooooo clumsy sometimes.

If you are interested the page in question is here;
https://catherinemcgreevy.com/books/

If you have any comments to add, they could be useful for future reference. Otherwise I will mark this as solved.

Thanks ??
Bernard

• This reply was modified 4 years, 6 months ago by BernWoz.
• This reply was modified 4 years, 6 months ago by BernWoz.
• This reply was modified 4 years, 6 months ago by BernWoz.

No, WordPress is not the problem. I found out the issue on my own and its Linux file permissions and ownership. I usually log in as root and move/copy files as root.

You need to change file ownership and/or permissions of the upload directory. To do this use:
chown -R www-data:www-data uploads
Where ‘-R’ means recursive and ‘www-data’ is the apache2 user/group.
Also this will probably work… chmod -R 777 uploads
…I can’t say which is best.
beware that chmod 777 allows EVERYONE to modify these directories which on a real deployment can cause BIG problems!
To check the apache2 user use… ps -aux | grep apache2

After you modify your owner/permissions, I deleted the flipbook pdf file I made and created a new one with the new ownership. I then used the new shortcode.

I did this on my development server at home and it worked fine, when you deploy to a public server, check with the sys admin for correct owner/permissions.

For more information search for errors on upload.php and similar issues on wordpress.
Also before and after, use this command to monitor file access, it will tell you what the web server is failing on.
tail -f /var/log/apache2/access.log

Deleting the ‘p’ did not work, there is no change in anything I see.
I am also using wpforms – is it possible this is controlling the opacity?
Also at the bottom of the ‘Cover Template’ panel, there is a slider control for overlay poacity – what is this supposed to control? it also seems to do nothing.

I saved it here https://snipboard.io/HRZO48.jpg

The web server is apache2 running on debian 10 on a VM.
The gateway is allowing web server and https to this VM.

• This reply was modified 4 years, 7 months ago by BernWoz.

Hm, I’m using a localhost with a pinhole on my gateway. I just tested this and I can get to a simple index.html in the root of 99.0.2.10 but I also get a timeout on the wordpress sites.
Not sure why this happens

Thanks Jarret,
I am using the default cover template & I tried your css as is, but it didn’t do the desired effect. Looking at the w3schools link you sent it seems I need a rgba setting. I am trying to make the color of a paragraph block semi transparent, so I can see the background image behind it but read the text easier. You can see my attempt here…
https://99.0.2.10/cathy/
The “Subscribe to my newsletter” is the paragraph block

Many thanks
Bernard

I found out a way to fix this and it is probably a generic issue with WordPress. I install WordPress as root which probably causes this problem.

You need to change file ownership and/or permissions of the upload directory. To do this use:
chown -R www-data:www-data uploads
Where ‘-R’ means recursive and ‘www-data’ is the apache2 user/group.
Also this will probably work… chmod -R 777 uploads
…I can’t say which is best.
beware that chmod 777 allows EVERYONE to modify these directories which on a real deployment can cause problems!
To check the apache2 user use… ps -aux | grep apache2

After you modify your owner/permissions, delete the flipbook you made and make a new one and use the new shortcode.

I did this on my development server at home and it worked fine, when you deploy to a public server, check with the sys admin for correct owner/permissions.

For more information search for errors on upload.php and similar issues on wordpress.
Also before and after use this command to monitor file access, it will tell you what has failed.
tail -f /var/log/apache2/access.log

GOOD LUCK ??