msebald

I got the same error just now from the plugin PHP Compatibility Checker when I did the check if I can upgrade PHP to 7.2:

FILE: wp-content/plugins/subscribe-to-comments-reloaded/options/stcr_system.php
——————————————————————————————————————-
FOUND 1 ERROR AFFECTING 1 LINE
——————————————————————————————————————-
484 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
——————————————————————————————————————-

Is it possible to fix this?

If the error is right then the function is gone since PHP 7.0 (which is also outdated).

Thanks and cheers,
Martin

Ok, that means the filters won’t work anymore in the future and that I can remove it and only use the new code posted today?

No worries, I won’t change anything. I don’t care a lot about the 404 errors, I just saw these in the stats. Hopefully no user experiences are harmed by proxy oder other caches.

I checked for today. There are some connects from Google Bot, but also “real” traffic. E.g.:

xxx.dip0.t-ipconnect.de – – [29/Nov/2018:00:43:21 +0100] “GET /wp-content/uploads/pro-taucher_site-logo.png HTTP/2.0” 200 22071 “https://www.pro-taucher.de/wp-content/plugins/easy-fancybox/fancybox/jquery.fancybox.min.css” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36”
xxx.dip0.t-ipconnect.de – – [29/Nov/2018:00:43:21 +0100] “GET /wp-content/plugins/sam-pro-free/js/sam.pro.layout.min.js?ver=1.0.0.10 HTTP/2.0” 200 620 “https://www.pro-taucher.de/wp-content/plugins/easy-fancybox/fancybox/jquery.fancybox.min.css” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36”
xxx.dip0.t-ipconnect.de – – [29/Nov/2018:00:43:21 +0100] “GET /wp-content/plugins/wp-gdpr-compliance/assets/vendor/micromodal/micromodal.min.js?ver=1543436779 HTTP/2.0” 200 2050 “https://www.pro-taucher.de/wp-content/plugins/easy-fancybox/fancybox/jquery.fancybox.min.css” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36”

Hi,

ok, I understand. I was wondering as there are so many 404 in just one month (November) and also many the months before.

Sorry that I rang a bell here.

Thanks again and cheers,
Martin

Hi,

the version I have installed is 1.8.9 which seems to be the current version.

The website is: https://www.pro-taucher.de

The main directory of the plugin has the following directories/files:
css/
images/
inc/
js/
languages/
easy-fancybox.php
readme.txt

For example, I do not see a fancybox directory where some of the files mentioned above should be in. Hm…

Cheers,
Martin

Hello,

I am not sure if I understand. What happens here is:

I use: %%title%% %%page%% %%sep%% %%parent_title%% %%sep%% %%sitename%%

For a child page like in the hierarchie like Home – Grandparent – Parent – Child it shows in the title:

Child Title | Parent Title | Sitename

The Page Home – Grandparent – Parent shows:

Parent Title | Grandparent Title | Sitename

So I do not see the complete breadcrumb in the page title her, only the direct parent.

I am having the problem with pages. Twentysixteen child theme with minor changes. I use this shortcode in my theme files:

<?php if ( function_exists(‘yoast_breadcrumb’) ) {yoast_breadcrumb(”,’ | ‘);} ?>

PHP 5.6.x, upgrade from Yoast SEO 6.x to 7.0.x.

I have the same problem. PHP 5.6.x.

Also next to disabled breadcrumbs a lot of other settings were at their defaults (also empty). Not the first time a Yoast SEO upgrade did kill (some) settings. Not good for SEO. Not everybody notices it right away. Also it sometimes is hard to recall the correct settings….

I am not aware of a patch / new feature. But I also did not take lots of time after posting my first request here without receiving any reply.

Frank, thank you for the information. I just upgraded to 1.9.4 and activated the earlier init of AO via wp-config.php. ??

That’s great, thank you! The IP address thing really was a show stopper here. No idea why it is not working what I entered on the google page.

PPS: Caching problem at Google. It works also for the second site. Strange that it worked after 2 seconds on the first but needed 5 minutes or longer for the second site.

I will stick with no IP restrictions, see above. Does not make much sense (for me). But something is not working as it should.

PS: Yes, this is my real IPv6 (and also IPv4) address. I did enter it like it is – also the examples which Google shows let me think that I entered it exactly as Google wants it.

Interesting, I thought I have to enter IP addresses – the dialog looks like it or it is pushing me very hard to enter IP addresses.

For the first site I was able to get a positive test result right away by removing all entered IP addresses. For the second site not…

Checking your key ...

API key not OK, your key seems to be valid, but restricted to an IP-address which is not your server's.Try changing the allowed IP for your API key to include this one: 5.9.143.45

This time the IPv4 address is shown, strange! More strange that now I see on the Google website that all IPs are allowed.

Hm…?

BTW: I think restricting IP addresses is a bit too much for most installations as there is the API key. If the key is not leaked, it does not make any sense to restrict IP addresses.