Brian_Milnes

Thank you Janis
I’ll use the workaround and report to wpDataTables

Thanks!

Hi, I’m also seeing errors generated in the log file – is this the same issue?

/wp-content/plugins/advanced-access-manager/application/Service/AdminMenu.php on line 214
[06-Dec-2023 13:11:40 UTC] PHP Notice: Undefined offset: 2 in /wp-content/plugins/advanced-access-manager/application/Service/AdminMenu.php on line 328
[06-Dec-2023 13:11:40 UTC] PHP Notice: Undefined offset: 2 in /wp-content/plugins/advanced-access-manager/application/Service/AdminMenu.php on line 332
[06-Dec-2023 13:11:40 UTC] PHP Notice: Undefined offset: 2 in /wp-content/plugins/advanced-access-manager/application/Service/AdminMenu.php on line 332
[06-Dec-2023 13:11:40 UTC] PHP Notice: Undefined offset: 2 in /wp-content/plugins/advanced-access-manager/application/Service/AdminMenu.php on line 332
[06-Dec-2023 13:11:40 UTC] PHP Notice: Undefined offset: 2 in /wp-content/plugins/advanced-access-manager/application/Service/AdminMenu.php on line 332
[06-Dec-2023 13:11:40 UTC] PHP Notice: Undefined offset: 2 in /wp-content/plugins/advanced-access-manager/application/Service/AdminMenu.php on line 332
[06-Dec-2023 13:11:40 UTC] PHP Notice: Undefined offset: 2 in /wp-content/plugins/advanced-access-manager/application/Service/AdminMenu.php on line 332
[06-Dec-2023 13:11:40 UTC] PHP Notice: Undefined offset: 2 in /wp-content/plugins/advanced-access-manager/application/Service/AdminMenu.php on line 332
[06-Dec-2023 13:11:40 UTC] PHP Notice: Undefined offset: 2 in /wp-content/plugins/advanced-access-manager/application/Service/AdminMenu.php on line 332
[06-Dec-2023 13:11:40 UTC] PHP Notice: Undefined offset: 2 in /wp-content/plugins/advanced-access-manager/application/Service/AdminMenu.php on line 332
[06-Dec-2023 13:11:40 UTC] PHP Notice: Undefined offset: 2 in /wp-content/plugins/advanced-access-manager/application/Service/AdminMenu.php on line 241

Thanks

Yes – we have same sort of problem here:

Nov 24, 09:18:37

E_WARNING: DOMDocument::loadHTML(): Tag header invalid in Entity, line: 630 in /home/customer/www/asd-stan.org/public_html/wp-content/plugins/email-encoder-bundle/core/includes/classes/class-email-encoder-bundle-validate.php on line 381

E_WARNING: DOMDocument::loadHTML(): Tag svg invalid in Entity, line: 635 in /home/customer/www/asd-stan.org/public_html/wp-content/plugins/email-encoder-bundle/core/includes/classes/class-email-encoder-bundle-validate.php on line 381

E_WARNING: DOMDocument::loadHTML(): Tag path invalid in Entity, line: 636 in /home/customer/www/asd-stan.org/public_html/wp-content/plugins/email-encoder-bundle/core/includes/classes/class-email-encoder-bundle-validate.php on line 381

E_WARNING: DOMDocument::loadHTML(): Tag footer invalid in Entity, line: 653 in /home/customer/www/asd-stan.org/public_html/wp-content/plugins/email-encoder-bundle/core/includes/classes/class-email-encoder-bundle-validate.php on line 381`

I’m also having this problem.
I have created a new install on a new host, ready to deploy my Duplicator Pro package.
But like the others above, I am being warned that utf8 is not available.
Of course, what I have done is created a database on the new standard as recommended.
When I did this previously, the migration slowed down to a crawl, possibly due to charset alias converting?

This test checks to make sure this database can support the character set and collations found in the dup-installer/dup-database__[HASH].sql script.

Character set list
utf8mb4	
latin1	
utf8	
Collations list
latin1_swedish_ci	
utf8_bin	
utf8_general_ci	
utf8_unicode_ci	
utf8mb4_general_ci	
utf8mb4_unicode_520_ci	
utf8mb4_unicode_ci	
The database where the package was created has a character set that is not supported on this server. This issue happens when a site is moved from an newer version of MySQL to a older version of MySQL. The recommended fix is to update MySQL on this server to support the character set that is failing below. If this is not an option for your host, then you can continue the installation. Invalid values will be replaced with the default values. For more details about this issue and other details regarding this issue see the FAQ link below.

Default charset and setting in current installation
DB_CHARSET = utf8mb4
DB_COLLATE = utf8mb4_0900_ai_ci

I’d be really happy to hear what’s going on – really don’t want to screw up this migration
Thanks!

Really disappointing that you haven’t addressed this yet, or even acknowledged it here.
I accidentally re-applied the update to 1.4.4, and the problem returned.

We have had similar problems

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 81920 bytes) in site/public_html/wp-content/plugins/pods/classes/fields/pick.php on line 1480

Thanks for this suggestion @silsbyc

I’ll give this a go and report back

Thanks catacaustic

I disagree with your analysis – this is same file set, tested with no other users active. And they are generally small files.
They also trigger the same specific error on failure ““Sorry, this file extension is not permitted for security reasons.” That is created by the rule that allow_unfiltered_uploads successfully bypasses.

Thanks Corrina

The reason for bothering posting here was to highlight that it appears to sometimes work, and sometimes not.(With the same files)

The “host is restricting your file” uploads doesn’t explain the (frustrating) inconsistency.

This is day-in day-out requirement, but the wp-config edit does work (further convincing me that it’s not the host).

Many thanks for the quick response, Diego.

I’ll try that later and let you know.

Cheers

Brian

When I clicked on Gather Image Information (after setting up Quic Cloud) it returned the button in the same state, and no collection occurred.
When I clicked on one of the options (page speed, I think) on the Quic Dashboard (in Litespeed) it then returned the error at the top of the Dashboard.
I have now, disappointingly, had to remove the Plugin.

I’ve just installed and had this same problem

Failed to communicate with QUIC.cloud server: Unknown error: Array [server] https://node2.quic.cloud [service] health

Ah – I didn’t change it on the live server – just on the local one. (To no avail.)

I’ve changed it now on live, but to no effect – you’ll see perhaps that the YouTube videos are more displaced than the mp4 embedded videos.

But please don’t worry – we have more work to be done elsewhere and then this old site will be retired!

Thanks again!

Editing the header, as you suggested, didn’t help, and (with my limited web skills) I did get to improve to this, less than perfect:
(I copy this here, in case this is something that the Plugin is doing that it shouldn’t)

View post on imgur.com