pranavmahapatra

Forgot to mention that, for me this problem is with both 2.4.0 and 2.4.1, however I rolled back to 2.3.0 and it’s now working.

Here’s the entire paragraph:

Most recent data about the breeding and slaughtering of animals for food has revealed that a staggering?92.2 billion land animals are killed every year?according to the Food and Agriculture Organization.((Kitty Block, ‘A Humane World’,?The Humane Society of the United States, 5 Jun 2023, https://blog.humanesociety.org/2023/06/more-animals-than-ever-before-92-2-billion-are-used-and-killed-each-year-for-food.html))

Here’s a snapshot of the reference generated with it:

@sdobreff I was quick to notice the space before “((” in the settings, so I have already tried testing both, with or without space in the settings correspondingly adding a space before (( in the posts.

Supporting @kmammasis here’s how it looks, on my site’s post pages.

The reference section at the last is being created and is perfect just that the ((reference text)) isn’t being replaced with the footnote identifiers.

Another problem on post_type=posts (which I now think is the actual culprit for schema implementation errors on GSC, while the placement condition issue persists), there are two schemas scripts being generated and placed.

The first one is proper, but the second one is faulty and probably has a bug.

The second one in my case looks like this:

<script type="application/ld+json" class="saswp-user-custom-schema-markup-output">Undergraduate Physics Major Student, and a generalist with scholarly interests in Nuclear Physics, Environmental Science/Studies, and Astronomy</script>

The “Undergraduate Physics Major Student, and a generalist with(…)” is actually the author’s description.

I also haven’t filled in the “Custom profile information: Custom Schema (SASWP)”.

@boomdevs I had already used them earlier, but that doesn’t work as well.

But thank you for your response, I took another look, and finally found the correct selectors:

.bd_toc_content .bd_toc_content_list ul li a
{font-size:20px !important}

• This reply was modified 1 year, 9 months ago by pranavmahapatra.

Why did no one tell me async is the same as async=””

;-; So sorry for the trouble and thank you so much for mega humble support. I thought it’s not equivalent, and that’s why the ads weren’t loading, but it was related to caching.

Thank you so much George.

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

No, you used the wrong code, it has async=”” already.

The right one is where it’s just async, WordPress changes it to async =””

Use this or something similar to it,

<script async src="https://somelink.do"></script>

Then copy the block using the copy block option under the “three dots”, and then paste it.

You’ll see async will be changed to async=””

Alternatively, not doing the copy-paste block thing, just have the code on the post, save it, and then refresh/revisit the post, you’ll see the same – async will change to async=””

Note that I was able to reproduce this without any plugins working on the site.

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