200 X-Frame-Options: SAMEORIGIN Content-Security-Policy: frame-ancestors 'self'; X-UA-Compatible: IE=Edge X-XSS-Protection: 1; mode=block X-Content-Type-Options: nosniff X-Telligent-Evolution: 12.x Pragma: no-cache Connection: close Accept-Ranges: bytes Cache-Control: no-store, no-cache, max-age=0 Date: Wed, 04 Dec 2024 19:27:31 GMT ETag: "0x8DD02F56CCD7D1F" Set-Cookie: .te.csrf=Z1iRfaN1pUYkBhcdzMgFG3Tw-nf2Qqe-BS9qvC2RNHQ; path=/; secure; SameSite=Lax Set-Cookie: .te.auth=NrjFpbJuUk%2b0WAMsOrg0L4hXD5WFEmccH0oaYxMVBdAXP2WTgH7FQWrNuFSBuXv5AW%2beKVJiLouu3%2fuCjR2lANE%2fQynBgdpwBXlcQjSQIQcnkdeDX8W05imiMwYcXgg79cuCg3fB7URFibhRwPKN9pSlhuU2NAlZDGZhHJdBZb%2f%2fCkQ%2bYeMfZUV9j8S%2bBvt1%2fClhalqgtTLge1BIEhplRcB7IqdDxKsZXK7iM02HiwQrTYRUA6GshePF%2fH%2fcRl9uNayVQkh6KOZKZyfCtqwTMw%3d%3d; path=/; secure; HttpOnly; SameSite=Lax Set-Cookie: e14Guest=1; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14Country=NL; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14Language=en; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14TimeZone=Etc/UTC; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Server-Timing: cdn-cache; desc=MISS Server-Timing: edge; dur=10 Server-Timing: origin; dur=21 Server-Timing: ak_p; desc="1733340451769_3090373303_296540098_3106_8205_6_7_-";dur=1 Strict-Transport-Security: max-age=86400 ; includeSubDomains ; preload #set ($UserId = $core_v2_user.Accessing.Id) #set ($Roles = $core_v2_utility.MakeList('Moderators', 'Almost Admins', 'Administrators')) #set ($IsAdminLike = $e14_utils.IsUserInRoleOrAdmin($UserId, $Roles)) #if($IsAdminLike == 'False') #end
Actions
Forum Thread Details
  • State Suggested Answer
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 12 subscribers
  • Views 582 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

BUgs, Bugs, in the publisher.

phoenixcomm

DANGER WILL ROBINSON!!!  I now know why my web page blogs are FUBAR! please look at this page: hacking-loadmeter-dual-weston-248697 It is crazy yes! The reason is in your code generation module. It puts a scroll bar in the middle of my page!!! And I cant get rid of it!!!!

This breaks clean HTML Code for no good reason!! This prevents me from publishing complex blogs with pictures and tables, 

These are more little things:

I noticed a problem with the editor, it seems to have a mind of its own. problem

#1  max-width in my opinion is being missed used. "

max-width property defines the maximum width of an element.
If the content is larger than the maximum width, it will automatically change the height of the element.
If the content is smaller than the maximum width, the max-widthproperty has no effect.
Note: This prevents the value of the width property from becoming larger than max-width. The value of the max-widthproperty overrides the width property.
www.w3schools.com and this is in a div  

max-width property that defines the maximum width of an element.
If the content is larger than the maximum width, it will automatically change the height of the element.
If the content is smaller than the maximum width, the max-width property has no effect.
Note: This prevents the value of the width property from becoming larger than max-width. The value of the max-width property overrides the width property.
www.w3schools.com

#2 

it is illogical to use a span for styling unless you want to emphasize something in the middle of a paragraph. like the word emphasizes.
It should not be used like this <p><span style="font-size: 14px;" but it should be in the paragraph tag like this <p style="font-size: 14px;"> instead,  it should be included in the paragraph tag itself as p style="styling commands" having the editor shotgun the span tags all over the place makes the code very hard to read. as the paragraph tag is the controlling tag Not the span.

#3 I call this a pishing contest.  please, please let me use <style> blocks in the header!! As this is normally how I build an HTML5 page! including inline CSS is very crude and time-consuming. 

All you have to do if you are afraid  of <link rel="stylesheet" href="styles.css"> is to just let us include <style> </style> in the header 

#4 Point of hate... Why does this editor put a <p> tag for each line of a carriage return?? it should be an <br> ie I have to use the source editor (BTW it STILL won't do full screen.)

FINS I think believe me there is more but I have to make my dinner

Parents
  • 0

    Thank you for bringing these issues to our attention. We understand that you have encountered problems with the layout and formatting of your blog posts and the limitations of the Verint community platform. We apologize for any frustration this may have caused.

    However, please be aware that some of the issues you have raised may be out of our control due to the purposeful restrictions we have in place to maintain the integrity and security of the platform. Additionally, some formatting and layout issues may be a result of the website's layout and formatting as well as styling specified in its CSS. We're also waiting for the opportunity to upgrade to a more recent version of the platform which contains a number of fixes to the site, at present version 12.1.4 and 13 are not available but should fix the majority of issues our members have with various areas.

    We suggest that you continue to use the available tools within the platform and manually adjust your code and formatting to extent of the ability within these limitations. Thank you for your understanding.

  • 0 in reply to cstanton

    Hi     has rightly pointed out that some of these issues regarding the Rich Text Editor are out of our control. The RTE used is baked into the platform. We will happily report your concerns to the platform vendor. However, please also note that removing css in many cases is on purpose because while you are using relatively innocuous css, css is very powerful and others could (and have in the past) used it to override/do harm to the overall styling of the site and the page, which we definitely don't want. We've encountered some of these challenges you're reporting ourselves and even our own content publishers have had to make their peace with the current limitations of the RTE for content we publish. I'm afraid my best recommendation is that you author things directly on the site as doing it in an outside editor and copy/pasting it over - as you've pointed out - often doesn't result in the display that you expect based on the editor you used originally. We are always working with the vendor, and  in particular has been extremely diligent about raising concerns from our members with them for future improvements. Thank you for taking the time to let us know about these concerns.

Reply
  • 0 in reply to cstanton

    Hi     has rightly pointed out that some of these issues regarding the Rich Text Editor are out of our control. The RTE used is baked into the platform. We will happily report your concerns to the platform vendor. However, please also note that removing css in many cases is on purpose because while you are using relatively innocuous css, css is very powerful and others could (and have in the past) used it to override/do harm to the overall styling of the site and the page, which we definitely don't want. We've encountered some of these challenges you're reporting ourselves and even our own content publishers have had to make their peace with the current limitations of the RTE for content we publish. I'm afraid my best recommendation is that you author things directly on the site as doing it in an outside editor and copy/pasting it over - as you've pointed out - often doesn't result in the display that you expect based on the editor you used originally. We are always working with the vendor, and  in particular has been extremely diligent about raising concerns from our members with them for future improvements. Thank you for taking the time to let us know about these concerns.

Children
  • 0 in reply to ChristyZ

    So what you are telling me the RTE editor is FUBAR! So I will resort to my hammer and nails and build my stuff in one large <table> This su**!!!

    also please NOTE that in HTML5 you have the <figure> tag its sort of like this
    <figure>
    <image scr="the picture" style="width: 200px; height: auto;>
    <figcaption>blah, blah, you get the idea</figcaption></figure>

    In my last attempt at this, the RTE put the caption to the left of the image!!?? WTH??

    OH yes one more point: why does this stupid editor put a "return/line-feed" instead of just a dam line-feed???

    yalf (UNIX speak Yet Another LIne Feed> This should never happen. 

  • 0 in reply to phoenixcomm

    So what you are telling me the RTE editor is FUBAR! So I will resort to my hammer and nails and build my stuff in one large <table> This su**!!!

    also please NOTE that in HTML5 you have the <figure> tag its sort of like this
    <figure>
    <image scr="the picture" style="width: 200px; height: auto;>
    <figcaption>blah, blah, you get the idea</figcaption></figure>

    In my last attempt at this, the RTE put the caption to the left of the image!!?? WTH??

    OH yes one more point: why does this stupid editor put a "return/line-feed" instead of just a dam line-feed???

    yalf (UNIX speak Yet Another LIne Feed> This should never happen. 

    "However, please also note that removing CSS in many cases is on purpose because while you are using relatively innocuous CSS, CSS is very powerful and others could (and have in the past) used it to override/do harm to the overall styling of the site and the page, which we definitely don't want."

    If they are that paranoid about <style> JUST DONT LET THEM DO THIS: <link rel="stylesheet" href="styles.css"> it's just that easy. which means no foreign fonts, and all the bad stuff. BTW  You can place HTML style tags in <head> or <body> elements. <please let us use the style tag in the body. 

    One last thing how wide is the blog page set to. I want to stop guessing at this.