balbert

Any info on this? We just upgraded and are running into the same issue.

stake trace:

in FacebookAds\Http\Exception\RequestException::create called at /mnt/nfs/html/ilikecrochet.com/wp-content/plugins/official-facebook-pixel/vendor/facebook/php-business-sdk/src/FacebookAds/Http/Client.php (226)
 in FacebookAds\Http\Client::sendRequest called at /mnt/nfs/html/ilikecrochet.com/wp-content/plugins/official-facebook-pixel/vendor/facebook/php-business-sdk/src/FacebookAds/Http/Request.php (286)
 in FacebookAds\Http\Request::execute called at /mnt/nfs/html/ilikecrochet.com/wp-content/plugins/official-facebook-pixel/vendor/facebook/php-business-sdk/src/FacebookAds/Api.php (152)
 in FacebookAds\Api::executeRequest called at /mnt/nfs/html/ilikecrochet.com/wp-content/plugins/official-facebook-pixel/vendor/facebook/php-business-sdk/src/FacebookAds/Api.php (205)
 in FacebookAds\Api::call called at /mnt/nfs/html/ilikecrochet.com/wp-content/plugins/official-facebook-pixel/vendor/facebook/php-business-sdk/src/FacebookAds/ApiRequest.php (172)
 in FacebookAds\ApiRequest::execute called at /mnt/nfs/html/ilikecrochet.com/wp-content/plugins/official-facebook-pixel/vendor/facebook/php-business-sdk/src/FacebookAds/Object/AdsPixel.php (240)
 in FacebookAds\Object\AdsPixel::createEvent called at /mnt/nfs/html/ilikecrochet.com/wp-content/plugins/official-facebook-pixel/vendor/facebook/php-business-sdk/src/FacebookAds/Object/ServerSide/EventRequest.php (285)
 in FacebookAds\Object\ServerSide\EventRequest::defaultExecute called at /mnt/nfs/html/ilikecrochet.com/wp-content/plugins/official-facebook-pixel/vendor/facebook/php-business-sdk/src/FacebookAds/Object/ServerSide/EventRequest.php (277)
 in FacebookAds\Object\ServerSide\EventRequest::sendToCAPIEndpoint called at /mnt/nfs/html/ilikecrochet.com/wp-content/plugins/official-facebook-pixel/vendor/facebook/php-business-sdk/src/FacebookAds/Object/ServerSide/EventRequest.php (247)
 in FacebookAds\Object\ServerSide\EventRequest::execute called at /mnt/nfs/html/ilikecrochet.com/wp-content/plugins/official-facebook-pixel/core/class-facebookserversideevent.php (197)
 in FacebookPixelPlugin\Core\FacebookServerSideEvent::send called at /mnt/nfs/html/ilikecrochet.com/wp-content/plugins/official-facebook-pixel/core/class-facebookwordpressopenbridge.php (162)
 in FacebookPixelPlugin\Core\FacebookWordpressOpenBridge::handle_open_bridge_req called at /mnt/nfs/html/ilikecrochet.com/wp-content/plugins/official-facebook-pixel/facebook-for-wordpress.php (125)
 in FacebookPixelPlugin\FacebookForWordpress::handle_events_request called at /mnt/nfs/html/ilikecrochet.com/wp-includes/class-wp-hook.php (324)
 in WP_Hook::apply_filters called at /mnt/nfs/html/ilikecrochet.com/wp-includes/class-wp-hook.php (348)
 in WP_Hook::do_action called at /mnt/nfs/html/ilikecrochet.com/wp-includes/plugin.php (565)
 in do_action_ref_array called at /mnt/nfs/html/ilikecrochet.com/wp-includes/class-wp.php (418)
 in WP::parse_request called at /mnt/nfs/html/ilikecrochet.com/wp-includes/class-wp.php (813)
 in WP::main called at /mnt/nfs/html/ilikecrochet.com/wp-includes/functions.php (1336)
 in wp called at /mnt/nfs/html/ilikecrochet.com/wp-blog-header.php (16)
 in require called at /mnt/nfs/html/ilikecrochet.com/index.php (17)

@vmarko any word on this. Is it possible to change the location of the file or filter where plugin writes to?

Not sure your exact situation but HyperDB doesn’t install like a regular plugin and actually files need to be copied to your “wp-content” and WordPress root folder to actually activate.

Further it is used when you have a certain DB setup like a Write DB with one or more Read DBs. This might be your setup.

This plugin is considered a “drop-in” plugin. If it is active you’d see it in your plugins page list in the admin if you click on the “drop-ins” type filter at the top of the page: /wp-admin/plugins.php?plugin_status=dropins

If it isn’t active then you are probably okay to remove those folders but again without knowing your actual setup I would take my advise with caution and make sure you don’t break your site.

I posted the same thing. Basically the version for download is the tagged 1.9 version but found out they forgot to update the version. So even though it says 1.8 it really is the 1.9 version.

Note that if you compare that with Trunk, there are a couple of other changes namely a fix for a deprecation error for WordPress 6.1 or higher.

if anyone has the same issue, basically the version for download is the tagged 1.9 version but found out they forgot to update the version.

If you compare this against trunk as of 12/15/2022 there are a couple of further updates which you might want to get. Namely the trunk version fixes a deprecation error for WordPress version 6.1 or higher.

I’m also getting this issue when upgrading to PHP 8.0.14. Could this be a 8.0.x incompatability?

Also it seems to be intermittent… i can load the users admin page, but then when i load admins only it fails, but not every time.

I guess could also be a server issue and/or cache issue?

great thanks for the info. I am seeing entries with pageviews column set to 2 or 3 or 4 etc…looks like this is all working.

When do you think this update would be integrated in an official update? 5.2.3?

thanks again for the quick response.
Bob

I implemented the change and so far it looks to have eliminated the warning.

is there anything else i should check to make sure no issues in functionality other than the widget appearing without issue?

any way to make sure caching is working correctly?

thanks,
Bob

also forgot to mention running WP v 5.4.2 soon to update to 5.5.

just saw your other question about time zone.

our servers are set to UTC, but WP is set to Eastern/New York.

Thanks for getting back so quick. Here is some more information:

– we are on PHP 7.3.17
– we are using Redis in AWS via elasticache
– we are running W3TC plugin Version 0.14.3

let me know if you need more info.
Bob

fyi… i updated the plugin for deprecated split().
//list($delim, $page_index) = split(‘/’, $query_string[‘page’]);
list($delim, $page_index) = explode(‘/’, $query_string[‘page’]);

according to php.net, split is deprecated thus you might run into issues with newer php server installs.

Greg,

Thanks for the info. Gave it a try and boy it is really slow on my site to add content, create slides and slideshows and to render. Not sure why it would have that issue. Once i remove the short code from a page or from a panel widget the page loads fast again.

I think the what they save and create slides/slideshow doesn’t work with my multisite install.

ever heard of this type of issue?

I had the same problem and was using wp 3.5 in my dev site. I upgraded to 3.8 and that issue went away.

What version are you using? could there be a conflict with older versions of wordpress?

Not sure if this will help, but this is how I think we are going to deal with this.

For images already placed in posts and pages, we’ve used a redirect in our .htaccess file. for our regular non-multi site wp, we’ve used:
RewriteRule ^wp-content/uploads/(.*)$ https://thebucketname.s3.amazonaws.com/wp-content/uploads/$1 [L]
of course your path might be different.

For our wp-mu site we’ve created our own ms-files.php to point to our s3 path and then pointed to it via .htaccess ala this:
RewriteRule ^(.*/)?files/(.*) wp-content/mu-plugins/vital-scripts/ourown-ms-files.php?file=$2 [L]

in that file basically we’ve replaced:
$file = rtrim( BLOGUPLOADDIR, '/' ) . '/' . str_replace( '..', '', $_GET[ 'file' ] );
with
$file = "{$bucket}.s3.amazonaws.com/blogs.dir/{$blog_id}/files" . '/' . str_replace( '..', '', $_GET[ 'file' ] ) ;
we also removed/updated some of the code to work with S3.

This is the down and dirty that we’ve done but since the plugin creates a global object of
$as3cf you could use that to get your bucket and other features set via the plugin to use in various urls.

So far it seems to be working.

Not implemented but and idea for older images that haven’t been place into posts yet, you could use the wp_get_attachment_url filter to filter the url before it gets inserted. Doing it on the fly would basically eliminate the need to update the db. Just a thought.

thanks