Toevallig ook nog uit de nieuwe Mega Greninja ex Premium Collection. Heb nu zo’n 25 pakjes geopend (vorige maand begonnen) en al 2 Chaos Rising SIRs gepulled (deze en Cinccino ex #119). Misschien toch alweer stoppen op het hoogtepunt? :)
Ik ben onlangs begonnen met verzamelen en ben nu bezig met mijn eerste master set (Chaos Rising). Ik heb al een aantal IRs en zelfs 1 SIR gepulled, alleen ik twijfel heel erg of ik deze duurdere kaarten wel in mijn gewone / niet-toploader binder (van VaultX) moet doen. Momenteel zitten ze in een sleeve + toploader, en misschien wil ik ze op termijn ook wel laten graden (zodra PSA in de EU open gaat). Aan de andere kant is het natuurlijk wel heel zonde dat sommige kaarten in de binder ontbreken terwijl ik ze wel gewoon al in bezit heb.
Hoe pakken jullie dit normaal aan / wat zouden jullie aanraden?
Since a few days, all of my sites that are using Cloudflare's Google Tag Gateway are being incidentally hit with 1019 errors. I've addressed this with CF support, and they told me this is an ongoing issue with the Google Tag Gateway. So heads up: if you're using Google Tag Gateway, make sure to disable it temporarily until the issue has been resolved.
Official reply from Cloudflare:
>Because Google Tag Gateway is a managed Cloudflare integration rather than a user-deployed Worker, it does not show up under Workers & Pages and would not surface in any of the diagnostic angles you checked (Workers, Workers Routes, APO, Snippets, Security Events), which is why your earlier ruling-out was thorough but did not land on it.
> The cause is a bug on the Cloudflare side, in how Google Tag Gateway's HTML-rewriting step handles a character-encoding value during tag injection. The exception is firing on a significant fraction of HTML page views on your zone, across multiple Cloudflare regions.
> The fastest immediate mitigation is to disable Google Tag Gateway on your zone. To do that:
- Open the Cloudflare dashboard.
- Go to Tag Management, then Google Tag Gateway: https://dash.cloudflare.com/?to=/:account/tag-management/google-tag-gateway.
- Select your zone and toggle the feature off.
> Once disabled, requests will stop going through the affected rewrite step and the 503s and 1019s should stop on the next page view. The tradeoff is that the first-party tag injection that Google Tag Gateway provides will stop. Your client-side GTM container (if installed directly on the page) will continue to work the standard way.
> A note on scoping: Google Tag Gateway cannot be limited to a single subdomain. When enabled, it applies to all hostnames and subdomains in the zone, so the disable is per-zone rather than per-host.
Moet zeggen dat het me niet tegenvalt. Gepulled uit een ETB en Booster Bundle (tevens mijn eerste packs ooit). Vooral erg bij met de Cinccino en Mega Floette. Deze hobby gaat me alleen wel geld kosten, maar dat is het me waard :)
Gisteravond (na een paar biertjes) mijn eerste booster bundle & ETB gekocht (Chaos Rising), alleen ik ben helemaal nieuw in deze hobby. Ik zat al meer dan 2 jaar te twijfelen om hiermee te beginnen en ja, ik weet dat het momenteel een heel slecht moment is, maar dat werd 2 jaar geleden ook al geroepen, dus so be it.
Iemand aanbevelingen wat betreft sleeves, toploaders en eventueel een binder? Ik wil dus vooral gaan verzamelen, maar de kaartjes moeten natuurlijk niet beschadigd raken. Thanks :)
I currently use WooCommerce for my clients' e-commerce projects, but I want to move away from WordPress entirely. I'm already using Filament for CMS features on simpler websites, and it works great, so now I want to start building webshops with it too. Building a full e-commerce solution from scratch is more work than I can take on right now, so I'm looking at existing solutions that use Filament for the admin panel and that I can extend myself.
My shortlist comes down to Lunar and Shopper. Lunar seems more mature, with more features and a larger community. Shopper's development principles appeal to me more though, and align better with how I build my regular Laravel projects (event-driven, with the ability to override specific components or features). Shopper's admin also feels a bit more user-friendly than Lunar's, but I haven't used either in depth yet, so that's just a first impression based off their websites & docs.
The first webshop will be a simple store with regular products and some variants. Other stores I've built with WooCommerce were more complex, with product bundles, custom shipping logic, EU OSS tax calculations, PDF invoice generation, third-party accounting integrations, and so on. I want to make sure whatever I pick can grow into that kind of complexity later on.
Looking for recommendations and experiences from anyone who has used either one, or both. Thanks!