Stefanowitsch

There has been an update to the ProcessWire LESS Module to make use of the latest version from wikimedia. You have to set it in the module settings: However this does not fix the error with the CSS ":is" selector in the latest UiKit version: But that is not the only error that is popping up. After commenting out this piece of code there are other errors and more errors. Again I think there is a conflict between the newest UiKit and the current Wikimedia LESS version. I will try to compile the UiKit less partials with a different compiler to see that happens there. So my personal advice would be to stick to a UiKit version < 3.24.0 for now.

Hello @ryan I just updated the UiKit Library to Version 3.24.0. There have been minor changes in the LESS files of UiKit to make use of newer features (for example the @property rule). But that results in an error when trying to compile those files. For example: It seems that the ProcessWire Less module is a bit outdated (or lets say: the wikimedia less parser that is used under the hood). I downloaded the latest wikimedia less parser version and replaced it with the version used in the ProcessWire LESS module which solved some of the errors but not all. For Example the ":is" CSS selector throws an error too (when used inside a LESS file). So I guess just updating the wikimedia less parser does not work 😞

Thank you! I guess that is just the way things work. I re-generated the token inside my facebook app and replaced it in the module settings. Then, after 30 minutes the Instagram Feed was working again. The token auto-renews from time to time but it seems that in some rare cases you have to simply generate a new one.

Hi @nbcommunication I am again struck with this error message in my log and the instagram posts don't show up on the website anymore. I generated a new access token but it did not help. Is there away to renew the expired session?

I find this is a really good addition, thank you for including it in your module!

Hi @Juergen! I tested your module, you did a great job and I found two small details that I would like to point out: 1. "for" attribute missing on labels (when using InputCheckboxMultiple and InputRadioMultiple) 2. <label> elements (when using InputCheckboxMultiple and InputRadioMultiple) need "uk-form-label" classes to apply margins (of course only when UI Kit styling is selected in the module settings) By default the <label> surrounds the input so that the "for" attribute is not needed. But if you use this option: $form->appendLabelOnCheckboxes(true); ...then clicking on the label does not activate the checkbox/radiobutton next to it (because of the missing for-attribute). Another thing that would be really convenient: Is it possible to allow multiple file uploads via the InputFile class and to show each file that is chosen for upload under the field (before submitting). Something like this: The idea is to get an overview over the files that should be submitted and also give the user the option to remove specific files.

@Juergen thank you! I was looking at the GitHub documentation and these classnames are still listed there: InputSelect text - InputSelectMultiple arrayVal -

@Juergen I am experimenting with your module to see if it fits my needs, I was wondering if you forgot to include the "InputSelect" and "InputSelectMultiple" Classes in your module? I get an error when trying to create a select field and the class file is missing in the InputElements folder: Error Class "FrontendForms\InputSelect" not found

Thank you very much @Robin S I modified the code a little bit to fit my needs and now it is a rally simple but very effective solution for handling global media / file management in ProcessWire.

Yes I already send a PM to kongondo asking where to download the latest version of the Media Manager. This module still looks very promising. But on the website https://mediamanager.kongondo.com/ neither a documentation nor a download link is available.

Hello there! Since I started creating sites with ProcessWire I wished there was a central media management option. You know - a place where you can upload all sorts of data (well, mostly images) to use them throughout the whole website. It is something that nearly every other CMS offers and many clients of me which used Wordpress or Typo3 are used to this kind of media management and it's kind of hard to tell them that this is not possible (in that way) with ProcessWire. I know from the past that there was a Media Manager Module from @kongondo but this module seems not to have been updated in years. Are there any other solutions or techniques that you developers use?

Thank your for letting me know! I updated the module to Version 1.0.1.

I can't help but agree!

@nbcommunication I found my problem. 🥵 It wasn't your module at all but instead another module that I was using which interfered with the webp image creation for the srcset attributes: Delayed Image Variations I was using this Module because the image variant generation on image-heavy sites (using the size method) took very long and resulting in time out errors of the server. As described in the module thread: After uninstalling the module all the paths in the srcset attribute point towards the webp versions of the image and also the quality settings are applied as set in the module settings page! I am sorry for causing so much work for your tests! 😔

The output of both is: "0 Bytes" I then tried this: <img src="<?php echo $image->size(2550, 1440, [ 'webpQuality' => 10, 'webpAdd' => true, 'webpOnly' => true, 'suffix' => 'q10', ])->webp->url; ?>" /> Which results in in a "502 Bad Gateway" error (for the jpg image file path), because the img src in the DOM refers to the "jpg" version: <img src="/site/assets/files/1651/startbild_architektur.2550x1440-q10.jpg" width="2550" height="1440" sizes="auto" alt="" uk-cover=""> The jpg version however is not created (probably because webpOnly is 'true'). The webp version is created in the filesystem (and the quality setting is working!) but this webp version is not used in the src attribute.