MailShark

Thank you kindly.

Just as an FYI, we did raise this about a year ago also when we were going through another round of SEO optimisation on the website. The developer / support we spoke to at the time said the Alt tag’s are used primarily used for the blind, which is true, but that doesn’t negate the fact that for SEO purposes every image must have Alt tags. Google looks for them and every SEO program out there looks for them and reports on not finding them.

We also realise this requires code changes, but so be it, SEO is required for every website.

Thanks again for your forwarding to the devs.

Hi. Is there any solution to this?

Which module is producing it?

We have this problem and don’t know what the actual fix is.

We have tried re-installing the post indexer, then rebuilding the index, but to no avail.

Any ideas?

Hi breakling. Just to confirm from the information you provided above, when you go into:

* Expert Settings in WP-Piwik Settings

for the “CDN URL https://: ” would you just put in the full URL (without the https:// ) to the piwik.js script?

Please read this post:

https://www.ads-software.com/support/topic/yoast-seo-30?replies=1

We had similar problems which went away with all cache clears.

Yoast SEO now works.

Please read this post:

https://www.ads-software.com/support/topic/yoast-seo-30?replies=1

We had similar problems which went away with all cache clears.

Yoast SEO now works.

We’re experiencing this problem also. Seems we all need to raise a support bug on Github here:

https://github.com/jdevalk/wordpress-seo/

Instead of this support forum.

Hi Fakhri,

Thank you kindly. I have gone to the contact us page and left you the email address.

Many thanks again.

Hi Chrystl. That is a good idea. We use over 60 plugins so it’s no small feat but will organise this over the weekend and hopefully report back to you, letting you know how it goes.

Thank you.

Hi. That is the option I need. I need that set by default when the Polylang is activated.

Because it’s disabled by default, I can’t ever click “Save Settings” because it always gives me “WordPress Failure Notice”.

If I couldhave the “Hide URL language information for default language” set I think the module will work.

Hi Chrystl. Yes, on the WP backend, as soon as we activate the Polylang module, it automatically *adds* the /en to our website.

Adding the https://www.example.com/en breaks the website as trying to visit https://www.example.com sends you to https://www.example.com/en

Because https://www.example.com/en doesn’t exist, a 404 is produced (no proper honepage is shown).

We then go to the WP backend, to Settings -> Languages -> Settings and the default is:

BULLET The language is set from the directory name in pretty permalinks

We then try and select:

BULLET The language is set from content

and click “Save Changes”

then get “WordPress Failure Notice” with:

Are you sure you want to do this?

Please try again.

and can’t continue. Have to deactivate the module.

Hi. Just checked, no, no /en off the wordpress root.

Checked .htaccess file also, nothing in there performing any redirections either.

The problem is Polylang adds the https://www.example.com/en to the end of the URL and trying to get rid of it from WordPress backend fails. Better if it didn’t add the /en to begin with, at least then can try and configure the module.

Hi Kishor,

Thanks, never thought of that. Unfortunately, that wasn’t it. I tried with Chrome, Firefox, IE and all had the same problem. Most thumbnails show up but there’s always at least one that doesn’t. Makes the website look unprofessional.

We used to have most of our content on the related items, and they didn’t show up the thumbnails. We raised with support and after a couple of weeks they confirmed the bug. They pull all the OpenGraph items and we present those. Turned out to be a bug in their end.

Unfortunately, to date we’ve never seen it fixed or heard back on the case. We follow up once a month.

Hi. I’m answering on behalf of dorza. We never did figure it out. We worked around it by simply adding it into the “footer” areas of the theme, which gives us 6 footer areas.

In the footer area we added HTML code to reference what we needed to.

Uninstalled 1.0.3 and installed 1.0.2, problem has been resolved.

Hi. I think the below:

1.0.3 shows all posts at one month at a wrong year, 1.0.2 shows all correctly.

is what I’m experiencing too. The year is 2014 and all posts are shown in Jul, with all other months 0.

The < and > have disappeared too, just showing 2014.

Does the author know about this problem?