Hi Ege
It was a while back now, and I ended up requesting a refund for the Yoast Premium licence as it was an issue that I could not resolve – I still use the free version of Yoast and I can make do without the social previews. Yoast acknowledged at the time that it was an issue and that they would refer it back to their development team. I didn’t hear back from them and it is a pity that it is still occurring. This would probably need the power of the team at Kriesi to pursue this.

Sorry that I couldn’t be of more help.

Warm regards
Diana

Hi Rikard
I’ve learnt that I need to find a neater way to customise code at times :).

I really appreciate the time you all give to answering and attempting to resolve queries. Please go ahead and close this topic.

Many thanks
Diana

Hi Victoria

Sorry I incorrectly mentioned minified in my original description. No, I’m not minifying anything (my mistake for mentioning that) and if you ignore that word and read the rest of my issue, the problem remains. My problem stems from avia-merged-styles loading after my child theme’s style.css (as in the title of this thread). I haven’t seen avia-merged-styles before and it looks like a new stylesheet with the latest Enfold version. I’m wondering why it is also the last stylesheet to load?

avia-merged-styles appears in Enfold’s new asset-manager.class.php in
function try_minifying_scripts() around line 65.

The live version of the website at crhlaw.com.au which uses Enfold version 4.2.3 has no such css file.
The staging version of the website as per the credentials I supplied, using Enfold version 4.2.6 now has the newly-defined Enfold avia-merged-styles stylesheet. If you search for it in the source, you’ll see it is listed as the very last stylesheet and hence whatever it contains overwrites the custom button styles I’ve specified in my child theme.

I’m not sure how else to make clear that this is a new Enfold class, with a new function, that loads a css file after all others have loaded and so causes problems with styles defined in a child theme. I’d like my child theme to load after any Enfold stylesheets without having to code a workaround in my functions.php, as I’m going to have to replicate this on all my client websites.

If you debug the source you’ll see what I mean ;)). Hope you can help.

Cheers
Diana

Hey Ismael

Spot on! The character encoding was set to latin on column ‘meta_value’ in table ‘wp_postmeta’. I’ve changed it to UTF8 and haven’t seen a question mark since. I should have thought of that one…

Thank you so much for the fix. The issue is now solved.

Warm regards
Diana

Hi Victoria
I’d like the overlay to be there as the image may be used to link to an advertiser’s page.

Thanks
Diana

Hey Ismael. I’ve used the Facebook Debug tool already to scrape images but the issue isn’t to do with how a post actually looks when it is shared to FB ;o). I’m kinda confused by the direction the answers are taking. The issue here is with a featured image not being picked up in the post editor, further down where the Yoast SEO plugin inserts it’s tabs. With the premium Yoast plugin installed, there is an extra feature available in the post editor (within Yoast’s tabs) that displays a preview of how the post would look if it is shared. With one of the ‘default’ themes like Twenty Fifteen, the Yoast FB preview picks up the post’s featured image okay. When I switch to Enfold, no preview image. Hence why I asked further up if the Enfold theme saves a post’s Featured Image in a different way say to the Twenty Fifteen theme. Yes or no would do, as that question hasn’t been answered. I feel like I’ve explained this several times… You’re normally right on-the-money with many of your answers so just a bit of background with how the Featured image is handled would help. I don’t think that looking at the dashboard is going to give any of us answers as to why the premium plugin isn’t working with Enfold.

Many thanks
Diana

Hey Victoria

Yoast already took a look at a live site belonging to one of my clients and suggested I switch off plugins, theme etc. They were happy with the open graph side of things. Since switching off plugins, or switching the theme wasn’t practical on a live site, I installed a very simple WordPress site (using Mamp PRO on my local dev PC) with only Enfold and Yoast SEO installed. Just to recap, I activated the Yoast SEO license on my local site – all good. The plugin worked as expected with the Twenty Fifteen theme, no dice with Enfold. I got back to Yoast with the issue and they have referred it to their development team. I don’t think its a server permission issue as per the link you shared, as it works with one theme and not Enfold. Wouldn’t the problem occur across all themes if that were the case?

I’ve given you access to a live site with the license activated. Please take care as you look around and let me know if you find anything.

Many thanks
Diana

Hi Rikard
Thank you for getting in touch and I’m pleased to report back that I’ve managed to sort the issues. The editor problems were essentially caused by some page optimization code I had inserted a while back in the functions.php. Namely I was stripping the version from scripts and stylesheets. I added a simple function (reproduced below) that is widely promoted on the internet to “remove query strings from static resources” but in my case, removing the versions from all js and css files caused a conflict with the TinyMCE editor and raised some errors/exceptions. I also have ‘expires header’ settings defined in .htaccess that would have prevented the files being replaced by the browser since they were lacking version numbers. The Editor problem appeared seemingly at random, after I made a minor change to the child theme’s stylesheet css. Why it had a knock-on effect at this time I’m not sure, but hopefully this has fixed the problems others have also seen regarding ‘invisible’ text and unresponsive Visual and Text tabs. It took me a while to debug, but I got there in the end.

Here is the functions that I have commented out:
/* Remove Query Strings from Static Resources Fix */
// stuffs up caching if versions are removed
function _remove_script_version( $src ){
$parts = explode( ‘?ver’, $src );
return $parts[0];
}
add_filter( ‘script_loader_src’, ‘_remove_script_version’, 15, 1 );
add_filter( ‘style_loader_src’, ‘_remove_script_version’, 15, 1 );