robert

Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

7 Neutral

About robert

  • Rank
    Distinguished Member

Contact Methods

  • Website URL
    https://robertweiss.de

Profile Information

  • Gender
    Not Telling
  • Location
    Düsseldorf, Germany

Recent Profile Visitors

1,666 profile views
  1. Hi Adrian, you are absolutely right! As soon as I switch output formatting off, the results are identically. Thanks for the fast clarification
  2. What a coincidence! Just one second after my post, I found this topic and horsts answer helped me as well. Thanks a lot, horst! I still don’t understand why there were differences between command line and browser, but when I add $img->first()->filename, I get identical results (although the maximum file amount in the imagefield was set to 1, btw).
  3. I’m trying to get the filename of a file in an imagefield via command line, but there seems to be a difference between the API access via browser and via command line. When I try the following (reduced case): $img = $pages->get('/')->name_of_imagefield; var_dump($img->filename); var_dump($img->basename); var_dump($img->url); var_dump($img->path); I get these results: Browser (as expected): filename: full path to file including name (e.g. /var/www/public/site/assets/files/1/filename.jpg) basename: only name without path (e.g. filename.jpg) url: webroot-based path to file including name (e.g. /site/assets/files/1/filename.jpg) path: NULL Command Line: filename: NULL basename: NULL url: webroot-based path to file WITHOUT filename (e.g. /site/assets/files/1/) path: full path to file WITHOUT filename (e.g. /var/www/public/site/assets/files/1/) What am I missing? Or is this normal behaviour and I just never noticed before? The website is running Processwire 3.0.94 with PHP 7.0. Thanks a lot for any help!
  4. Hi Henning, I had similar problems with 1&1 and fixed them by installing PW locally, then moving everything to the server (db via phpmyadmin), changing the config.php with the 1&1 db-credentials and finally adding the following line in the config: $config->dbSocket = '/tmp/mysql5.sock'; Not sure where I found it, but worked for me
  5. robert

    @horst: I’m sorry if my comment sounded like an advice or a complete solution, which is definitely wrong. I just wanted to say that it worked for me and it removed the posterization in my images. I got your link on the other thread with the explanation, I obviously missed it before – thanks for the info!
  6. robert

    Hi everyone, I had a similar problem with posterization/banding in darker image areas and found out the same workaround as chrizz (commenting out the gamma correction lines). I’m just guessing, but is it possible that the first gamma correction creates tonal gaps in those areas which can’t be fully reproduced afterwards? Btw: here is a new post which seems to describe the same problem: http://processwire.com/talk/topic/5889-image-quality-problem-on-resize/
  7. robert

    Hi humanafterall, I had a similar problem with the resizing function and posterization in dark image areas, my workaround was to comment out the gamma correction in the Imagesizer.php (lines 247 & 387). I’m not sure what that function is good for, but now everything looks good. There is a similar discussion going on over here.