Customizer not working

Hi @llynya1977,

I’m unable to reproduce this issue with the latest version of Complianz. Can you open the customizer when the browsers developers console is open and check if any errors appear? If so, can you post them here?

It’s in German, sorry:

Konsole:

Einige Cookies verwenden das empfohlene “SameSite”-Attribut inkorrekt. 3

MouseEvent.mozPressure sollte nicht mehr verwendet werden. Verwenden Sie PointerEvent.pressure stattdessen. tinymce.min.js:2:8856

MouseEvent.mozInputSource sollte nicht mehr verwendet werden. Verwenden Sie PointerEvent.pointerType stattdessen. tinymce.min.js:2:8856

Fehler:

GEThttps://kosmetik-killertal.de/wp-admin/customize.php?url=https://kosmetik-killertal.de/[HTTP/2 500 1158ms]

GET

https://kosmetik-killertal.de/wp-admin/customize.php?url=https://kosmetik-killertal.de/

Status

500

VersionHTTP/2

übertragen264,95 kB (1,48 MB Gr??e)

Referrer Policystrict-origin-when-cross-origin

Anfrage-Priorit?tHighest

DNS-Aufl?sungSystem

cache-control

no-cache, must-revalidate, max-age=0, no-store, privatecontent-encoding

gzipcontent-type

text/html; charset=UTF-8date

Sun, 31 Dec 2023 16:03:08 GMTexpires

Wed, 11 Jan 1984 05:00:00 GMTreferrer-policy

strict-origin-when-cross-originserver

Apachevary

Accept-Encoding,User-AgentX-Firefox-Spdy

h2x-frame-options

SAMEORIGINAccept

text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8Accept-Encoding

gzip, deflate, brAccept-Language

de,en-US;q=0.7,en;q=0.3Connection

keep-aliveCookie

wordpress_sec_1a675ccdf8f429cc7403eff5bab0b1db=Melanie%7C1704901671%7CxDM63y230xtI0scq9sv9VveVv0BBQXjJJG6LAR60oGq%7C72b0867247637c2fda52733ae9d9d664de784b0bfa0ce76a25b0b7c95325eed2; cmplz_banner-status=dismissed; cmplz_policy_id=17; cmplz_marketing=deny; cmplz_statistics=deny; cmplz_preferences=deny; cmplz_functional=allow; cmplz_consented_services=; wordpress_logged_in_1a675ccdf8f429cc7403eff5bab0b1db=Melanie%7C1704901671%7CxDM63y230xtI0scq9sv9VveVv0BBQXjJJG6LAR60oGq%7Ce8e7507bcd16cdb72c6ac0e0497a8c00dc9b4…ets_access%3Doff%26post_dfw%3Don%26posts_list_mode%3Dlist%26align%3Dcenter; wp-settings-time-1=1703692072; wfwaf-authcookie-3be1cdce302a6eb0303e52b510b62f6a=1%7Cadministrator%7Cmanage_options%2Cunfiltered_html%2Cedit_others_posts%2Cupload_files%2Cpublish_posts%2Cedit_posts%2Cread%7C388badaa445e2232a1a4998a88a6e6441f904b483a69cb8f487fd50b55a89144; tk_ai=woo%3Als6C0tu0aAGfoU0a7k%2FYB%2BD4; wp_llms_session_1a675ccdf8f429cc7403eff5bab0b1db=1%7C%7C1704059828%7C%7C1704056228%7C%7C7d2621ba9337d0782bb2702f1bf6f2bbHost

kosmetik-killertal.deReferer

https://kosmetik-killertal.de/Sec-Fetch-Dest

documentSec-Fetch-Mode

navigateSec-Fetch-Site

same-originSec-Fetch-User

?1TE

trailersUpgrade-Insecure-Requests

1User-Agent

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:121.0) Gecko/20100101 Firefox/121.0

Hi @llynya1977,

It looks like the console reports a “500 Internal Server Error”, which by itself is unfortunately not very descriptive.

I would recommend to enable Debugging on WordPress (you can do this by using the WP Debugging plugin, and then triggering the issue once more with this plugin enbaled). A debug log file should then be generated, containing more information about the issue that you are experiencing.

Kind regards, Jarno

Hi Jarno,

Debug.log sais:

[04-Jan-2024 15:23:26 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 716800 bytes) in /www/htdocs/w01dd77f/kosmetik-killertal.de/wp-includes/class-wp-scripts.php on line 446
[04-Jan-2024 15:31:54 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 733184 bytes) in /www/htdocs/w01dd77f/kosmetik-killertal.de/wp-includes/class-wp-scripts.php on line 446
[04-Jan-2024 15:31:54 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 733184 bytes) in /www/htdocs/w01dd77f/kosmetik-killertal.de/wp-includes/functions.php on line 3844

Kind regards,

Melanie

Hi @llynya1977,

Your WordPress site is exceeding the memory limit of 256MB, and these errors appear as a result of that. That does explain why things like the Customizer stop working on your site.

If the combination of plugins on your site require more memory than the current limit on your environment allows, you might need to increase the memory limit to solve the issue.

Kind regards, Jarno

Thanks, that’s what I thought when I saw the log file. But why does this problem only occur when the compliance plugin is activated and disappears when I deactivate it? If I deactivate another, larger plugin while Complianz is active, the problem persists.

Hi @llynya1977,

Fair question, the combination of activated plugins on the site could cause the memory limit to be reached. For example, if you have a combination of a few relatively ‘heavy’ plugins/theme activated.

Perhaps you could verify if it still occurs with Complianz as the sole activated plugin on the site?

But I would also check if it can be resolved by increasing the memory limit (512MB, for example). If not, consider using a plugin such as Query Monitor to identify which plugins contribute to the memory limit being exceeded.

Kind regards, Jarno

Hello,

“Perhaps you could verify if it still occurs with Complianz as the sole activated plugin on the site?” Yes it does.

“But I would also check if it can be resolved by increasing the memory limit (512MB, for example)” It works. Thank you very much!