K H

What worked for me (at least to get rid of the warnings) is the following.

In the ‘mail’ tab use

to: [email protected]
from: [your-name] <[email protected]>
additional headers: ‘Reply-To:[your-email]’

Never mind – something else is going wrong.

• This reply was modified 7 years, 9 months ago by K H. Reason: elaboration
• This reply was modified 7 years, 9 months ago by K H.

BTW – ideally it will also show the parent category and its subcategory’s.

As in the following structure:

category 1
> subcategory a
> subcategory b
category 2
> subcategory c
> subcategory d

When I’m in subcategory c (post or category page), I’d like the widget to show category 2 & it’s subcategories. And as I said in my previous post: the widget should figure out in which category it is, so it knows which category & subcategories it should show.

What I haven’t figured out is the selector for the hover over the ‘previous’ and ‘next’ arrows on the main blog-page. See at the bottom of https://www.allconsidering.com/ for instance.

I had the same problem. I solved it in part with the following CSS:

.widget_calendar tbody a,
.customize-support button,
.customize-support button[disabled]:focus,
.customize-support input[type=”button”],
.customize-support input[type=”button”][disabled]:focus,
.customize-support input[type=”reset”],
.customize-support input[type=”reset”][disabled]:focus,
.customize-support input[type=”submit”],
.customize-support input[type=”submit”][disabled]:focus,
.customize-support .menu-toggle.toggled-on,
.customize-support .menu-toggle.toggled-on:focus,
.customize-support .pagination:before,
.customize-support .pagination:after,
.customize-support .pagination .prev,
.customize-support .pagination .next,
.customize-support .page-links a
{
background-color: #6d3b48; color:#efddc9 };
}
.customize-support button:hover,
.customize-support button:focus,
.customize-support input[type=”button”]:hover,
.customize-support input[type=”button”]:focus,
.customize-support input[type=”reset”]:hover,
.customize-support input[type=”reset”]:focus,
.customize-support input[type=”submit”]:hover,
.customize-support input[type=”submit”]:focus,
.customize-support .page-links a:hover,
.customize-support .page-links a:focus,
.customize-support .pagination .nav-links .prev:hover,
.customize-support .pagination .nav-links .prev:focus,
.customize-support .pagination .nav-links .next:hover,
.customize-support .pagination .nav-links .next:focus,
.customize-support button[disabled]:hover,
.customize-support input[type=”button”][disabled]:hover,
.customize-support input[type=”reset”][disabled]:hover,
.customize-support input[type=”submit”][disabled]:hover,
.customize-support .menu-toggle.toggled-on:hover,
.customize-support .widget_calendar tbody a:hover,
.customize-support .widget_calendar tbody a:focus,
.customize-support .page-links a:hover,
.customize-support .page-links a:focus
{
background: #2a3691; color:#efddc9;
}

That fixes the main buttons, at least for me. It’s probably more code than is necessary, but it works.

There is no way to use a font that isn’t already on the users computer, or in the Google font-directory. It’s just not possible.

Assuming the Spicy Rice font is in the Google font directory, you can activate using it (as it were) by something like this in the CSS file of your child theme:

body {font-family: ‘spicy rice’, sans-serif;}

That way if the users pc can’t find spicy rice, it will fall back on a sans-serif font.

Thanks. For me that fixed it ?? (with jetpack related posts & sharing buttons).

That may be what’s happening in my case as well. Posts don’t stay sticky for some reason. In my case it’s a wp multisite installation.

Yes, but it reappears when I go to another page on the same site.

I’ve gone through all my blogs again (sigh) and find that most are working fine.

On most that didn’t – I could get the non-standard url (with or without www) working through the method outlined above.

In one case I had to:

– Go to supercache settings “Easy” tab
– select “caching off” and update status
– press “delete cache” twice (!)
– test redirect, it should work now
– select “caching on”
– test again, it still didn’t work
– turned off wp supercache completely – as in deactivate through wp plugins page
– restored default htaccess code through BPS
– allowed BPS to recreate it’s htaccess codes
– test again: still no luck (!)
– add wp supercache commented out line in htaccess through BPS plugin
# WPSuperCache
– activate wp supercache (turning it on doesn’t seem necessary)
– to get caching going again: turn it on, don’t mess with default settings (The commented out line above means you need to use PHP, not mod-rewrite)

Unfortunately today my main blog (430 subscribers) was not accessible at either the main blog (with www) or without www. I’m turning off this plugin for now.

Sure – the problem gets temporarily solved if you delete the cache twice, but it doesn’t last.

No, but I’m afraid you’ll have to keep monitoring it. The combination WP SuperCache and BPS is somewhat tricky. So far every issue I’ve had with it can be fixed, but it can lead to some weird htaccess content.

I ‘solved’ this in a similar manner: turned off caching in supercache, cleared the cache (twice) and then turned it back on.

What’s more, uninstalling WP Supercache and deleting the Supercache lines from the Htacces fill didn’t solve the problem on this site:

https://www.bestflutereview.com/ (inaccessible)
https://bestflutereview.com/ (default URL and accessible)

I have no idea. I’m on a shared host, I don’t think I have access to my PHP error log.

In the meantime I’m moving host and if the problem persists, I’ll get back here.