wbmnfktr

Just in case and in order to complete the list of possible ways and solutions. And this comment by @szabesz to even more possible solutions:

Check your server configuration. No matter which tool I use or what page I check your site always tries to redirect the visitor to the URL that's already loading.

Found another thing... My 404 page has the same template as most of my other pages as it's kind of a page builder. Trying to reset the page count for that template the 404 page still has it counts while other's dont. Trying to be clever and looking up the ID of that page (27) in order to reset the view count an error message shows up. SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') AND `data` > 0' at line 1

Just spotted a curiosity in my Jumplinks 404 log... .. and found out it's from here PageHitCounter.min.js. "use strict";(window.PHC=window.PHC||{}).t=function(){try{var e=document.getElementsByTagName("BODY")[0],t=parseInt(e.getAttribute("data-phc"));if(!isNaN(t)){var n=new XMLHttpRequest;n.open("POST",location.pathname.replace(/\/?$/,'/')+"phcv1",!0),n.setRequestHeader("Content-Type","application/x-www-form-urlencoded"),n.setRequestHeader("X-Requested-With","XMLHttpRequest"),n.send(encodeURI("pid="+t))}}catch(e){}},PHC.t(); Did I missed that before or is this not working as intended?

Looking at your Devilbox config NGINX seems to be the problem. Or at least was the problem. As far as I know it's not supported - but others are using it (with custom configs). PHP 7.2 is working perfectly - at least from what I can tell. Regarding MySQL I personally use the 5.6 version(s). Oh... and regarding ProcessWire... it gets better and better the longer you use and play around with it. ?

@bartelsmedia in your case HannaCode could be an option.

In my testing project there is no need to do anything right now. But I plan to test it on a more established site in the near future and in that case I will replace everything manually as I redo the SEO stuff then as well.

Wow... good to see there is someone else who needs this as well. My personal preference would be: right in the meta group after keywords. By now I think creating a new group seems to be kind of an overhead. We could argue about semantics and meanings but having this option almost above the fold seems to be a much nicer user experience.

Fingers crossed!

If you @Melvin Suter or everyone else wants to play around with a recipe site profile: https://github.com/webmanufaktur/pwrecipes It's by far not complete or a ready-made website but it shows some things I mentioned in first anwer here.

Repeaters are kind of awesome. https://modules.processwire.com/modules/fieldtype-repeater/ You have to install repeater and select options (maybe even page reference - I'm not sure about them) first in order to use them. You will find them under /youradminurl/module/ (Core tab) - look for repeater, select options and page reference.

Allow creating new pages from page reference field and ingredients aren't a thing anymore. Add autosuggest and everything is fine. I actually imported lots of ingredients before. So authors typed bro... and they got broccoli already. Less typos. Perfect. I clean up once in a while but that's a matter of minutes now.

I use WireMailSmtp successfully with the following services/webhosting providers: Gmail (@gmail.com) Google for Domains (Google Apps) Yandex for Domains Outlook.com (Freemail) Strato (Webhosting, DE) 1&1 (Webhosting, DE) Checkdomain (Webhosting, DE) webgo (Webhosting, DE) Dreamhost (Webhosting, US) A2hosting (Webhosting, US)

Great work @Wanze! Haven't had the chance to deploy it on a client's project but I gave it a test-drive within an experiment I prepare right now and I really like it. Everything worked as expected as far as I can tell by now and I should be able to replace my previous set of fields with this module but there is one thing I miss.(One tiny thing I miss in every SEO module/plugin I used in the past.) Custom canonical URL I need the option to change the canonical URL of a page. I could use the module and a custom field for that. Problem solved. I don't know if anyone else ever had the need to change it but I didn't want to miss the opportunity to give this as a kind of feedback - and not as a kind of feature request.

Correct. Ingredient database and therefore filters/presets.

There are so many ways in ProcessWire to do or save things. Depending on your background and history with ProcessWire you will find other ways or solutions. I know recipe-collectors that would only need two fields. A title and a textarea. I personally would go a more abstract way to be able to much more and other things. Template: Recipe Fields: title (text) summary/introduction (textarea) preparation (textarea) ingredients (repeater) Fields: ingredient (page reference - pages with template ingredient) amount (int or text) unit (select options - grams, cups, liters, hint) images (image) Template: Ingredient Fields: title With that setup I can easily collect all my recipes, create a list of all ingredients I need for all of my recipes. Can look for recipes with a special ingredient and so on.

I face a problem with dependencies right now. A field should only be shown and be mandatory if a checkmark (within the repeater matrix type section) is set but this doesn't work all the time. Right now I disabled this dependency and focused on other things but yes... it still seems to be a little bit... unstable.

Ok... sorry... I guess I wasn't accurate enough. In my understanding the hook is fine. As it is ready to get called whenever the API is ready - which is almost every time in your case. No matter if front-end or admin back-end. That's totally fine. But your function won't be executed until !$session->get("shopifyShopCurrency"). Which is fine too and the exact thing you wanted. So... yes... it's bizarre that you already reached your limits. Maybe. I don't know the API limits or the traffic your site gets. Maybe there are lots and lots of bots/spiders on your site that trigger your hook. Or there is enough regular traffic and you need more API requests. Can you log each request/function call to count how often it's executed?

Is hosting provided by 1&1 as well? If so... you could ask their support if you have to use another server/port or whatever in that case. Have you tried another mail service like Gmail? Does that work? If so... 1&1 might have the right answer. if not... there is another problem. What's the complete error message WireMailSmtp shows?

Source: https://processwire.com/blog/posts/processwire-2.6.7-core-updates-and-more/ So... in your case it seems as it's called and used almost every time a page loads/renders.

There have been several threads regarding rewriting page URLs but most of them went towards different directions. You could probably hook into several things and rewrite URLs. I don't have a proper solution for this right now but I'm quite curious about the WHY. Why do you want a URL structure like that? It feels kind of outdated or Contao-like nowadays. If it's because of OLD vs. NEW setup and URLs you could go different ways and redirect the old structure to the new structure.

Regarding symlinks... you should check that htaccess and mod_rewrite play nice together. 1. htaccess # ----------------------------------------------------------------------------------------------- # 1. Don't show directory indexes, but do follow symbolic links # 500 NOTE: Some cloud hosting companies don't allow +FollowSymLinks. # Uncomment +SymLinksifOwnerMatch and comment +FollowSymLinks if you have 500 errors. # If that doesn't resolve the error, then set it back to +FollowSymLinks. # ----------------------------------------------------------------------------------------------- Options -Indexes Options +FollowSymLinks # Options +SymLinksifOwnerMatch 2. Apache / mod_rewrite conf In some cases each document root needs individual configuration settings. Especially in vServer/root server environments.

It's more about server/hosting security than validation as it happens server-side and before any request reaches ProcessWire. ProcessWire works out of the box in about 95-99% situations already. Maybe not in case of NGINX but that's another thing. Knowing more about systems and their configuration isn't a bad thing at all. I don't want to miss anything I know about servers and how to handle them. Have you ever installed Typo3? It is (or at least was) pain in the a** and they still have a nice market share. I'm more afraid of doing my taxes and still I have to deal with it. There are professionals for those things. I wouldn't spend too much time and effort in replacing some lines in the .htaccess file. Why bother with something that's already working almost all of the time? Debugging those installation or migration issues within the core of a CMS is way more difficult than (un-)commenting some lines in a plain-text file. And to be honest... I'm quite shocked that WordPress has just a few lines in its .htaccess. Last but not least... In my opinion: No... I think the .htaccess could do even more in some cases. For example: https://processwire.com/blog/posts/optimizing-404s-in-processwire/

Some fresh sounds I discovered recently. I didn't know I'd like this Synthwave music but... can't get anything done without it. Whole YT Channel: https://www.youtube.com/channel/UCmYTgpKxd-QOJCPDrmaXuqQ Some more on Basecamp. If you loved Stranger Things (Netflix) you will probably like this too. https://synthwavecafe.bandcamp.com/album/stranger-things-tribute