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 Robin S
      Repeater Images
      Adds options to modify Repeater fields to make them convenient for "page-per-image" usage. Using a page-per-image approach allows for additional fields to be associated with each image, to record things such as photographer, date, license, links, etc.
      When Repeater Images is enabled for a Repeater field the module changes the appearance of the Repeater inputfield to be similar (but not identical) to an Images field. The collapsed view shows a thumbnail for each Repeater item, and items can be expanded for field editing.
      Screencast

      Installation
      Install the Repeater Images module.
      Setup
      Create an image field to use in the Repeater field. Recommended settings for the image field are "Maximum files allowed" set to 1 and "Formatted value" set to "Single item (null if empty)". Create a Repeater field. Add the image field to the Repeater. If you want additional fields in the Repeater create and add these also. Repeater Images configuration
      Tick the "Activate Repeater Images for this Repeater field" checkbox. In the "Image field within Repeater" dropdown select the single image field. You must save the Repeater field settings to see any newly added Image fields in the dropdown. Adjust the image thumbnail height if you want (unlike the core Images field there is no slider to change thumbnail height within Page Edit). Note: the depth option for Repeater fields is not compatible with the Repeater Images module.
      Image uploads feature
      There is a checkbox to activate image uploads. This feature allows users to quickly and easily add images to the Repeater Images field by uploading them to an adjacent "upload" field.
      To use this feature you must add the image field selected in the Repeater Images config to the template of the page containing the Repeater Images field - immediately above or below the Repeater Images field would be a good position.
      It's recommended to set the label for this field in template context to "Upload images" or similar, and set the visibility of the field to "Closed" so that it takes up less room when it's not being used. Note that when you drag images to a closed Images field it will automatically open. You don't need to worry about the "Maximum files allowed" setting because the Repeater Images module overrides this for the upload field.
      New Repeater items will be created from the images uploaded to the upload field when the page is saved. The user can add descriptions and tags to the images while they are still in the upload field and these will be retained in the Repeater items. Images are automatically deleted from the upload field when the page is saved.
      Tips
      The "Use accordion mode?" option in the Repeater field settings is useful for keeping the inputfield compact, with only one image item open for editing at a time. The "Repeater item labels" setting determines what is shown in the thumbnail overlay on hover. Example for an image field named "image": {image.basename} ({image.width}x{image.height})  
      https://github.com/Toutouwai/RepeaterImages
      https://modules.processwire.com/modules/repeater-images/
    • By EyeDentify
      Hello There Guys.

      I am in the process of getting into making my first modules for PW and i had a question for you PHP and PW gurus in here.

      I was wondering how i could use an external library, lets say TwitterOAuth in my PW module.
      Link to library
      https://twitteroauth.com/

      Would the code below be correct or how would i go about this:
      <?PHP namespace ProcessWire; /* load the TwitterOAuth library from my Module folder */ require "twitteroauth/autoload.php"; use Abraham\TwitterOAuth\TwitterOAuth; class EyeTwitter extends WireData,TwitterOAuth implements Module { /* vars */ protected $twConnection; /* extend parent TwitterOAuth contructor $connection = new TwitterOAuth(CONSUMER_KEY, CONSUMER_SECRET, $access_token, $access_token_secret); */ public function myTwitterConnection ($consumer_key, $consumer_secret, $access_token, $access_token_secret) { /* save the connection for use later */ $this->twConnection = TwitterOAuth::__construct($consumer_key, $consumer_secret, $access_token, $access_token_secret); } } ?> Am i on the right trail here or i am barking up the wrong tree?
      I don´t need a complete solution, i just wonder if i am including the external library the right way.
      If not, then give me a few hint´s and i will figure it out.

      Thanks a bunch.

      /EyeDentify
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version (has been tested up to v3.3), add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "http://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


    • By kongondo
      FieldtypeRuntimeMarkup and InputfieldRuntimeMarkup
       
      Modules Directory: http://modules.processwire.com/modules/fieldtype-runtime-markup/
      GitHub: https://github.com/kongondo/FieldtypeRuntimeMarkup
      As of 11 May 2019 ProcessWire versions earlier than 3.x are not supported
      This module allows for custom markup to be dynamically (PHP) generated and output within a page's edit screen (in Admin).
       
      The value for the fieldtype is generated at runtime. No data is saved in the database. The accompanying InputfieldRuntimeMarkup is only used to render/display the markup in the page edit screen.
       
      The field's value is accessible from the ProcessWire API in the frontend like any other field, i.e. it has access to $page and $pages.
       
      The module was commissioned/sponsored by @Valan. Although there's certainly other ways to achieve what this module does, it offers a dynamic and flexible alternative to generating your own markup in a page's edit screen whilst also allowing access to that markup in the frontend. Thanks Valan!
       
      Warning/Consideration
      Although access to ProcessWire's Fields' admin pages is only available to Superusers, this Fieldtype will evaluate and run the custom PHP Code entered and saved in the field's settings (Details tab). Utmost care should therefore be taken in making sure your code does not perform any CRUD operations!! (unless of course that's intentional) The value for this fieldtype is generated at runtime and thus no data is stored in the database. This means that you cannot directly query a RuntimeMarkup field from $pages->find(). Usage and API
       
      Backend
      Enter your custom PHP snippet in the Details tab of your field (it is RECOMMENDED though that you use wireRenderFile() instead. See example below). Your code can be as simple or as complicated as you want as long as in the end you return a value that is not an array or an object or anything other than a string/integer.
       
      FieldtypeRuntimeMarkup has access to $page (the current page being edited/viewed) and $pages. 
       
      A very simple example.
      return 'Hello'; Simple example.
      return $page->title; Simple example with markup.
      return '<h2>' . $page->title . '</h2>'; Another simple example with markup.
      $out = '<h1>hello '; $out .= $page->title; $out .= '</h1>'; return $out; A more advanced example.
      $p = $pages->get('/about-us/')->child('sort=random'); return '<p>' . $p->title . '</p>'; An even more complex example.
      $str =''; if($page->name == 'about-us') { $p = $page->children->last(); $str = "<h2><a href='{$p->url}'>{$p->title}</a></h2>"; } else { $str = "<h2><a href='{$page->url}'>{$page->title}</a></h2>"; } return $str; Rather than type your code directly in the Details tab of the field, it is highly recommended that you placed all your code in an external file and call that file using the core wireRenderFile() method. Taking this approach means you will be able to edit your code in your favourite text editor. It also means you will be able to type more text without having to scroll. Editing the file is also easier than editing the field. To use this approach, simply do:
      return wireRenderFile('name-of-file');// file will be in /site/templates/ If using ProcessWire 3.x, you will need to use namespace as follows:
      return ProcessWire\wireRenderFile('name-of-file'); How to access the value of RuntimeMarkup in the frontend (our field is called 'runtime_markup')
       
      Access the field on the current page (just like any other field)
      echo $page->runtime_markup; Access the field on another page
      echo $pages->get('/about-us/')->runtime_markup; Screenshots
       
      Backend
       

       

       
      Frontend
       

×
×
  • Create New...