artesea

I’ve emailed my .htaccess file (ticket 489967754) that works fine, below is what I found on the server this morning after complaints about the links to posts no longer working, no other rules were showing.

#Begin Really Simple Security
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{HTTP:CF-Visitor} '"scheme":"http"'
RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]
</IfModule>

#End Really Simple Security

I have the plugin set to auto-update with WordPress, plus as the site is hosted through a server managed with cPanel, that has it’s own WordPress updater.
Looking at my daily backups the file created this morning had 6.0.3 backed up in it with a timestamp of 20:09 UTC.
The .htaccess file is complicated so I’d rather not publish it here, but can email it over if you provide me an address.

@megamenu thanks for the tip. Was confused when I noticed my menu broken yesterday and even more confused when I realised neither Max Mega Menu or WordPress Core had been updated.
Was able to make some small changes to ensure my menu didn’t look broken, but after seeing your suggestion about wp-user-avatar which updated with bloat during the week, I’ve disabled that and as if by magic everything looks fine again.

Been looking at the code and can’t find any obvious hooks to run against. Still getting complaints from my users that comments are missing on the mobile version.

@waffenss, it can’t be the Facebook API. The Jetpack plugin is sending the avatar url in the picture field.
Using any number of other plugins doesn’t have this issue.

Just enabled Publicize after we noticed the previous method of pulling in content to Facebook had stop. Now I have my Avatar showing against a story which has nothing to do with me. I’m not the author or the subject, but as it was me set it up, my photo.
Why it bothers with the image in the first place I don’t know. I’ve already got Open Graph set up to display the picture I want and if I just pasted the URL of the post Facebook would have done the rest.

Please provide at least one of the options below:
a) disable gravatar
b) use the og:image tag
c) custom default image

tcharmy, hopefully for at least a couple of years, but then twitter seem to change the rules to suit them.
Twitter Tools 3.0 is your best bet for something stable, however I’m fine with how it worked before and am using me tweaks on the two sites I run.

Twitter turned off support for api calls to https://twitter.com URLs yesterday https://dev.twitter.com/discussions/10803
I suggest using the latest version of the API which is slightly different from the advice so far.

define('AKTT_API_POST_STATUS', 'https://api.twitter.com/1.1/statuses/update.json');
define('AKTT_API_USER_TIMELINE', 'https://api.twitter.com/1.1/statuses/user_timeline.json');
define('AKTT_API_STATUS_SHOW', 'https://api.twitter.com/1.1/statuses/show.json?id=###ID###');
define('AKTT_PROFILE_URL', 'https://twitter.com/###USERNAME###');
define('AKTT_STATUS_URL', 'https://twitter.com/###USERNAME###/statuses/###STATUS###');
define('AKTT_HASHTAG_URL', 'https://search.twitter.com/search?q=###HASHTAG###');

still have the issue, and I’m sure the answer is just a couple of lines of code, just not sure where to start.

Yup the dev version fixed the issue.

Have had the same issue reported to me from readers, the site auto tweets new posts, yet people visiting the home page couldn’t find them.
Turned on debugging on a post I just scheduled and got the same issue with post is draft do nothing.
About to install the dev version.

Thanks, replaced and tested and no additions to the error_log.

Cheers, worked with the upgrade

Getting similar errors here when trying to upload a custom folder

Syncing [355/469] wp-content/authors/Gareth_Epps-791.png
Warning: finfo_file() [function.finfo-file]: File or path not found '/home/meh/public_html//home/meh/public_html/wp-content/authors/Gareth_Epps-791.png' in /home/meh/public_html/wp-content/plugins/cdn-sync-tool/lib/Cdn/Aws.php on line 114

Warning: fopen(/home/meh/public_html//home/meh/public_html/wp-content/authors/Gareth_Epps-791.png) [function.fopen]: failed to open stream: No such file or directory in /home/meh/public_html/wp-content/plugins/cdn-sync-tool/lib/awssdk/lib/requestcore/requestcore.class.php on line 527

Warning: fstat() expects parameter 1 to be resource, boolean given in /home/meh/public_html/wp-content/plugins/cdn-sync-tool/lib/awssdk/lib/requestcore/requestcore.class.php on line 489

Warning: fclose() expects parameter 1 to be resource, boolean given in /home/meh/public_html/wp-content/plugins/cdn-sync-tool/lib/awssdk/lib/requestcore/requestcore.class.php on line 276
The stream size for the streaming upload cannot be determined. done

It appears it’s trying to find the file in the wrong place /home/meh/public_html//home/meh/public_html/wp-content/authors/Gareth_Epps-791.png

But like I said I had a CNAME for m.libdemvoice.org pointing at https://www.libdemvoice.org
The Mobile Pack plugin detects if you are at m. and displays the mobile version of the website.
With WP Super Cache I ended up with two cache directory, one for www and one for m.

With W3TC I found that my main site at one point was displaying the mobile version, and a few times on my phone I ended up with the full site.

I don’t want to use UA detection in which theme to display, nor do I want a cache for every UA, what I want is for people visiting www to get the full site, and those visiting m to get the mobile one.
This allows people to choose which version they want, not which version I think that they might need.

I don’t mind playing about installing another plugin if that will result in W3TC understanding that m. is a different version and needs it’s own cache.