emails sent to the same page should create comments or append/prepend/replace according to admin config
This feature allows emails that would normally be processed to create page to be sent when the page already exists. For example, a reply to the original email.
This feature will perform a default (configured by admin) action on a page when it already exists.
This feature does not work on blogs. In recent versions of this app there is support for actions on existing blogs using an explicitly declared action (comment, append, prepend). See for command tags for comment, append, prepend. Also see the "Email to This Page..." menu item which uses plus addressing to comment, add attachments, append, prepend to an existing blog.
Create a Support Ticket
adds command tags for actions on existing pages/blogs.
actions for pages:
comment, prepend, append, attachments, child (page)
actions for blog posts:
comment, prepend, append, attachments
We can use this bug to add functionality for adding a comment to an existing blog without using a command tag to specify the action.
This will be done by fully implementing this feature that is shown in the admin tool:
Currently, for emails to existing pages, the default action when none is specified is to replace the content in the existing page.
This change will allow admins to specify the default action for their site. Also, we will probably change the default to "comment" when the admin has not made a choice. Replace is higher impact than comment so is a potentially more disruptive action when a mistake is made by the sender.
In addition, the current default action logic does not consider blogs, only pages. This change will consider both.
In this change we will also want to add an option for an email without an explicit action to be rejected when it is sent to an existing page. The options will probably be:
prepend content to beginning of page or blog post
append content to end of page or blog post
replace page/blog content
create new page or blog post w/ timestamp in title
reject the email
Freshdesk ticket status changed to : Closed
Note added by Brendan in Freshdesk:
OK good news. I created a test setup with permissions for anonymous to create blogs and it worked very nicely. You do have to grant permissions for anonymous in your space. Here is a screenshot....I granted everything but note the arrow for what I think you need:
And for the removal of content......sorry ignore that. It was a question I had from another ticket
Brendan Patterson | firstname.lastname@example.org | www.artemissoftware.net | 720-515-6760
Freshdesk ticket status changed to : Resolved
Freshdesk ticket status changed to : Open