Version: 2.9.2 Reporter: Bjørn Børresen —
This is an archived bug report. If you are experiencing a similar issue, upgrade to the latest release and if that does not solve the problem, submit a new bug report
Hi, I was given an EE 2.7.3 website developed by someone else that was to be upgraded to 2.9.2. I encountered an issue with the Cron + Cron Email plugins developed by EllisLab.
I’m not sure if these are still supported (?) (can’t find them on ellislab.com anymore at least, although they are still listed on devot-ee), however I thought I’d notify you of the issue anyway.
Basically after upgrade to 2.9.2 the cron still works, but the content of the emails sent out include several random strings in expressionengine comments, like this:
The was able to find out that it was Cron_email who added these strings, since when I just had used cron or the itself without wrapping it in the exp:cron tag these strings did not appear.
On line 124 in pi.cron_email.php I added this line to remove the EE comments:
$message = $this->EE->TMPL->remove_ee_comments($message);
Not a perfect solution of course since these comments might have been EE code that wasn’t parsed properly, but in my case they weren’t.
ExpressionEngine implements Markdown Extra and BBCode. Please see the Markdown Extra docs and the BBCode Wikipedia article for a full reference.
**bold**, __bold__, *italics*, _italics_, ~strike/del~, `code()`
bold, italics, strike/del, code()
Link: [link title](https://example.com)
Image: 
[blockquote]...[/blockquote], [quote]...[/quote], and Markdown style:
> Some quoted text. > > This is all one quote.
[code]...[/code], and you can also specify the language for syntax highlighting, [code=php]...[/code]
GitHub flavored Markdown code fences are also supported:
```
public function decoderRing($str)
{
return str_rot13($str);
}
```