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

What can i do?
The website isn't working for days now ...

 

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

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 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/
    • 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-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 ----
       
×
×
  • Create New...