Also applies to the 2.1 branch (currently on 2.1.1).

Even if you delete the external blog, the blog entries stay in Moodle and can't even be deleted by the initial moodle admin.
Really would encourage addition of this feature!

I second this feature/requirement. This really should be a control that a user has.

I vote for this as well

+1 for this.
External blogs pulled into the online learning environment is a great feature.
Need this one solved before we can really use it. Thanks!

won't be adding this to old versions of Moodle, will implement it for 2.3dev as it's a new feature/improvement. Hopefully the code I create will allow for back porting though

Carrying over to new sprint.

done for 2.3dev, will cherry pick backwards after peer review

I've only enabled deletion of external blog entries, rather than editing too, this is because the edited articles retain their link to the original (and unedited) article on the external website, and I feel allowing users to edit content that says it comes from an external, reputable, website may allow for the misrepresentation of information, and raises issues of trust and authenticity.

Some comments about this fix.

• Some comments are needed to distinguish the cases here.
• The lines are longer than allowed and should be broken down.
• Does the session key need to be passed with editing/deleting? Perhaps it should be.

In the testing instructions, it would be good to test what happens after an external entry is collected then the feed is re-checked.

In the docs, there is no mention of the potential for editing/deleting blog entries from an external source.

http://docs.moodle.org/22/en/Using_Blogs#External_blogs

There should be a note that says that entries, once imported into Moodle, can be deleted but not edited.

The main moodle.git repository has just been updated (yesterday) with latest weekly modifications. You may wish to rebase your PULL branches to simplify history and avoid any possible merge conflicts. This would also make integrator's life easier next week.

TIA and ciao

Just spoke to Jason about this - it seems this can be easily backported since its quite trivial.

Also just a comment that I I think that the changing in the documentation before the fix has landed is not advisable as it leads our users to be confused (especially if this was going to be master only, that definitely should've stayed out of the 2.2 wiki).

Thanks, this has been integrated now to master, 22 and 21.

Just a trivial note that the coding style rules have recently been refined to says that inline comments should have a space after the //. We also recommend a punctation mark closing the comment. The code checkers will warn about this. See http://docs.moodle.org/dev/Coding_style#Inline_comments

Thank you guys!

Thanks Jason,
Blog entry can be deleted now and is not coming back after running cron.

Jolly good show!

Your changes have made it into the Moodle release - its time to celebrate! I suggest a hot cup of English tea (with milk, no sugar) or a hoppy English ale.

Tally-ho!