horst

In the parent page you have to set the sorting to manually drag. DO NOT set any hard sort order there. Then you can use the add new childs first method from AOS. This results into the following behave: Everytime you add a new child to that parent page, it is added on top of the list, as first child under the parent. From there on, you can drag and sort this and all other pages manually as you like.

This is not a direct answer on the current problem, but shows a different method for using a custom var in different scopes: Instead of using a superglobal var it may also be possible to use ProcessWires Functions API with a custom var name. // initialize a custom var, maybe in your site/_init.php region('hannaCounter', 0); // later in your templates or modules or where ever, count up the counter region('hannaCounter', region('hannaCounter') + 1); // and where ever you need it, get the current (or final) counter value echo region('hannaCounter');

Are you using AOS? (AdminOnSteroids module) It enables to configure a lot in regard of CKE.

In template files I use the page-id to get the page or, where I have set a specific template name, I use this to get the page, and then uses the $p->url. There are different ways and concepts people uses. I prefer to give own template names to specific pages, limited to one page only, so that I securely can get them from everywhere, regardless what name a editor gives them, or if a site owner deletes a page and creates a new one (what changes the page id). In the templates settings I use the property for mapping a different template (render) file. So, for an unlimited number of basic-pages, 1 imprint page and 1 contact page I use 3 template names and one template file: template file is: site/templates/basic-page.php template names are: basic-page, can be used for (unlimited) new pages imprint, can be used only for one page and is mapped to basic-page (template file) contact, can be used only for one page and is mapped to basic-page (template file) But as already said, that's only my preferred way. ?

Whats about creating an empty WireArray and then do the foreach loop on the $meevo_response_array? $meevo_response_array = json_decode( $meevo_response ); $reviews = new WireArray(); foreach($meevo_response_array as $meevo_response_item) { $tmp = new WireArray(); $tmp->import($meevo_response_item); $reviews->add($tmp); } https://processwire.com/api/ref/wire-array/add/

No, looks fine. Exactly how I do it too most of the time. ? So, there must be something other interfere. Weird.

Do you have set any access settings or family settings between the parent and child page templates?

PW does not process any real existing folder. You don't have to do anything for making it ignore them. That's the default behavior.

Hey, I found two vinyl albums of the group Tuxedomoon from the early eighties. If someone knows them and like to get them, please drop me a note. (for the shipping cost) 1) TUXEDOMOON - "Half Mute / Scream With a View", (1980) 2) TUXEDOMOON - "A thousand lives by pictures", (1983) 25 years back, I moved from Vinyls to CDs. Over the years I gave away all vinyls, only kept a number of around 50 pieces that I initially wanted to digitize. But I do not hear this music any more and never missed it. Also there were some more or less rare vinyls I really digitized, maybe 10 albums, but for all others it definetly is to much work. ?

What is about starting at early state without that feature? Just with the possibility or limitation to use it for new (empty) projects? Who has said this: "Release early and often"? Don't remember. And yes, I know, there are not only pros with this strategy. ?

? ? ? ???? ?? ????????? ?‍♂️?‍♂️??‍♂️?‍♂️?‍♂️?‍♂️

+1 ?

Hi @adrian, this is very old legacy code from before 2013 when I joined PW, - and it is from a community member named "mrx": https://github.com/processwire/processwire/blob/master/wire/core/ImageSizerEngineGD.php#L863 So, the referenced SO post seems to be the solution already. Maybe you can send me an image that has this error, so that I can test it. Or would you like to write and test the fix yourself? (As you already have done all necessary work.) ?

You need to create enough rows and columns, and span your contents, I believe. See Jen Simmons here:

It works when used via JS AJAX calls in (static) HTML (ProCache)pages.

As far as I know, you only can store strings in localStorage. So, without having a look into the code, I know it is common usage to stringify objects before writing them into localStorage, and to JSON.parse() them after retrieving from it. Just try something like this: var obj = JSON.parse(window.localStorage.getItem('privacyWire'));

According to the bureau of the Datenschutzbeauftragte of NRW, germany: If you (self)host Matomo on the same domain or subdomain with anonymized IPs, you can start to use it without opt-in, regardless if cookie-less or a use with cookies. Only thing you must provide and respect is a opt-out option. Don't know if this is different in other Bundesländer of germany, but I have gotten a written answer with the above content from the NRW-bureau. ?

Yes, I remember that there were some core updates has to be made between PHP 7.2 - 7.4.This must have been somewhere at PW version 3.0.98 ? or 3.0.128 ?, don't remember exactly, but the PW core 2.7 does not have these changes! Why do you not want to upgrade to PW 3? From PW 2.7 to PW 3 is to 97.5 % just switching the wire folder! And another question in this regard: are you sure that your site profile code is PHP 7.4 ready? ?

EXIF data is stripped out with every processing function that uses GD-lib. So, if you just use creating a 100% width "variation" and store it as the "new" original image, all your EXIF data is lost. (GD-lib simply does not keep any image markers by design. Historically it was build to create small images for the web, and everything that may bloat filesize is dropped) PW every time reads the EXIF data from the original image that regularly will be kept untouched.

Modern PHP Cheat Sheet A to-the-point summary of all awesome PHP features https://front-line-php.com/cheat-sheet

Until today, since 20+ years, every time when I inspected such behaves, it comes out at 100% that the source image simply got the wrong notation in the EXIF rotation flag. Mostly directly when created from a camera, but also came from image tools that rotated images without updating the EXIF rotation flag. In my opinion, the new browser behave isn't of any help but makes it more "mysterious" for regular users when working within image processing chains. The ONLY point where this new behave is helpful is when original images will be displayed on the front in a webpage (and have uncorrected rotation).

What I do not understand is why the original code has worked for 15+ years and now (within a sudden) it should not do anymore. As far as I could not find any changes in the EXIF specs. ?? Are you sure that the corrections arrays are wrong, really? Or may it be that the browsers have changed to a behave that rotates images ONLY BY VIEW, and that this new browser behave has to be corrected elsewhere in the inspection and processing workflow? Just wondering.

Hehe. Documentation often lags far behind development. ?

Thats an interesting approach! Thanks. ? And there is this tool that can help a lot by finding alternative fonts for the stack: https://font-match.netlify.app/ @all: Many thanks for the help and thoughts! ?

This is Corbel and not Corbel Light. ANd it is TrueType and not Webfonts (woff woff2). Yes it is part of Win10, but is it legal to use them in a website of a professional freelancer without a license from MS? A license for Corbel (Webfonts and usage with self hosting) can be bought at www.fonts.com, for example.