mealto

I am using Generatepress and it seems Mac users are seeing Helvetica. Font loads properly on Windows 10 and Chrome OS (using Chrome browser).

Is there a way to send you the site URL privately?

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

I have been doing more troubleshooting and found that this combination is the onyl way to fix this overflow issue:

.no-sidebar .entry-content .alignfull {
/* margin-left: calc(-100vw/2 + 100%/2); */
/* margin-right: calc(-100vw/2 + 100%/2); */
max-width: 100vw;
width: auto;
}

html, body, div, span, applet, object, iframe, h1, h2, h3, h4, h5, h6, p, blockquote, pre, a, abbr, acronym, address, big, cite, code, del, dfn, em, font, ins, kbd, q, s, samp, small, strike, strong, sub, sup, tt, var, dl, dt, dd, ol, ul, li, fieldset, form, label, legend, table, caption, tbody, tfoot, thead, tr, th, td {
border: 0;
/* margin: 0; */
padding: 0;
}

Looks like something is conflicting causing Google Chrome to push the container beyond the browser limits. Is there a resolution for this?

Spoke too soon, overiding the above CSS did help but a new container now creates a small scroll able section. I hope there is a fix as your plugin has lots of potential. But not being able to use a Container without causing a horizontal scrollbar is an issue.

Thanks.

I am now able to isolate the issue caused by this CSS:

.no-sidebar .entry-content .alignfull {
margin-right: calc(-100vw/2 + 100%/2);
}

With this unchecked using Chrome inspect, the horizontal scrollbar is fixed.

How do I fix this short of overriding this CSS? Thanks.

• This reply was modified 4 years, 9 months ago by mealto.

Found something that may help with the troubleshooting. When I add a background color is when the horizontal scrollbar appears. Have tired to set Left and Right padding to 0 and even selected No padding but still the same. Looks like there is left and right margins pushing the container wider than the browser. This happens right away with noting in the container and only background color enabled. Any ideas?

Thank you about the information about the Autopurge. I had that set to 0 just in case. And thank you for letting me know about the Double Check feature. I have disabled this too, at least for now.

If you want to do some testing, I would be happy to try and help. Maybe by email is best. Which contact form can I reach you at?

Thanks again!

Thanks so much for your efforts here. Here is what I have discovered and hope this may help you as well.

1. It is indeed 6G WAF blocking bad request. The data center tech could not find an easy way to let this specific page request through the firewall. But if I disable -bad-request monitoring for the entire site, the verification link works!

2. Now, before I discovered this, I went and removed the verification link from the first email as I have “Subscribe” checked automatically. My next question is, if users who not verify, although they seem to be getting notification emails as others comment on the post, do they stay being subscribed until they remove themselves. I think I read somewhere that users who do not verify will be automatically unsubscribed after a certain length of time. If this is the case, I am forced to put the verification link back in and just disable all -bag-request within 6G WAF.

I can’t send over a real domain but here is the actual 6G error: [DATE-TIME] [“:bad_request_7:”] IPADDRESS https://www.domain.com “GET /comment-subscriptions/?LONGSTRINGUSEDTOVERIFYLINK HTTP/2.0” 403 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.106 Safari/537.36”

Hope that makes sense.

By the way, for the “Double Check Message”. What is the second line that includes the verification link that comes after this? I forgot to save that portion.

You have requested to be notified every time a new comment is added to:
[post_permalink]

• This reply was modified 4 years, 9 months ago by mealto.

Thank you. I have created the real page and included [stcr_management_page].

One other issue, it seems Postman had issues with sending out comment notifications. nginx was complaining something about Bcc, not sure exactly the error. Switched to WP Mail and everything works again. Thought to pass that along.

One other thing, our nginx server has the 6G WAF enabled. And the server was throwing an error when users clicked on the Verification link after subscribing to a comment thread. The odd thing is, when they click on the Manage Subscription link in subsequent emails, they were able to access it. I wonder if the firewall thought including too many parameters (like the user’s email) in the actual URL was blocked for security reasons? Any ideas on how to get around this? Right now, I have remove the verification link in the original email notification.

ok, I have no information to add. Looks like it was a combination of things. Firewall was blocking Postman to send the comment notification emails. Now that I have switched to WP Mail and using Mailgun to send out emails, everything, is going out properly again.

Now, nginx is blocking the link that allow the user to verify their subscription. Clicking on that link leads to a 403 Forbidden nginx page.

Any ideas?

Maybe I have to create a real page instead of a dynamic page. If so, what content should be included inside the Real page?

Odd thing is, when you go directly to the dynamic URL, everything works. It’s just the link from the verification email. Maybe it includes the email in the URL itself as this may be a security issue?

• This reply was modified 4 years, 9 months ago by mealto.

I should add more details. When using Mailgun, other transactional emails still work. WordPress is set to approve all new comments so those emails still arrive from WP itself. Using the contact form also works. Just not sure why comment notification emails are not arriving.

Also re-tested this on a site using Sendgrid and they have also stopped working. So it looks like something beside Sendgrid vs Mailgun. Maybe a plugin conflict or server security config blocking something?

How would I go about troubleshooting this short of disabling all plugins etc…?

Here is one line from the WP Debug log:

PHP Notice: is_tax was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /var/www/domain.com/htdocs/wp-includes/functions.php on line 5167

Thank you! Really appreciate your reply and great work on this plugin!

Thank you! The error was in the title. Let me paste it below:

is_tax was called incorrectly

I have opened a ticket with Beaver Builder devs too. Will post back once I hear back for them as well. Appreciate it!

• This reply was modified 4 years, 10 months ago by mealto.

I have done more testing and here is what I have found. Since Shortpixel does create x.webp files, I disabled Cache Enabler and tried to upload images again. Only x.jpg and x.webp files are crated. When I enabled Cache Enabler, the above files are created alongside x.jpg.webp files. Deleting the image inside WordPress > Media > Library removes the first 2 on the server but leaves behind an orphaned x.jpg.webp file.

From this, I can only surmise that having both SP and Cache Enabler running causes this issue. The only reason I am trying this combination is that the SP blog mentioned that Cache Enabler could be used to server webp files while SP created them.

Maybe this is something that has not been reported yet?

This is very interesting. Both you and SP support had now indicated that neither of your plugins create these *.jpg.webp files.

Let’s how much more testing I can do to try and find whatever is creating these extra files before I disable either plugins.

If you have any more advice, I am open for more troubleshooting on my end.