The Water Cooler

 View Only
Expand all | Collapse all

More woes around "thank you for submitting your message"

  • 1.  More woes around "thank you for submitting your message"

    Posted Mar 31, 2020 05:31 AM
    ​Hi.

    This is not the biggest issue as there is a workaround, but it's another bit in HigherLogic that's really quite anoying. Maybe the vendor can be made to do something about it.

    As @Michael A. Lowry pointed out earlier, after posting, the URL has "&SuccessMsg=Thank+you+for+submitting+your+message." attached it it. After I post, one often times may want to send the URL with ones answer included to a colleague or client. When I send the "thank you" URL, that gives odd results. One can not even click on the post title to get back to the "regular" thread view. One needs, as far as I can see, navigate back to, e.g. the Water Cooler thread list, open the thread again, and only then can I copy the URL proper.

    Would be splendid if that could be eased.

    Thanks!



  • 2.  RE: More woes around "thank you for submitting your message"

    Posted Mar 31, 2020 06:14 AM
    Edited by Michael A. Lowry Mar 31, 2020 06:15 AM
    Oh god the URLs are such a mess. The documentation site is another example.

    Here's the (somewhat) clean URL to a particular documentation page:
    https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/12.3/Automic%20Automation%20Guides/help.htm#Script/Reference/PUT_PROCESS_LINE.htm

    Here's the URL of the same page if you navigate to it via the table of contents sidebar:
    https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/12.3/Automic%20Automation%20Guides/help.htm#Script/Reference/PUT_PROCESS_LINE.htm%3FTocPath%3DReference%7CAutomation%2520Engine%2520Script%2520Reference%7CScript%2520Elements%2520Ordered%2520by%2520Purpose%7CData%2520Sequences%7C_____17

    Why this info is encoded in the URL, I cannot fathom. It's not stuff that belongs there. Put it in a cookie, or store it just for the session.

    Making matters worse, the URL in the address bar is often not even updated when one navigates via the TOC. So if you copy the link, you are often copying the link of the first page your visited, not the page you're currently viewing.


  • 3.  RE: More woes around "thank you for submitting your message"

    Posted Mar 31, 2020 07:18 AM
    Edited by Carsten Schmitz Mar 31, 2020 07:22 AM
    Why this info is encoded in the URL, I cannot fathom. It's not stuff that belongs there

    Annecdote time:

    A company I worked for developed a web app and it encoded certain images and other binary data as part of the URL. I once debugged an issue with it where an URL had four gigabytes of data encoded into it, to which our head developer merely pointed out (correctly) that the RFC allows it, and also: why not?

    I rest my case.

    (n.b. just if that wasn't clear, I think this is an absolutely silly idea)

    (n.n.b. while the RFC allows it, there are things known as "browsers" for which I can certify that they don't like 4GB in the URL, or already the few megabytes this would entail in most "regular" cases. However, due to the magic of modular task assignment, our head developer almost exclusively used curl for working on that part, and iirc curl even handled a giganormous URL without any issues).




    ------------------------------
    These contain very good advise on asking questions and describing supposed bugs (no, you do not need to go to StackExchange for Automic questions, but yes, the parts on asking detailed, useful questions ARE usually relevant):

    http://www.catb.org/~esr/faqs/smart-questions.html

    https://www.chiark.greenend.org.uk/~sgtatham/bugs.html

    I will not respond to PM asking for help unless there's an actual reason to keep the discussion off of the public forums.
    ------------------------------



  • 4.  RE: More woes around "thank you for submitting your message"

    Posted Apr 22, 2020 06:45 AM
    Edited by Michael A. Lowry Apr 22, 2020 06:49 AM
    Check out this link.


  • 5.  RE: More woes around "thank you for submitting your message"

    Posted Apr 22, 2020 07:08 AM
    ​Good thing I am in the office all alone, I laughed waaaaaaaay to hard at this :D


  • 6.  RE: More woes around "thank you for submitting your message"

    Posted Apr 22, 2020 07:37 AM
    Edited by Carsten Schmitz Apr 22, 2020 07:37 AM
    Hm, when you put simple HTML tags, URL escaped, into it, it is not parsed. That's okay.

    Put an URL-encoded​ img tag into it, it generates a 404.
    Put an URL-encoded img tag with a syntax error, it generates an Internal Server Error.

    Which would indicate that this is not just escaping, but seemingly parsing HTML entities on the server?

    I am rather glad I am not responsible for coding this and I can see absolutely no way how that could possibly go wrong.

    ------------------------------
    # signature.sh --verbose=[true|false]
    # no configurables beyond this point, only signature

    Does using the slide show widget for posting individual images spread Corona? Don't take the risk, use the "insert image" button in the editor!

    Did you know? I will NOT respond to PM asking for help unless there's an actual reason to keep the discussion off of the public forums!

    "Efficient Solutions Monthly Magazine" says: These contain very good advise on asking good questions. No, you do not need StackExchange for Automic, but asking questions the right way never hurts:

    http://www.catb.org/~esr/faqs/smart-questions.html

    https://www.chiark.greenend.org.uk/~sgtatham/bugs.html
    ------------------------------



  • 7.  RE: More woes around "thank you for submitting your message"

    Posted Jul 06, 2020 07:35 AM
    Edited by Michael A. Lowry Jul 08, 2020 05:58 AM
    This problem still exists.


  • 8.  RE: More woes around "thank you for submitting your message"

    Community Manager
    Posted Sep 03, 2020 11:10 PM
    @Michael A. Lowry  -  this request was rolled into a larger security request for the platform (pen tests, etc).   The vendor replied - I still have to run tests regarding the thank you issue.   Below is the reply from the HL security team per my ticket.  Thx ~jm

    "Hi Jason,

    Thank you very much for your reply. I was able to verify with our Engineering team that there should not be any issues with adding this parameter, which would interfere with the site. I have updated this parameter for the https://community.broadcom.com/ site.

    I was able to obtain a few suggested scripts for testing purposes, though you can definitely test with the original example. Per one of our Engineers:

    As for test scripts, here are two I can easily think of. They can test by adding these to private message HTML fields or other fields where members can add HTML (like the bio section)

    <script> alert('This message should no longer pop up'); </script>

    <script> console.log('Pop open the developer tools, look at the JS tab and see... nothing'); </script>

    I hope that these might assist you.

    Please let us know once you have been able to test if this might address your concerns for the original issue raised. ​​"

    ------------------------------
    Thank you
    Jason
    Broadcom Community Platform Admin, IT
    ------------------------------



  • 9.  RE: More woes around "thank you for submitting your message"

    Posted Oct 22, 2020 02:48 AM
    The problem is still happening today.


  • 10.  RE: More woes around "thank you for submitting your message"

    Community Manager
    Posted Oct 22, 2020 10:54 PM
    Reopening ticket with vendor.   ~jm

    ------------------------------
    Thank you
    Jason
    Broadcom Community Platform Admin, IT
    ------------------------------



  • 11.  RE: More woes around "thank you for submitting your message"

    Community Manager
    Posted Oct 23, 2020 11:04 AM
    Reply this morning after opening a branch off the original ticket.

    #response#

    Hi Jason,

    Thank you very much for your follow up. I would like to let you know that this previously reported issue had been reviewed and created as a BUG for our Development team to review. I must apologize as it seems that this may have gotten lost in the shuffle within your previous request, 162150, as there were several issues raised via that request.

    However, this BUG request is still open and I can see that it has been assigned to one of our Product Managers. I will do my best to try to get an update regarding this issue.

    For the moment, I will keep this request open and in an "On Hold" status until we have some additional information for you.

    Thank you for your continued patience,

    Kieran
    Customer Support Specialist




    ------------------------------
    Thank you
    Jason
    Broadcom Community Platform Admin, IT
    ------------------------------