latti
Forum Replies Created
-
Thank you very much, I’ve made all the changes you requested and released the new version 3.2.60 . If you notice anything missing, please let me know here. In the meantime, you need to download and install the new version from the plugin’s wp.org page because the update notification will appear after 6 hours.
Hi,
Thank you very much, this is now released in 3.2.60.
The filter is exactly as you proposed:
$meta_keys = apply_filters( 'brikpanel_product_search_meta_keys', array( '_sku' ), $search_term );It is applied inside
Brikpanel_Products_List::filter_search_include_sku(), and both subqueries, the product’s own meta and the variation-to-parent one, are now built from the returned list instead of the hardcoded_sku. So a supplier code stored on a variation returns the parent product, the same way a variation SKU already did.The default is still exactly
array( '_sku' ), so nothing changes for anyone who does not use the filter.You can drop your priority 20
posts_searchclause now.Two notes on the list itself. Keys that are not plain meta key names are discarded rather than escaped, and at most 10 keys are scanned, since each extra key widens an unindexable
LIKEscan on every keystroke. If you ever need more than that, the second argument is the search term, so you can return the wider list only for terms that look like your own identifiers and keep the scan narrow for everything else.While I was in that code I also fixed two related things: a SKU containing an apostrophe could never be matched, and the extra search rule could stay attached for the rest of the request if another plugin threw an error mid-query, which quietly widened unrelated searches.
The filter is documented with a copyable example under WooCommerce, Settings, BrikPanel, Developers.
Please download and install the new version from the plugin’s wp.org page, as the update notification takes about 6 hours to appear. If anything is missing, let me know here.
Thank you very much for such a clear report, it was genuinely useful. I’ve made all the changes you requested and released them in version 3.2.60.
What’s new: a Wait for cookie consent switch under WooCommerce → Settings → BrikPanel → Analytics (off by default). With it on, BrikPanel creates no cookie, no local storage entry and no request until the visitor allows analytics. Consent takes effect without a page reload, and withdrawing it stops tracking and deletes BrikPanel’s own cookies and local storage for that visitor.
All four integration paths you asked for are there: native WordPress Consent API support (the
statisticscategory, including live changes), thebrikpanel_frontend_tracking_allowedPHP filter, andbrikpanel_start_tracking()/brikpanel_stop_tracking()in JavaScript. Both are documented under Settings → BrikPanel → Developers.I tested it against the most used banners. Working with no setup: Complianz, CookieYes, GDPR Cookie Compliance (Moove), WPConsent, Cookiebot, iubenda, Beautiful Cookie Consent. CookieAdmin, Real Cookie Banner and Termly don’t use the Consent API, so there’s a short tested bridge snippet in the FAQ for those.
Your questions:
brikpanel_vidlasts one year, first party and HttpOnly, and with the setting on it’s only created after consent.- Only live session state is tied to it: current page, whether there are cart items, device type, and a salted one way hash of the IP (the raw IP is never stored). It lives in a cache that expires after two minutes, never in the database.
- Yes, it stays entirely on your own site. Nothing is sent anywhere.
wp_brikpanel_visitors,wp_brikpanel_visited_pages,wp_brikpanel_referrersandwp_brikpanel_cart_tracking. All of them hold anonymous daily counters with no visitor identifier column, which is why withdrawing consent doesn’t need to touch them.
You’re right that a persistent analytics identifier needs consent even when the data never leaves the site, and that’s exactly what this closes.
In the meantime, you need to download and install the new version from the plugin’s wp.org page because the update notification will appear after 6 hours.
By the way, if you like the plugin, leaving a review would also be a huge help to me 🙏
- This reply was modified 3 hours, 51 minutes ago by latti.
Merhaba, güzel sözleriniz için çok teşekkür ederim.
Bildirdiğiniz konuyu baştan sona inceledim, istediğiniz tüm değişiklikleri yapıp yeni sürüm 3.2.60‘ı yayınladım. Durum şöyle:
Mevcut çevirilerin kayması veya bozulması BrikPanel’den kaynaklanmıyor. BrikPanel WordPress’in çeviri sistemine hiç müdahale etmiyor ve mağaza tarafında kendi başına metin basmıyor. Test ettim: eklenti açıkken ve kapalıyken sitenin ön yüzü tıpatıp aynı çıkıyor. Yani mevcut bir çeviriyi değiştirmesi mümkün değil, o kısım büyük ihtimalle başka bir eklentiden geliyor.
Ama “birkaç çeviri ekledi” dediğiniz kısımda haklıydınız, o gerçekti. BrikPanel, yalnızca yönetici panelinde görünen bazı metinleri her ziyaretçi sayfası açıldığında da gereksiz yere işliyordu. TranslatePress de bunları site metni sanıp kendi listesine ekliyordu. Düzelttim.
3.2.60’a geçtikten sonra şöyle kontrol edebilirsiniz: TranslatePress’in çeviri listesinde, sitede hiçbir yerde görünmeyen “Cost of goods (COGS)”, “Permalink (URL slug)”, “Featured product star” gibi kayıtlar varsa silin. Siteyi normal gezdiğinizde bir daha eklenmemeleri gerekiyor.
Önerileriniz için ayrıca teşekkürler:
- Live Visitors’ta mobil/masaüstü ikonu: yapıldı, 3.2.60’ta yayında.
- Recent Orders yenileme butonu ve sipariş tarihleri: şu an için biraz kapsamlı kalıyor, yol haritamıza ekledik.
Bu arada aynı sürümde, varyasyonlu ürünlerde başka bir eklentiyle çakışmadan doğan bir kayıt hatasını da düzelttim.
Küçük bir not: güncelleme bildirimi size yaklaşık 6 saat sonra düşecek, o yüzden hemen denemek isterseniz yeni sürümü eklentinin wp.org sayfasından indirip yükleyebilirsiniz.
Eksik veya ters giden bir şey fark ederseniz lütfen buradan bana yazın, hemen bakarım. Eklentiyi beğendiyseniz bir yorum bırakmanız da bana çok büyük katkı sağlar 🙏
Tekrar teşekkürler, iyi çalışmalar.
Thank you very much, I’ve made all the changes you requested and released the new version 3.2.60 . If you notice anything missing, please let me know here. In the meantime, you need to download and install the new version from the plugin’s wp.org page because the update notification will appear after 6 hours.
By the way, if you like the plugin, leaving a review would also be a huge help to me 🙏
Thank you very much, I’ve made all the changes you requested and released the new version 3.2.60 . If you notice anything missing, please let me know here. In the meantime, you need to download and install the new version from the plugin’s wp.org page because the update notification will appear after 6 hours.
Hi, and thanks for testing so quickly.
I’ve released 3.2.60 with fixes and one thing I need your help on.
Copy and paste with a separator – my fault. It was only splitting on the
|symbol, not on commas. It now accepts both. If your text contains a|it splits on that, otherwise it splits on commas, so a value that has a comma in it (like “Lime, Basil and Mandarin”) still stays in one piece.The manual variation, the COGS, and Select all – these three are actually the same problem. The “An error occurred” message means the save never completed at all, so nothing you changed was stored, whichever feature you used. That’s also why the variation disappeared on refresh.
I’ve tested these on my side many times and they save correctly, so the cause is something specific to your site, most likely another plugin interrupting the save. Rather than guess, I’ve made the error message tell you what actually happened. Instead of “An error occurred” it now names the server’s reply and, when another plugin’s error caused it, the error and the file it came from.
Could you do this after updating: try the save again and send me the exact wording of the red message. If you can, also press F12, open the Console tab, and send a screenshot of the red line there. That will tell us exactly what’s killing the save, and I’ll fix it straight away.
Sorry for the extra round trip, and thanks for the detailed reports. They’re genuinely useful.
Thank you very much, I’ve made all the changes you requested and released the new version 3.2.44 . If you notice anything missing, please let me know here. In the meantime, you need to download and install the new version from the plugin’s wp.org page because the update notification will appear after 6 hours.
Under BrikPanel Settings → Products, there’s a new checkbox: “Use the full screen width” – it’s off by default.
Thank you very much, these comments are truly very valuable to me, I had been developing websites with WooCommerce for 6 years and I was hurting so much while developing them, and even though I knew it would be difficult, I genuinely wanted this problem to be solved at its root, thank you once again for your valuable feedback 🙏
Thank you very much, I’ve made all the changes you requested and released the new version 3.2.42 . If you notice anything missing, please let me know here. In the meantime, you need to download and install the new version from the plugin’s wp.org page because the update notification will appear after 6 hours.
By the way, if you like the plugin, leaving a review would also be a huge help to me 🙏
Thank you very much, I’ve made all the changes you requested and released the new version 3.2.42 . If you notice anything missing, please let me know here. In the meantime, you need to download and install the new version from the plugin’s wp.org page because the update notification will appear after 6 hours.
By the way, if you like the plugin, leaving a review would also be a huge help to me 🙏
Settings → Products → “Visible editor sections” You can add it from that section.
By the way, if you like the plugin, leaving a review would also be a huge help to me 🙏
Thank you very much 🙏
Thank you very much 🙏
Thank you very much, I’ve made all the changes you requested and released the new version 3.2.36 . If you notice anything missing, please let me know here. In the meantime, you need to download and install the new version from the plugin’s wp.org page because the update notification will appear after 6 hours.