daricedotorg

Jetpack stats is working correctly again after downgrading PHP from 8.4.3 to 8.2

In the error logs I found I had one error in my code in single.php
I was using double quotes in one line instead of single quotes. The template was working fine all that time even with PHP 8.4.3

It might be possible tho that that error in PHP 8.4.3 was interferring with the jetpack visitors registration code. Because single.php is the page on which we receive most of our visitors and it would explain the reduced visitors registration.

In any case. I downgraded the PHP version and fixed the code error. Everything works fine again.

I went through the error log. It was just 2 errors that was related to wrong single quote use in one line of code in single.php. It was an error that was there a long time. I fixed it and I had the hosting downgrade the PHP version to 8.2.

Looks like that amount of visitors is now registering to our usual Friday amounts.

Next week when I have more data I’ll know for sure if it is fixed now. But the issue with low visitors amount in Jetpack stats started the moment 8.4.3 was activated. We have years of Jetpack stats data so it was immediatly noticable that something was wrong.

I’ll update next week if it was fixed for sure.

• This reply was modified 1 month, 1 week ago by daricedotorg. Reason: spelling error

Thanks!!

Hi!

Yes, I tested in other browsers on macOs (Safari, Brave and Orion) and it works fine. The user who contacted me about the issue is on Windows. And his main browsers is Firefox. He detected the issue. And told me it does work in Chrome in Windows.

I just tested again and it seems like the latest update of Jetpack fixed the problem. It works again. Although the change log doesn’t mention anything about the comment module.

I’m gonna consider this as a temporary bug in Jetpack that is now fixed.

Sorry for the very late answer. Life happened and I was away from work.

The problem is solved it was this that was breaking it after the update:

“By the way, ‘views per day’ is not a valid order_by option ?? The order_by parameter accepts the following values: ‘comments’, ‘views’ (default), or ‘avg’ (see Parameters).”

I changed the ‘order_by’ to ‘avg’ and it works fine now.

Thanks!

Thanks!

As for the width issue. An editor would insert an image with media credit in the article with a 600px width for example. The original image is 1200px. The instruction is for them to insert it at at least 900px. Which often they don’t do.

When I edit the article and click on the edit icon on the image to adjust the width in the custom width option. It doesn’t take. I have to remove the media credit tags for the new width to take. Probably because the media credit retains the previous width of 600px.

It is solved:

I think it was a port/router issue. After opening HTTP and HTTPS ports it started working after an hour or more. Cache had to clear.

Hi @brainstormteam,

You didn’t mention if it is the WordPress site address in WordPress settings or the Google Map address. But in any case, they are all filled.

Screenshot of plugin in editor: https://www.dropbox.com/s/xg74nm8cl6nh2no/Screenshot%202020-07-23%20at%2008.55.22.png?dl=0

Screenshot of WordPress address settings: https://www.dropbox.com/s/qom1tiyaqe2kige/Screenshot%202020-07-23%20at%2008.56.49.png?dl=0

I even made sure to open port 80 on my router. But I still get the same error

I turned on wp_debug on a live site and managed to find the problem. An old plugin that uses has_cap and a line of code in fuctions.php that uses create_function

Either of those two can break plugin updates and install. I removed them and hopefully, the problem is solved when the next plugin updates are available.

It’s not a problem specific to one plugin, I was using Shortcode as an example. All plugins have this problem. I already tried deleting plugins and installing them again.

Hence my suspicion that the problem has something to do with updating to PHP 7.3

Thanks! That Resolved the problem.

• This reply was modified 7 years, 4 months ago by daricedotorg.

Solved: conflicting archive pages + browser not displaying correct errors.

Create a non archive template for the code above and a standard loop archive.php to display results.

Thnx! The problem seems to be solved. Will monitor it.

Here its is:

[media-credit id=14 align="alignnone" width="600"]<img class="size-full wp-image-26986" src="https://profielen.hr.nl/wp-content/uploads/geld-spaarvarken.jpg" alt="geld spaarvarken" width="600" height="424" />[/media-credit]
De Landelijke Studenten Vakbond is gefrustreerd over de onderwijsbegroting van 2015, laat Hoven weten. Studenten die volgend jaar september aan hun opleiding beginnen, ontvangen geen basisbeurs meer en krijgen daar volgens hem niets voor terug.

Well this is clearly a bug in WordPress.

I tried the Twenty Fourteen Theme and that one also did not show the “Interview” category and its child with wp_list_categories()

I finally solved it by creating a new child category and assigned it the same posts as the existing child category and the categories started showing. I deleted the newly created child category and the category and child is still showing.

Now this creates another problem: when viewing all posts in the parent category in the wordpress admin it also shows all posts form the child category. On https://mysite.com/category/interview/ same thing. It will list all post in “Interview” and also posts in its child “De lector en het nieuws”.

What a headache.