mark l chaves

Hello @jaygr3y,

Just to clarify that I’m not implying that you add my code snippet directly to any WordPress PHP template files.

Since you said you are using the Insert Headers and Footers plugin, I am suggesting to move your code into the footer section of the plugin. I’ve already stated this in my CodePen that I posted earlier ;-).

If you decide to manually enqueue that script yourself (must be comfortable with coding PHP), then please use the enqueue method that @bcworkz kindly pointed out.

Here’s a usage example of enqueuing CSS, a JS library, and inline JS: https://gist.github.com/marklchaves/1c616eb28382b813232c23e0f29d164a

Cheers 🙂

• This reply was modified 5 years, 8 months ago by mark l chaves. Reason: Typos

Hello @antiqueverma,

Have you asked the theme authors? They would know the best way to do that for their theme.

If they’re are available or don’t support the theme anymore, you should consider moving to a well supported theme.

In the meantime, if you post the link to one of the pages you need to remove the sidebar, I can look to see if you can remove/hide with custom CSS.

Thanks!

Hello @gracebraedon,

I assume the text under your hero image is the tag line? I hope 😉

Here’s the CSS for making that bigger.

/* Make the tagline bigger. */
.page-header-title.clr {
  font-size: 3.5rem; /* Change number (size) as needed.
}

Cheers!

P.s. You previous code attempts might be correct, just in the wrong spot. Read how to add CSS to WordPress here.

My pleasure @antonop4u 🙂

Take care!

Hi @antonop4u,

Not exactly sure what the issue is. Instead of trying to debug your code, I modified it to use a CSS keyframes at rule for the transition.

For example, I assigned this class to your popup-win.

/* Fade in Once for Three Seconds */
.fade-in-1 {
  animation: 3s 1 fadeIn; /* Do the Fade. */
}

Which in turns uses this at rule.

/* The fading in part. Reused above. */
@keyframes fadeIn {
  from {
    opacity: 0;
  }
  to {
    opacity: 1;
  }
}

Full code and live demo on CodePen.

Shout if you have any questions.

Thanks!

Hello @hifumi,

Sorry. I should have been more specific for the long-term fix.

I wouldn’t alter the index.php or footer.php files. These are core WordPress files that can be overwritten any time WordPress is updated.

The better approach is to use the code samples I provided in your child theme’s functions.php.

Please read up on WordPress template files, child themes, and wp_add_inine_script (to specify to load the Masonry library first before your inline).

BTW, the code I shared with you earlier already has a check to display only on certain pages. You should alter this array to add/remove for your specific pages.

if( is_page( array( 'about-us', 'contact', 'home' ) ) ) {

If you didn’t realise this earlier, I recommend brushing up on your PHP.

Happy coding 😉

Hello @hifumi,

index.php is the main WordPress template file. So, your JS code is being called in every page that uses/inherits from index.php. This is mostly likely why you’re seeing the Reference error.

The quick fix is to modify your JS to test for Masonry first or wrap it in a try/catch.

I’ve got code samples of this in CodePen.

The long term fix is insert your inline JS only for the page you need it using the WordPress hook API.

Here’s an example.

<?php
/* Add inline JS in the footer for specific pages. */
function add_my_js_script_to_wp_footer() {
    if( is_page( array( 'about-us', 'contact', 'home' ) ) ) {
    ?>
        <script>
            // Masonry JS goes here.
        </script>
    <?php
    } // if
}
add_action('wp_footer', 'add_my_js_script_to_wp_footer');

However, this inline might be loaded before Masonry lib is loaded. So, you’ll see the JS error once again. That means you’ll need to use something like this when you enqueue Masonry:

wp_add_inline_script('MASONRY_HANDLE_GOES_HERE', $the_script_source_above_stuffed_in_a_variable, 'before');

Please read up on wp_add_inine_script if this is the case.

Thanks!

• This reply was modified 5 years, 9 months ago by mark l chaves. Reason: Typo

Hey Everyone,

If you have an active custom login URL, it will interrupt the connection process between Google Analytics and MonsterInsight.

Just like @carganet mentions, try temporary disabling any custom login URL plugin (or any code that does a login redirect) to let the connection process run its full course. When it’s done, enable your custom login/redirect code.

Thanks!