We are based in Europe with a GMT+1/GMT+2 time zone - support replies may be delayed due to time zone differences with your country.
- This topic has 14 replies, 1 voice, and was last updated 3 years ago by
.
-
Posts
-
i try to open the stats page i cant.
An E_COMPILE_ERROR error occurred due to line 65 in the file /home/faharasnet/public_html/wp-content/plugins/post-pay-counter-pro/classes/google-api-php-client-master/src/Google/Utils.php . Error message: Array and string offset access syntax with curly braces is no longer supported
but once i enter the option page i found
Google Analytics/Adsense Status
There has been a critical error on this website. Please check your site admin email inbox for instructions.Hi there,
this is a similar issue to what you have already encountered https://postpaycounter.com/forums2/topic/your-site-is-experiencing-a-technical-problem/ and is due to a conflict with some other plugin that uses Google’s APIs. I donΝ’t have much guidance I can provide, unfortunately, other than trying to disable the other plugin and see if the issue persists.A nice day,
Stefanoits solved one i downgrade the php from php 8 to php 7.4
Oh, that’s interesting, thanks for reporting that! I must say I haven’t yet tested PHP 8, will do so ASAP!
I can confirm the current Analytics API version is incompatible with PHP 8. I will work on this to get it fixed as soon as possible!
This reply has been marked as private.PPC Pro works on php 8 now, but I get another error by email on core PPC now, when I try to filter posts by post status (draft, pending, scheduled, etc).
Error type E_ERROR was caused in line 347 of the file /var/www/vhosts/<siteurl>/httpdocs/wp-content/plugins/post-pay-counter/classes/ppc_generate_stats_class.php. Error message: Uncaught TypeError: current(): Argument #1 ($array) must be of type array, null given in /var/www/vhosts/<siteurl>/httpdocs/wp-content/plugins/post-pay-counter/classes/ppc_generate_stats_class.php:347
Stack trace:
#0 /var/www/vhosts/<siteurl>/httpdocs/wp-content/plugins/post-pay-counter/classes/ppc_generate_stats_class.php(347): current()
#1 /var/www/vhosts/<siteurl>/httpdocs/wp-content/plugins/post-pay-counter-pro/classes/ppcp_stats_class.php(112): PPC_generate_stats::format_stats_for_output()
#2 /var/www/vhosts/<siteurl>/httpdocs/wp-content/plugins/post-pay-counter-pro/classes/ppcp_edit_posts_list_class.php(62): PPCP_stats::get_stats_by_post_ids()
#3 /var/www/vhosts/<siteurl>/httpdocs/wp-includes/class-wp-hook.php(303): PPCP_edit_posts_list::on_load_edit()
#4 /var/www/vhosts/<siteurl>/httpdocs/wp-includes/plugin.php(189): WP_Hook->apply_filters()
#5 /var/www/vhosts/<siteurl>/httpdocs/wp-admin/includes/class-wp-posts-list-table.php(177): apply_filters()
#6 /var/www/vhosts/<siteurl>/httpdocs/wp-admin/edit.php(225): WP_Posts_List_Table->prepare_items()
#7 {main}
thrownI set php to 8.0.12 (FPM by Apache), go to post list and click any of the post statuses to filter post (drafts, published, scheduled or any custom ones). That produces an error (This site received a critical error. For more detials check administrators email) and emails me the error report above.
There could be a conflict with any of my other 100 plugins (sorry, huge site), but the error report only lists PPC as causing them. The thing that comes to mind is, the custom post statuses created with Oasis workflow. But it gives errors even on default WP statuses. I’ll do more testing on my test site, to see if there’s a cross plugin conflict.
WordPressa 5.8.2
Theme: Newspaper (11.3.2)
Plugin: Post Pay Counter (2.765)
PHP 8.0.12Thatnks for the details, I can confirm the issue exists in PPC.
It can be fixed by replacing line 342 of the file classes/ppc_generate_stats_class.php with the following:
if( is_array( $author ) and ! empty( $author ) ) {I will release a public update soon, but let me know if you try this out so I can be sure it also fixes the problem for you! π
A nice day,
StefanoThis fixes it. Thank you very much Stefano π
plz Stefano issue the new update and thin about new design for stats
- The topic ‘There has been a critical error on this website’ is closed to new replies.