Projects

xstandard-for-wordpress

Contributors: iroybot Donate link: http://contactsheet.de/donate.xhtml Tags: wysiwyg, authoring, editor, edit, rich editor, rich text editor, rich formatting, text formatting, css, valid, xhtml, html, tiny, replacement, backend, admin panel, admin cp, xml, xsl XStandard Version included: 2.0.0.0 ... [More] Requires at least: 2.7.1 Tested up to: 2.7.1 Trunk Version: 0.5 Stable Version: -DescriptionIntegrates XStandard Editor into WordPress. XStandard is a standards-compliant, flexible and highly customizable WYSIWYG-solution. It ensures, the that your markup validates against XHTML 1.0 Strict and XHTML 1.1 specifications. Configure your WYSIWYGs on the XStandard Options Page (if you enable this feature, users can customize their WYSIWYG settings in their Profile Page or on a per post basis. By Erik Pöhler. Screenshot News, Info, Updateswill announce stable version here Changelog22/03/2009 - v0.5 added postmeta_field 'edited_with_xstandard' in order not try fixing valid markup. still incomplete alpha. serious browser problems. need more testing. 03/02/2009 - v0.5 mocking up the options page. still an incomplete alpha. 02/24/2009 - v0.5 uploaded new rewrite of the plugin. (yes, from scratch). still an incomplete alpha 02/23/2009 - moved v0.2 to a branch folder - deprecated from wp2.0.x days 02/23/2007 - v0.2 initial release/testing version. seemed to work. TODO and Brainstorminglow priority enhancement: button. for now more stays intact. low priority task: Get your hands on features not yet implemented such as proxy settings, additional HTTP headers normal priority: Intensive testing with random theme stylesheets. low priority: Theming the editor could be a big plus. for example two or three different themes (basically icons, placeholders) normal priority: Make a tutorial on how to use the JS hooks. For example by providing something useful like a microformats plugin-addon, or a more-button. Collect ideas and Feedback from pioneer users. high priority: Make sure the numerous typography plugins like typogrify will still work with XStandard normal priority: manage User and Role specific settings. (I had good experiences with the role manager plugins in the past. However, the downside is that only people with this tool installed are able to fully make use of applying new xstandard privileges to single users, user groups and roles. If I would code a solution for this on my own it would be an hilarious amount of work... high priority: There are many risky scenarios where the inserted content is not what it should be. (verify the encoding. twice. important task.) disabling wpautop makes sense in many ways (performance, making sure valid xhtml doesn't get messed up with all those regex guessing), but what happens with published posts? We need a test here. A flag/meta field or something that tells WordPress if a post has been published with XStandard (thus it IS XHTML and doesn't need that filters that tinkerMCE obviously needs so much) normal priority:Beautify the folder structure. Think this through some more. File based customization (eg. the user xmls or an interface to customize?) low priority: Add Inline Editing feature. (so logged-in users can quickly edit articles on the website) high priority: Bad problem with the folded menu in the admin cp. XStandard behaves like max z-index. Resolvedhigh priority: find out how to save valid xhtml posts in a way, that doesn't make wordpress strip all markup when the plugin is deactivated (and regular post filters apply).(comment: regular post filters should have no problem with valid markup) Run far far away if people report bugs. (comment: no one does. :) pheew. ) [Less]