Yes, all of README files now have garbled php code in their README's (http://www.symfony-project.org/plugins/sfDoctrineGuardPlugin).
Is there now a different way that code blocks should be specified? Can we turn off the escaping inside pre tags? Thanks On Jun 24, 1:55 pm, Bicou <[email protected]> wrote: > I think it's related, in php code blocks, the > is escaped : $this- > >article = $this->getRoute()->getObject(); > > On Jun 24, 11:12 am, Christian Schaefer <[email protected]> wrote: > > > > > Oh and it doesn't explain that some of the images are not shown, does > > it? > > > On Jun 24, 10:59 am, Christian Schaefer <[email protected]> wrote: > > > > ah, understood. a pity though for simple things like anchors.. Is > > > there a chance you allow some selected tags? > > > > On Jun 24, 10:56 am, Fabien Potencier <fabien.potenc...@symfony- > > > > project.com> wrote: > > > > On 6/24/10 10:37 AM, Christian Schaefer wrote: > > > > > > Hi all, > > > > > > have a look > > > > > athttp://www.symfony-project.org/plugins/sfImageTransformExtraPlugin/1_... > > > > > It seems totally broken as most images are not shown and all anchors > > > > > are escaped. Yet the same markdown in the dingus works just fine. > > > > > > Can anyone have a look at this please? > > > > > That's because for security reasons, I disabled the possibility to embed > > > > HTML in the Markdown. > > > > > Fabien > > > > > > Cheers > > > > > /Christian -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
