puregraphx

Indeed, like I said, it’s possible the IP has not yet propagated all around. That is indeed the old website.
But as the issue is visible now on the live site, I’ll have to revert the changes. I’ve made another screenshot that might help
https://prnt.sc/qbmkHVEU8qas

The site has not yet resolved on the new IP yet, so you’ll have to edit your hosts file are we’ll have to wait until the new site is IP fully propagated..

Hi, 4 months later this issue still isn’t fixed. We still get

Uncaught TypeError: e.indexOf is not a function
    at S.fn.init.S.fn.load (jquery.min.js?ver=3.6.0:2:84932)
    at (index):299:16
S.fn.load @ jquery.min.js?ver=3.6.0:2
(anonymous) @ (index):299

The only way to currently load the players is to enable jQuery Migrate script.

<script type='text/javascript' id='audioalbum-js-after'>
jQuery(window).load(function() { jQuery(".albumtrack").css("visibility", "visible"); jQuery(".track").css("background-image", "none"); });
</script>

Oh, posted too soon.
I can’t set anything else than the default width of the cookie banner. Whatever I set, after the save it’s back to 564px.
In addition to that, even if 400px would be saved properly, the layout of the banner is not 400px, only the Categories block is, title and buttons are still 564px.

https://prnt.sc/26w42kx

The width of the banner also automatically changes when editing the title size
.cmplz-cookiebanner .cmplz-title {font-family:"Montserrat", Sans-serif;font-weight:700;font-size:20px}
After this css, the width jumps to +/- 700px

• This reply was modified 4 years, 2 months ago by puregraphx.

I restored a backup to the pre 6.x version, these are the columns I currently have in the DB. I will update to a 6.x later this evening and check columns again and the debug log.

ID	int(11) Auto Increment	
banner_version	int(11)	
default	int(11)	
archived	int(11)	
title	text	
position	text	
theme	text	
checkbox_style	text	
revoke	text	
header	text	
dismiss	text	
save_preferences	text	
view_preferences	text	
accept_all	text	
category_functional	text	
category_all	text	
category_stats	text	
category_prefs	text	
accept	text	
message_optin	text	
readmore_optin	text	
use_categories	text	
tagmanager_categories	text	
use_categories_optinstats	varchar(255)	
hide_revoke	int(11)	
disable_cookiebanner	int(11)	
banner_width	int(11)	
soft_cookiewall	int(11)	
dismiss_on_scroll	int(11)	
dismiss_on_timeout	int(11)	
dismiss_timeout	text	
accept_informational	text	
message_optout	text	
readmore_optout	text	
readmore_optout_dnsmpi	text	
readmore_privacy	text	
readmore_impressum	text	
use_custom_cookie_css	text	
custom_css	text	
statistics	text	
colorpalette_background	text	
colorpalette_text	text	
colorpalette_toggles	text	
colorpalette_border_radius	text	
border_width	text	
colorpalette_button_accept	text	
colorpalette_button_deny	text	
colorpalette_button_settings	text	
buttons_border_radius	text	
animation	text	
use_box_shadow	int(11)	
hide_preview	int(11)

@rogierlankhorst
I just downloaded the branch you linked above and it seems the issue is PARTLY fixed in that way that any settings I change in the admin are still reverted after saving. So no matter which toggle I switch or width I enter, after Save, it’s back to defaults.
However, those changes ARE visible in the frontend. BUT, and now it gets even more confusing… as each block of settings has its own Save button, the reverted changes in another block are also saved.
TIP: have 1 SAVE button for the whole settings page.

Example: in Categories block, I disable all 3 descriptions, hit Save, page reloads, descriptions are enabled again in admin but invisible in frontend. If I now toggle the Deny button in the Banner Settings and hit Save. The Deny button will indeed be invisible in the frontend BUT the 3 descriptions will be visible again.

This is now the 4th or 5th site I updated to the 6.x version and ALL have issues. If this were the paying version of the plugin, I’d be VERY annoyed.

So how does the database upgrade work? I downloaded the zip, uploaded into WP, it shows Complianz 6.1.0. I deactivated 6.0.6. The issue is not fixed with 6.1
How do I trigger the DB upgrade if it’s not automatically triggered?

+ in 6.1. the Anonymous statistics description toggle is broken (again), the toggle remains visible even with the setting disabled. >> this seems due to the fact that no matter what I change, after Saving, the setting remains like default. The thing that ought to be fixed with 6.1.0

• This reply was modified 4 years, 3 months ago by puregraphx.
• This reply was modified 4 years, 3 months ago by puregraphx.