Jump to content

horst

PW-Moderators
  • Posts

    4,088
  • Joined

  • Last visited

  • Days Won

    88

Everything posted by horst

  1. @Martijn: I cannot replicate this. I have no errors in the logs and I have no error outputs. Error display is set to strict all. I'm on PW 2.5.11 Which version of WiremailSMTP do you use? Do you have set a smtp- hostname, user and pass? Or do you have left one / some fields empty?
  2. This is on the ToDo already. But we ("we" == "Martijn" in this case) haven't had time to rebuild the UI of the editor. It is still how it was in Thumbnails just with the two selects for quality and sharpening added.
  3. I know from hosts where it comes to timeouts with around 10 images in 30 seconds. So with your host it seems to be 5 images in 60 seconds, what is super lazy processing.??
  4. horst

    Windows IIS

    That's what google says, but don't know if IIS7 is noted somewhere there. IIS is noted.
  5. You should take out the debug code snippets, now after we have solved that path thingy. How many images are in the pipe for processing? around 10 or more?
  6. AH, it says file does not exist!!! So, we have to use path instead of url, I think. // not ->urls $AlphaImageUser = "{$config->urls->assets}images/authorwmk/swmb-{$username}.png"; // but ->paths $AlphaImageUser = "{$config->paths->assets}images/authorwmk/swmb-{$username}.png";
  7. Oh, so does you have differences between your path and the output from realpath: echo "<pre>" . $AlphaImageUser . "\n"; echo realpath($AlphaImageUser) . "\n"; ?? ..., and what does it say here with this tests: echo "<pre>with realpath:\n"; // test with realpath echo (file_exists(realpath($AlphaImageUser)) ? 'file exists' : 'file do NOT exist!') . "\n; echo (is_readable(realpath($AlphaImageUser)) ? 'is readable' : 'UHM, is NOT readable!') . "\n"; // test without realpath echo "\nwithout realpath:\n"; echo (file_exists($AlphaImageUser) ? 'file exists' : 'file do NOT exist!') . "\n; echo (is_readable($AlphaImageUser) ? 'is readable' : 'UHM, is NOT readable!') . "\n"; echo "</pre>";
  8. Ah, sorry. I'm in hurry. Haven't read thoroughly. So, 24 bit photoshop png should be fine. The error is triggered here: https://github.com/horst-n/PageImageManipulator/blob/master/ImageManipulator.class.php#L1651 It is only triggered when the file isn't existing or isn't readable: https://github.com/horst-n/PageImageManipulator/blob/master/ImageManipulator.class.php#L2437 It has nothing todo with the PNG type at this point here. Are you sure the filename is correct? You can test it in your code here before passing it to the pim: echo "<pre>" . $AlphaImageUser . "\n"; echo realpath($AlphaImageUser) . "\n"; echo (is_readable(realpath($AlphaImageUser)) ? 'is readable' : 'UHM, is NOT readable!') . "\n</pre>";
  9. Hey, I think you simply need to respect the scope here in Line 26: $config->urls->assets ... Try it with: wire("config")->urls->assets $AlphaImageUser = wire("config")->urls->assets . "images/authorwmk/swmb-{$username}.png";
  10. Hi Henning, this feature (connecting to other PW installations within one script) is on the Roadmap for 2.6 or 3.0. But for now you should go with Module Webservices, that's how it is done normaly I think. https://processwire.com/talk/topic/1654-pages-web-service-servicepages/
  11. Actually it is displaying pages and they look very well! But there seems to be some more things that need fixes. I get 500 internal server error when try to serve from sitemap to a page like : http://www.davidsongalleries.com/artists/contemporary/sergey-hrapov/ EDIT: a little typo: Kathe Kollwitz should be Käthe Kollwitz, and if it should be 100% perfect, the url part should be changed from kathe-kollwitz-from-many-wounds to kaethe-kollwitz-from-many-wounds. EDIT2: Not sure, but maybe double entries? Konstantin Antiohken <==> Konstantin Antiouhkin
  12. Hi @creativejay, I definitely would go with Hanna codes in RTEs.
  13. @Mike Anthony: you used SwiftMailer with a contactform? Than this is for you: modules/wire-mail-swift-mailer
  14. @PeterDK, I'm not sure if this is really possible nor if it is a good idea, but I want to throw it into the discussion: If you can use symlinks, maybe you can setup two hosts that point to the same directories of wire and site, but have there own index.php and own .htaccess. admin.domain.tld | |--index |--htaccess | |-------------------site-symlink----------| |-------------------wire-symlink--------| | | | | |---------------------site-real | | |---------wire-real | | | | | |-------------------wire-symlink-------------| | |-------------------site-symlink------------------------------------ | |--index |--htaccess | www.doamin.tld
  15. Hey, today a newbie question from me: "Is it possible to get one of those addressboxes with the MapMarker-Field?" I use it the first time and with a single marker only. Would be nice to have directly such a box displayed.
  16. Hey, actually there is no time, even not for thinking in depth about this request. But maybe this suites your needs better: https://processwire.com/talk/topic/8079-imagefocusarea/
  17. I could quickly set a shared host account via its config panel to run under PHP 5.3.28 cgi. The CroppableImage Editor worked, - but I could not test all functions in depth. If you want use it in a none productional site with PHP < 5.4.0, simply change the values in the 3 *.info.json files // from this "requires": "ProcessWire>=2.5.11, PHP>=5.4.0, FieldtypeCroppableImage>=82", // to this "requires": "ProcessWire>=2.5.11, PHP>=5.3.8, FieldtypeCroppableImage>=82", modules/CroppableImage/FieldtypeCroppableImage/FieldtypeCroppableImage.info.json modules/CroppableImage/InputfieldCroppableImage/InputfieldCroppableImage.info.json modules/CroppableImage/ProcessCroppableImage/ProcessCroppableImage.info.json
  18. I can't remember why it was set to PHP >= 5.4.0. (@owzim: can you remember it?) I also have no server with PHP 5.3 at hand. Maybe you (or someone other) can edit the three *.info.json files to point to PHP>=5.3.8 and try if it runs or throws any error? If not it will take a while for me to get ready testing this. But it is noted on my ToDo now.
  19. Hey @sarah_hue, welcome to the forums and thanks for the kind words. The recreation is forced by the optional second param of pimLoad. If you let it out or set it to false it takes the cached variation: $imagewithwatermark = $img->pimLoad('tw'[, false] )-> ... . . PS: viele Grüße in die Narrenhochburg Köln, Tätä!
  20. horst

    Debugging tips

    @adrian, that would be a good PW recipe too!
  21. Hey @Marvin, 1) Please add a Supportboard-Link to this entry in the modules directory. . . 2) Is it right that you do not respect any of the sitewide PW default settings for images? Not those that optionally can be defined especially for ImageManipulator nor those that are defined for the ImageSizer? // from core imageSizer 'autoRotation' 'upscaling' 'cropping' 'quality' 'sharpening' 'defaultGamma' 'useUSM' // for manipulator only 'bgcolor' 'targetFilename' 'outputFormat' . . 3) In the description of Gim you say that the only options that can be specified and set are quality and outputFormat, but Quality seems not to work, I always get the same result in filesize. OutputFormat works partly, means: when I try to create a jpeg and a png from the same image, (what I can do with Pim), it does not create the second file without forcing a recreate! And when I force recreation, it overwrites my first image with the second rendering. This is because it does not reflect the outputFormat in the filename. I use this test code: $image = $page->images->eq(0); $w = intval($image->width / 10 * 2); $h = intval($image->height / 10 * 2); echo "<p>test with defaults<br />"; $gim = $image->gimLoad('gim1')->resize($w, $h)->save(); echo filesize($gim->filename) . ' :: ' . $gim->url . '</p>'; echo "<p>test with outputFormat PNG<br />"; $gim = $image->gimLoad('gim1')->resize($w, $h); $gim = $gim->setOptions(array('outputFormat' => 'png'))->save(); echo filesize($gim->filename) . ' :: ' . $gim->url . '</p>'; echo "<p>test with quality 100<br />"; $gim = $image->gimLoad('gim2')->resize($w, $h); $gim = $gim->setOptions(array('quality' => 100))->save(); echo filesize($gim->filename) . ' :: ' . $gim->url . '</p>'; echo "<p>test with quality 20<br />"; $gim = $image->gimLoad('gim4')->resize($w, $h); $gim = $gim->setOptions(array('quality' => 20))->save(); echo filesize($gim->filename) . ' :: ' . $gim->url . '</p>'; and get this result: test with defaults 21235 :: /site/assets/files/1/pim_gim1_basename_02.jpg test with outputFormat PNG (and not forcing recreation) 21235 :: /site/assets/files/1/pim_gim1_basename_02.jpg or test with outputFormat PNG forcing recreation (look filesize!!) 178060 :: /site/assets/files/1/pim_gim1_basename_02.jpg test with quality 100 21235 :: /site/assets/files/1/pim_gim2_basename_02.jpg test with quality 20 21235 :: /site/assets/files/1/pim_gim4_basename_02.jpg . Also there is no validation done. Not for supported filetypes nor typos, and also not for a valid range for quality. . . 4) Why do you not keep IPTC, what is (sort of) mandatory within PW? At least you should print a big warning at the very top of the announcement for those that rely on this. (because AFAIK it is supported by every other image related part in PW since Version 2.3, or do I miss something?) . . 5) Same with the big warning should be done in regard of sharpening! The lib you implemented does not support any sharpening method! As a sidenote, one of the most timeconsuming image manipulations with GD / PHP is sharpening! . . 6) Also the lib does not support transparency in GIF, it renders them with black background. Detecting the need for AutoRotation is not supported too. . . 7) Ah, - regarding my post about the Imagick adapter I have seen there, this looks a bit like a stillbirth. (https://github.com/Gregwar/Image/pull/65) . . . When first reading your announcement here I was very happy because I have started a few times to rewrite the Pim to make it faster and more robust, but couldn't finish it, (lots of work to do). But now for me it sounds a bit more like a marketing strategy than a real chance for me to get my hands on a better Pim implementation in PW. . . . Besides the above mentioned, here is a list of not supported methods in Gim: getOptions (very limited) setOptions (very limited) getImageInfo (returns nothing) getPimVariations removePimVariations sharpen unsharpMask stepResize watermarkLogo watermarkLogoTiled watermarkText canvas blur pixelate getMemoryImage setMemoryImage . The supported methods are: brightness colorize contrast edgedetect emboss flip grayscale negate rotate sepia smooth . New methods, that are in Gim, but not in Pim: mergePageImage (can be used for watermarking) merge (can be used for watermarking) write (can be used for watermarking) overlayImageStretched (can be used for watermarking) // drawing functions circle ellipse line rectangle roundedRectangle . And those are methods from Gim that could be used to emulate our PW crop and upscaling settings: crop zoomCrop cropResize forceResize scaleResize
  22. Hey @kurbel: I guess you use PW 2.5 stable? If you can upgrade to the dev version all related to this is fixed! To upgrade there is a new module available here: https://processwire.com/talk/topic/7525-module-processwire-core-upgrade/ It works just fine.
  23. If you know the pageid, you only need to get the page: // get the page for that id $internalpage = $wire->pages->get($pageid); // now check if the page could be found if ($internalpage->id != $pageid) return false; // you can also check for the id not 0 if ($internalpage->id == 0) return false; So, assuming your $pageid is right, you will pass the lines above and you should be able to access your images field as usual: $images = $internalpage->images; // lets check if there are images available or if the field in this page is empty, e.g. not uploaded any image to it if (count($images)) { foreach($images as $image) { // do stuff with the images ... } } BTW, welcome to the forums.
  24. No, you need to give it your email account credentials as you do with your favourite local Emailclient. It uses libs that tests and establishes connection to your account at a smtp provider (like gmail for example) and handles over the messages to it. It has nothing to do with your settings in the php.ini. Settings in php.ini are related to the php mail() function only!
  25. @renobird: Save open/close state of sidebar (via cookie).Does this include: save and recreate show / hide the complete sidebar save and recreate the collapsed state of each group (pages, setup, modules, ...) ? This would be awesome!
×
×
  • Create New...