Ate Up With Motor

@bsfherman I did exactly as you show in the video, but nothing visibly happens at all. It makes no difference if I choose px or em, or if the values are positive or negative — there’s simply no effect. Can you think why that might be? I’m baffled.

Thanks!

Hi,

I looked at Blog Layouts > Blog > Single Post > Design, but adjusting Outside Container Spacing (which is what I would assume controls the padding) has no effect. Am I looking at the wrong thing?

Thanks!

@bsfherman – There’s been some confusion — I am not asking about (and don’t use) the Pro version. I am asking about the free version distributed through www.ads-software.com, and my question remains the same as before.

The ONLY reason I mentioned the Pro version is that I was very confused by your previous answer. All I need to know is how I can fix the padding described in the free version of the theme, whether with Additional CSS or in some other way. My previous solution with Additional CSS now only works in the main blog view, not on individual posts/pages.

• This reply was modified 2 years, 4 months ago by Ate Up With Motor.
• This reply was modified 2 years, 4 months ago by Ate Up With Motor.

Following a suggestion offered by a user of the Really Simple SSL plugin, I switched the site’s PHP version from 7.4 non-FastCGI to 7.4 FastCGI. After refreshing permalinks again, the error message disappeared and Site Health now says “The Authorization header is working as expected.”

So, as the developer suggests in the post linked above, this appears to have been a server configuration issue. I want to wait a bit to see if the issue recurs before pronouncing it fixed, but for the moment, it appears it may be.

(Note: After changing the PHP version, it appears it’s necessary to reset the permalinks again, to make sure that WordPress registers that the Authorization directive is indeed present.)

The thing is, the directive IS there — it was placed there by WordPress core itself, and I verified that is was — so I can’t fathom why it wouldn’t find it.

I just tried manually deleting the directive from .htaccess, flushing the permalinks again, and allowing WordPress to reset them (which recreated the HTTP:Authorization directive). This definitely restored the directive to .htaccess, but the warning persists.

The authorization header line IS present in .htaccess, which poses an obvious question: If the header is present (and it definitely was, I just checked), why is the Site Health component warning that the header is missing?

I have Additional CSS set with:

.ast-separate-container .ast-article-post { padding: 3em;}

This reduced the padding for the default view, but if I click on any individual page or post, the container padding is substantially greater than the default view, so it looks like the .ast-article-post class is no longer valid, and I don’t know what the class is for posts.

Where are the spacing options? I don’t see them in Astra Options, and Spacing is still listed as an Astra Pro Option. (I do have Astra 3.8.4 installed on that site.)

If you look at previous forum posts, everyone who updated to 3.0.9 or later is having the same issue, and version 3.1 did not fix it. As a temporary measure, switching back to version 3.0.8 fixes it. The plugin author has been unresponsive.

Great, that’s what I needed to figure out. Thank you!

Well, it’s a short-term fix, because the shared hosting plan’s allotted resources are limited. What’s puzzling is that my site’s resource usage has not significantly changed in quite a while, and I’ve never had WP-Optimize glitch in this way. (Usually, if I run short of resources while running some intensive operation like optimization, the worst it’ll do is time out for a minute, whereas in these instances, the process kept running and had to be forcibly stopped by the host.) There was no indication in the PHP logs or server error logs of why it happened, and since the optimization function has been working fine otherwise, it doesn’t appear to be a plugin conflict. It’s mystifying.

Thanks for your help!

Yes, I believe this is essentially what my web host did to temporarily alleviate the problem, in addition to performing a server reset to cancel current processes.

Ahh! I hadn’t realize that little-bitty symbol was for mobile options. I will experiment with that. Thanks!

I was just revisiting the solution to this exact problem not 30 minutes ago.

See this previous post on the WordPress support forums. The function described should be added to the functions.php file of your site’s child theme.

(I had forgotten how I did this, and had to figure it out again to set up Astra on a different site.)