Jump to content
Pete

ProcessEmailToPage

Recommended Posts

Yes, I've tried it without ==blog== written in also hoping it would just write the the body field but nothing. It's very odd, it successfully brings the title across. And as the title is coming across it would make sense that the connection to the mail server is successful. The mail server is on a separate box but connection appears to succeed.

I did have the module stored in the root of the modules directory, but since then I've uninstalled the module, moved the files to /site/modules/ProcessEmailToPage and reinstalled.

Is there anything else I can try as I really like the idea of the module.

had the same issue. it works if you make following change in ProcessEmailToPage.php on line 271:

//$message['html'] = str_replace(' ', '', $message['html']);
// change to
$message['html'] = str_replace(' ', '', $message['text']);
  • Like 1

Share this post


Link to post
Share on other sites

had the same issue. it works if you make following change in ProcessEmailToPage.php on line 271:

//$message['html'] = str_replace(' ', '', $message['html']);
// change to
$message['html'] = str_replace(' ', '', $message['text']);

Bingo! Yes it does indeed. Thank you. I'm assuming this is because my email was encoded as plain text and not html

Share this post


Link to post
Share on other sites

Hi Pete,

Just playing with this module for the first time - looks fantastic - thank you.

Just a couple of things:

  1. there are lots of undefined variable and undefined index notices on the module config page that would be nice to have cleaned up.
     
  2. You still have "live" in the js file. I like the approach that Wanze took with live vs on in the batcher module depending on the version of jquery.
     
  3. Also, the "Add another category" button seems to be missing - I am guessing this is a class issue with Ryan's new default admin theme that I am testing it with.

Thanks a lot for looking into these.

Share this post


Link to post
Share on other sites

is this great module working ok with the latest dev version 2.3.11 with default admin-theme?

the problem i see is, that on module-admin page following fields can`t get saved: "publishDefault":"","emailAddress":"","emailCategory":0,"emailTemplate":"","categoryData":""

Share this post


Link to post
Share on other sites

ok, for my case it was possible to fix it by adding the categoryData array manually to the modules json via mysql. something like

[{\"emailAddress\":\"my@me.com\",\"emailCategory\":\"1013\",\"emailTemplate\":\"46\"}]
  • Like 1

Share this post


Link to post
Share on other sites

Thanks for this great module, pete.

Unfortunately i've got some problems with the setup.

In my testenviroment ( pw 2.4 ) there is no possibility to save email categories. The button "add new category" simply lacks.

Could you give me any advice, what i supposed to do.

Thanks a lot!

Share this post


Link to post
Share on other sites

I have attached a revised version of the module. I know Pete is pretty busy with other things at the moment, so I thought I'd try to help out.

I haven't tested this thoroughly, but I think it should take care of things. It also includes a few other fixes, like adding delete buttons for each category and also fixing a bunch of PHP warnings.

If you could test and let me know if everything is working fine and then I'll submit a pull request for Pete.

My forked version

  • Like 2

Share this post


Link to post
Share on other sites

Thanks adrian,

now the button is visible. I can setup an email-categorie but now a server error occurs, when i´m calling the Cron-Job url

Error: Exception: There was an error connecting to the server (in /kunden/...xxx....site/modules/ProcessEmailToPage/flourishlib/fMailbox.php line 981)

I´ve tried serveral email-server setup combinations without any success ( imap/pop3 over secure or unsecured ports - 143 or 995 ).

Are there anny known fixes or functioning setups?

Share this post


Link to post
Share on other sites

Glad that sorted out the category adding issue. I'll submit that pull request to Pete.

As for the server connection issue - I am really not sure, but I don't think it is related to this module. Perhaps there are some issues with the Flourish library (included in this module) and your pop/imap server, or a firewall issue.

Maybe someone who has been using the module more might have a better idea.

Share this post


Link to post
Share on other sites

Ok, I decided to do some testing at my end on the connection issue. I was trying with a gmail account using imap and found I needed to force a secure connection:

http://flourishlib.com/docs/fMailbox

It seems to me like this module should have an config option to define this true/false, but for the moment I just changed this line in the .module file from:

$mailbox = new fMailbox($this->emailType, $this->emailHost, $category->emailAddress, $this->emailPassword, $this->emailPort);

to:

$mailbox = new fMailbox($this->emailType, $this->emailHost, $category->emailAddress, $this->emailPassword, NULL, TRUE);

I was having connection or username/password issues until I made this change, but now it works perfectly and pages are created as expected.

Can you let me know if that works for you and if it does I'll add a config setting for it and add that to the pull request to Pete.

Share this post


Link to post
Share on other sites

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

  • Like 3

Share this post


Link to post
Share on other sites

adrian - sorry for my delayed answer. the time delay...i had to sleep ;-)

great job, thank you - i think it seems to work now. but i have to continue testing, because there is still an error occurring after the cron-call:

Error: Call to a member function add() on a non-object (line 345 of /kunden/.../pw/site/modules/ProcessEmailToPage/ProcessEmailToPage.module)

i think the reason for this could be an incorrect setup of the template ( missing/wrong fields ?! ).

my email contains only the subject and a jpg-file. after the cron-call the jpg has been downloaded in pw-folder ( root ). from the subject the module builds a child of the category i´ve chosen in the modules - setup ( as it should, i think ). but although i added an image field to the template, the image won´t appear in the "category". there is only the title ( email-subject ).

Share this post


Link to post
Share on other sites

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

Edited by adrian
  • Like 3

Share this post


Link to post
Share on other sites

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

  • Like 4

Share this post


Link to post
Share on other sites

great job, adrian!

i´ve tested it with an attached file and as an embedded image. both works ( tested with outlook for mac and iPhone ).

but let me know your thoughts about embedding the image into the body. in my opinion ( when the image was sent embedded ) the image has to be treated separately ( over the field images e.g. ), then the developer can decide what happens with the image in the FE.

what do you think?

Another question: when the mail was sent over iphone there is same strange behaviour with the folder ( assets/files/1283/ ) the image is saved in.

you can see it in the attaced pic.post-2037-0-81347800-1393311019_thumb.pn

Share this post


Link to post
Share on other sites

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.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks for all the updates adrian - I've commited the latest updates on Github and am looking forward to your latest addition for embedded images.

I wonder if it might be worth making the embedded images feature optional though? I'm thinking of a case where this could be used in a company where people have images in their email signatures and these would come through as well - just a thought.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

Adrian.

There´re two images saved in this folder 1283. One named foto.jpg and one thumb named foto.0x100.jpg

Share this post


Link to post
Share on other sites

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?

Share this post


Link to post
Share on other sites

no - there was only one foto submitted. that "image" is no image. i think it´s some kind of waste due to the email-sending process ;-)

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

Cheers adrian - I'll check it out later unless someone beats me to it.

The problem I found is that even just between Thunderbird and Outlook signatures are treated a bit differently and there's no code in the source of the email to say when a signature starts in an email unfortunately. I honestly don't think that until someone big enough like Google (joining forces with Microsoft and possibly supermom) redesigns how emails should work from the ground up we'll ever see a satisfactory standard for handling email signatures :)

  • Like 1

Share this post


Link to post
Share on other sites

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 :)

Share this post


Link to post
Share on other sites

First thank you very much for this!

Read the whole treat....may i've missed it.

get a connection error for wrong PW and Username....

All settings are done so far - where i have to set the username? this one is missing to set since it is not the emailadress it is like PW: mypass USER: webxxxp1

regards mr-fan

***Realy great module if it works - it would complete/extend my Recipe HTML App for my wife to collect there cooking power digital ;)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By bernhard
      #######################
      Please use the new RockFinder2
      #######################
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://github.com/BernhardBaumrock/RockFinder
       
      Changelog
      180817, v1.0.6, support for joining multiple finders 180810, v1.0.5, basic support for options fields 180528, v1.0.4, add custom select statement option 180516, change sql query method, bump version to 1.0.0 180515, multilang bugfix 180513, beta release <180513, preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • By MoritzLost
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) [Module directory pending approval] Module configuration

    • By MoritzLost
      Process Cache Control
      This module provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Clear the ProCache page render cache (if your site is using ProCache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Plans for improvements
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
×
×
  • Create New...