Yeah, I agree and I think Richard was asking about the same thing. The change would have to come from feature request. More requests, the sooner we see the change in the next patch.
Sent from my iPhone On Nov 1, 2012, at 11:47 AM, Chris Jamieson <[email protected]> wrote: > That's really interesting Jian, thanks for the maths, makes sense. > > We usually user attribute elements to get the alt text for an image too, I > guess that has a similar performance hit on the DB. Our performance is > pretty bad here, so this may be some of the reason why. > > Still seems a little odd to have to specify the '/' as a 'supplement' instead > of just having a switch to allow Reddot to output xHTML tags as standard. > > Cheers! > > > On 1 November 2012 13:34, Jian Huang <[email protected]> wrote: > Richard, good point. Usually, this should be done as best practice during > initial implementation. For older projects that need this to be applied > retroactively, I did write a plugin that goes like this: > > For each content class in all content classes > for each image placeholder > append / to end of supplement field > > > Chris, if the stf_alt is used for the title attribute, then your method is > the best. If stf_alt is used for the alt attribute, then it is better to use > the alt that already come with the image placeholder. Here is the > performance math behind it: > > Each placeholder in a page instance of a content class is represented as a > table row. > > 100 page instances of a content class with just image placeholder, 100 rows > 100 page instances of a content class with image holder AND standard field, > 200 rows > > That's 100% more database space needed. More rows = slow data search and > retrieval speed = slower publish or page view in SmartEdit and page preview = > longer locks = less concurrent user per system allowed. > > > On Thursday, November 1, 2012 4:26:03 AM UTC-4, ChrisJ wrote: > We never use full image placeholders in our templates but write our own img > tags (in xhtml) and only insert the path and filename into the src attribute. > > Sent from my mobile, please excuse typos & brevity. > > On 1 Nov 2012 01:34, "Richard Hauer" <[email protected]> wrote: > Hey Jian… > > > > Is there a way to alter the “default” value for the “supplement” so that it > goes everywhere? > > Not too cute if you have to do that for dozens/hundreds of image placeholders > across your system … > > > > Regards, > > Richard Hauer > > > > From: [email protected] [mailto:[email protected]] On > Behalf Of Jian Huang > > > Sent: Thursday, 1 November 2012 7:14 AM > To: [email protected] > Cc: [email protected] > > Subject: Re: xhtml compliant image tags and embedded styles > > > Edit image placeholder, under supplement field, enter / > > > > EASY > > Sent from my iPhone > > > On Oct 31, 2012, at 3:36 PM, Kosi <[email protected]> wrote: > > I can remember that there was a possibility (earlier) to do something like > > > > <%img%><img src="" /> > > > > Opentetxt should the Render the Imagetag with the information if the image > Variable. I do not know if this is still working, because we are always using > the tag like <img src="<%img%>" alt="sf_alt" /> and only using Filename for > the Image-Vatriable. > > > > Kind Regards, > > Am Montag, 29. Oktober 2012 15:26:53 UTC+1 schrieb Richard Hauer (5 Limes): > > I can’t remember whether it’s possible to emit XHTML compliant image tags. > If nobody pipes up with the answer I will dig around if you really need it. > > I presume the telerik editor has a config setting for that somewhere. > > > > In regards to the style tags, I’m surprised that the CMS would include > internal style tags in published content. Do you have a specific example? > > It is published content we’re talking about, and not SmartEdit, right? > > > > Richard. > > > > > > From: [email protected] [mailto:[email protected]] On > Behalf Of Joel Kinzel > Sent: Tuesday, 30 October 2012 1:17 AM > To: [email protected] > Subject: Re: xhtml compliant image tags and embedded styles > > > > That is a good question, no real reason behind it. The one tag that > "concerns" me (for lack of better terms) is the style tag. I was hoping there > was a check box or something that I had just missed with regard to the image > tags. > > On Monday, October 29, 2012 9:06:35 AM UTC-5, Richard Hauer (5 Limes) wrote: > > Hey Joel, > > > > Maybe a silly question, but why are you aiming for XHTML compliance? > > > > Regards, > > Richard. > > > > From: [email protected] [mailto:[email protected]] On > Behalf Of Joel Kinzel > Sent: Tuesday, 30 October 2012 1:00 AM > To: [email protected] > Subject: xhtml compliant image tags and embedded styles > > > > All, > > > > I just ran the W3C against a published site, and it came back with 17 errors, > all of which were from CMS-generated code. > > > > 16 were from image tags that were not closed properly. Some were place > holders (image elements in the code), others were from images in the text > area. Additionally the embedded style did not have a type specified, so that > causes an error as well. > > > > My question is, how can we eliminate these errors? > > > > We are on CMS 10.1.2.341 and Telerik RadEditor. > > -- > You received this message because you are subscribed to the Google Groups > "RedDot CMS Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/reddot-cms-users/-/bxqaRbLfhNMJ. > 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/reddot-cms-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "RedDot CMS Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/reddot-cms-users/-/3o-EYycrpUcJ. > 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/reddot-cms-users?hl=en. > > > > The contents of this e-mail and any attachments are confidential to the > intended recipient. They may not be disclosed to or used by or copied in any > way by anyone other than the intended recipient. If this email is received in > error, please immediately notify the sender and delete the e-mail and > attached documents. > Please note that neither the sender nor the sender’s company accept any > responsibility for viruses and it is your responsibility to scan or otherwise > check this e-mail and any attachments. > > -- > You received this message because you are subscribed to the Google Groups > "RedDot CMS Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/reddot-cms-users/-/xD_6eUpFGywJ. > 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/reddot-cms-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "RedDot CMS Users" 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/reddot-cms-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "RedDot CMS Users" 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/reddot-cms-users?hl=en. > -- > You received this message because you are subscribed to the Google Groups > "RedDot CMS Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/reddot-cms-users/-/4D189vMF5W8J. > > 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/reddot-cms-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "RedDot CMS Users" 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/reddot-cms-users?hl=en. -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" 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/reddot-cms-users?hl=en.
