horst

You need to select your prefered admin theme from within the guest user.

Hi @Mailte, thats bad. There were a pull request added some time ago, that should make the config page a bit more shiny. Unfortunately, now I recognized that it broke the backwards compatibility. I have tested it with PW 2.5.0, where I get exactly the error you described. With PW 2.5.11+ it runs as expected, without errors! So, you may have 2 options now: my prioritized option is to get the WireMail SMTP version 0.2.5, they are known to work with PW 2.4.1 - 2.5.10 too, (https://github.com/horst-n/WireMailSmtp/tree/532dd94752597a4b2b9f3a2c02ef48b21db77f84) or upgrade your pw version to at least 2.5.11 or 2.6.0. But when upgrading your PW version, please first try it in a copy, not on a live site. With and after PW +2.5.11 there were some changes in images variation naming scheme, that may lead to issues like massive images recreations and a lot of orphaned variation files! Or, you have to wait until I get time to rearange the last commits to also work with prior PW versions than 2.5.11, as it was before. I updated the code of the config screen to make it backwards compatible again. Please download / install the latest module version 0.3.0 to use it with PW 2.5.3 https://github.com/horst-n/WireMailSmtp or http://modules.processwire.com/modules/wire-mail-smtp/

What g**gle want you to do is optimizing your images beyond what GD or imagick or other image libraries do. They want you to optimize *every* *final* image variation with tools like jpegOptim or others. Or to use an image optimization service for your final variation images. And besides the image compression, this analyzing system is not very intelligent! As an example, when you use one single css and one single js file for a whole site, and you use it with aggressive client caching, you will get bad results for a single page url, because gpsi doesn't take into account, that a browser has this already in its cache after retrieving it one time. And another thing is, that I never have seen a bad ranking for fetching g**gle fonts from there servers with every f**ckig page reload or page call. You know why those fonts are not kept in the browser cache, yes? When selfhosting those fonts, every page load after the first one gets the fonts from the browser cache, no extra remote connection is needed!

Hi @theo , curious to know what you get when outputing something like echo "<pre> path {$config->paths->templates} url {$config->urls->templates} ";

If you have an array from wire/config.php like the imageSizerOptions: $config->adminThumbOptions = array( 'width' => 0, // max width of admin thumbnail or 0 for proportional to height (@deprecated, for legacy use) 'height' => 100, // max height of admin thumbnail or 0 for proportional to width (@deprecated, for legacy use) 'gridSize' => 130, // Squared grid size for images (replaces the 'width' and 'height' settings) 'scale' => 1, // admin thumb scale (1=allow hidpi, 0.5=always hidpi, 1.0=force non-hidpi) 'upscaling' => false, 'cropping' => true, 'autoRotation' => true, // automatically correct orientation? 'sharpening' => 'soft', // sharpening: none | soft | medium | strong 'quality' => 90, 'suffix' => '', ); and you then attach a new array to $config->imageSizerOptions with a smaller set of key/value pairs, you wipe out: width, height, gridSize, scale, upscaling, autoRotation, suffix. Besides using PHP function array_merge, you also may use this to override your desired keys without deleting the others: (THE FOLLOWING IS WRONG)

this is really a bad idea! with this, you wibes out all other properties of the imgaeSizerOptions: before your correction, the imageSizerOptions array contain items for sharpening, quality gamma etc. After your correction, the defaultGamma is the only one item. All others are wiped out! PLEASE, repeat all other items with there respective values, or use array_merge() !! $config->imageSizerOptions = array_merge( $config->imageSizerOptions, // all items from wire/config array( // overwrite specific items 'defaultGamma' => -1, 'sharpening' => 'medium' ) ); -------- But in @dreerr s case, I can't think of that this is the issue / solution. Disabling "defaultGamma" is usefull if you gets clippings in dark to black regions. According to what @dreerr describes, my first question is: "How does the original image looks like?" If this already has arctefacts, you ever will get artefacts also in quality 100. Where does the source- or master image comes from? What processes gets it passed through before the upload to PW? Any restrictions on upload? (max size?) Maybe you can provide a link to that image online, or via PM to me?

you need to echo out your desired array key, or object property, depending on what you choosed. You choosed an array for the return, therefore you need to output the key "FNumber" of the array: $result = $page->galleryimages->first()->getExif( array('FNumber') ); // output the value for one key of the returned array echo $result['FNumber']; // if you have choosen the result as object, you would use echo $result->FNumber; This all you can read in the initial post of this thread.

Sorry, now I see that you are using a single value string as $options. This is not possible. Please refer to the examples above: you need to pass an array to the function, also if you want to retrieve a single value: $image->getExif( array('FNumber') );

your url does not contain an image name, it only points to the folder. and the last var_dump should get the EXIf from the single image, not from the image collection!!

var_dump(count($page->galleryimages)); $image = $page->galleryimages->first(); var_dump($image->url); var_dump($image->getExif()); please verify that: your field has at least one image that the image is of type jpeg that it (the original version) contains EXIF-data that it contain an entry FNumber

and what is the outcome? can you try var_dump($page->galleryimages->first()->getExif('FNumber'));

how does your code look like for getting the (first) image from your field and getting the exif information?

the current version is 1.1.15 please update and try again. We have fixed this already.

just to clarify: I have to offer a quote first! It is a 3 languages site with ~ (3x) 100 pages and part of the deal is to transfer the content too. That's why I want to see the mysqldump before. I don't want to change something at this point. I hope they will find / get the FTP credentials, that I can have a look into the configuration file. So, seeing this, (my first joomla admin), I'm very happy to use PW.

please can you describe a bit precise: wich version are you using what are you doing exactly (how do you do it) what is the desired output / behave and what is the real output / behave

Hi, I have a need to get a mysql dump from a joomla site. The owner has admin access to the backend only, no FTP or other. I have looked a bit around but couldn't quickly find something that lets me fetch a mysql dump. Does someone know if this is possible in more or less basic joomla installations, or if it needs a special plugin? Or how to find the db credentials within the admin? I need some content from it to build a new PW site. Thankful for any hint!

Hi, and thanks for notifying about the change. For alif it was thought as an additional security step. But using a special role for this is appropriate too.

There seems to be a little quirks with the different parts. First, a user will submit a from with a filefield. You need to check if there was sent a file, and if yes, get the file from this field. Do you use the GET or POST method with your form submit? Please refer to the PW vars $input->post->{...FIELDNAME...} or $input->get->{...FIELDNAME...}. Once you have your file / filename, you can attach it to the wiremail object. To check your process step by step, you may write some little prooflines into your script, like: $filename = $input->post->.... ; // get the file / filename from your form submission // now debug / check, if all went good for this step var_dump(is_file($filename)); // also possible PHP functions: is_readable($filename) die('DEBUG BREAK AT: ' . __FILE__ . ':' . __LINE__); If this is true, you can delete this debug lines from your script and sent the email with attachment to a testaccount first.

Another question: Is PW a great peace of software? If yes, hmmm, - you know it's build in PHP. In short: there may be some better or less better programming languages regarding to use cases, and yes, there are also some points in PHP that are bad, like in other languages too. But all that doesn't take to much account in comparision with what a developer do with it. So, it depends on the developer to 90% and 10% on the programming language. just my 2 cents

Hi @AndZyk, regarding Cron, please look here: This can handle all kind of PW things within a central cron config.

Ok, I may add a workaround to my own question: I have found out, that, for what ever reason, the largest variation never was fetched from the server !! ?? With my example form above, the largest variation fetched was the 1200x0. Then, with adding a 1801x0 to the list, the 1800x0 was fetched as largest. So, not sure why this behave is. Has anyone else seen this for bg-sets? Besides the workaround, it isn't useful to get the HDs filled up with (regularly) unnessecary large variations.

Maybe that my question is a bit OT. As the new modules version works perfect! My question is related to data-bgset. I want to show an image covering the whole vieport. Therefor I use a div with background image. The css for the div is: position: relative !important; display: block; height: 100vh; background-position: 50% 50%; background-repeat: no-repeat; background-size: cover; My list is defined like: 600x0, 1200x0, 1800x0 Related to the background-size: cover, I believe, I get always the image displayed what is one step to small from the list, because they get stretched by css, to cover the viewport. Can someone tell me how to solve this with MarkupSrcSet?

No, I believe @BitPoet means you should add it as your custom/personal property to $config. Please don't overwrite the imageSizerOptions! // Global image options, different from default imageSizerOptions (!) $config->mySpecialImageOptions = array("upscaling" => true, 'cropping' => "center", "quality" => 90); If you overwrite the ImageSizerOptions with an array that does not include all key->value pairs, somewhere a kitten will die!! Or you do it with array_merge: $config->imageSizerOptions = array_merge($config->imageSizerOptions, array("upscaling" => true, 'cropping' => "center", "quality" => 90)); Then you always increment every key->value you don't want specifically change, (even future unknown ones, thinking on PW-Version-Upgrades!!)

It is hirarchically ordered, highest first: $element->size() options are the highest, overrides all other individual ImageEngine-Settings, override all below them, if you have installed two or more engines, only the setting of the finally invoked engine is used site/config.php => $config->imageSizerOptions wire/config.php => $config->imageSizerOptions and last, but more theoretically, if all above would be missing, the hardcoded defaults of the module-file (php-class) would be used The higher override all lower

Another one: https://processwire.com/talk/topic/11047-best-way-of-organising-imported-data/?tab=comments#comment-104700