Cyrille37

Yaeh! Thanks @viablethought ! It does the job ??

Here is a thread with more users : https://www.ads-software.com/support/topic/unknown-file-false-positives-after-upgrade-to-wp-6-7/

Hi.
It’s the same on my websites. I haven’t found the reason yet.
Cheers.

Hi

It’s the same on my websites. I haven’t found the reason yet.

Cheers.

Hello

I have this error too on “/wp-admin/options-general.php”

Uncaught TypeError: document.getElementById(...) is null

setTimeout(()=>{
document.getElementById("discard_content").classList.add("discard_button_outside_settings")
document.getElementById("discard_content").classList.remove("discard_button")
if( document.getElementById("user-consent-form") ){

This code comes from plugin google-sitemap-generator.

• This reply was modified 1 year, 10 months ago by Cyrille37. Reason: did no see that I was in google-sitemap-generator support forum :-)

I forgot to tell it’ll permit to use the “custom oauth” with Nextcloud like the email is stored at “ocs.data.email”.

Regards & Cheers.

Yeah! It works ??
Thanks.

I was about to delete my message because I was not sure of myself anymore
??

Hi Stefano,

Thanks a lot for your work.

Since I’ve updated from 7.2.2 to 7.2.6 my newsletter templates does not work anymore.

When creating a new NL I choose a pre-recorded template, but the NL body is empty. There is a Javascript error is the console (see bellow).

By the way, editing a existed NL draft is working fine, with the same error in javascript console.

Uncaught TypeError: document.getElementById("tnpc-mobile-preview") is null in newsletter-builder-v2.js line 363

document.getElementById(...) is null
    tnpc_mobile_preview https://xyz.devhost/wp-content/plugins/newsletter/emails/tnp-composer/_scripts/newsletter-builder-v2.js?ver=7.2.6:363
    start_composer https://xyz.devhost/wp-content/plugins/newsletter/emails/tnp-composer/_scripts/newsletter-builder-v2.js?ver=7.2.6:330
    onClose https://xyz.devhost/wp-content/plugins/newsletter/emails/tnp-composer/_scripts/newsletter-builder-v2.js?ver=7.2.6:506
    close https://xyz.devhost/wp-content/plugins/newsletter/admin/modal.js?ver=7.2.6:47
    tnpc_load_preset https://xyz.devhost/wp-content/plugins/newsletter/emails/tnp-composer/_scripts/newsletter-builder-v2.js?ver=7.2.6:534
    onclick https://xyz.devhost/wp-admin/admin.php?page=newsletter_emails_composer:1
newsletter-builder-v2.js:363:22

Regards & cheers, Cyrille.

Hi,
Thanks, it is resolved.
Cheers.

Hello Peter.

Thanks a lot for you answer.

I think it’s enough for the development team, they just have to make sure that the function wfAdminNoticeQueue::::_notices() returns the expected value type. Checks are to be done inside has needed.

Regards & Cheers

Hello,

the error is Error Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8mb4_unicode_520_ci,COERCIBLE). It seems that data and tables have differents encoding. Perhaps changing your tables collation to “utf8mb”. Also look at the wp-config.php at define( 'DB_CHARSET', 'utf8mb4' ) and define('DB_COLLATE', '');.

The error is because some config does not match the same collation settings.

Hello,

Have a look at Wordfence admin panels where you can which users and/or are blocked.

The var_dump($notices); give bool(false)

$notices = self::_notices();
var_dump($notices);
foreach ($notices as $nid => $n) {

A simple solution could be add some tests in osm-config.php like :

if( ! defined("OSM_default_lat"))
 define ("OSM_default_lat", 51.251);
if( ! defined("OSM_default_lon"))
 define ("OSM_default_lon", 7.096);
if( ! defined("OSM_default_zoom"))
 define ("OSM_default_zoom", 15);

Like we can override those constants in other WP files like functions.php.

Cheers,
Cyrille