horst

http://processwire.com/talk/topic/5742-showing-field-name-on-label-hover-not-working/

... imagevedette->size(140, 85) // integer, not string with px

Oh, if it isn't in the docs or when I cannot find it, I look into the code: https://github.com/ryancramerdesign/ProcessWire/blob/master/wire/core/WireUpload.php#L85 using the browsers "find function" searching for "maxFiles" point me quickly to the interesting parts. So, best would be to have it in the docs, but to look at the code is better than nothing

@Zahari: nice video, nice car. Maybe you find this interesting for some stills in your videos: http://www.photofilmstrip.org/1-1-Home.html I have used it here on this old (and private) site where a 6 year old child want to present his new built time machine. (the video is the sepia one)

Hi SwimToWin, don't know the answer but have found this in Wishlist: http://processwire.com/talk/topic/394-default-field-value/ EDIT: in this thread are a good discussion about the pro and cons of default values (redundant data and more) http://processwire.com/talk/topic/1593-how-can-i-specify-default-value-for-certain-input-field/ --- BTW, the forum search isn't very good, better you use google with site:processwire.com or site:processwire.com/talk plus your search terms https://www.google.de/search?q=site:processwire.com/talk+field+default+value

Get Lucky! https://www.youtube.com/watch?v=Wf68FTYoGKQ#t=134 and: https://soundcloud.com/johnlemke/01-walizka PS: How can I embedd a youtube video directly here in the post? (what BBcode)

updated to version 0.0.7 Added a new flag that tells the send() method to make usage of the new logging methods for handling large amounts of recipients by using permanent storage across multiple script calls: useSentLog( true | false ) Tells the send()-method to make usage of the SentLog-methods! sentLogReset() It starts a new LogSession - Best usage would be interactively once when setting up a new Newsletter. sentLogGet() is called automaticly by the send() method - returns an array containing all previously used emailaddresses sentLogAdd($emailaddress) is called automaticly by the send() method - stores each successfully sent emailaddress into the provided log This is intended to use within third party modules for newsletter systems. All three sentLog methods are made hookable, so, e.g. if you don't want log into files you may provide your own storage, or add additional functionality here. The usage is really simple, I think. When starting a new Newsletter Session, you once have to call wireMail()->sentLogReset() to clear any previously stored content in the log. This best should be done manually / interactively I think. After that you only have to set the useSentLog flag to true, e.g by passing an options array into the procedural function call $options = array( 'sendBulk' => true, 'useSentLog' => true ); $numSent = wireMail($to, $from, $textBody, $options); or in object-oriented style like this $numSent = wireMail()->sendBulk(true)->useSentLog(true)->to($to)->from($from)->body($textBody)->send(); That's all. Now you can call your newsletter sending script multiple times (for example bind to lazy cron) and no recipient get lost nor will receive multiple messages. No more worries about script timeouts or other interruptions, just call your script in regular intervals, but ensure that only one instance is running at the time and not multiple in parallel. It would not mess up the logfile because it uses filelocking, but you may get trouble with your SMTP provider if you stress the server. PS: @Nico: want to test it in the near future?

Yes it is. I think with Ryan's changes given to all email-related stuff it is much easier as of it was as we have talked about it. If I remember right, you call only at one point in your code php's mail function. This part maybe get reorganized depending of if it is called a single time (then it is just fine to pass all recipients into wireMail at this point) or if it is within a loop (called multiple times), than you have to change this. You have to pass $options array('sendBulk'=>true) with the wireMail($to, $from, $subject, $textBody, $options); You need to update the wire folder to 2.4.1 (the current dev branch)! EDIT: There is only rare support built in for bulk mail sending, at least when focusing on robustness and comfortable handling of large amounts. Actually there is only a check in it that skips duplicate emailaddress entries. Actually it is needed that the script runs within one request from start to end. If it gets interrupted somehow you end up in a mess. I think it is fine to use it with small amounts of recipients actually (0-200). Oh, - while writing here I got an idea how to implement a simple hookable feedback for that. I will try this and add it to the module if it comes out functional. EDIT2: added! see next post

Hi, I think you need to save the field after calling setMaxFiles.

These three are valid points. But it would depend on if the SQL-syntax of SQLite covers all of what is used in PW with MySQL. I'm not familiar with this and don't know it, neither what PW needs to use nor if this is supported by SQLite.

Hhm, sorry! With the 0.0.5 I have added a configuration option that lets you choose when an optional MailSignature should be send, but have left a boolean true somewhere in the code that overrides always these setting. Have corrected this now and committed the v 0.0.6 to GitHub. (ZIP)

I have updated the class to version 0.0.5 and also have edited the first post of this thread (added some short examples and a list of available options/methods). Now per default the module sends multiple messages in a loop, (one for each TO-recipient) like the base class do. Additionaly you can call sendBulk to send larger amount of messages at once in an optimized manner, - or you can call sendSingle to set the module to allow only one TO-recipient but additionally CC-recipients. More information are now in the first post here.

Thanks for the coffee and the well formed and corrected code!

Yes, same with me! As a sitenote, if you like a post here in the forums (any post, not only that in your threads) you can show that by clicking the [like this] button. This is a forums internal system, not fac*bo*k. There is no harm to use it (I remember that I first realized this after 4 weeks posting and reading here)

@teppo: I think logging is mandatory, even if you throw an exception. Also doing an automated fallback from SMTP to php-mail, without the users knowing isn't good in my opinion. Per default I would raise an error (and log it), but would give a configuration setting under advanced (or something) where the user have the possibility to enable that useful behave. If he check that option, _he_ has done so and not _you_, means he has at least be informed about that behave one times. I'm a big fan of (automated) corrections for the user with missconfigurations, but with emails are a million possibilities given. Maybe on a company site they must use SMTP through a special company server to send company-internal messages, it could be that there are very restrictive settings and a mail from php-mail gets blocked and never reaching the recipients. (Sure, a rare case, but may be possible).

Hi Bbeer, you can try the sharpening option values: $options = array( 'cropping' => 'center', 'sharpening' => 'medium' // none | soft | medium | strong ); You may also check your default setting in the site/config.php file: $config->imageSizerOptions = array( 'upscaling' => true, // upscale if necessary to reach target size? 'cropping' => true, // crop if necessary to reach target size? 'autoRotation' => true, // automatically correct orientation? 'sharpening' => 'soft', // sharpening: none | soft | medium | strong 'quality' => 90, // quality: 1-100 where higher is better but bigger ); EDIT: if you want to test out different settings, remember to use $thumb->removeVariations() before creating the new thumb.

Hi Zahari, $yourRegularLimit = 10; $cur = $input->pageNum; $max = intval($pages->find("$yourSelector, limit=2")->getTotal() / $yourRegularLimit); // limit = 2 so it is fast and uses less memory! $next = $cur<$max ? $cur + 1 : false; $prev = $cur>1 ? $cur - 1 : false; echo '<link rel="canonical" href="http://site.com/parent/page' . $cur . '/" />'; if(false!==$prev) echo '<link rel="prev" href="http://site.com/parent/page' . $prev . '/" />'; if(false!==$next) echo '<link rel="next" href="http://site.com/parent/page' . $next . '/" />'; Not tested, just to ge you started,

This sounds a bit shizophren to me: clients want to have a powerful and great website but are not willing to pay 10$ per month for a good working shared host? This is similar to people that buy a big windows machine for 2.000+ with viodeoadapter(s) that cost 500 per unit. Buy games that cost (I don't know) but want to save 29,95 for a commercial Antivirus-App. --- And also with this sluggish shared hosts you will run into other serious problems like not enough memory for php (when it comes to image manipulation), very restrictive settings or using a not well configured apache with php as fastcgi (wath is in fact the opposite of fast), etc. etc. It doesn't depend on the DB alone, so what will be next that would be great to build into PW to _help_ the clients save 5$ per month?

what (default) settings have you used for upscaling and cropping when called $img->size(200,100) ? (ich frage hier auch noch mal nach falls Du die Email nicht siehst. skype nutze / habe ich nicht) EDIT 1: I got the mail EDIT 2: issue seems to be solved! (PR will follow)

You can traverse the "parent" property of the found page of type category | subcategory | file until you find a page that has a template file. Here is some pseudo code: while($page->template->filename == "") { $page = $page->parent; } I haven't tested this and I'm not sure if this is working. It is meant as starting point.

You may send a PullRequest on Github ( https://github.com/apeisa/Thumbnails )

Yes have read it in SwiftMailer-Thread before. I will update the module after posting this. Also have allready downloaded a fresh wire folder from Github. Lazyness! If using the object->style (not the procedural function call), there is no need to specify it when a default sender is set in config settings. But it could be overwritten by the $mail->from. Maybe I should make it an optional setting, not a required one. I have thought of a setting that prevents overwriting settings from the config screen. Default Sender is the only one valid. Recipients could be a whitelist (currently a textarea under tab advanced) and a checkbox to include emailaddresses from PW users or not. If a security restriction like this is implemented and checked, mails only get send to recipients from the valid_recipients list. Is this a useful feature? This is used when connecting to the SMTP-Server. You find it as the first entry in the Received header of every received mail. For example my local test account is called pw4.kawobi.local, this is what the headers look: Return-Path: <xxxx@xxxxxxx.xx> X-Original-To: xxxx@xxxxxxx.xx Received: from pw4.kawobi.local (dslb-084-099-066-105.t-online [84.99.66.105]) by xyz1234.smtpserver.com (Postfix) with ESMTPSA id 5EDBC2C004E6 for <xxxx@xxxxxxx.xx>; Mon, 3 Mar 2014 19:00:10 +0100 (CET) To: Peter Mueller <xxxx@xxxxxxx.xx> Subject: WireMailSmtp Test MultipartAlternative As far as I know, this is common usage, but with most clients you cannot influence the chosen name. EDIT: Module is updated to v0.0.4, look into the first post please.

Ryan, this is awesome! Many thanks for this magical email handling

Hi hajo, per default new pages have a status unpublished. You can edit them multiple times and still save them as unpublished. You should have a [ save + keep unpublished ] button two times (top and bottom) when first editing a page and a [ publish ] button only one time at the bottom. If this is not enough for your needs, I think you have to create a few lines of code that hook into an event when a new page is created and do this setting there.

it depends on what you want to do with the installation in new.mydomain.com If you drop them after successfully copied over, there is no need for transferring the DB. If you want keep the new.mydomain.com for future testings, you should not use the same DB for both. Then you should copy your DB and modify your test-domain to use that insteed. Just my thoughts,