Jump to content
Pete

ProcessEmailToPage

Recommended Posts

Thanks Charles - glad to hear it is working well for you. 

I have another brand new version for you with a LOT of new features.

  1. You can prevent creation of pages from email addresses with host names that are not in the whitelist - great antispam option
  2. You can limit creation of pages to email addresses that match registered PW users - in this case, the ability to add the page will also be determined by the user's permissions for creating pages on the selected template
  3. You can determine whether the page should be published based on the user's page-publish/edit permissions
  4. You can set up customized email notification messages when a new pages is created, including choosing who they should be sent to.

The config settings should also help to see all the new changes. Please let me know if you find any problems with this new version - quite a bit changed. Also please let me know if you think of improvements to the logic of the way things are set up.

post-985-0-53891100-1419824414_thumb.png

Edited by adrian
Added screenshot
  • Like 3

Share this post


Link to post
Share on other sites

Hi Adrian

Thanks for all your work on this.

I've added you as a collaborator on my repo so I think you might be able to merge changes into the main repo yourself if you like?

I certainly don't see a problem with anything you've added (aside from me not having tried any of the new things out yet :)) so happy for it all to be merged.

  • Like 2

Share this post


Link to post
Share on other sites

Thanks Pete - it's been fun to work on :)

I'll update the Readme to detail the new features and merge all the changes shortly.

Share this post


Link to post
Share on other sites

Feel free to stick your name in with mine in the author attribute on the module too if you haven't already done so.

  • Like 2

Share this post


Link to post
Share on other sites

I'd like to make this work on a shared hosting account, but am not sure if it's possible.

cPanel doesn't allow me to use some characters. 

Directory paths cannot be empty or contain the following characters: \ ? % * : | " > <

Is there a workaround?

Share this post


Link to post
Share on other sites

I'd like to make this work on a shared hosting account, but am not sure if it's possible.

cPanel doesn't allow me to use some characters. 

Is there a workaround?

Sorry, I might be missing something obvious, but can you explain the issue with directory paths and why you can't use this module?

Share this post


Link to post
Share on other sites

The module seems to work fine, but..

I have tested the URL, that needs to be executed by the CRON, in the browser using the locationbar and works like a charm, but I can't set the URL in cPanel.

cPanel doesnt allow me to use the following characters (which are used in the URL): \ ? % * : | " > <

  • Like 1

Share this post


Link to post
Share on other sites

On my CPanel I have things listed as following:

curl -sS "https://yourdomain.com/?hash=0ae6cff16bc1e1ad77c2706acaf0358b2848395g" > /dev/null

This works for me.

  • Like 3

Share this post


Link to post
Share on other sites

Looks like you aren't doing the correct thing here. I am not very experienced with cPanel, but you don't want to be forwarding the email to the PW link. You need to set up a cronjob (from cPanel) using that format that @cstevensjr showed you. That cronjob will then periodically check the email address.

Does that make sense?

  • Like 2

Share this post


Link to post
Share on other sites

Thanks guys, it's working!  :)

@adrian, thanks for putting me on the right track. I was at the wrong one

@cstevensjr, thanks! The cron is running

  • Like 2

Share this post


Link to post
Share on other sites

In the cPanel CRON job documentation:

post-756-0-95988600-1421082388_thumb.png

In the COMMAND text box is where you enter the correct command syntax

EDIT:  You got it!  Welcome to ProcessWire.

  • Like 1

Share this post


Link to post
Share on other sites

I just opened an issue on Github regarding a configuration problem I'm having on a recent installation of this module.  It could well be operator error, on my part, however I just need some expert help and assistance.

Share this post


Link to post
Share on other sites

UPDATE

I was able to figure out where I was going wrong in this module's configuration.

For anyone who may not check Github, listed below is the resolution of the issue I opened there.

Resolution

  cstevensjr commented just now

Ok, I finally figured this out. It was a configuration problem on my webhost (Dreamhost).

My webhost uses mail clusters for outgoing mail. I've never had a problem before where I needed to list the mail cluster name for the "Host" setting. When I finally changed the setting to the mail cluster name, the Flourishlib portion worked without error.

Closing this issue

@adrian, thanks again for your quick follow-up and troubleshooting expertise.

  • Like 1

Share this post


Link to post
Share on other sites

Sorry about this Charles - I'll take a look a little later today or maybe tomorrow - I had a similar issue with CustomUploadNames which actually stole the "Add Category" code from this module. I'll probably just need to make the same changes I made to that, so should be a fairly easy fix.

  • Like 1

Share this post


Link to post
Share on other sites

Actually the issue is not what I thought - it is a recent PW dev problem. I checked a PW 2.6.1 stable site and it works fine. I am not sure what has changed in PW dev to cause this - I will need to investigate further - hopefully I can find some time in the next few days to figure it out.

EDIT: This is the PW commit that breaks things: https://github.com/ryancramerdesign/ProcessWire/commit/fd719abc6ad4dc12792592b6715f986d29af2625

  • Like 1

Share this post


Link to post
Share on other sites

Ok, it should be fixed in the latest version. This fix is only needed for PW 2.6.6+ but I think it should also work fine on older versions.

  • Like 1

Share this post


Link to post
Share on other sites

I love this module, thanks :) .

All working fine but on Cpanel every time I run script is run via cron it generates an output file in the web root folder

e.g. index.html?hash\=d5c0307523750320573253247177dc.9999

Files soon build up when the script is run every 5 min!

Any way to suppress the output file (it contains an html copy of the page being updated)?

Share this post


Link to post
Share on other sites

Hi @dab,

Glad you're finding it useful. I haven't used the module on a shared host with cpanel, so I am not sure whether there is maybe some interaction going on there. I don't think I have ever seen the module itself create these files. Obviously the module responds to: http://pw.dev/?hash=4ba942b72726bbc0fa527c0c3aa69f2bc6817534 but I don't know where that index.html version is coming from.

Any chance there is a caching mechanism at play here. Maybe even ProCache? although I doubt it.

Share this post


Link to post
Share on other sites

Thanks....No ProCache running.

Most odd. I'll try & see if I can find way was causing this.

Share this post


Link to post
Share on other sites

Can't you just suppress the cron task messages by adding "/dev/null 2>&1" to the end of your cron command.

That sends the messages to null which means there aren't any messages.

Perhaps I am missing the point though?

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 eelkenet
      Hi! I've created a small Inputfield module called InputfieldFloatRange which allows you to use an HTML5 <input type="range" ../> slider as an InputField. I needed something like this for a project where the client needs to be able to tweak this value more based on 'a feeling' than just entering a boring old number. Maybe more people can use this so I'm hereby releasing it into the wild. 
      EDIT: You can now install it directly from the Modules directory: http://modules.processwire.com/modules/inputfield-float-range/
       
      What is it?
      The missing range slider Inputfield for Processwire. 
      What does it do?
      This module extends InputfieldFloat and allows you to use HTML5 range sliders for number fields in your templates.
      It includes a visible and editable value field, to override/tweak the value if required.  
      Features
      Min/max values Precision (number of decimals) Optional step value (Read more) Optional manual override of the selected value (will still adhere to the rules above) Configurable rounding of manually entered values (floor, round, ceil, disable) Usage
      Clone / zip repo Install FieldtypeFloatRange, this automatically installs the Inputfield Create new field of type `Float (range)` or convert an existing `Float`, `Integer` or `Text` field. To render the field's value simply echo `$page->field` Demo
      A field with Min=0, Max=1, Step=0.2, Precision=2

      Field with settings Min=0, Max=200, Step=0.25, Precision=2

       
      Todo
      Make the display-field's size configurable (will use the Input Size field setting)  Hopefully become redundant  
      Changelog
      004 (current version)
      - Make rounding of manually entered values configurable (floor, round, ceil or disable)
      - Fix small JS bug when the value-display field was not displayed
      - Update README
      003
      - Code cleanup, add some ModuleInfo data & LICENSE
      - Submit to PW Modules directory (http://modules.processwire.com/modules/inputfield-float-range/)
      002
      - Fix issue where setting the step value to an empty value created problem with validation
      - Make the display-field optional
      001
      - Initial release
       
      Thanks!
       
       
    • By Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      2019-10-18
      2019-08-08
      2019-06-15
      2019-06-02
      2019-05-25
      If you are interested, you can test the current state of development:
      https://github.com/gadgetto/SnipWire
      Please note that the software is not yet intended for use in a production system (alpha version).
      If you like, you can also submit feature requests and suggestions for improvement. I also accept pull requests.
      ---- INITIAL POST FROM 2019-05-25 ----
      I wanted to let you know that I am currently working on a new ProcessWire module that fully integrates the Snipcart Shopping Cart System into ProcessWire. (this is a customer project, so I had to postpone the development of my other module GroupMailer).
      The new module SnipWire offers full integration of the Snipcart Shopping Cart System into ProcessWire.
      Here are some highlights:
      simple setup with (optional) pre-installed templates, product fields, sample products (quasi a complete shop system to get started immediately) store dashboard with all data from the snipcart system (no change to the snipcart dashboard itself required) Integrated REST API for controlling and querying snipcart data webhooks to trigger events from Snipcart (new order, new customer, etc.) multi currency support self-defined/configurable tax rates etc. Development is already well advanced and I plan to release the module in the next 2-3 months.
      I'm not sure yet if this will be a "Pro" module or if it will be made available for free.
      I would be grateful for suggestions and hints!
      (please have a look at the screenshots to get an idea what I'm talking about)
       




    • By Robin S
      Another little admin helper module...
      Template Field Widths
      Adds a "Field widths" field to Edit Template that allows you to quickly set the widths of inputfields in the template.

      Why?
      When setting up a new template or trying out different field layouts I find it a bit slow and tedious to have to open each field individually in a modal just to set the width. This module speeds up the process.
      Installation
      Install the Template Field Widths module.
      Config options
      You can set the default presentation of the "Field widths" field to collapsed or open. Field widths entered into the Template Field Widths inputfield are only applied if the Edit Template form is submitted with the Template Field Widths inputfield in an opened state. "Collapsed" is the recommended setting if you think you might also use core inputs for setting field widths in a template context. You can choose Name or Label as the primary identifier shown for the field. The unchosen alternative will become the title attribute shown on hover. You can choose to show the original field width next to the template context field width.  
      https://github.com/Toutouwai/TemplateFieldWidths
      https://modules.processwire.com/modules/template-field-widths/
    • By adrian
      Tracy Debugger for ProcessWire
      The ultimate “swiss army knife” debugging and development tool for the ProcessWire CMF/CMS

       
      Integrates and extends Nette's Tracy debugging tool and adds 35+ custom tools designed for effective ProcessWire debugging and lightning fast development
      The most comprehensive set of instructions and examples is available at: https://adrianbj.github.io/TracyDebugger
      Modules Directory: http://modules.processwire.com/modules/tracy-debugger/
      Github: https://github.com/adrianbj/TracyDebugger
      A big thanks to @tpr for introducing me to Tracy and for the idea for this module and for significant feedback, testing, and feature suggestions.
×
×
  • Create New...