Michael van Laar

Members
  • Content count

    97
  • Joined

  • Last visited

Community Reputation

75 Excellent

About Michael van Laar

  • Rank
    Distinguished Member
  • Birthday 10/19/1978

Contact Methods

  • Website URL
    https://digitalardor.com/

Profile Information

  • Gender
    Male
  • Location
    Fürth, Germany
  • Interests
    Digital marketer, avid cufflink wearer, part-time wannabe-recluse. Passionate about web design, marketing technology and music. Reflective on inbound marketing.

Recent Profile Visitors

8,183 profile views
  1. Michael van Laar

    Obviously ImageMagick causes this bug in combination with uploading JPG files, according to the AJAX error message. After deinstalling the IMagick Image Sizer module, uploading JPGs is no problem. This was my test case: Uploading the PNG file testupload1png.png With ImageMagick: upload works Without ImageMagick: upload works Uploading the same image as above converted into the JPG file testupload1jpg.jpg With ImageMagick: upload results in an error message and doesn’t show up in Media Manager. AJAX error message: “no decode delegate for this image format `JPEG' @ error/constitute.c/ReadImage/504” Without ImageMagick: upload works Uploading a second PMG file testupload2png.png With ImageMagick: upload works AND somehow “pushes” the failed JPG upload into the Media Manager, so now all three uploaded files show up as they should. Without ImageMagick: upload works I guess I can now either not use ImageMagick (which I just used because my hoster provides it on their servers as a default and it was recommended because of better memory usage). Or I can ask the support of my hoster about this problem.
  2. Michael van Laar

    I just bought and installed the module (v0.1.1 with Jquery File Upload v0.0.6), but get the same “Empty file upload result” error messages as mentioned a year ago. (Using PW 3.0.98) A little bit of testing revealed an interesting pattern: I upload a single image which is processed without problems. -> Shows up as it should. (I use “After Uploading“ setting no. 1.) I upload a second single image which returns the “Empty file upload result” error message. -> New image doesn’t show up in the Media Manager and the three temporary files in /site/assets/MediaManager/jqfu/.files_no_show and in /site/assets/MediaManager/jqfu/.files_no_show/thumbnails exist and look good when looked at in the browser. I upload a third single image which is processed without problems. -> Now all three images (including the second one) show up correctly in the Media Manager. Unfortunately I can’t tell the exact reason why the error message appears. I even tested small images (around 260 KB, so that should not trigger any memory problems while processing): The png version of one image could be uploaded while the jpg version triggered the “Empty file upload result” error message. The jpg version had about the same filesize as the png file—compressed as well as uncompressed, according to the infos in GIMP.
  3. Michael van Laar

    I just used a Repeater field on a hidden “website config” page to create my own menu building tool with exactly the features I needed for that website, including using multi-language fields within the repeater.
  4. Michael van Laar

    @Standard Forge, if you just want to make one or two minor changes to a rendered menu without having to build all the markup yourself (using getMenuItems()), you can do a quick str_replace. Example: $menu = $modules->get('MarkupMenuBuilder'); // cache the rendered menu $schema_menu = $menu->render('my-menu-name'); // alter the rendered menu to your desire $schema_menu = str_replace('<li ', '<li itemprop="name" ', $schema_menu); $schema_menu = str_replace('<a ', '<a itemprop="url" ', $schema_menu); // output the altered menu echo $schema_menu; Quick and dirty, I know. But if you are using delayed output anyway, it’s just one or two lines of code.
  5. Michael van Laar

    I took a few minutes to investigate. As far as I understand, the variable $redirectURL in /wire/modulesProcessProcessPageView.module is used to perform the above mentioned redirect (as well as any redirect which is necessary when handling URLs). In this case the varibale $redirectURL is set in /wire/modules/LanguageSupport/LanguageSupportPageNames.module, between line 202 and line 317. If it’s possible at all to eliminate the default language’s name segment from the URLs of pages of a specific tree branch – which is something @ryan or someone knowing the core really well could tell –, writing a hook that alters $redirectURL before it is used would be the direction I’d think of. But since I still haven’t had much time to learn more about the different hooks, this is only a guess.
  6. Michael van Laar

    I have the same challenge now on a multilang site. Using PW 3.0.42 with the default multi-language setup. A certain branch of the page tree should act as a kind of microsite, with different templates etc. But only in the default language (English). As far as I understand I’d “only” have to disable the automatic redirect from domain.com/microsite to domain.com/en/microsite – which is obviously a default feature of the multi-language setup – for the specific branch. I guess this feature is hidden somewhere in the LanguageSupport core module. So it should be hookable (since pretty much everything in PW is hookable). Anyone has a deeper understanding of the LanguageSupport core module and can provide a hint?
  7. Michael van Laar

    Great idea and great module! Saves me some rather ugly additions to the displayed title page in the page tree. One thing for the Christmas wish list: It would be even greater if the module would provide a way to set up several different rule sets. So you could set up different icons to mark different things.
  8. Michael van Laar

    Ah, great. Gotta test this the next days.
  9. Michael van Laar

    Thanks for the explanation, @matjazp. As I said, I'm fine with being able to use resmush.it via the module, since resmush.it works like a charm, and I don’t have any images which are not sooner or later made publicly available (so there are no privacy issues). Being independent from resmush.it would be a nice extra, but it’s not really required from my side. This would be interesting for cases where PW and Autosmush are used to build a website for a closed user group with confidential content which should not be send around between servers.
  10. Michael van Laar

    Of course I used the individual options. I also tried commenting out the pngquant_bin setting, hoping that the modiule would go on trying to use the next available PNG optimizer. But it didn’t work. I got the error message that pngquant could not be found.
  11. Michael van Laar

    Since my Linux knowledge is quite limited, I had to research and try a bit. Only the last option (inserting the path into the module file) worked – but only for jpegoptim. If i try to upload a png, I receive an error message telling me that the pngquant command doesn’t work, even if the module now knows the path to the binary. To be honest, that’s too much work to investigate. I just use resmush.it as long as it works.
  12. Michael van Laar

    Anyone has a solution for multi-language menus with custom menu items? For pages localisation works using the default_title option. But this is not possible with custom menu items. And since the items’ title field is not a multi-language field, I have no idea how to solve this. But I’m probably not the first one stumbling over this. ;-) If not, I think I have an idea how to build a solution using nested repeater fields.
  13. Michael van Laar

    Is there anything I have to set up to use the local optimization tools? I'm on a shared webspace, but each customer has a separate FastCGI PHP interpreter. So it should work according to the module’s documentation. Or did I miss anything? The error messages say “Command "jpegoptim" not found.” or the similar message for pngs.
  14. Michael van Laar

    Great! I was looking for a module like this after https://minimize.pw/ closed the doors. I have to test it tomorrow. I guess it works with Croppable Image 3, too, doesn’t it? Or let’s better phrase it: Does automatic mode work with all modules which extend the functionality of PW’s default image field? That would really make optimizing images a no-brainer.
  15. Michael van Laar

    I know, images differ from the other media types a little bit. As an alternative to the above described I could think of input field types which work like Croppable Image 3 or ImageFocusArea, but use a Media Manager image instead of a directly uploaded image. I know this is not something which can be done with Media Manager itself. It would rather be a concept of being able not just to extend the standard image field but to extend a king of “remote image” fieldtype the same way. But I think this would have to be in the core, so that every module which extends or uses the standard (direct upload) image field could use this “get an image from Media Manager and apply the module’s magic to it” image field.