meijersjc

The new version is resulting in a new glitch: An error occured in the ‘keywordDensity’ assessment.

Going to see if there isn’t something else throwing a spanner in the works.

Incidentally, content analysis now works flawlessly.

Partially. It’s still erratic, in regards to content analysis. Most feature sets work in a stable manner, but reading Fusion Builder generated syntax can still cause issues. Some of those can be attributed to Avada, I should mention, there are content elements which simply do not play well (title blocks, for example, also jump/anchor links throw a spanner in the works of the metabox). Others are very similar to the Yoast / VC issues.

Keep in mind content analysis can be turned off now, a consideration to be made – though wasteful as it is a very powerful Yoast feature.

Let’s hope it’ll get tackled. The new content analysis is quite interesting. And while in some realms of products and services it’s a no-go (i.e. where names match both keywords and moment id’s) for everything else it’s quite a good starting point.

A rollback? That removes the glitches, the pre 3.3.0 version was fine.

Correct. I’ve cloned the site to a local instance to run a test list of function mods, plugins, etc. Unfortunately, the glitches prevail. I’ve done a reset of it to see if there’s anything within modified contents that could throw a spanner in the works, but both with the unit test as blank it still pops up. It also makes no difference whether it’s in development mode or compiled (not surprising, but still, you never know).

What’s bugging me is that the glitches are so unpredictable. Making edits in any order within the Yoast metabox can suddenly cause the content analysis to work, or just partially, or not at all. Same for keyword analysis. It’s just an impression, but I get the idea that Yoast is having problems with reading content elements after an instance of a title block / text block combo.

The really wierd thing is that when I use a test page without that Avada Fusion Builder the quirks also happen, though only for content analysis.

4.0.3

Well, the 3.3.1 update did not help, I’m afraid. Where before there were glitches, currently content analysis produces no results, and keyword analysis fails to read a variety of Avada elements. To give an example, any title block it doesn’t read as h1/h2/etc, but as regular text.

No, none. Nothing of php errors either. Quite puzzling.

I can’t put the finger on it, it’s as if the metabox elements simply lag behind, or selectively update when utilised.

Same observation as the original message in this topic, curiously though I see no js errors in the console. No php errors either.

I bumped into the same strange issue. As far as I can tell, TOC+ doesn’t have a mobile-savvy offset mechanism to work around it, but it is strange as the last time I tried it (several versions ago) I didn’t stumble into the middle of sections.

Wonderful ??

As for breadcrumbs, this is with Yoast’s breadcrumb feature active, as well as inactive (native WP). So yeah, time to figure out a rewrite function which also handles the post type labels.

I left a comment in the Github issue – somehow I managed to completely miss Stellar Places there, apologies.

Popping back in, I noticed that the slug ID isn’t rewritting in breadcrumbs, it’s displayed as “Place”.

Now it might be me, trying to rewrite the above function to take this into acount, but I just can’t seem to find where that specific “Place” comes from?

(also, any chance you’d consider extending the shortcode options to also display a text list of the address details? ?? Maybe best as a second shortcut, so that it could be placed elsewhere?)

G’day:-)

Cheers for the response! Alright, let’s see. That directions search, yeah that should be able to do at least part of the trick. Also, 24 hours a day never seems enough, doesn’t it ??

The traffic layer, that’s neat. Very neat. Cheers!

No worries!

A seperate stylesheet would be good. That would make it more straightforward to tweak and then compile (LESS) yes.

That way it’s simpler to keep the plugin output seperate from theme css editing, while at the same time easier to manage – especially as skins. The alternative in my case is adding styles within the child theme, as opposed to keeping things within the plugin feature.