Pete

ProcessEmailToPage

Recommended Posts

Hi @adrian 

I tried the new version of Flourish and it's the same. I also switched to PHP 7.0.4 and it still does the same. Whereas my improved version works in both versions of PHP.

The problem that Werner and I had isn't to do with PHP 7 or HTTPS vs HTTP rather connecting to the POP3 server using an unsecured connection (Force secure set to off). 

My version fixes the fMailbox.php file while keeping all security settings in place.

 

I've included it for anybody who comes across this same problem.

fMailbox.php

Share this post


Link to post
Share on other sites

Thanks again @RDC - I am wondering if perhaps you'd consider submitting a PR to the Flourish guys - seems like it would be a good change for all their users. Once it is in their repo, I'd be happy to include the updated version in this module.

Share this post


Link to post
Share on other sites

I'll see if I can (flat out at the moment but needed an email image module for Processwire as Ryan's isn't supported in PW 3)

  • Like 1

Share this post


Link to post
Share on other sites

I want to use tags in the pages i create (in addition to categories).

Is there a way to split an email text (for example the subject text) with an hash (#) to save it in a field?

Or is there a better way to do this?

Share this post


Link to post
Share on other sites
2 hours ago, tires said:

Is there a way to split an email text (for example the subject text) with an hash (#) to save it in a field?

I think the only way to send different content from the email to different fields is using the delimiters options. Have you tried to achieve what you want with that? Or am I missing the point? I don't think I really understand the "hash" idea you are talking about.

Share this post


Link to post
Share on other sites

Delimiters are good ... but i think a bit to complicated for inexperienced users.

My idea was to keep it simpler:
If the subject of the email is "My super test email #test #cool #funky", the title of my page should be "My super test email" an the tags should be "test", "cool" and "funky".

 

Share this post


Link to post
Share on other sites
On 9/1/2018 at 11:51 AM, tires said:

Delimiters are good ... but i think a bit to complicated for inexperienced users.

My idea was to keep it simpler:
If the subject of the email is "My super test email #test #cool #funky", the title of my page should be "My super test email" an the tags should be "test", "cool" and "funky".

 

This should be doable, but I guess the problem may be how the tags field stores these. Are you using page reference field for tags, or a select options field, or some other approach? In implementing this I'd want to make sure it worked in as many scenarios as possible.

Although I am not really sure if this module gets much use at all - it seems pretty quiet around here and personally I have never had a use for it (even though I helped extend it quite a bit since Pete's initial development). 

Share this post


Link to post
Share on other sites
5 hours ago, adrian said:

Although I am not really sure if this module gets much use at all - it seems pretty quiet around here and personally I have never had a use for it (even though I helped extend it quite a bit since Pete's initial development). 

I use this module on every website I have built for myself personally and also clients

  • Like 4

Share this post


Link to post
Share on other sites
12 hours ago, adrian said:

I am not really sure if this module gets much use at all - it seems pretty quiet around here

This may also be an indication for modules that work well and fulfil a task perfectly, leaving nothing to be desired. 🙂

  • Like 4

Share this post


Link to post
Share on other sites
41 minutes ago, horst said:

This may also be an indication for modules that work well and fulfil a task perfectly, leaving nothing to be desired. 🙂

That's indeed the case, for me.  As both a Telecommunications Engineer and Web Developer, this module allows me to use emails (from submitted forms or sent directly from someone's mail account) to aid in generating webpages.  Just a few of the many things that I use this module for:

  • Blog Submissions
  • Article For Review/Approval Submissions
  • Form Builder Submissions
  • Status Updates (to already created subject areas)

The fact that you can submit to multiple email addresses allows for multiple uses of this module.

If you can think outside-of-the-box, you would be surprised how useful this module can be.  I'm glad that you extended the original module from @ryan.  When you did, I saw instant usability for this module.

 

  • Like 3

Share this post


Link to post
Share on other sites

Thanks for the feedback @cstevensjr - glad to hear it has served you well, although I must point out that Pete was the one who did all the initial work with this module - I just picked up the torch and added a bunch of new features.

I'll wait to hear back from @tires about how he is storing tags and we'll go from there.

  • Like 2

Share this post


Link to post
Share on other sites

I'am actual setup a usecase - where a customer have to create directly from his smartphone new pages with some kind of marketplace content (second hand agriculture machines) so the easy way to go is telling him - take a picuture go to the share button write a title and a description...tidy up later if you want back in the office...

Using it private for recipies....cooking same procedure i like it very much and out of the box thinking is may default way to think since i'm not so experienced in programming i've to use the tools that i could handle 😉

best regards mr-fan

 

  • Like 1

Share this post


Link to post
Share on other sites
On 9/3/2018 at 7:13 AM, adrian said:

This should be doable, but I guess the problem may be how the tags field stores these. Are you using page reference field for tags, or a select options field, or some other approach? In implementing this I'd want to make sure it worked in as many scenarios as possible. 

You are right. The tags should be saved as a new page via page reference field.
I guess that is the most common way to handle it, right?

Share this post


Link to post
Share on other sites

Hi everyone,

@dab has kindly sponsored support for multi-language subjects and content which I have just added to v1.3.0

Here is my test email content which will hopefully show you how it works.

Subject

English Subject ==#es== Spanish Subject ==#fr==  French Subject

 

Body

English body

==#es==

Spanish body

==#fr==

French body

==sidebar==

Sidebar english

==sidebar==#es==

Sidebar spanish

==sidebar==#fr==

Sidebar french

 

There is also a new "Auto Activate Languages" checkbox that you'll probably want to check in the module config settings.

Please let me know if you have any problems with this new functionality.

Cheers,
Adrian

  • Like 2

Share this post


Link to post
Share on other sites

Also just wanted to mention that when building this ML stuff, I had to setup a new test email address because gmail addresses no longer work with this module. Turns out Outlook (hotmail) ones don't either. I ended up using a Yandex address. In case anyone finds it useful, these are the settings I used:

image.thumb.png.6b0c4b81127139de29cbedbdb9fe5758.png

Hope that helps!

Share this post


Link to post
Share on other sites

@adrian thanks for the work on this!

It's a super module that just got even better!  Hope it's of use to others in its new multi-language support mode.

  • Like 2

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 blad
      Hi guys!
      I just uploaded a module to explore files based on elFinder. By default it will show the "Files" folder.
      Screenshots:

      Video:
       
      To do:
       More options To fix:
       The function of rotating or scaling an image fails  Image editors V 1.01 (view issue)
      Fixed the bug working with the Multi-Language support ( translation of folders ). Fixed the name of elfinder.en  Github:
      https://github.com/LuisSantiago/ProcessElFinder/
      I hope you like it.
    • By BitPoet
      I'm really in love with FormBuilder, but the one thing missing to match all my end users' expectations were repeatable field groups. Think repeaters, in ProcessWire terms. Our primary application of PW is our corporate intranet, so "lines" of fields are quite common in the forms I build. We have all kinds of request forms where the information for a varying number of colleagues needs to be entered (from meal order to flight booking request) and where it is simply impractical to send a form for each, and I don't want to clutter my forms with multiple instances of fields that may only get used ten percent of the time.
      That's why I started to build FormBuilderMultiplier (link to GitHub).
      What it does:
      Adds an option to make a regular Fieldgroup repeatable Lets you limit the number of instances of a Fieldgroup on the form Adds an "Add row" button the form that adds another instance of the Fieldgroup's fields Adds a counter suffix at the end of every affected field's label Stores the entered values just like regular fields Makes the entered values available in preview and email notifications Supports most text based fields, textareas and selects (really, I haven't had enough time to test all the available choices yet) What it doesn't do (yet):
      Support saving to ProcessWire pages (i.e. real Repeaters) I haven't tested all the validation stuff, Date/Time inputs etc. yet, but since I'm utterly swamped with other stuff at work, I didn't want to wait until I have it polished. Any feedback is welcome. There might also be some issues with different output frameworks that I haven't encountered yet. The forms I work with mostly use UIKit.
      Status:
      Still alpha, so test well before using it in the field.
      Known issues:
      When rows are added, the form's iframe needs to be resized, which isn't completely clean yet.
      How it works:
      The Fieldgroup settings are added through regular hooks, as is the logic that adds the necessary field copies for processing the form and displaying previews.
      "Multiplied" field instances are suffixed with _NUM, where NUM is an incremental integer starting from 1. So if you have add two fields named "surname" and "givenname" to a fieldgroup and check the "multiply" checkbox, the form will initially have "surname_1" and "givenname_1" field (I'm still considering changing that to make the risk to shoot oneself into the foot by having a regular "surname_1" field somewhere else in the form less likely).
      When a "row" is added, the first row is cloned through JS and the counter in the fields' IDs, names and "for" attributes as well as the counter in the label are incremented before appending the copies to the Fieldset container in the form.
      To keep backend and frontend in sync, a hidden field named [name of the fieldset]__multiplier_rows is added to the form. Both the backend and the frontend script use this to store and retrieve the number of "rows".
      ToDo:
      Naturally, add the option to store the data in real repeaters when saving to pages. Do a lot of testing (and likely fixing). Make a few things (like the "Add row" button label etc.) configurable in field(set) context. Add a smooth API to retrieve the multiplied values as WireArrays. The mandatory moving screenshot:

    • By MoritzLost
      Hello there,
      I'm working on a tiny textformatter module that searches the text for titles of other pages on your site and creates hyperlinks to them. I'm not sure if something like this exists already, but I haven't found anything in the module directory, so I wrote my own solution 🙂
      It's not properly tested yet and is still missing some functionality I would like to implement, so at the moment it should be considered in BETA. Features include limiting the pages that will get searched by template, and adding a custom CSS class to the generated hyperlinks. As I'm writing this I noticed that it will probably include unpublished and hidden pages at the moment, so yeah ... it's still in development alright 😅
      You can download the module from Github:
      https://github.com/MoritzLost/TextformatterPageTitleLinks
      There's some more information in the readme as well.
      Anyway, let me know what you think! I'm happy about any feedback, possible improvements or ideas on how to improve the module. Cheers.
    • By adrian
      This module provides a way to rapidly generate Page fields and the required templates and pages for use as a drop down select (or any other Page field type).
      This module will let you create a full page field setup in literally a few seconds 
      To use, run Page Field Select Creator from the Setup Menu
      Enter a Field Title, eg: Room Types Select Options - These will become the child pages that will populate the page field select options. There are two different options.
       
      Option 1. TITLE FIELD ONLY - enter one option per line, eg:
       
      Single
      Double
      Suite
       
       
      Option 2. MULTIPLE FIELDS - the first line is used for the field names and the first field must be 'Title'. Subsequent lines are the values for the fields, eg:
       
      Title, Number of Beds, Number of People, Kitchen Facilities
      Single, 1, 1, Fridge Only
      Double, 2, 2, Fridge Only
      Suite, 3, 6, Full Kitchen
        Choose the parent where the page tree of options will be created, eg a hidden "Options" parent page Select a "Deference in API as" option depending on your needs Choose the input field type Check whether "Allow new pages to be created from field?" should be enabled. As an example, if you entered "Room Types" as the field title, you would end up with all of the following automatically created:
      a fully configured page field called: room_types MULTIPLE FIELDS OPTION - 3 additional fields - number_of_beds, number_of_people, kitchen a parent template called: room_types a child template called: room_types_items (with either just a title field, or with the 3 additional fields as well) a parent page called: Room Types a series of child pages named and titled based on the per line entries in the Select Options textarea The templates are configured such that the "room_types_items" child template can only have the main "room_types" template as a parent, and vice versa.

      Then all you have to do is add the newly created page field to any template you want and you're ready to go!
       
      You can grab it from:
       
      Modules directory: http://modules.processwire.com/modules/process-page-field-select-creator/
      Github: https://github.com/adrianbj/ProcessPageFieldSelectCreator
       

    • By bernhard
      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/