rmmcclay

Same here for this…
Deprecated: WPCF7_TagGenerator::add(): Use of tag generator instances older than version 2 is deprecated. Version 1 instance (Select and Multi-Select) detected.?

> in /wp-includes/functions.php on line 6085

Same error started popping up on two of my sites. I’ll wait for the official release.

Hi Kuba -- Running the server on AWS / EC2 Instance of Linux, php -m outputs this: 

107 bash [root - Tokyo:/]-> php -m
[PHP Modules]
bz2
calendar
Core
ctype
curl
date
dom
exif
fileinfo
filter
ftp
gd
gettext
hash
iconv
json
libxml
mbstring
mysqli
mysqlnd
openssl
pcntl
pcre
PDO
pdo_mysql
pdo_sqlite
Phar
readline
Reflection
session
SimpleXML
sockets
SPL
sqlite3
standard
tokenizer
xml
xmlreader
xmlwriter
xsl
Zend OPcache
zip
zlib

Anything else I might need to install? The?php -m command?is a quick and simple way to list all installed PHP extensions on a Linux machine. This method also proves useful when we need to check which PHP extensions are currently loaded. Here, -m represents the modules and it directs PHP to list all enabled PHP extensions or modules.

109 bash [root – Tokyo:/]-> php -v
PHP 8.1.23 (cli) (built: Sep 15 2023 21:56:29) (NTS)

• This reply was modified 11 months, 3 weeks ago by rmmcclay.

Thank you KZeni! Removing the comma solved the problem. I would like to add that I noticed something odd today when I was updating many of our sites. When I went to update Contact Form 7, I saw this very unusual error: Update failed: Download failed. Not Found

I reloaded the dashboard and tried again and then it showed the “green” Updated. But then soon after, the site locked down. But after removing the comma… all was well.

It has now happened to yet another site, this makes 3 sites affected.

This has now happened on another one of our sites:

https://imgur.com/a/tWRfI3B

@biovenezuela Your solution worked for me too. Thanks!

Hi David — Yes, we successfully do daily backups from QNAP devices in Shenzhen and Ningbo to S3 buckets in both AWS Ningxia and Beijing.

Thanks, David, I didn’t have any endpoints, but I created one for a bucket, but no sure about how to configure it (create policies) yet.

On the AWS Beijing endpoint list there is a message at the bottom of the list:

The Amazon S3 s3.cn-north-1.amazonaws.com.cn Region supports only Signature Version 4 in request authentications.

Not sure if that means anything to the Updraft developers.

The failure message I’m getting now is slightly different from before:

S3 settings test result: Failure: We successfully accessed the bucket, but the attempt to create a file in it failed. Please check your access credentials. (UpdraftPlus_S3::putObject(): [6] Could not resolve host: s3-control.cn-north-1.amazonaws.com.cn)

Until I sort this out, backing up to an S3 bucket at AWS Singapore works fine.

Thanks for the reply, DNutbourne. I tried Beijing region with both Amazon S3 and S3-Compatible and neither succeed. I’ll check in 443 port, but it appears to be open.

Hi Tom —

That works! Thank you so much!

-r

Hi Tom!

Really appreciate the reply. I set the Unbind JavaScript Event from Yes to No. Then tried this bit of code (put it in the footer, easily visible in the source):

<script type='text/javascript'>
$("#mega-menu-item-1744 > a.mega-menu-link").on('click', function() {
    alert('clicked item 1744');
});
</script>

The site is: proqc.com, the link is the very top of the page, it’s “[email protected]”, a mailto link. Can’t trigger it with javascript for some reason.

• This reply was modified 6 years, 5 months ago by rmmcclay.

I’m using 1.7.11. The alert ” “Your database needs to be upgraded following the latest Popup Maker or Popup Maker extension update.” appears, I click to proceed. After twenty minutes the spinner just spins. Nothing happens. Gave up.

I had this problem too with v4.9. So to test I deleted the Contact 7 (v4.9) plugin folder and installed Contact 7 (v4.7). Everything was working again. Then I deleted the Contact 7 (v4.7) plugin folder and installed Contact 7 (v4.9) and everything started working again. Strange problem.

Thank you for the prompt reply, Themeisle!

I think you are correct as I have another installation of WordPress running PHP 5.3 on which 3.1.7 is no problem. The other system where I had the problem is running 5.2.17. Too old I know. Time to update that server.