timbearcub

Update: weird, it works with headers and Cover/Image blocks in a FSE header, but not Custom HTML (I was trying to put a custom CSS in according to author, hence the Custom HTML) so it seems there is an issue with Custom HTML and FSE.

So at least I can do the author headers! Was dreading trying to do that with CSS…

• This reply was modified 1 year, 10 months ago by timbearcub.

OMG THANK YOU!

I have been trying to change the gallery caption size for actual years…everything I tried affected only the main captions, but the so-tiny-only-ants-can-see-it captions on the gallery I had to live with. (why oh why WordPress is the default SO unreadable?)

Really WordPress needs to sort out stuff like that if it wants true Full Site Editing…caption typography needs to be in the block. I shouldn’t have to hack advanced CSS just to change a caption size?

• This reply was modified 1 year, 10 months ago by timbearcub.
• This reply was modified 1 year, 10 months ago by timbearcub.

P.S. using it it’s a much better interface, really good work – it works far better than the old one – shame it doesn’t migrate the old settings, that might have saved some headaches here.

• This reply was modified 3 years, 1 month ago by timbearcub.

Yes thanks for this – had to re-add my Dandelion API details but it is working fine. Like the new? ability to tune the accuracy level – I usually prefer broader and then choose from those.

And thanks for adding my fix for the OpenCalais API in as well – my first ever Git submit!

OpenCalais has been odd for a long time – sometimes it works great, sometimes it gives weird results, it is 50/50, or maybe a bit better, 60/40 working to not.

• This reply was modified 3 years, 8 months ago by timbearcub.

OK thanks for letting me know, I’ve rolled back for now,

Thanks for all the work on this! Look forward to this becoming bigger and better in future.

Yes it was Dandelion I used a lot, the responses were very good from there.

• This reply was modified 3 years, 9 months ago by timbearcub.

Browers:

Safari Version 13.1.2 (13609.3.5.1.5)
Brave Version 1.13.82 Chromium: 85.0.4183.83 (Official Build) (64-bit)
Chrome Version 84.0.4147.105 (Official Build) (64-bit)

– I tried it in all of these and I think FF Quantum too.

Platform: OSX 10.13

WordPress 5.5.0–en_GB

Editor – Gutenberg, the default standard one, I do have Classic Editor plugin activated but don’t think I tried that.

• This reply was modified 4 years, 2 months ago by timbearcub.

Uncommenting ob_start() worked for me – had the same error on authorisation:

Warning: session_start(): Cannot send session cookie – headers already sent by (output started at /var/www/…/wp-includes/script-loader.php:1542) in /var/www/…/wp-content/plugins/facebook-auto-publish/admin/authorization.php on line 9 Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /var/…/wp-includes/script-loader.php:1542) in /var/www/…/wp-content/plugins/facebook-auto-publish/admin/authorization.php on line 9

I guess I have to re-add that when the plugin is upgraded? Would be good if there was a ‘fix’ setting for that in options in future? BTW I definitely have curl and fopen on, and output buffering – checked in settings and phpinfo()

• This reply was modified 6 years, 10 months ago by timbearcub.

Exactly.

How do I report them?

If you want to remove them, this plugin is good: WP Hide Plugin Updates and Warnings.

SPAM GONE! Oddly only a few of my sites refuse to remove this update spam, the rest are fine…others do the login page thing.

Really…

I’m having the same problem…about to disable all plugin nags because this is getting silly, plugin authors are abusing them, WordPress needs to sort it out

(Joost is another I’ve already disabled SEO notifications due to his abuse of them).

First thing I did was look at the XMLRPC, reinstall WordPress and disable all the plugins…nope.

EDIT – finally found the debug log, hidden under that drop down? Well hidden!

SELF:
	Array
(
    [headers] => Array
        (
            [server] => nginx
            [date] => Mon, 04 Apr 2016 19:38:01 GMT
            [content-type] => text/plain;charset=utf-8
            [connection] => close
            [expires] => Wed, 11 Jan 1984 05:00:00 GMT
            [cache-control] => no-cache, must-revalidate, max-age=60
            [pragma] => no-cache
            [x-hacker] => Jetpack Test
            [x-ac] => 3.dca _dca
            [strict-transport-security] => max-age=15552000
        )

    [body] => {"error":"Communication error","error_description":"We were unable to make an XML-RPC request to your website. Please make sure that XML-RPC is turned on and that Jetpack is installed, activated and connected with your WordPress.com account. If the error persists, try disconnecting and connecting Jetpack again."}
    [response] => Array
        (
            [code] => 400
            [message] => Bad Request
        )

    [cookies] => Array
        (
        )

    [filename] =>
)

I tried the SSL suggestions ($_SERVER['SERVER_PORT'] = 443; etc), doesn't solve it either. And SSLLabs returns an A-grade for my cert.

Ahh I was going to ask this too – great! For anyone wondering, that’s now in the released version.

I’ve also solved a problem I had with an site sometimes complaining about not being indexed – I had switched off the search engines!

Thanks for all your work. Much appreciated.

I guess this is resolved.