Jump to content
Pete

ProcessEmailToPage

Recommended Posts

Great Module!

But i have problems with the {pagetitle} in the "notify subject" field, even in the latest version.
When i recieve the notify email the word "{pagetitle}" itself is in the subject.
The same shortcode in the Notify Body works fine.

By the way, is there a way to use other shortcodes here and in the Notify Body such as {pagelink}, {author}, {publishdate} and so on?

 

 

 

Share this post


Link to post
Share on other sites
7 minutes ago, tires said:

When i recieve the notify email the word "{pagetitle}" itself is in the subject.

Try the new version just committed.

7 minutes ago, tires said:

By the way, is there a way to use other shortcodes here and in the Notify Body such as {pagelink}, {author}, {publishdate} and so on?

Not currently, but it should be pretty easy to implement - do you feel like having a go at enhancing the replaceShortcodes() method to handle this? PRs greatly appreciated!

Share this post


Link to post
Share on other sites

Sorry for the late answer!

THANK YOU for the reply an debugging of the module!

On 7/2/2019 at 5:51 PM, adrian said:

Not currently, but it should be pretty easy to implement - do you feel like having a go at enhancing the replaceShortcodes() method to handle this? PRs greatly appreciated!

I will take a look  ...

 

Share this post


Link to post
Share on other sites

I got a new problem with the new version.

One of the mails on the server creates a new article each time the mails are downloaded.
Because of a cronjob there are now a bunch of articles with the same content.

How is the way the module looks if there is already an article with this title etc.?
Or is there a way to delete the mails after download?

Any ideas?

Share this post


Link to post
Share on other sites

I just see when i am logged in there is an error message:

Quote

Error: Call to a member function is() on null (line 724 of /abc/xyz/web/site/modules/ProcessEmailToPage/ProcessEmailToPage.module)

This error message was shown because: you are logged in as a Superuser. Error has been logged.

In line 724 in this file there is this code
 

$published = $page->is(Page::statusUnpublished) ? 'unpublished' : 'published'; 

What else can i do to debug?

By the way, these are my module settings:

1942492217_ModulesProcessWire.thumb.png.8c88fef5a4edd58a803584a6a661d0dd.png

Share this post


Link to post
Share on other sites

@tires - that error should be fixed in the latest version - not sure if that helps your issue with deletion of the email / duplicate copies of page creation though.

  • Like 1

Share this post


Link to post
Share on other sites

Ok, it is finally working with the Version 1.3.3!

But there is an interesting bug: if the from email contains a period like "my.mail@email.com" the module don't save the mail as a page!
It takes me a few minutes to find it out.

 

 

Share this post


Link to post
Share on other sites

@tires - could you please investigate where those "period containing" email addresses get ignored? Is the email being read, but not processed, or is it not read at all? Does it help if the "Only Users" checkbox is unchecked?

Share this post


Link to post
Share on other sites

@adrian I can see the "period containing" mails on the mailserver, they being read and deleted with the cronjob. But they don't appear as page.

I tried every setting. It neither work with "whitelist" nor with "only users" ...

 

 

Share this post


Link to post
Share on other sites

@tires - I just tested here with a period containing email address and it worked as expected.

I think you'll need to debug at your end. Start at this line: https://github.com/Notanotherdotcom/ProcessEmailToPage/blob/6b192fc6e01e50217e8be2b0e48c8745824630ed/ProcessEmailToPage.module#L470 and make sure the message is in that array. Then go inside the foreach and figure out what rule in there is preventing the message from creating a new page which happens here: https://github.com/Notanotherdotcom/ProcessEmailToPage/blob/6b192fc6e01e50217e8be2b0e48c8745824630ed/ProcessEmailToPage.module#L522

Sorry, I think Pete is no longer supporting this module and I don't have much time to help out anymore either I'm afraid.

Reality is that the flourish library that this module uses is also abandoned, so this module really needs to be rewritten with an alternate mail library. That said, it still works for me, so you should be able to figure out where the problem is that is affecting you.

Share this post


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

 - I just tested here with a period containing email address and it worked as expected.

This is really strange!
I sent my (exactly same) test mail from the same email provider one from the "non period containing email" without any problems and one from the "period containing email" with the described errors.

I dont know, if i am able to debug the module.
But i will have a look.

Share this post


Link to post
Share on other sites

Ok, i compared the sourcecode of the "period containing" and the "non period containing" emails more closer.

It seemed to be some "X-Spam" infos in the mail head that might be the problem.

I also tried a nother "period containing" mailaddress without any problems.

  • Like 2

Share this post


Link to post
Share on other sites

Still some problems.

Some mails from the same sender are saved as page so are not!

The only difference i can see in the sourcecode of the mail is the "x-spam-status".

This is not saved as page:

X-Spam-Status: No, hits=-6.6 required=9999.0 tests=BAYES_00 autolearn=disabled
	version=3.4.0

This is saved as page:

X-Spam-Status: No, hits=-1.9 required=9999.0 tests=BAYES_20 autolearn=disabled
	version=3.4.0

Strange, isn't it?

Share this post


Link to post
Share on other sites

Little addition for the module.

I wanted to add a link to the saved article in the Notify mail.

So i changed:

211 'notes'=>"Possible shortcodes:\n{editlink} to insert a link to edit the page\n{pagelink} to insert a link to the page\n{pagetitle} for the title of the new page\n{publishstatus} for 'unpublished' or 'published'"),

and added:

723 $text = str_replace('{pagelink}', $page->httpUrl, $text);

 

PS. There are to many "s" in all "Posssible"s in the module ...

Share this post


Link to post
Share on other sites

I'm having problems adding a second category to check for emails & save to pages no PW errors (or php errors).

On "save" no new Email Category is added.

Anyone else encountering difficulties? I'm using ProcessEmailToPage v. 1.3.3, PW 3.0.123 & php PHP 7.2.

Thanks Nick

Share this post


Link to post
Share on other sites

Not sure if this is dead or if anyone is still working on it. I have a problem where emails sent from Outlook only work about 20% of the time. The other 80% the module just leaves sitting on the mail server untouched. I can't seem to find any reason why. If I send the exact same email from a non-outlook client, the module picks it up no problem. Any ideas why this may be the case?

Share this post


Link to post
Share on other sites

@formulate - I think Pete ran out of steam on this years ago, which is when I picked it up, but I haven't actually ever used it myself so my motivation to continue is not really there I'm afraid. The module really needs a complete overhaul and most importantly needs a replacement for the flourish library which is no longer maintained.

Do you feel like investigating alternatives for Flourish and perhaps taking over the module?

Share this post


Link to post
Share on other sites

Rather than take over, I'd probably just do something from scratch. However, I'm extremely short on time at the moment. Heck, I don't even have time to be trying to debug this issue my client is having. Embarrassingly, at the moment I'm just processing his emails by hand as it's faster for me to just manually input his 2 or 3 emails a week than it is to try and fix this thing. Obviously not a long-term solution, but something I can afford to do with my limited time.

Share this post


Link to post
Share on other sites

Hi @formulate - I'm using the module, without any problems, from Outlook and other email clients. So I'm not sure it's anything about Outlook per se. Have you checked what are the restrictions on sending addresses?

  • Like 1

Share this post


Link to post
Share on other sites
On 11/26/2019 at 1:33 AM, MarkE said:

Hi @formulate - I'm using the module, without any problems, from Outlook and other email clients. So I'm not sure it's anything about Outlook per se. Have you checked what are the restrictions on sending addresses?

No restrictions on the address (I've experimented a lot with the module restrictions) and I have it whitelisted in the SPAM filter. It's weird that from that same address, some emails work fine and some don't. I would expect that it would be all or nothing.

At any rate, I may work on switching the module over from the Flourish library to the newer/better/maintained Fetch library.

Another approach I'm toying with is to just have the email address pipe to a script on the server that bootstraps PW's index.php and simply creates the page. No need to mess around with checking an email account, etc.

  • Like 1

Share this post


Link to post
Share on other sites

I got the error

Fehler: Exception: Can’t save page 0: /artikel/: It has an empty 'name' field (in /xyz/wire/core/PagesEditor.php line 424)

#0 /xyz/wire/core/Pages.php(417): ProcessWire\PagesEditor->save(Object(ProcessWire\Page), Array)
#1 /xyz/wire/core/Wire.php(386): ProcessWire\Pages->___save(Object(ProcessWire\Page), Array)
#2 /xyz/wire/core/WireHooks.php(723): ProcessWire\Wire->_callMethod('___save', Array)
#3 /xyz/wire/core/Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessWire\Pages), 'save', Array)
#4 /xyz/wire/core/Page.php(2584): ProcessWire\Wire->__call('save', Array)
#5 /xyz/site/modules/ProcessEmailToPage/ProcessEmailToPage.module(619): ProcessWire\Page->save(NULL)
#6 /xyz/wire/ 

I think it is because i tried to load an email with arabic characters in the subject.

But even after i deleted this mail the error ist displayed ...

Any ideas?
Thanks!

Share this post


Link to post
Share on other sites

@tires - sorry this module really isn't seeing much love these days. Pete is long gone and I have never needed to use it so it's hard for me to continue supporting it, especially given that it really needs a new mail library among other things. To get your site working again, I think you probably just need to delete the email with the arabic characters in the subject that is causing the problem. If that's not available, I think you should be ok.

It probably shouldn't be too hard to fix the bug though either but we'd need to know what $message['headers']['subject'] is returning - actually, dumping $arr just after line 536 would be best. 

  • Like 1

Share this post


Link to post
Share on other sites

Damn it!
It was just a problem with the email account!

I only got access to the mail account with a webmailer and the mail was just flagged as "deleted" but really removed from the server.
Now roundcube deleted it ... and everything is working!

 

  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • 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-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 Process refunds and send customer notifications 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 (alpha version only available via GitHub) 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 d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Robin S
      This module is inspired by and similar to the Template Stubs module. The author of that module has not been active in the PW community for several years now and parts of the code for that module didn't make sense to me, so I decided to create my own module. Auto Template Stubs has only been tested with PhpStorm because that is the IDE that I use.
      Auto Template Stubs
      Automatically creates stub files for templates when fields or fieldgroups are saved.
      Stub files are useful if you are using an IDE (e.g. PhpStorm) that provides code assistance - the stub files let the IDE know what fields exist in each template and what data type each field returns. Depending on your IDE's features you get benefits such as code completion for field names as you type, type inference, inspection, documentation, etc.
      Installation
      Install the Auto Template Stubs module.
      Configuration
      You can change the class name prefix setting in the module config if you like. It's good to use a class name prefix because it reduces the chance that the class name will clash with an existing class name.
      The directory path used to store the stub files is configurable.
      There is a checkbox to manually trigger the regeneration of all stub files if needed.
      Usage
      Add a line near the top of each of your template files to tell your IDE what stub class name to associate with the $page variable within the template file. For example, with the default class name prefix you would add the following line at the top of the home.php template file:
      /** @var tpl_home $page */ Now enjoy code completion, etc, in your IDE.

      Adding data types for non-core Fieldtype modules
      The module includes the data types returned by all the core Fieldtype modules. If you want to add data types returned by one or more non-core Fieldtype modules then you can hook the AutoTemplateStubs::getReturnTypes() method. For example, in /site/ready.php:
      // Add data types for some non-core Fieldtype modules $wire->addHookAfter('AutoTemplateStubs::getReturnTypes', function(HookEvent $event) { $extra_types = [ 'FieldtypeDecimal' => 'string', 'FieldtypeLeafletMapMarker' => 'LeafletMapMarker', 'FieldtypeRepeaterMatrix' => 'RepeaterMatrixPageArray', 'FieldtypeTable' => 'TableRows', ]; $event->return = $event->return + $extra_types; }); Credits
      Inspired by and much credit to the Template Stubs module by mindplay.dk.
       
      https://github.com/Toutouwai/AutoTemplateStubs
      https://modules.processwire.com/modules/auto-template-stubs/
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.60
      Composer: rockett/jumplinks
      ⚠️ NOTICE: 1.5.60 is an important security patch-release for an XSS vulnerability discovered by @phlp. It's HIGHLY RECOMMENDED that all Jumplinks users update to the latest version as soon as possible.
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! 🙂
    • By Robin S
      Add Image URLs
      Allows images/files to be added to Image/File fields by pasting URLs.

      Usage
      Install the Add Image URLs module.
      A "Paste URLs" button will be added to all image and file fields. Use the button to show a textarea where URLs may be pasted, one per line. Images/files are added when the page is saved.
       
      https://github.com/Toutouwai/AddImageUrls
      https://modules.processwire.com/modules/add-image-urls/
×
×
  • Create New...