This is searchable archive of our old support forums, which operated from 2012 - 2016. To find out how to get support for your current theme, please visit our support page.

msnaughty

Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • Author
    Replies
  • in reply to: Css code for buttons #1220
    msnaughty
    Member

    The whole table came from Zombaio. The bit that says “Any charges through Zombaio Payment Services will read ZOMBAIO.COM on your cardholder statement for the merchant Nightly Entertainment.” is actually generated by a script.

    I put the entry content td css into the Custom CSS form and that’s done the job. So I might just leave it at that for now rather than risk screwing up the tracking scripts.

    Thank you for this extra bit of help, I do appreciate it.

    in reply to: Css code for buttons #1217
    msnaughty
    Member

    OK thanks for this. The code Zombaio gave me also includes a script attached to the image which is why I pasted it in mostly unaltered. I will have a play with what you have given me and see what works. Perhaps I can just paste the scripty-image code in between one_third and /one_third.

    in reply to: Css code for buttons #1214
    msnaughty
    Member

    I read your paragraph. Nowhere does it say: “put this code in your custom css”. What I was seeing was just code and general discussion about css. No instructions. And yes, you pissed me off.

    In any case, the code you’ve given me works. So, after all this lengthy discussion and confusion, thank you.

    in reply to: Css code for buttons #1212
    msnaughty
    Member

    Excuse me. “Quite the attitude”? Really? Really?
    I know you’re busy. But so am I. I’m a paying customer and I’m trying to ask a question about your code. Perhaps I could have phrased it differently so you understood my question. But jeez. Thanks for insulting me.

    Unfortunately I’m a DIY coder and I’m not always sure what I’m doing. In this case I don’t know how to create the css code that will make that form look clickable. Because really, that’s all I want. I need those BUY ME buttons to look clickable so the customer is absolutely certain that that’s what they’re supposed to do. Right now, it’s uncertain because they’re faded-looking and they don’t change when you mouseover them.

    At this point, I’m going to go off and experiment by removing all the css code that you’ve just quoted and I’ll see how it looks. This is the only way I know how to work with css, trial and error. And, from what you’re saying, it’s the only way I’ll be able to see if it looks clickable across all browsers.

    in reply to: Css code for buttons #1209
    msnaughty
    Member

    Wait wait wait.
    It is not *my* custom CSS that doesn’t work with the hover. I have not made any changes to that part of the code. So I’m not asking for support about customizations. I was trying to work out which bit of the theme deals with forms and why the existing Akita css code is not giving me the standard buttons look with mouseovering.

    So I’ll just delete the section in the Akita css that specifies how to deal with forms. Maybe then it will look how it’s supposed to look And yes, I’ll use a child theme.

    in reply to: Css code for buttons #1204
    msnaughty
    Member

    OK to clarify again. I was essentially asking where in the various css files were the rules regarding forms. I worked that out eventually. And I’ve managed to change it a bit. But as I wrote in the post from 12.53am, I don’t know why the hover function is not working, or why the css changes are only showing up in some browsers.

    Any suggestions as to why the mouse won’t change to a hand when I mouseover the buttons?

    in reply to: Css code for buttons #1123
    msnaughty
    Member

    OK so by searching on the exact colours of the buttons I found the bit in theme.css that deals with forms. I’ve changed the colour of the text so the buttons don’t look faded (although this now only works in Firefox; they still look faded in Chrome and IE). And I still don’t know why the mouse isn’t changing when I hover over the buttons.

    This is the current css styling:

    /* Forms */
    input,
    textarea,
    select {
    	border: 1px solid #d1d1d1;
    	color: #9e9e9e;
    	padding: 7px;
    }
    input {
    	line-height: 100%;
    }
    textarea {
    	width: 98%;
    }
    input:focus,
    textarea:focus {
    	border: 1px solid #bbbbbb;
    }
    input[type=submit] {
    	background-color: #f4f4f4;
    	border: 1px solid #d1d1d1;
    	color: #666666;
    	font-weight: bold;
    	margin: 0;
    	padding: 8px 15px;
    }
    input[type=submit]:hover {
    	color: #666666;
    }

    Suggestions as to why the hover thing isn’t working?

    in reply to: Css code for buttons #1122
    msnaughty
    Member

    I tried adding your suggestion into the custom css bit on the theme options page, it made no difference.

    So just to clarify, I was asking if the Akita css had a pre-existing rule in it that was making the form buttons look like that (faded, different font, the mouse doesn’t become a hand when you hover). Because I’m not looking to make the buttons look “nicer”. I want them to just look how they would look without any css styling.

    When I inspect using Firefox, it says the button’s css is called “input”. Unfortunately there are numerous “input” styles to choose from in Akita. I was originally asking if you have a suggestion as to which it would be?

    If there is no pre-existing rule about how form buttons should look within the theme, can you suggest why they don’t look or behave like normal form buttons? Would it be something that wordpress is doing? Is it because the form is contained within a table?

Viewing 8 replies - 1 through 8 (of 8 total)