wbmnfktr

Have you cleared all previous cookies and session files? Just to make sure there aren't any "old habits".

Just thinking about it... could this replace all of my custom code snippets in ready.php? If so... this could be way more handy than I thought at first.

Oh...kay... that clears up some things. So instead of waiting for the official fix we can now apply our fix to our environment whenever needed. Sounds great for those like you and @adrian who love to dig deeper into the core code. ?

Even though I feel pretty confident in using and working with Processwire and building lots and lots of different projects with it... your task/idea would be still a challenge for me - in some kind. There is so much more involved than just a registration form, all those fields, user restrictions, notifications, and whatsoever. To be fair... you will have to code and customize a lot here. Installing a few (more) modules wouldn't do the trick. If this is kind of a long-term or fun project to get more into coding and challenging yourself: just start, try and break things, rebuild your code, do whatever is needed. If this is a paid job or something you really want to share with others: well... maybe look for something that already exists, that is tested and maintained. Like this forum. It's a super solid piece of software. Not that cheap but robust, tested and maintained.

? I'm a bit confused... to say at least. What are these fixes for? Are these custom changes to the backend - manageable through this module?

Well... at least you had some exercises in debugging now. ?

I honestly don't know. Never bootstraped ProcessWire into something in the last two years or installed it into a subfolder. Sorry.

I really don't know if this might help here or if you already tried it but in version 3.0.141 Ryan made ProcessWire system URLs/paths now more customizable: https://processwire.com/blog/posts/pw-3.0.141/#processwire-system-urls-paths-now-more-customizable

That could do the trick. Yet another thing comes to my mind. It needs to be somehow managable for users to see what decision they made. How do you handle that in your fork/version? I didn't see anything in your code that tells users their "only necessary cookies" decision. Maybe it's there but I haven't installed your version yet.

That's exactly what I thought about. As it's a change with bigger impact it might break already existing installations/setups. Therefore this has to be announced very well in that upcoming release - whenever it will happen. While DNT is kind of great and standard I had issues with it in the past - quite some time ago - but I actually love the idea. As it would support Privacy by default it might be something not everyone (site owners, marketers, ...) wants, so it could be another option in the settings. I really appreciate your input and ideas!

Whenever I experienced this issue it was somehow related to mod_rewrite. At first I'd make sure mod_rewrite is installed and enabled - which I guess it is, as you can access the admin. If possible restart Apache. Delete whatever cache (template cache, markup cache, WireCache, ProCache, FileCompiler) you use. Even the cache in your browser. Try to set the rewrite base - you will find it in your .htaccess under number 11. A little warning: use another browser or use it in Private Mode while testing your changes. Browsers sometimes cache way too much for way too long. ? And of course: change only one thing at the time.

On first look this sounds like a really nice and handy addition and workaround for several use cases that were already mentioned here. I have to take a closer look how this works out in the backend and frontend of course but I guess I'll be happy to add this to the module - somehow. But as you use cookieMonster.block() for your necessary cookies the stored information (localStorage) says cookies denied/blocked and there might be a difference in these so it might be better to store a different value than blocked.

Same here! There a some really nice examples, explanations and already "ready to use" snippets.

I have to admit that it doesn't look that bad for 7 years without a proper cleaning. I'm quite impressed actually. There is only dust and one bit of whatever... maybe paper. That's not a coder keyboard. Never! Where are all the chips bits, spilled soda and coffee stains and whatsoever? ?

They do it all the time. No matter how many accounts exists... most of the time all people use just one. Some just don't want to be responsible for changes so they take the credentials from another user or "admin" account they somehow can get.

https://vanillajstoolkit.com/ is another good location to look for VanillaJS

Enable pagination/page numbers in your template (the overview template) settings.

I could add a second option to that dropdown. Something like CustomCSS, add a specific class to the HTML and you can add your very own CSS and style it however you like it. Another way would be disabling the auto-load assets option in the settings and add custom CSS right away. I thought about something like that but I'm not sure which way to go here - for now. The solution used by Deezer is provided by CookieBot and is quite powerful. Yet a bit too much for most I guess. What/which options do you need in most of your projects? I'm happy to hear more opinions, suggestions and ideas.

It's probably not an issue with a missing 404.html/.php or a missing config entry. But I'm happy to see you worked through possible solutions. Possible reasons As you are using a DEV release there can be a problem with an installed (3rd party) module. Maybe it's just an error in a query/selector you are using in your template.php or _init.php or init.php or ready.php - yes, there are several possible reasons for that error but let's start at the beginning. Did you just installed ProcessWire or are you in the middle of an ongoing project? If you just installed ProcessWire you want to look in your .htaccess file - look here: https://processwire.com/docs/start/install/troubleshooting/#resolving-an-apache-500-error and check if mod_rewrite is enabled. If you are in an ongoing project open up the used template, take a look at your page selectors there and doublecheck them. Btw... welcome to the forums!

No matter how large a website will become... the main elements will stay the same. Just a different location, order or color. Most developers don't create (the) content anyway and in an agency or colab you split work most time as well. It's not totally impossible to maintain a large set of elements - especially when you have a few years of experience in doing and building such things AND have the ability and time to plan things out. I really like UIKIT and what their dev team has created there but... I still don't want to use it but get why others like it (or Bootstrap or Foundation or ...). And in my opinion... the best foundation for a large webproject is a blank file. ?

Another idea or maybe even a solution for this scenario. I never used it in any of my projects so far but I know that @bernhard's RockGrid(?) or at least one of his modules is really really fast while handling LOTS of data and could possibly handle even a few thousand referenced pages. BUT to be honest I don't know if his module only works in the backend or if it can be a problem solver in the frontend, too.

I use a similar setup within a product catalogue. The average is about ~60 referenced pages. Performance is still perfect. How many users are there that could read those hundreds of pages? Maybe you could save the users that read a page to that page instead.

+1 for UIKIT only

A weird way to protect against DDoS but ok... Fingers crossed they will find a fix soon.

There is this the fieldtype Color module and the ColorPicker module. You could get you a copy of those, dig through the code to see how they have done it. That's the way I would go in this case. Afterwards I'd take an existing 3rd-party tool or library (GPL oder MIT license) and implement it somehow.