Forum Replies Created

Viewing 21 posts - 1 through 21 (of 21 total)
  • Author
    Posts
  • in reply to: All Forms down since – wordpress auto-update 4.0.1. #357267

    @ralph12 – I don’t think that’s the issue. I uploaded manually several times and verified that the style.css file uploaded successfully. However, the WordPress admin didn’t at least update the theme version number.

    in reply to: All Forms down since – wordpress auto-update 4.0.1. #356054

    @josue problems on my site has been fixed. I first manually updated the Enfold theme by FTP. Files were 3.0.4, but it functioned like 3.0.2. I then went back to Enfold Themes Update panel to enter my ThemeForest API key for automatic theme update. Updating the theme through the Enfold Panel pushed the version to 3.0.4. The Google map and contact form came back afterward. (Just curious, any idea why manual update by FTP didn’t work?)

    in reply to: All Forms down since – wordpress auto-update 4.0.1. #355497

    @josue – sure, here’s my website http://osso.ws/contact . i haven’t installed any recent plugin and have tried disabling all of them.

    in reply to: All Forms down since – wordpress auto-update 4.0.1. #354907

    Hi Josue. I’m having the same problem and can confirm:

    Updated Enfold to 3.0.4
    Tested Contact Form 7, which works

    Along with the Enfold Contact Form, the Google Map module also stopped working. I’m not requesting support, just reporting it so the support team knows what to look for.

    in reply to: Slider cation option #343141

    I’m not familiar with older Enfold versions, but in the latest version the Full Width Easy Slider pretty much has the same Caption settings as the Full Screen Slider. Are you using the latest version?

    in reply to: And sign in the special heading #343132

    I am on a Windows laptop. I viewed your site using Chrome and Firefox. Both browsers displayed an ampersand fancier than the big bold one so we know at least its font style is italic. However, it’s still not the exact one that you’re displaying in the bottom screenshot. My guess is, at some point, your custom fonts aren’t working and the ampersand is using one of the fall-back font families.

    in reply to: Proper page ID code for page-specific CSS #343127

    I can’t see your site so my response is based on your screenshot. From what I can see, I would recommend:

    .page-id-3279 .template-page .entry-content-wrapper h1,
    .template-page .entry-content-wrapper h2 {
    	margin-bottom: 40px;
    }
    
    .page-id-3424 .template-page .entry-content-wrapper h1,
    .page-id-3424 .template-page .entry-content-wrapper h2 {
    	margin-bottom: 10px;
    }

    When you put .page-id-3424 in front of template-page .entry-content-wrapper h2, it gives it more weight. Generally, this should give H2 10px margin bottom instead of 40px. However, if your 40px rule requires !important to work in the first place then your 10px rule will need !important as well.

    The difference between your version and my version is the last step. My last step is telling the CSS to replace the 40px rule with the 10px rule only when you’re on page 3424.

    in reply to: And sign in the special heading #342895

    It’s rendering correctly for me. You’re using italic Baskerville. Maybe clear your browser cache, refresh, and view the site again?

    in reply to: Proper page ID code for page-specific CSS #342894

    You actually have two groups of CSS rules there, one for 3279 and another for 3424. However, both groups has .template-page .entry-content-wrapper h2 in common and THAT is actually the rule being used whenever you’re viewing 3279 and 3424. Therefore, this has nothing to do with page-id mix up.

    It’s the CSS !important declaration that’s forcing margin-bottom: 40px on both pages.

    For page-specific CSS, using page-id is good, but you’re also grouping other stuff with it and using !important as well. Don’t do that. As you can see, it gets confusing very quickly. Lean toward using CSS ID instead of Classes for very specific stuff.

    in reply to: And sign in the special heading #342885

    It would help if you link to the site so we can see what is being loaded. The fat ampersand display usually means italic is NOT implemented.

    in reply to: Function for adding additional head html #342595

    Hi Darryl. My mistake. The following should work:

    add_action( 'wp_enqueue_scripts', 'enfold_child_load_google_fonts' );
    function enfold_child_load_google_fonts() {
    	wp_register_style( 'enfold-child-fonts', '//fonts.googleapis.com/css?family=Lora:400' );
    	wp_enqueue_style( 'enfold-child-fonts' );
    }

    See how the second line now matches a part of the first line?

    in reply to: White Screen of Death #342567

    If that reply was meant for me, I can’t view it because it’s private and I’m not one of the support staff, just a fellow user trying to help :)

    in reply to: colour bar under menu on left. #342565

    You can put the following in the Quick CSS box or your child theme style.css file:

    .html_main_nav_header #top .main_menu .menu>li:last-child>a {
    padding-right: 13px;
    }
    in reply to: Function for adding additional head html #342562

    There are many ways to do this.

    Adding a Google Font
    1ST OPTION: enqueue it via the child theme functions.php file. Example:

    add_action( 'wp_enqueue_scripts', 'enfold_child_load_google_fonts' );
    function enfold_child_load_google_fonts() {
    	wp_register_style( 'enfold-child-fonts', '//fonts.googleapis.com/css?family=Lora:400' );
    	wp_enqueue_style( 'enfold-child-fonts' );
    }

    2ND OPTION: embed the Google Font using your child theme style.css file. (The example above is recommended.) Example:
    @import url(https://fonts.googleapis.com/css?family=Open+Sans);

    3RD OPTION: Use the Google Font embed link in your child theme header.php file. Again, I recommend option one.

    Adding scripts
    Very similar, almost exactly, to the examples above. Look into wp_enqueue_scripts. At the bottom of that documentation page, there are links to other functions that should help you as well, like print, register, or localize scripts.

    in reply to: logo will not upload from dashboard #342558

    You could do it through the Media > Add New page first then go back to your settings page to set your logo.

    Side note: any time you click a button and expect something to pop up, but nothing happens, check what plugin you recently installed and whether deactivating that plugin fixes the problem.

    in reply to: White Screen of Death #342557

    Many things can cause the white screen of death. This WordPress.org documentation page will guide you through the most common problems.

    @calcite – That’s how it’s supposed to work. Whatever’s available in the parent theme, the child theme inherits it — including updates. There’s an exception and that’s when you purposely have things in the child theme that takes the place of parent theme features.

    Template files aren’t features, but it works the same so for example… having a header.php file in the child theme folder means that file will always be used instead of the parent theme header.php file, regardless of what changes or updates you make to the parent theme file. Once you remove the child theme header.php file, it goes back to using the parent theme version.

    in reply to: Main Menu links broken #341764

    Edit: Thought you said .htaccess was not empty, but your follow-up reply says it IS empty.

    If .htaccess file is empty, follow instructions from Creating and editing (.htaccess).

    In the future, you can make automatic changes to your .htaccess file if you follow Automatically updating your .htaccess file. I would recommend following these instructions instead of the one above to get your .htaccess file working automatically with the Permalink settings page.

    • This reply was modified 10 years, 1 month ago by Tung Do.
    in reply to: Main Menu links broken #341737

    “Refresh the site” — I meant refresh the browser.

    Here’s WordPress.org’s documentations on permalinks. I suspect there’s a problem with your .htaccess file so on that documentations page, scroll down to “Where’s my .htaccess file?” and follow those instructions.

    You can quickly tell whether it’s an .htaccess file problem by downloading it via FTP then view it on your computer or by viewing the file through the web host control panel. If the file is empty then that’s the problem.

    Hope that helps!

    in reply to: Main Menu links broken #341722

    Every time you visit the Settings > Permalinks page to save your permalink settings, that’s flushing your permalinks. Go there, select an option other than the first one, save your setting then refresh the site to use the new permalink structure.

    Child theme set up instructions rarely need update — has been the same for years on many other theme sites. This sounds like the code went wrong somewhere. You can show the support team what you’ve done so far by posting your code at PasteBin.org and link it back here.

    edit:
    ===
    Submitted my response right after a moderator answered. Nevermind.

    • This reply was modified 10 years, 1 month ago by Tung Do.
Viewing 21 posts - 1 through 21 (of 21 total)