I’m curious as to what you think these things are? Could you give me an example?
Sure in the thread I started here…
The code at the above forum link is working HTML code. With the URLs and some input fields modified for privacy. The code has been functioning since 2000, when I first included it in a webpage.
I have tried using the Form Component with a button defined as a type Submit. All the “hidden” fields are defined in the form prefaced with “type hidden”.
When the Submit button is pressed, the url in the action is visited and replies that there is no “vendor_id” field supplied.
I took the hidden attributes out of the form body and placed them in a Hidden Input Component in the form. Thinking that would work.
When the Submit button is pressed, the url in the action is visited and replies that there is no “vendor_id” field supplied. This field is clearly defined in both implementations.
So without documentation, it’s kind of hard to determine why the BSS generated code does not work. One would expect that if a UI component were used that it should function without issues. Obviously, there is a setting, or a toggle, or some field the UI that needs something for this to work. The submit actually goes to the webpage as defined in the “action” field, but the BSS code fails to send the hidden input fields.
I should point out that the “Contact Us” template form that is provided by BSS also does nothing when the submit button is pressed, so maybe it’s the same problem. Again, without documentation, it’s kid of difficult to know where to start looking to resolve the issue.
I hate to point out the obvious again, but the way the BSS product is marketed is as a “drag and drop”..with the ability to easily modify CSS IF you want to. One shouldn’t need to dig into the HTML or CSS the UI creates to make things work. You should be able to work entirely within the BSS UI. I should mention that even if you import working HTML code to try to make things work, you can’t edit what you import..or so I thought. I figured that since you could not access the attributes of the Custom Code you were not allowed to make changes. I finally realized you could edit it in another pane..just not in the Attributes pane. Documentation would have pointed this out.
I imported my working HTML code as a page and it gets added to the project as Custom Code. Running it in preview mode works..just like the code has for the last 19 years.
I can make a hack or work-around to fix the issue, but what I would REALLY like is to work within the BSS UI.
The good thing is, the web is built on standards, and those standards are very well documented. Learning them, IMO, should precede trying to build sites with any builder, because it always make any task easier when you understand the underlying mechanics.
Right. The trouble is that the entire reasoning behind my purchase of BSS was to NOT have to learn all the ins and outs of HTML and CSS. I’ve already done websites from scratch using HTML. I would prefer to do other types of programming.
But so far, I’ve yet to have to convert a single object to HTML. Everything I’ve needed to do could be done by using the visual tools, or writing a little CSS.
Maybe your websites have been of a more generic nature..IDK. Though I don’t consider a simple form post with hidden input out of the ordinary or complex, the BSS UI does not appear to handle this in a reasonable or straightforward way.
And I’ve RARELY had to refer to the documentation.
Ah. What documentation would that be again, exactly? ;-). And, FWIW, I do think BSS is a very good tool. I just wish there were a little more documentation or examples for us "noobs".