Arno Peck

To resolve this issue, you’ll need to modify the code in the String.php, and a bunch of other files in PHPExcel folder, to use supported syntax. Since curly brace array and string offset access is no longer allowed, you’ll need to identify the specific lines of code that are causing the error and update them to use valid syntax.

Here’s a brief overview of how curly brace array and string offset access is typically used and how it has changed:

Old syntax (no longer supported):

$value = $array{0}; // This syntax is no longer supported

New syntax (supported):

$value = $array[0]; // Use square brackets for array access

You’ll need to search for occurrences of curly brace array and string offset access in the files and update them to use the supported syntax.

i did it and it was a bit tedious, I had to reload several time the page, get the error showing which file I had to modify, and after 15 mins of work the script runs again.

The most annoying part is when the script begins to run, but the excel has the error instead of the data, but again, you can fix the files that are shown in the error ()at least 4 or 5) and then at the end it works.

Then better to make a copy of the folder “advanced-cf7-db/admin/class/PHPExcel in case the plugin will be updated and the problem not fixed…

Same error
it is an incompatibility with PHP 8

Will be fixed in an update or do we have to fix the code manually?
thx

Same problem…
the CSV is working,
looks like the excel export has some code that is not compatible with the last PHP versions.
Will be fixed or the Excel export will be removed?

Same problem here, any solution?
Until solution will be available I am going to disable the plugin,
Thx

• This reply was modified 1 year, 3 months ago by Arno Peck. Reason: added 2 lines
• This reply was modified 1 year, 3 months ago by Arno Peck. Reason: correct typo

Hello @jamesosborne

I asked to the hosting about firewall rules and REST,
they disabled some WAF rules and they told me that sitekit.withgoogle.com was reachable.
I have checked the site admin, but te errors where still there…
So i tried first disable and re-enable the plugin, but still was not working.
Then I disabled AND uninstall the plugin, and then reinstall it.
After reinstall, and activated it, it was working fine!

So, i cannot say exactly what was the problem, but now has gone.
I hope can help

ciao ciao

Finally I have solved in this way:
– disable Site Kit Plugin
– uninstall it
– reinstall it
then IT WORKED for me!

I hope this can help
ciao ciao

Hello @jamesosborne

I have done as you suggested, but yes the error still there even with only Site Kit activated.

Here the screenshot

Thanks

Hello @jamesosborne
I am in the same situation as @salik21 and (I did the same procedure)
only Site Kit have this error

In admin, in console:

Failed to load resource: the server responded with a status of 500:
https://MYDOMAIN.com/wp-json/google-site-kit/v1/modules/search-console/data/searchanalytics?dimensions=date&startDate=2021-05-03&endDate=2021-06-27&_locale=user

which have this content:
{“code”:”rest_forbidden”,”message”:”Non hai i permessi per farlo.”,”data”:{“status”:401}}

Hello James,

Here the error:
Data error in Analytics
<p>Si è verificato un errore critico sul tuo sito web.</p><p>Scopri di più riguardo la risoluzione dei problemi in WordPress.</p>

This error appears in every sitekit widget

I have no issues in Site Health, and php is 7.4

Hello, same problem here!
from today (no plugin updates) we have this php errors in dashboard widgets and frontend site kit’s menu

Many tanks

Please don’t do that again, really!
Thanks

What about this request?
How can be the default messages be filled in the right language in wpml translation manager?
It is really necessary to have a way to have pre-filled those fields!
otherwise this plugin cannot be used easily for multilanguage sites…
thank you very much

Come tradure il banner con wpml?
è possibile fare in modo che testo e testo pulsante siano registrati da wpml?
https://codex.www.ads-software.com/Function_Reference/wp_localize_script

grazie per l’ottimo plugin

ironically you have to set a cookie to the user that DO NOT accept… but can be an “allowed” cookie!

—
I think the browser should manage this stupid law, not the sites or developers, it would be more logic and consistent…