Missing Attributes...

User 2906089 Photo


Registered User
222 posts

Simple question, how do I add attributes that are not yet in SD3. For example, I wanted to add a placeholder attribute to a form, but I could not find the option. It's not in WFB, but it's in FB. It would seem to be inefficient to change between multiple apps to get it done. What am I missing?

Thanks in advance.
Learn something, Share something.
User 10077 Photo


Senior Advisor
1,095 posts

In SD3, go to the Elements Pane. Look in the Selected Elements properties. You will see an attribute dropdown there. When you dropdown, choose custom and it will let you add whatever attribute you would like.

Regarding WFB and FB, design your forms in FB. Use WFB as the form processor. They work nicely together that way.
ASK ME ANYTHING
I provide personalized help for Coffeecup Users including training for Site Designer and Web Form Builder via Zoom.
Email me at support@usconsumernet.org or call 865-687-7698.

Did you know that Web Form Builder can be used for both simple and complicated forms and that it's not limited to the default fonts and buttons? Take a look at a form we developed for WindowTinting.com.
https://forms.windowtinting.com/forms/w … ppingcart/
User 2906089 Photo


Registered User
222 posts

When I try to enter "placeholder" in the name field I get a warning that says placeholder is reserved. When I choose the only option of ok, the name field goes back to it's default state. We are so close.
Learn something, Share something.
User 10077 Photo


Senior Advisor
1,095 posts

I didn't realize that Placeholder is a reserved word. I've run into that kind of thing before. Though it doesn't fix the issue, the workarounds I can think of are either to use FB to develop your forms and use an HTML Element to put them on the SD3 pages or to add the attributes after export.
ASK ME ANYTHING
I provide personalized help for Coffeecup Users including training for Site Designer and Web Form Builder via Zoom.
Email me at support@usconsumernet.org or call 865-687-7698.

Did you know that Web Form Builder can be used for both simple and complicated forms and that it's not limited to the default fonts and buttons? Take a look at a form we developed for WindowTinting.com.
https://forms.windowtinting.com/forms/w … ppingcart/
User 122279 Photo


Senior Advisor
14,447 posts
Online Now

I asked about this once (it was at the time Scott was working at CC), and got the reply that originally Placeholder had been included in the attribute list, but because of some trouble with Chrome it had been taken out again. Then I discussed it with Bob, could be as much as a year ago, saying they ought to try again, maybe Chrome had been fixed in the meantime. Anyway, I have some forms (created with RSD and SD3) in my sharing folder, in which I had added the Placeholder after export, and Chrome doesn't seem to have any objections to that.
Ha en riktig god dag!
Inger, Norway

My work in progress:
Components for Site Designer and the HTML Editor: https://mock-up.coffeecup.com


User 2906089 Photo


Registered User
222 posts

Since CC put it in their latest product, form designer, they must believe the problems have been sorted.

Does SD3 change code that you have modified outside of SD3 if you reload the project?

Thank you for your input.
Learn something, Share something.
User 122279 Photo


Senior Advisor
14,447 posts
Online Now

If I resave and re-export, I have to add all changes after export again - and again, yes.:/

If this has been added to Form Designer and is working, I'd much rather that they fix it for SD3 too, than adding things like pop-ups showing the pixels at each breakpoint.
Ha en riktig god dag!
Inger, Norway

My work in progress:
Components for Site Designer and the HTML Editor: https://mock-up.coffeecup.com


User 2906089 Photo


Registered User
222 posts

I'm very new to the CC Universe, what is the thinking behind not being able to edit the CSS and html in sd3? Showing the CSS with the read-only next to it is just a crule tease when you know you could fix this in a jiffy.

Learn something, Share something.
User 2699991 Photo


Registered User
4,782 posts
Online Now

Bosco wrote:
I'm very new to the CC Universe, what is the thinking behind not being able to edit the CSS and html in sd3? Showing the CSS with the read-only next to it is just a crule tease when you know you could fix this in a jiffy.



I think it is because if they allow one to edit the css file then it no longer becomes a what you see is what you get app. & not everyone knows what they are doing regarding editing stuff like that.
also, it could become a nightmare for support, with people complaining something is wrong with the project, at the moment everything that you do is what you get, if something goes wrong then its easy to see where, if they allow css editing, then who knows where it is going wrong.

after exporting if one messes it up then it is their responsibility, not CC (or the app that is wrong)

Finally the cost for such an app would be a lot higher that what it is now, & support would have to be a paid for thing, making it prohibitive for those who want to make something, without paying higher prices to do it.

If you want to do your own css (maybe additional styling whatever then you use custom css & put it in the resources folder.

Maybe one day Coffee cup might release a "Professional" version of SDv3 or whatever follows, which could include all the editing you need, but it would be more expensive (probably on a par with Adobe stuff.

I for one would always vote for NOT allowing any internal editing (should it ever come to that), it's hard enough to help people who are struggling now.
Mastering The Understanding With Hands-On Learning
NEW TO "COFFEECUP SITE DESIGNER" FOUNDATION 6 FRAMEWORK?
STUCK ON SOMETHING?

LEARNING & UNDERSTANDING "THE HOW TO"? THE WHY'S & THE WHEREFORE'S?
WITH WAYAN'S STEP BY STEP TUTORIALS
Contact Me For One To One Assistance
https://alphathemes.coffeecup.com/forms … an%281%29/
User 379556 Photo


Registered User
1,533 posts

I believe that the last-read style sheet takes priority over ones that are earlier in the header, and SD V3 (like its predecessors) puts one's custom css files later in the header than the main.css file.

The above seems to me to mean that one can cut and paste the first part of the read-only css into one's custom css file to override whatever one needs.*

I'm wondering whether there could be an option built into SD V3 that allowed one to turn on or off the showing of the effect of one's custom css (or js) file on the canvas, at least in preview mode.

Would that perhaps be a useful, and not too messy, compromise arrangement?

Frank

* For example (obviously not needing the override in practice as one could just change it within the program), in the SD V3 program I styled a paragraph to have white text on a red background, and the Your CSS (Read Only box) showed

p.paragraph.paragraph-1 {
background-color: rgba(255, 0, 0, .31);
color: #fff;
}


Creating a custom css with with the following shows the background as blue in 'Preview on ...', but not on the canvas -
p.paragraph.paragraph-1 {background-color: blue;}

Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.