WPKube

Hi Carlos,

You’re welcome, happy to hear the issue is resolved. And thank you for the rating.

Hi @wpfiend

This is on line 171 of the source code of homepage:

<script><meta name="google-site-verification" content="..." /></script>

It’s just before the </head> closing tag.

The error from the developer console:

domain.com/:171 Uncaught SyntaxError: Unexpected token '<'

• This reply was modified 3 years, 7 months ago by WPKube.

Hi @egurry

The update is released (version 1.2.8).

Give it a try and let me know if it resolves the issue.

One thing to note, the “show_count” functionality isn’t limited by the taxonomy/term filter.

The WordPress function count_user_posts() that returns the amount of posts a user has, does not have the option of filtering by taxonomy/term.

If that is an issue then let us know and we’ll figure out a custom approach to getting the counts so the taxonomy/term can also be part of it.

Hi @progonat @labi2000

The new update (version 2.28) is released.

If you are using the widget you’ll see the new option called “On Archive Display” with the options “All”, “Siblings”, “Children” and “Descendants”.

“All” is the default behavior.

“Siblings” shows the terms that are at the same level as the term for which the archive is for.

“Children” shows the terms whose parent is the term that the archive is for. That’s the one you want @progonat

“Descendants” shows all the child/grandchild/… terms of the term that the archive is for.

If you use the shortcode then the attribute is on_archive_display and the values are the labels mentioned above, just lowercase.

[cool_tag_cloud on_archive_display="children"]

• This reply was modified 3 years, 7 months ago by WPKube.

Hi @wpfiend,

MailChimp accepts the first name and last name as separate fields.

In order to have one field shown but actually populate the 2 fields for MailChimp we use some JavaScript to split the value of the shown field to get the separate first name and last name.

But I see JavaScript errors on your site, which means that JavaScript functionality gets broken for all JavaScript code that comes after the error.

The issue is that you have google site verification code inside of a <script> tag. It’s a <meta> tag so it should not be inside of <script>

I’m assuming you are using some plugin to insert code into header, so go there and make sure the <meta name="google-site-verification"...> is not wrapped inside of <script></script>

Hi @progonat @labi2000

Sorry for the delay, the update will be released today.

Hi @wpfiend

Not at the moment, sorry. We are working on a new version of the plugin which will have many more features, but that feature will most likely not be part of the free version of plugin, I can’t say for sure at the moment.