40% OFF EVERYTHING
BLACK FRIDAY SALE
Buy Now

'HTML Variable Name must not be blank' on Fieldset

This topic contains 8 replies, has 2 voices, and was last updated by  adyp 8 years, 12 months ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket

Tagged: , ,

  • Author
    Posts
  • November 24, 2015 at 5:17 pm #61374

    adyp
    Expired Member
    Post count: 496

    I am not sure if this should be posted here or in CPT addon bugs (it has happened on a couple of CPTs – but might happen on Places without CPT addon enabled?) – so please move if appropriate …

    anyway, I have the worst type of bug: intermittent (I’d say happening between 5 and 10% of the time).

    When adding a Fieldset in Custon Fields, I get to the point of pressing the save button and it pops up a message box: ‘HTML Variable Name must not be blank’ – now, there isn’t a HTML Variable name on Fieldsets! if I press ‘OK’ then it pops up the same message, supplemented by a checkbox with the following message: ‘Prevent this page from creating additional dialogues’ I don’t check the box, but do press ok to get rid of the box. I then delete the fieldset and create a new one, put in the same info and it saves fine… most frustrating.

    Let me know if you need any more details, but I think that’s about it.

    November 24, 2015 at 6:01 pm #61379

    Paolo
    Site Admin
    Post count: 31206

    HI,

    I can’t recreate this in our demo, please provide url and admin details to test directly on your website.

    Thanks

    November 24, 2015 at 6:54 pm #61399

    adyp
    Expired Member
    Post count: 496
    This reply has been marked as private.
    November 25, 2015 at 9:18 am #61429

    adyp
    Expired Member
    Post count: 496
    This reply has been marked as private.
    November 25, 2015 at 8:24 pm #61520

    Paolo
    Site Admin
    Post count: 31206

    Hi,

    I couldn’t see this happening.

    A software cannot do something wrong sometimes, either will do it always right, or always wrong. In addition, nobody else reported this problem.

    There is a variable that make this change and that is human intervention. There must be something you are doing wrong few times that is amking the software tilt.

    Possibly adding a fieldset with a new field already in it… That would require the html variable to be set.

    Thanks

    November 25, 2015 at 8:29 pm #61521

    adyp
    Expired Member
    Post count: 496

    Hi Paolo,

    Possibly adding a fieldset with a new field already in it…

    I’m not sure what this means?

    Can you please spell it out for me?

    Thanks

    November 26, 2015 at 11:39 am #61551

    adyp
    Expired Member
    Post count: 496

    … on reflection, I tend to add fieldsets and fields in batches – e.g., click on fieldset, then radio, radio, text area, etc – before scrolling down and completing the details for each (it saves a lot of scrolling up/down when I am adding a lot of custom fields).Os this the type of behaviour you mean?

    November 26, 2015 at 6:07 pm #61596

    Paolo
    Site Admin
    Post count: 31206

    That is correct. You should add the fieldset, rename it and save it before adding anything else.

    Thanks

    November 26, 2015 at 7:17 pm #61614

    adyp
    Expired Member
    Post count: 496

    Thanks Paolo – relieved to find that I don’t have a ‘ghost in the machine’.

    Adrian

  • Author
    Posts
Viewing 9 posts - 1 through 9 (of 9 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket
20% Discount Offer
Hurry! Get your 20% discount before it expires. Get 20% Discount