Advanced Designer CSS: Comment closing tags are not saved correctly, if there are two comments set next to each other

  • Profile Image
    rwaldenjr
    Asked on September 21, 2017 at 01:10 AM

    I have some previously-used CSS code on my "Contractor Questionnaire" that I originally used for alignment. I don't want to totally delete it yet, while I'm experimenting with alternate CSS solutions. So, I keep trying to comment out the old code. I had a typo in my tag placement the first time I enclosed the old code in comment tags. Now, no matter how many times I reposition the offending end-of-comment tag, " */ " (which eliminates the error), and click Save, the error is still there the next time I open the Advanced Form Designer. What's causing this problem, and how come I can't seem to eliminate this errant code? How do I correct the problem?

    Thanks for your help!

  • Profile Image
    Nik_C
    Answered on September 21, 2017 at 01:54 AM

    I checked your code and you had one extra closing selector:

     

    Remove it and you will not have any errors there. 

    If you have any further questions please let us know.

    Thank you!

  • Profile Image
    rwaldenjr
    Answered on September 21, 2017 at 03:46 PM

    You've identified the result Nik, but not the problem. I've tried time and again to edit that errant "close" tag; moving it from Line 44 (below my comment), to Line 42 where its intended to close the hidden section of old code above it. Yet, every time I make the edit, save it, close the editor (and the form), then reopen it, the stray close tag is back on Line 44 again! Not sure what's causing this, or how to fix it!?!

  • Profile Image
    Marvih
    Answered on September 21, 2017 at 05:33 PM

    I have cleared your forms cache can you please check and see if it is now fixed?

    Let us know how it goes.


    Thanks

  • Profile Image
    rwaldenjr
    Answered on September 21, 2017 at 11:59 PM

    Thanks for your efforts. Unfortunately, nothing has changed! The close tag still won't save.   :-(

  • Profile Image
    Nik_C
    Answered on September 22, 2017 at 01:17 AM

    I went to your Advanced designer of the Questionnaire form and removed the closing tag. It worked fine after saving and re-entering the Advanced designer.

    Could you please check?

    Thank you!

  • Profile Image
    rwaldenjr
    Answered on September 22, 2017 at 01:54 AM

    Thank-you Nik for your suggestion! Yes, I realized I could have removed the second closing tag, and basically created a single combined comment section (with an additional opening " /* " tag before my note). But, that doesn't explain why I can't seem to be able to have two separate comment sections on the same form. Typical coding technique includes multiple comments! Still don't know why I can't save the closing tag for the first section (old code)!?!

  • Profile Image
    BJoanna
    Answered on September 22, 2017 at 03:14 AM

    You should be able to have two separate comment sections on the same form. However, you should first close the first comment section. Based on the screenshots on this thread, you should close the first comment section on line 42 and then create a new comment section on line 43. 

    However, I am not sure why the changes you made were not save. If the same issue happens again, please try to save the changes inside of the Form Designer CSS tab. 

  • Profile Image
    rwaldenjr
    Answered on September 22, 2017 at 11:30 AM

    Okay BJoanna, I made the "close tag" edit in  Form Designer (again). And this time, it stayed! Not sure why it won't Save in Advanced CSS Editor!?! But, apparently you guys have a bug that needs to be fixed between the two different CSS editors.

    Thanks for your help. And, please make sure your developers pursue this as soon as possible so other people don't waste as much time as I have trying to add simple comment sections to their CSS code.

  • Profile Image
    BJoanna
    Answered on September 22, 2017 at 11:51 AM

    I will report this issue to our developers and we will inform you via this thread once this issue is resolved.