wbmnfktr

Are there any modules or hooks in place that could be responsible for that behaviour? How do you create those painting-pages? Which version of ProcessWire do you use? I just tried to reproduce that behaviour but without success.

With ProcessWire 3.0.98 I can't confirm your bug. How do you create your pages? - in browser or via API Which versions do you use? Process wire and modules What modules do you use? Do you have hooks in place?

I would agree with that to a certain point. Imagine your client uploads a few hundred images with 12 MB+ each. If they explicitly ask for the possibility to upload super high-res images it's another story.

In case of images I would limit upload sizes as in height/width and MB. In case of videos it depends on where they were used. As a movie I wouldn't care that much about size but I would load them only on demand. As a background video I would limit size.

You only get about 22 MB? The video I get is already way larger than that.

Just out of curiosity but will you try to downsize the homepage's size in the future? 82.6 MB is quite a big number.

I guess... we have to thank you!

This works as expected. Tested in Chrome, EDGE, Firefox, Opera (all latest versions).

Ok... now I understand what they tried. Didn't see that very first line. I'm using 3.3.1 right now.

I know [method] very well but only from documentations noone understands and not from productive code. Especially with jQuery I miss often new things so maybe this is the new way to get things done. ?

I can confirm the behaviour @iank describes but I'm quite surprised that I notice this change just as of today. I changed line 182 from [method] to .prop to get the functionality back. $(this).parents('.pwcmb-option-wrapper').siblings().find('.pwcmb-widget__row-cb').prop('checked', !checked); Is it me or is [method] wrong at that and some other places?

So... you haven't tested it with external addresses, right?

In my case it wasn't cropping the image which led to unexpected results it was only resizing. It took me hours without any results until I used a different image. I don't know if you test with only one or several images but if there is only one image you use, please try another one. My .jpg was more of a corrupted-Frankenstein-PNG-saved-to.jpg file. May sound ridiculous but you never know.

Clean code, less code than content (ratio), and fast content delivery aren't a guarantee of good SERP results. You can build the smallest, cleanest and bestest website ever and get outranked by a crappy WordPress instance. Sometimes other things matter more than that. Links, links, links, spammy content, PBN links, more PBN links, more spammy content... all those grey to black techniques still work for almost every site. Old domain with trust but spammy content and WordPress footprint? Perfect! We already love it. New domain with better content, better UI, better load times? Are you kidding me? We will never rank that! You build clean, fast sites as a base for more. Good SERP results are a thing you have accomplish with several other things. Spend a few hundred dollars for a good, old, trustworthy domain, create 100 pages of optimized content pages for another 200 - 300 dollars, get lots of links from trusted sources (Reddit, LinkedIn, Blogs, ...), buy 10-30 more good old domains, build spammy sites with matching content, create backlinks, outreach to other spammers bloggers, get more links and you are in the Top 10 to Top 3. Don't play fair on money keywords. That won't work.

Noone wants to blame small offices and business that are in need for a website that won't break the bank. I blame those professional scammers that sell 80-dollar-theme-based sites as custom-made [whatever buzzword fits here] website and either charge way too much or dump prices with it.

Oh yeah... I love those super creative full stack and full service brand entrepreneur happy guys agencies that sell websites this way and claiming they are the best in the market doing highly coughstomized websites and brand building. I know agencies that charge five-figure numbers for 80-dollar-theme-based sites. Only if you do basic website jobs without any real custom data. Pages and posts slightly customized with visual page builders but that's it. A win-win situation for both sites.

It's WordPress... there must be a plugin for that!

I saw it was mentioned somewhere but haven't done any further testing with GTM, GA, Matomo or anything else by now. My first site with this module will go online the next days and I will test all three mentioned trackers then.

I'm fine with that. Thought you already tested this new option and looked into it. But for those who want to know more... auto-accept mode is kind of a silent opt-in. While the first view only triggers the banner itself and returns false for if(localStorage.getItem('pwcmbAllowCookies') == 'y') the second and all follow-up page views allow tracking and therefore return true for if(localStorage.getItem('pwcmbAllowCookies') == 'y'). Users will still see the banner and have to either accept (again) or have to opt-out.

What's happening here in detail now?

This question is kind of a joke, right? True! But its purpose is editing page content for logged-in users (editors with knowledge about the system and the process) and not taking event registrations from people that don't know what they do there.

Ok... I got this totally wrong in your first post and didn't get this @-comment/feedback process. Sorry if my answer was therefore kind of rough. With this comment/feedback process I'd agree with your concept of closing unanswered-open-but-fixed issues.

I know... closing issues and tickets comes straight after writing documentation. ? Some things just have to evolve and need to be established. Doing a clean-up once a week doesn't hurt. Ok first due to so many open issues but later on it gets easier.

Sure... but it wouldn't help resolving those issues. Someone doesn't close an issue just because x amount of time has passed. Issues were opened for a reason. Therefore they should be closed for a reason, too.

There are two things coming up my mind to get this done: FormBuilder + some hooks for checking and saving responses something similar like the Social Impact Award tool @bernhard built in the past