wbmnfktr

Which version of ProcessWire and PHP are you using? How did you install the module? Is it a clean installation or a running project? Try another browser or private mode. Take a look at site/assets/logs/errors.txt for more details. Enable debug mode in your configs.php. @adrian is it safe to rename or remove Tracy from within the file-system? Btw.: this is the official Tracy Support Thread where this post would have been better. ?

Why in a hook and why saving the image to another field and so on? Why not just checking it in the template and outputting different values for OG/SEO?

Didn't @bernhard write something similar about how to be efficient in creating thousands of pages a few days/weeks back? Those weren' files but at least performance wasn't the problem if I remember correctly.

Try the $user->isLoggedin() option. I don't know enough about session handling in ProcessWire and why this is the way it works in your setup. Which version of ProcessWire are you running? Are there any other broader modifications/custom codes for session or user handling? Did you install any session related modules that may interfere here?

That would be a masterpiece of course! As @szabesz already wrote... sometimes you want to take care of some fixes you need and aren't available at time. Therefore the idea of naming this module PWQuickFixes seems to be pretty accurate.

IMHO... I see your concern and fear here but... this module isn't for the average user as they aren't that deep into the core details of ProcessWire. Mentioning an issue is easy, reporting an issue is work, fixing an issue with this module is art.

Similar background... totally different solution: 2,000 recipients 1 older lady weekly newsletter Nothing worked out good enough. No software, no CMS plugin, no nothing. For a small fee each newsletter she now gets kind of proofreading, formatting and everything her newsletter needs. She writes and sends the newsletter in her mail client (Thunderbird) to me, I copy/paste everything into a plaintext file, format everything, read everything, put it together in Mailchimp and send it out to her recipients. It takes about 20 minutes. Everyone is happy. As it works so well for her, she wants to send more newsletters with more content, more links in the future. Lucky me.

Maybe not related but in the past I always stumbled across two things: code in templates needed a $page->save whenever I changed something in an image field while in a module/hook it wasn't necessary or caused strange errors another thing was that I always had to foreach() through the image field I try to find an old module I built... images were a huge deal in it.

I added $config->sessionExpireSeconds = 120; to my config.php deleted all cookies and sessions (/site/assets/sessions/) opened a private window and logged in waited 2+ minutes clicked a link and was redirected to the login page It works in the backend. How and why there might be a difference in an application or frontend... I don't know. Maybe caching, maybing something that keeps the session alive. Another thing is session()->isLoggedin where did you find that? All I know is $user->isLoggedin(). Maybe you could try: if(!$user()->isLoggedin) session()->redirect(config()->loginUrl);

? ? ? ? ? ? ? Because you never know when a crocodile shows up in your office! In the last couple of years I went through a lot of keyboards 2x Microsoft Bluetooth Design Keyboards 3x Thinkpad X1 Carbon (2015) keyboards 2x Surface TypeCover 1x Razer Black Chroma Something No coffee, soda, cigarettes, tobacco, fast food, children or crocodiles involved! They just stop working. E, A, S, C, X, V, Esc, Ctrl, Alt... all left/left lower keys. ?

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.