jgcordes

Forum Replies Created

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • in reply to: Mantra 3.1 problem – links and selecting text #73021
    jgcordes
    Participant

    And another followup. I found that removing Mailchimp from the Widgets area was sufficient to fix the problem, just leaving a Mailchimp sign-up form on one of the pages. So the problem isn’t with the overall Mailchimp plugin, but just the particular use of it as a widget.
    This is probably a reasonable work-around.

    in reply to: Mantra 3.1 problem – links and selecting text #73010
    jgcordes
    Participant

    A followup on the problem I posted about yesterday: I found that deactivating the MailChimp plugin on the site seems to fix the problem. The problem looks as though some javascript is disabling mouse actions on the post – unable to select text and link not working.
    I have no idea how to deal with this interaction problem between Mailchimp and Mantra v3.1.0. My society really does need Mailchimp working, so people can sign up to our mailing list. Is there some hope of a solution, please?

    Website: www.rnshs.ca

    in reply to: Changes in the 3.0 update #58700
    jgcordes
    Participant

    What was the issue pointed out by @carnegie – that message is marked private. I’m wondering if there is any need to update to 3.0.4.
    Thanks,
    John

    Website: rnshs.ca

    in reply to: Problem with v3 update – customizations #57945
    jgcordes
    Participant

    Thank you Zed. After realizing that it was only the files I already had in the mantra-child directory which needed some editing (eg. category-27.php and style.css), I was somewhat surprised to find that I also needed the “includes” sub-directory (containing theme-frontpage.php) to be under mantra-child as well. (This is just by testing on a test site; I still haven’t updated the live site yet.)
    Does that seem to be expected, to you? I don’t appear to need the other sub-directories content, resources or templates, to be under mantra-child; they are OK just in the main mantra folder.

    in reply to: Problem with v3 update – customizations #57923
    jgcordes
    Participant

    I found that using
    #access .menu-item a {…
    }
    gave enough specificity to make it work.

    So now to check for other issues.

    in reply to: Problem with v3 update – customizations #57922
    jgcordes
    Participant

    Another update. The padding in the menu bar titles is in the main Mantra style. I’ve tried to override that with this entry in my mantra-child/style.css file:

    #access a {
    padding: 0.5em; 0.5em;
    }

    but it is not working. (The parent Mantra theme as padding: 0.5em; 1.5em;)

    I have also tried including !important but that doesn’t help either. I don’t know if there is a css speficity issue here or if there is something else wrong.

    Any ideas, anyone?

    John

    in reply to: Problem with v3 update – customizations #57908
    jgcordes
    Participant

    Partial solution found, thanks to my son. I edited the category-27.php file which is directly under the mantra-child directory (the old location before Mantra 3 came along) to use the “content/content” as indicated above. I believe this is now picking up the posts as desired.

    At the moment this leaves the other problem, of modifying the css for the padding in the menu titles — I don’t know what class names are involved, or where that particular css is located.

    Thanks,
    John

    in reply to: Mantra child theme – problem with cryout_branding_hook #38498
    jgcordes
    Participant

    Thanks Zed. I believe I have this under control now. It is useful to see your list of settings which don’t get inherited by a child theme. May have more questions later!

    in reply to: Mantra child theme – problem with cryout_branding_hook #38398
    jgcordes
    Participant

    Following up on my own post. After more searching of this Forum I eventually found what I think is the answer. Our site is using the header background image, set by WordPress -> Appearance -> Header (I had not appreciated that before). This seems to resolve my problem, so that I no longer need an edited header.php file in the mantra-child directory.
    Apologies for the false alarm.

    John Cordes

Viewing 9 posts - 1 through 9 (of 9 total)