silverstripe-framework: Centered image alignment crashes on save

Hi everyone, I’m the author of mentioned Shortcode library. I’d like to address some of the concerns raised here and in #5535. I’ll link the comments and answer them here:

• https://github.com/silverstripe/silverstripe-framework/issues/5535#issuecomment-219629328 I was also surprised that there are literally no generic shortcode parsers out there, they either copy WordPress regex or implement only a non-extensible set of BBCodes. That was the main reason to provide the proper solution using an actual parser, and that’s Shortcode was born,
• https://github.com/silverstripe/silverstripe-framework/issues/5535#issuecomment-219629544 yes, I’m the only maintainer, but I’m committed to supporting it. This library is quite popular, nears 30k downloads in total and over 100 daily. It is also well-designed, very extensible, and I’m open to any suggestions on how to make it better, on the basis that those improvements serve the shortcode processing problem for which it was created. Also, I guess that that key feature is HTML awareness? I’ll be happy to discuss what you need here, maybe there is something I can do?
• https://github.com/silverstripe/silverstripe-framework/issues/5535#issuecomment-220478558 I agree that this would be a substantial change, but it’s definitely possible to use one of my parsers to extract the shortcodes and then just write ProcessorInterface compliant processor, that’s exactly the reason I made the library so extensible,
• https://github.com/silverstripe/silverstripe-framework/issues/5535#issuecomment-220571935 I consider the current state of Shortcode to be stable, even though there is no 1.0.0 release. As for the <p> tag issue, please see my recent answer https://github.com/thunderer/Shortcode/issues/40#issuecomment-257632082 ,
• https://github.com/silverstripe/silverstripe-framework/issues/5987#issuecomment-256250145 simple replacement is definitely something my library can do, as for the preceding / following text removal, please see my recent comment on the issue: https://github.com/thunderer/Shortcode/issues/40#issuecomment-257632082 ,
• https://github.com/silverstripe/silverstripe-framework/issues/5987#issuecomment-256258404 my recommended way of setting up Shortcode in your project is to wrap the whole logic into the service and treat it as such by exposing only what’s necessary - you pass the input, you get the replaced output. I’d be happy to help make it easier, so please let me know what problems did you encounter. I’d be very grateful for your feedback.

I’d throw my weight behind @thunderer’s package. It can’t be worse than writing our own and there’s nothing stopping us forking it if things go bad with it in the long term (no offence). If that happens we’re just in the same place we are now, maintaining a shortcode parser.

Maybe if @thunderer was happy to recruit some more contributors it could alleviate our worries?