horst

Yep, another me too here. On the first day getting contact to PW, I saw this video and it put me on fire to try it out and to understand it. And some time later, after finding this "PW-spirit" in the community, to contribute to the image handling. (Thanks @Ivan Gretsky, for reminding on it. ?)

Yep, using an own admin module is possible since at least PW 2.0, if I remember right. ?

@cstevensjr, @LostKobrakai, Thanks! ? I've already downloaded MusicBrainz Picard, as it is OpenSource (Python), and I also already found a plugin source code that fetches covers via a fanart.tv, where one can register for a API-key. That seems to be pretty fine and I will test this out. And if it doesn't work out as expected, I will use the MusicBrainz Picard GUI-App.

Hey there. I'm (re-)ripping my 1k+ CDs in a better quality than I've done in the '90s, where 192k was good, because HD-space wasn't that cheap like today. ? Does someone has knowledge or a idea how to programatically find CD-Album-Covers by Interpret and/or Albumname? Primarily I'm searching for a web source that has cover images.

Not while programming, but when doing image manipulations and administrative tasks like site transitions (dev > stage > public) etc: HipHop in german language, from a young women living in cologne (germany), Leila Akinyi. For those who do not understand the text, it also is worth to listen the music and view the videos. ? My favourite is this one: And my second favourite:

Whats about your own styles for CKE, maybe with one or two "!important"? (Via CKE-Custom-Styles, or via AOS or via Admin Custom Files)

It both depends on how a server environment is setup. Especially if the PHP running user has write access to these files and directories. So, if you already know that the PHP user has no write access, you can do this before you start the installation process. If you don't know this, you can run the installation process and PW will tell you about the situation and guide you through the manually needed tasks. (Namly: select your drsired site profile or rename it to "site", delete the unused profiles, and also delete the install.php file after finished the process".

Good point @Robin S. When searching the class name StreetAdress in one word, it is the first result. But it has to be it also when searched in two words!

You need to enable the use of the Functios API in your site/config.php: $config->useFunctionsAPI = true; // pages()->find(), sanitizer()->pageName(), region('content', $markup),

I encountered this issue too. Maybe one can call it a bug? I only used this functionality once, so I added a quick workaround in my template file. If the fields content is empty, I injected some chars " ... ", so the field is clickable. (The spacers are added to the $page->fieldnames in memory, it does not get saved into the DB.) Following the dirty copy/paste of my used code

DEFINETLY ?

Hhm, sorry, I was very busy and disabled all notifications for the last 7 hours, to get not distracted. On the topic: We can hide it, or we can keep it. It is not (only) my decision. (?) @kongondo has locked it, maybe that is enough in this case? (So everybody can read what happened, but we avoid further discussions into the wrong directions.)

Thanks @szabesz! @bernhard should I hide / delete that thread?

Is there a slack channel already?

@psy thanks for the link and info. As I use(d) (un)serialize a lot, I never encountered that problem myself. Maybe I simply had luck that the processed data mainly were key/value pairs and no long strings or texts. But I don't get the context with JSON in the title? Only thing that directly comes to my mind is to use json_encode and json_decode instead of the (un)serialize functions. JSON_encode/_decode seems to be free of workarounds with extra steps of base64 encoding or others. (And I don't think base64-encoding is a plus in regard of privacy/security.) Until now, I mainly preferred the (un)serialze functions. But now, with this information, I will switch to only use json_encode / _decode. So, thanks again for sharing! ?

@ryan Get well soon.

Look / debug what you get from ->images->getRandom(), maybe via die(var_dump($randomImage)); Then you will know what to do, or you come back with the new information and ask how to proceed further.

Hey @teppo, the user 8-bit-guy is one of my sons favourites. My 12 years old son loves to work and hack retro hardware, like commodore 64 and a whole bunch of gaming handhelds or consoles, (besides others). Every third or second time, when he get something to work, and I ask him how he got it to work, he answers: "I found some useful information from the 8-bit-guy." ?

Cool specs! ?

Yep, it then definetly removes all variations. ? But in some cases it may become handy to use a scalpell instead of a hammer. For example, if you use the same images in different locations, as with centralized image pages, you may have a total of 100 variations but only 7 do belong to your current template. Just a thought: Maybe a programmatically created suffix, based on the (page | template | imagefield), can be embedded into the variation names? This way, you only need a delete-function that gets passed that suffix, to remove only variations containing it in their names.

Yep, I know. My comment was addressed to Bernhard and his main question in this thread. Sorry for being unclear.

This will not work well together with a centralized (and included) version number. There are multiple possibilities to mix wrong files together. My personal conclusion is to keep the version number hard written in each class file, ( the old schooled way). ?

You need wireHTTP to send a GET or HEAD request to get back the status code. ?

What about a proxy script on site B that gets invoked via htaccess for all images coming from site A. This script determines which variation is desired and redirect to it on site B. If the desired variations are yet not pre created, the script from site B must talk to a script on site A that is possible to create a variation before finally redirecting to it.

Hi, thank you for the write up. ? For me it looks you found the right balance for beginners and experienced users. A following second part would be very nice and useful. Additionally to that, if you don't mind, I would be interested in a third part too. This one should cover how the function(s) recognize or act upon changes of a focus point or zoom value, if used. Does it recognize it, and recreate all variations? Do you also include / provide or already use a function to remove exactly the previously created variations? Maybe useful during developing a site, when my first used sizes need to be adjusted. (Otherwise I would have a lot unused variations). If you don't use this already, I think it could be done very easy by using a suffix for the variations.