adrian

2.4 should probably still run on 5.2.17, just not officially supported. http://processwire.com/talk/topic/5543-processwire-24-possible-to-run-on-php-533/?p=54099 Maybe try contacting renobird (from that post) about his setup with 5.2.17. Also, this from Ryan: PS You can always get an older release of PW here: https://github.com/ryancramerdesign/ProcessWire/releases

It really does sound like PDO isn't running on your server. Have you double checked your phpinfo output or done a php -i from the command line and confirmed that you see something like: PDO PDO support => enabled PDO drivers => sqlite, mysql pdo_mysql PDO Driver for MySQL => enabled

I think basic dependency support has already been committed: https://github.com/ryancramerdesign/ProcessWire/issues/359

Did you play with other operators other than "="? Brown != James Brown, so try ~= or %= depending on exactly how you want the matches to work. More info in the intro post: http://processwire.com/talk/topic/1654-module-pages-web-service-servicepages/

From my understanding, the version of FormBuilder that fixes that issue is 0.22, which is available from the forumbuilder forum: http://processwire.com/talk/topic/1844-form-builder-updates-022 That link won't work if you don't have access to that support board. If you don't have access yet, you should PM Ryan and he will set you up. Once you do have access you should post all future support questions to that board as Ryan prioritizes his time to get those answered as quickly as possible. PS Welcome to PW!

Hey Pete - agreed signatures are currently horrible, especially when people insist on embedding images in their signature, rather than writing them in HTML with a linked image, often resulting in every email from that person having the image show up as an attachment depending on the combination of the sending and receiving email client and settings. My biggest beef is Mac Mail's displaying of images/pdfs inline in the body even if they were added as attachments. Just my opinion, but I think Outlook and others got this right, but I am ranting now

Hey - that's what I suggested in post #5 above I just typed it as PageSelectlist accidentally! Anyway, glad you have it working now. EDIT: Looking at that other post, I think I finally understand things. If you are not actually ever changing the value of this field manually, you could also just store the page ID of the article in a simple text field. You might even want to make it a hidden or locked field.

Glad you got this sorted out! Just a thought - you might find: nl2br($page->get($options['markerTitleField']) better if you want to preserve those line breaks in the output.

Ok, this is a really quickly assembled update. It adds an option to determine whether embedded images will be added to the body field of the page or not. This seems to work great but would appreciate you checking it, especially from different devices / email clients. At the moment this setting is site-wide, but it might potentially make more sense to have it for each email address / category. The other change will hopefully fix that ghost image you had, although I haven't been able to replicate it at my end, so haven't really been able to test. Please let me know if it fixes it for you. My forked version

Sorry, I am still quite confused about the use of this field. I think if you could provide some more details of your exact scenario we might be able to better help.

I would suggest changing your input field type (on the page field's Input tab) to PageSelectlist. It is going to be an impossible user experience for someone to scroll down through a select with 23559 items, let alone 293363 items. Another possibility might be to a Page Auto Complete input field type. This is included in the core modules section, but must be installed before it will be available from the Page field's input tab. Try those and let us know how you go.

Nasty space at the end of the URL is breaking it!

Good to know. So that image named "1283" in the images folder is something extra, rather than an image that you emailed that was somehow corrupted then?

Here is a cleaner function based approach to this: http://processwire.com/talk/topic/5397-assigning-fields-to-repeaters-with-the-api/?p=52123

Just to wrap this up, here is a function that should do everything needed to set up a repeater and assign fields to it: http://processwire.com/talk/topic/5397-assigning-fields-to-repeaters-with-the-api/?p=52123

Hey Pete - no problem. Thanks for committing those initial bug fixes. Good point about the email signatures for sure. The issue I have is how Mac Mail seems to embed all attachments. Maybe someone else can enlighten me as to firstly why this is a good idea and how we can use flourish to determine the difference between signature images which should really be html with a linked image, vs an image that was attached to the message. Maybe it's a matter of playing around more with flourish's inline vs related options. I'll look into it more later.

Thanks for the feedback. I may not have time to look into the ios issue today, but will get to it as soon as I can. Could you please let me know the actual filename of that image in the 1283 folder? Regarding the behaviour of images and whether they should automatically end up in the body field or not. My thought was that if they were attached images, they should just end up in the images field and not embedded into the body field, but if they were embedded in the email text (html), then they should be embedded in the body field, just as they were in the email. Perhaps I could add an option to control this behaviour. The complication to all this seems to be that Mac Mail always sends images inline within the message body, which being relatively new to Mac, is still a mystery to me. I think we can end up with something pretty robust here, but it might take some testing with different email clients and some tweaking to get everything always working as expected.

If you need to offer a user a forgot password reset, there is this module included in the core: http://modules.processwire.com/modules/process-forgot-password/ If you need to do it for frontend users, then this post from our fearless leader should get you going: http://processwire.com/talk/topic/1716-integrating-a-member-visitor-login-form/?p=15919

It should work fine the other way, but if you are using the time() function you need to format like so: $newsposts = wire("pages")->find('parent=/news-articles/, $category, template=TUT_news, Datum>'.time().', limit=10'); Note the single quotes and concatenation with periods.

Ok, I have just added support for images that are embedded into the text within an email. These images are now added to the page's images field and then embedded into the body RTE field, just as they appeared in the email. Minimal testing so far, but seems to work great even with multiple images. Would appreciate some testing of the attached version before I submit to Pete. My forked version ProcessEmailToPage.zip

Did you try: Datum>date('Y-m-d')

joe_ma, I think the cleanest option would be to limit posts by date in your initial selector. That saves the resources of getting all the posts and foreach'ing through all of them. Something like this should work for you. $newsposts = wire("pages")->find("parent=/news-articles/, $category, template=TUT_news, Datum>time(), limit=10"); foreach($newsposts as $newspost){ $out .="<hr><div class='clearfix'>"; if($newspost->Artikelbild){ $out .="<a href='{$newspost->Artikelbild->url}' class=''>"; $out .="<img class='align_left' src='{$newspost->Artikelbild->url}'>"; $out .="</a>"; } $out .="<p>{$newspost->Datum}</p>"; $out .="<a href='{$newspost->url}'><h3>{$newspost->title}</h3></a>"; $out .= $newspost->body; $out .="</div>"; } I am not sure if that selector is exactly what you need - I grabbed most of it from the tutorial, just adding in the date check. Also, it will depend on how the date is stored. You might need to change time() to something like date("Y-m-d"). Let us know how you go.

I am curious as to the name of your images field. That error you are getting makes me think you don't have a field called "images". The module currently has the field hardcoded as "images" so clearly that needs to be made flexible so that other fields can be used. Not sure the best approach for this though. If there is only one image field in the selected template, it's easy, but if there is more than one we'd have to either just choose the first, or ask what field to use in the config settings, which might be best. Also, if there is more than one image attached, and the chosen field is set to only store one image, then there is also an issue. Also I see that there isn't anything to determine if the attachment is in fact an image which is something that should also be checked, and if it's not should the file be added to a files field on the page? Anyway, please check that your images field is in fact named "images" and see if that helps. I am curious about nothing showing up in the body of your page though. Do you have a "body" field in the selected template? Sorry, I see that you didn't enter any text in the body of the email, so this is expected. Regardless, I think this is something else that needs to be made configurable - at the moment the body field must be named "body" as this is the hardcoded name. EDIT: I haven't narrowed down why yet, but if I send the email from Mac Mail, no attachments get converted to images, but if I send them from gmail from within the web interface, everything works perfectly - maybe there is some limitation with flourish and its ability to detect attachments in some case, or maybe it is the crazy way Macs attach files ANOTHER UPDATE: I just sent an email with an attached image from MS Outlook and it also works perfectly, so I am beginning to think there really is something amiss with attachments and the Flourish/Mac Mail combination. Can anyone else confirm this with the version of the module attached to my previous message? AND ANOTHER: I have added support for inline attachments and this seems to be helping with Mac Mail. I had also been using this setting: defaults write com.apple.mail DisableInlineAttachmentViewing -bool yes on my Mac, but reversing that (change yes to false), along with the new inline support and images are now being added. The one outstanding problem I can see at the moment is that if a Mac Mail message also has text in it, the image won't work, so test without anything but the image for now if you are using Mac Mail. Turns out this needed "related", not "inline". I have added support for this in the new version attached this morning. One other thing I think might be a nice addition to this module is support for embedding images into the body field if they were embedded inline in the email. I need sleep now, but might look into this tomorrow! My forked version

Here is Ryan's take on the matter: http://processwire.com/talk/topic/4417-password-field-required-compatibility/?p=43615

Just added a new forceSecure option to the config. Also made sure that if port is left blank, that it sends NULL, rather than blank which seems to be a requirement. Also added a fix for the HTML vs text email issue reported by @martind All these will go to another PR for Pete in a few minutes. Please let me know if the attached version works for you now. My forked version