I18n for RhaptosCommunity
The last two weeks, I cleaned up some bugs with the RhaptosCommunity product, and it is now closer to being ready for release:
- removed dependencies on RhaptosCommunity from other products that I had altered
- altered the HTML fields so that they will not accept or display dangerous HTML tags like <script>
- made the similar content link in the search results functional.
- customized the CMFBoard profile to point to my author profiles and the topic form to only accept html.
- altered the install script so that the CommunityFolder instance that is created is called "communities" instead of "Communities" to be consistent with the rest of the site.
- fixed one button that was displayed even if the user didn't have permission to click it
- fixed the newest content portlet so that is displays inside the forum
The next step was to add i18n support to all my page templates. This mostly just involves adding a i18n:translate or i18n:name attrbibute to any html/tal tag that is displayed on the page. For the most part, it went very quick. However, I had a couple cases where the default translation wasn't being passed through correctly. I even tested the example from the tutorial on plone.org and it didn't work! After a long time trying to figure out the reason why it doesn't work, Brent and I finally figured out that you cannot have hyphens in an i18n:name attribute. So, I changed the -'s to _'s and everything worked fine.
Also, as a final test, I created a mockup DSP community based on an example that Doug Jones sent us. It looks pretty useful to me. If you want to check it out, IM me for a link to my Plone instance.
