eragonsoftware

@masaakitanaka Brother you are a legend !
Thank you very much for your reply, and your explanation.
If I would not have been in such a hurry, I would have noticed it.

Thank you for your great plugin !

I personally simply changed the version number in the main PHP file, that’s where the issue is, the content of that file may have changed, I don’t know, haven’t checked, but if the repository says its version number should be 3.3.3, then consequently that’s what has to stand at the top header of the PHP file

facebook-for-woocommerce.php has this at the top / the comment header

// phpcs:ignoreFile
/**

• Copyright (c) Facebook, Inc. and its affiliates. All Rights Reserved
  *
• This source code is licensed under the license found in the
• LICENSE file in the root directory of this source tree.
  *
• Plugin Name: Facebook for WooCommerce
• Plugin URI: https://github.com/woocommerce/facebook-for-woocommerce/
• Description: Grow your business on Facebook! Use this official plugin to help sell more of your products using Facebook. After completing the setup, you’ll be ready to create ads that promote your products and you can also create a shop section on your Page where customers can browse your products on Facebook.
• Author: Facebook
• Author URI: https://www.facebook.com/
• Version: 3.3.2
• Requires at least: 5.6
• Requires PHP: 7.4
• Text Domain: facebook-for-woocommerce
• Requires Plugins: woocommerce
• Tested up to: 6.7
• WC requires at least: 6.4
• WC tested up to: 9.6
  *
• @package FacebookCommerce
  */

I changed 3.3.2 to 3.3.3 AFTER updating, and it’s allright, the nag disappeared.

Hi Danny, thank you for your reply

No errors are present, even if I turn debugging on.
Cron works allright, sometimes Litespeed cron fails to execute, but it executes later (as in … same day, but with a delay)

There is an events_buffer.php file in the uploads/koko_analyitics folder, however, it seems strange that its content is exit() right after the php startline, but after the ?> closing php bracker, there are some serialised data lines
like
a:6:{i:0;s:1:”p”;i:1;i:1739027226;i:2;i:38004;i:3;i:0;i:4;i:1;i:5;s:22:”http://m.facebook.com/”;}
Is that how it’s supposed to be ?

I’ve replaced the real path below, for safety reasons, with 3 dots

<?php
/**

• @package koko-analytics
• @license GPL-3.0+
• @author Danny van Kooten
  *
• This file acts as an optimized endpoint file for the Koko Analytics plugin.
  */

// path to pageviews.php file in uploads directory
define(‘KOKO_ANALYTICS_BUFFER_FILE’, ‘/…/public_html/wp-content/uploads/pageviews.php’);

// path to functions.php file in Koko Analytics plugin directory
require ‘/…/public_html/wp-content/plugins/koko-analytics/src/collect-functions.php’;

// function call to collect the request data
KokoAnalytics\collect_request();

atec cache info is 1.3.9, there is no update available from ww.wp.xz.cn

the apcu I installed yesterday, was indeed, 1.5.1
Since there was no update available, I presumed there’s no newer version online.
Now I have deleted both, (apcu cache and cache info), and installed them, and now they work together, no error is generated, however, the object-cache.php can only be generated if I turn off all other caching plugins, like Litespeed.

Thank you for all your effort and keep up the good work. Wish you all the best !

Good to see you care about the plugin and tried to update it. I have followed your instruction, but unfortunately it cannot be activated, upon activation, it triggers a fatal error.

“Plugin could not be activated because it triggered a fatal error.”
That’s the notification that appears with red, from the plugins screen and it cannot be activated. If I try activating right from the plugin installation screen, a slightly different error shows
Activation failed: error

Thank you for your reply.

I don’t know how else to replicate this scenario, other then what I’ve encountered.
So try this: edit a new page, add a block or two, specifically a block with a text and image in one of them, then save the page, view it, then go back and edit anything in the page, then save it again. I enlarged the picture compared to the previous size, and modified some text in the box.
Regardless of what I did later, how many times I updated the post, the frontpage still reflected the 1st version saved.
I had no cache at server level, no caching plugin, even turned off cache in wp_config.
I tried so many times, I gave up on it, I deleted the entire block and then redesigned it from scratch, and then it worked.

Thank you for taking the time to respond, I believe the simplest solution should be always applied, which is … add a piece of code to spectra that makes sure that wp cache is cleared, output buffering, and whatever else cache can be cleared.

Sorry if I was too harsh in my first comment, I was indeed frustrated and feeling powerless because I had lost a lot of time with it.

The issue is coming from the fact that “nonce” is not transmitted via the request, as you can see in the wpc-ajax-search.php, here’s the part that displays the error:

if ( ! isset( $_POST[‘nonce’] ) || ! wp_verify_nonce( $_POST[‘nonce’], ‘wpcas-security’ ) ) {
die( ‘Permissions check failed.’ );
}
This same check is executed in 3 functions, ajax_search(), ajax_add_rule() and ajax_add_condition().

Maybe something changed in recent wordpress versions, and a different way to transmit the nonce should be used ?