Using CS 2.1
This is kind of weird and annoying... I had some existing content that I wanted to use as a blog entry. I drag and dropped it into the editor and everything looked great. I previewed it and everything looked great (at least it did in CS 2.0 -- now in CS 2.1 it doesn't anymore). I posted it and . . . whoops! Everything was not great.
This specific issue: the start="n" attribute was removed from the <OL> element in my HTML.
I had an ordered list that ran 1-4, broke for an image or table, and then picked up again at 5-n. But 5 was now rendering as 1. Why, because the start="n" attribute was stripped out.
The attribute was still present in the stored HTML because it shows correctly again when editing. But when previewing and viewing, the attribute is gone from the HTML.
Why is this? This is a bug and needs to be corrected. When writing direct HTML, I expect my HTML to remain intact. If this is not the case, then a warning message should be presented to notify me that certain HTML features will not work (such as the start attribute being stripped from the OL tag).
Greg,
The following post may help:
http://communityserver.org/forums/thread/520837.aspx
Thanks. So if the globalAttributes are the solution -- my request would be to include the start attribute by default in the next service pack or release. Seems silly to not have that attribute enabled.
The second thing is to find out why these config file settings are not accessible via the UI? As an administrator, I would like to be able to make such configuration changes via the UI rather than needing to use a text editor to modify a config file in the file system.
Thoughts?
Well, I can't (and don't) speak for Telligent, but it would seem to require a fairly large UI needed to the settings across these config files. Something similar to the Microsoft Group Policy Editor comes to mind. And it would have to be web-based, given the different hosting arrangements that need to be accommodated.
Using a tool like WinMerge, as several of the Telligent folks have pointed out recently, makes it very easy to manage upgrades without losing any customizations that one has developed for his or her own CS projects/deployments. For me, this is MUCH faster than a GUI solution. Yeah, yeah, I know that I wouldn't be forced to use the GUI, and that having a UI would appeal to a broader number of folks...
Perhaps, someone will generate a mod for this long-term.
In terms of things needed to be controlled by a comprehensive UI, I'm more intent on skinning functionality than this. It will be interesting to see how this platform grows and matures.
One thing I will say, is that as the documentation matures, the 3rd party enhancement options will grow as well.
Just my 2.5 cents.
Copyright© 2008 Telligent Systems Inc. All rights reserved CommunityServer.com • Telligent.com