puregraphx
Forum Replies Created
-
Forum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] v6 should go back to the drawing boardI think these errors don’t have such a large impact
WordPress database error: [Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs] ALTER TABLE wp_cmplz_cookiebanners ADD COLUMN <code>use_logo</code> text NOT NULL WordPress database error: [Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs] ALTER TABLE wp_cmplz_cookiebanners ADD COLUMN <code>logo_attachment_id</code> text NOT NULL WordPress database error: [Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs] ALTER TABLE wp_cmplz_cookiebanners ADD COLUMN <code>close_button</code> text NOT NULL WordPress database error: [Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs] ALTER TABLE wp_cmplz_cookiebanners ADD COLUMN <code>functional_text</code> text NOT NULL WordPress database error: [Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs] ALTER TABLE wp_cmplz_cookiebanners ADD COLUMN <code>statistics_text</code> text NOT NULL WordPress database error: [Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs] ALTER TABLE wp_cmplz_cookiebanners ADD COLUMN <code>statistics_text_anonymous</code> text NOT NULL WordPress database error: [Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs] ALTER TABLE wp_cmplz_cookiebanners ADD COLUMN <code>preferences_text</code> text NOT NULL WordPress database error: [Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs] ALTER TABLE wp_cmplz_cookiebanners ADD COLUMN <code>marketing_text</code> text NOT NULL WordPress database error: [Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs] ALTER TABLE wp_cmplz_cookiebanners ADD COLUMN <code>header_footer_shadow</code> int(11) NOT NULLBut this one most probably causes the settings to not be saved
WordPress database error: [Unknown column 'use_logo' in 'field list'] UPDATE <code>wp_cmplz_cookiebanners</code> SET <code>position</code> = 'bottom-right', <code>banner_version</code> = '17', <code>archived</code> = '0', <code>title</code> = 'bottom-right minimal', <code>theme</code> = 'minimal', <code>checkbox_style</code> = 'slider', <code>use_logo</code> = 'hide', <code>logo_attachment_id</code> = '0', <code>close_button</code> = '1', <code>category_functional</code> = 'Functioneel', <code>category_prefs</code> = 'a:2:{s:4:\"text\";s:0:\"\";s:4:\"show\";b:1;}', <code>category_stats</code> = 'a:2:{s:4:\"text\";s:10:\"Statistics\";s:4:\"show\";i:1;}', <code>category_all</code> = 'a:2:{s:4:\"text\";s:9:\"Marketing\";s:4:\"show\";i:1;}', <code>header</code> = 'a:2:{s:4:\"text\";s:21:\"Manage Cookie Consent\";s:4:\"show\";i:1;}', <code>dismiss</code> = 'a:2:{s:4:\"text\";s:4:\"Deny\";s:4:\"show\";i:1;}', <code>revoke</code> = 'a:2:{s:4:\"text\";s:14:\"Manage consent\";s:4:\"show\";i:1;}', <code>save_preferences</code> = 'Voorkeuren opslaan', <code>view_preferences</code> = 'Voorkeuren bekijken', <code>accept</code> = 'Accept', <code>message_optin</code> = 'We maken gebruik van cookies om jou optimaal gebruik te laten maken van onze website en diensten.', <code>use_categories</code> = 'view-preferences', <code>disable_cookiebanner</code> = '0', <code>banner_width</code> = '0', <code>soft_cookiewall</code> = '0', <code>dismiss_on_scroll</code> = '0', <code>dismiss_on_timeout</code> = '0', <code>dismiss_timeout</code> = '10', <code>accept_informational</code> = 'a:2:{s:4:\"text\";s:6:\"Accept\";s:4:\"show\";i:1;}', <code>message_optout</code> = 'We use cookies to optimize our website and our service.', <code>use_custom_cookie_css</code> = '1', <code>custom_css</code> = '.cc-message{}\r\n /* styles for the message box */\r\n.cc-dismiss{}\r\n /* styles for the dismiss button */\r\n.cc-btn{}\r\n /* styles for buttons */\r\n.cc-allow{} \r\n/* styles for the accept button */\r\n.cc-accept-all{} \r\n/* styles for the accept all button */\r\n.cc-window{} \r\n/* styles for the popup banner */\r\n.cc-window .cc-category{} \r\n/* styles for categories*/\r\n.cc-window .cc-check{} \r\n/* styles for the checkboxes with categories */\r\n.cc-revoke{} \r\n/* styles for the revoke / settings popup */\r\n.cmplz-slider-checkbox{} \r\n/* styles for the checkboxes */\r\n.cmplz-soft-cookiewall{} \r\n/* styles for the soft cookie wall */\r\n\r\n/* styles for the AMP notice */\r\n#cmplz-consent-ui, #cmplz-post-consent-ui {} \r\n/* styles for entire banner */\r\n#cmplz-consent-ui .cmplz-consent-message {} \r\n/* styles for the message area */\r\n#cmplz-consent-ui button, #cmplz-post-consent-ui button {} \r\n/* styles for the buttons */', <code>statistics</code> = 'a:0:{}', <code>functional_text</code> = 'a:2:{s:4:\"text\";s:289:\"The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.\";s:4:\"show\";i:1;}', <code>preferences_text</code> = 'a:2:{s:4:\"text\";s:144:\"The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.\";s:4:\"show\";i:1;}', <code>statistics_text</code> = 'a:2:{s:4:\"text\";s:82:\"The technical storage or access that is used exclusively for statistical purposes.\";s:4:\"show\";i:1;}', <code>statistics_text_anonymous</code> = 'a:2:{s:4:\"text\";s:317:\"The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.\";s:4:\"show\";i:1;}', <code>marketing_text</code> = 'a:2:{s:4:\"text\";s:181:\"The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.\";s:4:\"show\";i:1;}', <code>colorpalette_background</code> = 'a:2:{s:5:\"color\";s:7:\"#ffffff\";s:6:\"border\";s:7:\"#f9f9f9\";}', <code>colorpalette_text</code> = 'a:2:{s:5:\"color\";s:7:\"#0a0707\";s:9:\"hyperlink\";s:7:\"#191e23\";}', <code>colorpalette_toggles</code> = 'a:3:{s:10:\"background\";s:7:\"#21759b\";s:6:\"bullet\";s:7:\"#ffffff\";s:8:\"inactive\";s:7:\"#F56E28\";}', <code>colorpalette_border_radius</code> = 'a:5:{s:3:\"top\";i:10;s:5:\"right\";i:10;s:6:\"bottom\";i:10;s:4:\"left\";i:10;s:4:\"type\";s:2:\"px\";}', <code>border_width</code> = 'a:4:{s:3:\"top\";i:0;s:5:\"right\";i:0;s:6:\"bottom\";i:0;s:4:\"left\";i:0;}', <code>colorpalette_button_accept</code> = 'a:3:{s:10:\"background\";s:7:\"#5c73b8\";s:6:\"border\";s:7:\"#5c73b8\";s:4:\"text\";s:7:\"#ffffff\";}', <code>colorpalette_button_deny</code> = 'a:3:{s:10:\"background\";s:7:\"#f1f1f1\";s:6:\"border\";s:7:\"#f1f1f1\";s:4:\"text\";s:7:\"#000000\";}', <code>colorpalette_button_settings</code> = 'a:3:{s:10:\"background\";s:7:\"#f1f1f1\";s:6:\"border\";s:7:\"#f1f1f1\";s:4:\"text\";s:7:\"#000000\";}', <code>buttons_border_radius</code> = 'a:5:{s:3:\"top\";i:5;s:5:\"right\";i:5;s:6:\"bottom\";i:5;s:4:\"left\";i:5;s:4:\"type\";s:2:\"px\";}', <code>animation</code> = 'none', <code>use_box_shadow</code> = '0', <code>header_footer_shadow</code> = '0', <code>hide_preview</code> = '0' WHERE <code>ID</code> = 1Forum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] v6 should go back to the drawing board@rogierlankhorst I’ve made a screencast to show you what’s wrong with the settings.
This is on another site than the issue I mentioned above, so this means I can reproduce the error on 2 different sites.
https://screencast-o-matic.com/watch/c3VOXDVDl7CThe JS error is in your Theme file https://dev3.homepage-balingen.de/wp-content/themes/Total/assets/js/total.min.js
Try switching to the default WP Theme and try again. You can use the Troubleshooting plugin if it’s a live site and you can’t switch themes. This way, only the logged in users will see the changes.Forum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] v6 should go back to the drawing boardI hope this still gets answered even if the ticket is marked as solved, as it’s not, unfortunately.
In 6.0.5 I can’t delete custom css. When I clear the editor, click save. The alert says Saved, it scrolls to the bottom, all css is still there.
I disable the Close button, click Save. Page reloads, scrolls down to that setting. Close button is still enabled.
Same issue with every setting. Change setting, Click Save, Page reloads, settings still the same.You have absolutely no idea how many hours I have already wasted on +/- 80 client websites.
My best advice. Fix the security issue in 5.5.3. and launch that as 5.5.4. and give people the chance to use the 5.x version until the 6.x version has been properly reviewed. Based on the amount of tickets that have been created in the last 2 weeks, you must begin to realize this version was really not suited for release, it’s beta at best.
Forum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] Can we roll back to pre 6.05https://nl.wordpress.org/plugins/complianz-gdpr/advanced/
Scroll to the bottom, select 5.5.3. and download.I ditched the RC/OLS server, so this problem fixed itself for me 🙂
100% sure I’m on 3.1.
I was on an earlier version which indeed did not display an update was available. It was only after I downloaded 3.0.2 from the repo that the WP Admin alert me of version 3.1.
Will create a ticket on your website and link to this thread.Forum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] v6 should go back to the drawing boardAs I’ve spent 3 hours now fiddling with the new plugin, I decided to rollback to 5.5.3. I have several deadlines, can’t keep clients waiting any longer.
However, I am now stuck with “Array” here and “Array” there https://prnt.sc/26enhclForum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] v6 should go back to the drawing boardHere is the next list of bugs:
– If I set width to 400, click Save, the page refreshes and the width is 684.
– Even if I manage to get the banner to shrink in size via custom css, the CSS Grid makes it nearly impossible to create smaller banners (cmplz header is 3 columns so you have massive whitespace left/right; the categories are also grid, so the toggles are cut off on smaller banners, …). Once again, it’s Flexbox that you need, not Grid, trust me!
– If I disable the Anonymous statistics description, the Open/Close toggle is still visible.
– There is no option to edit the “Cookies” link at the bottom. In the old version we could at least say “click here to view our [cookies policy]”.
– no more mo files provided?
– @media (max-width: 425px) {.cmplz-cookiebanner .cmplz-header .cmplz-title {display: none;}} : why? why would you decide to hide the title? If you must, make it a toggle “Hide title on mobile”.- This reply was modified 4 years, 3 months ago by puregraphx.
- This reply was modified 4 years, 3 months ago by puregraphx.
- This reply was modified 4 years, 3 months ago by puregraphx.
@rogierlankhorst that catch 8.1. issues fixed the error.
Out of curiosity, what caused the fatal error?[11-Jan-2022 14:41:56 UTC] PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /home/519488.cloudwaysapps.com/cpsetxssmu/public_html/wp-content/plugins/*complianz-gdpr/upgrade.php:279 Stack trace: #0 /home/519488.cloudwaysapps.com/cpsetxssmu/public_html/wp-includes/class-wp-hook.php(303): cmplz_check_upgrade() #1 /home/519488.cloudwaysapps.com/cpsetxssmu/public_html/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters() #2 /home/519488.cloudwaysapps.com/cpsetxssmu/public_html/wp-includes/plugin.php(470): WP_Hook->do_action() #3 /home/519488.cloudwaysapps.com/cpsetxssmu/public_html/wp-settings.php(578): do_action() #4 /home/519488.cloudwaysapps.com/cpsetxssmu/public_html/wp-config.php(76): require_once('/home/519488.cl...') #5 /home/519488.cloudwaysapps.com/cpsetxssmu/public_html/wp-load.php(50): require_once('/home/519488.cl...') #6 /home/519488.cloudwaysapps.com/cpsetxssmu/public_html/wp-admin/admin-ajax.php(22): require_once('/home/519488.cl...') #7 {main} thrown in /home/519488.cloudwaysapps.com/cpsetxssmu/public_html/wp-content/plugins/*complianz-gdpr/upgrade.php on line 279- This reply was modified 4 years, 4 months ago by puregraphx.
- This reply was modified 4 years, 4 months ago by puregraphx.
Sorry for the late reply, didn’t get an update email from this ticket.
I get this error upon clicking Save & Optimize.
Have not yet encountered this error on other WP sites though.Forum: Plugins
In reply to: [Image Photo Gallery Final Tiles Grid] Gallery height set to “1e+08px”It seems I can’t currently reproduce the height issue, but the plugin is definitely incompatible with Shortpixel.
https://wordpress-606845-2171569.cloudwaysapps.com/test/Sorry, code above belongs to Audio Album plugin, not MP3 Audio Player plugin.
I have invited a WPML support member to continue the discussion here, but they are not inclined to, they stick to their Go Global Program “Yes, what the developer mentioned is correct. But the go global program also gives access to pass the info to our compatibility developers directly.”
I can only kindly ask you once again to consider posting your feedback via that channel. If not, we will continue to use their workaround. I understand your time is precious, so no hard feelings.
Have a nice day.