Jump to content

David Karich

  • Content Count

  • Joined

  • Last visited

  • Days Won


David Karich last won the day on February 22 2014

David Karich had the most liked content!

Community Reputation

224 Excellent


About David Karich

  • Rank
    Sr. Member
  • Birthday 06/19/1986

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Remagen, Germany

Recent Profile Visitors

4,595 profile views
  1. Hey Erik, here's a suggestion how you can do it manually, at least for those templates that have an AMP version. But I haven't tested it. Remove the specific template from the "Templates for automatic tracking" configuration and Add this specific template in the "Templates for allowed API tracking" configuration In the non-AMP version of the template, you add the following data atrribute to the body tag, with the ID of the current page which should be tracked. For example: <body data-phc="<?php echo $page->id; ?>"> Now manually add the tracking script for the non-AMP version before the closing body tag. <!-- For debugging use PageHitCounter.js --> <script defer src="<?php echo $config->urls->PageHitCounter; ?>PageHitCounter.min.js"></script> That's it.
  2. Version 1.2.6 as new master version available All information about the changelog and bug fixings in the first post.
  3. @horst Sorry for the later feedback, but here's the summary. PW Version: 3.0.143 (dev, from 28. October 2019) IMagick Image Sizer: 0.0.3 PHP imagick: 3.4.3 PHP: 7.2.x and 7.3.x Otherwise no other image modules activated. I think that problem with PNG8 has occurred since the change in the module from 7.6.2019 or 6.7.2019. However you formatted the comment. I deactivate the ImageSizerEngineIMagick, and GD takes over, I have no problems. In the attachment two test PNGs, one without compression (which works) and one compressed with tinypng.com (this one will change from a transparent background to a black background when resizing). test-PNGs.zip
  4. Thank you, I'm glad it's useful to you and thank you for your donation. 🙂 Unfortunately, cross-copying is not possible because at the point where you initialize the copy, the module does not know the name of the other field. So it can only read the current name of the matrix field and use this name when copying to the target. I'll think about whether you can introduce an option to select the target field before copying. But I think there is a lot of potential for errors when copying. So first of all, unfortunately not possible at the moment. BTW, @ryan, the module has been in checking for the module directory for several months now and has not yet been released. Does this module bother you in the context of a free extension for your ProModule?
  5. I've had this problem for quite some time, even without WebP. Somewhere I think there is a bug in the ImageSizers. This happens with compressed PNGs, which were previously compressed via tinypng.com, for example.
  6. Welcome to the forum 🙂 Maybe this solves your problem. If there are multiple paginations or API calls, you must also set the "start=0" selector so that other page arrays are not paginated. See under "Are there any side effects?".
  7. I can also tell you what bothered her the most, besides the visual component. My customers like to think in folders. They would like to click through a tree and categorize the data into folders. As PW itself is structured. Because the biggest problem here again is laziness itself. If you upload a picture and don't immediately describe and tag it properly, later searching becomes difficult. And my customers are all hectic and have no time for that. 😄
  8. To be fair, the last version I worked with is 011. Of course there have been some changes with the new version, but optically I see some deficits as well. Apropos: I never received a download link for the update to 012 by mail. Or do I have to buy a new license?
  9. I can only speak for myself. But I feel the same way. I bought the Media Manager, but never used it. Once I used it in a customer project, I had feedback from the customers that the visualization and usability was not good for them. Personally, I'm also a little bothered by that. Why have I never submitted this as a suggestion for improvement? You know: laziness. I always had the hope that others would do it and that there would be an update at some point. 😄
  10. @lokomotivan @Sergio I have now experimented with many options to solve this problem. However, there is only one way, which covers both behaviors. If you don't want segments to be counted, just enable the option as the behavior is current. But if segments are to be counted as well, the segments MUST be defined in the template configuration. For dynamic segments with RegEx. For this I have inserted a passage in the readme with the link to the PW help. There is currently no other option. The problem is that the Page Hit Counter hooked into the PageNotFound process (But I also tried PageRender, etc.). If URL segments are allowed but not defined, a 404 is never triggered from Processwire. This means that the Page Hit Counter cannot be called. For the tracking of segments, so simply define the segments. 🙂 I also released an update with version 1.2.5, which improves the behavior when tracking 404 errors. All infos and download as always in the first post.
  11. Okay, thanks for the report. I'll take a look next week. Probably going to be hard to combine.
  12. Right, I haven't tested it yet. Can you send me your sample configuration? Or did you just activate the option without defining segments?
  13. PageHitCounter Version 1.2.4 Thanks to @wbmnfktr for reporting the issues. And thanks to @Sergio for the corrections. Both issues have been fixed in version 1.2.4 and the corrections have been applied. Changelog as always updated in the first post. Explanations of the bugs below. The functionality has always been and is correct. The module sends the data to a fictitious endpoint of the current page. Then the module hooked in before a 404 is triggered and writes the data. The problem here was that the module "Jumplinks" had a lower priority than PageHitCounter. Therefore the request was logged as 404, because jumplinks were executed earlier. Now fixed, PageHits are not logged as 404, regular 404s will be. Here was the problem that system templates or pages are excluded in the normal search, without the selector "include=all". This is now included by default. Oh, my gosh, there were a lot of typos in there. So if you have a lot on your mind what you're going to code next, you don't look at the comments. Anyway, many thanks for the corrections! And by the way, I'd love to. Take the code and build something new out of it! 🙂
  14. Hey @ryan, great update! I wonder if the new CacheRender function can also be used for repeaters or repeater matrix items? Like this: foreach($page->repeater_field as $item) { echo $cache->renderFile($item->render(), WireCache::expireSave); } It would be great, especially with a lot of repeater items and outsourced render files the rendering can take a few seconds.
  15. Hey @bartelsmedia, if you mean that you want to copy single items and you use the ProField repeater matrix, I wrote a module for it.
  • Create New...