Forum Replies Created

Viewing 15 replies - 61 through 75 (of 102 total)
  • Thread Starter 1waytoheaven

    (@1waytoheaven)

    Yes, I confirm the h1 code works as required ?? Many thanks.

    I didn’t use the .h3 code, because I can control that parameter within WP editor, it’s just the H1 Titles on posts and pages that Neve controls that needed this tweak.

    So, to hopefully close-off this thread, and help others who may be needing to centre justify their site titles, this is the “Additional CSS” code I now have in my Neve theme Customiser.
    (Note: I discovered the order of the lines is important to make it function properly.)

    h1.title.entry-title {
        text-align: center;
    }
    
    .layout-grid .content>.blog-entry-title {
       text-align: center !important;
    }
    
    .nv-page-title-wrap.nv-big-title .nv-page-title h1 {
        text-align: center !important;
    }
    Thread Starter 1waytoheaven

    (@1waytoheaven)

    The h1 tile is now center justified on Posts, but…

    I notice that on Pages the h1 Title is still left justified instead of center justified.

    So I looked in browser Developer tools and Web Inspector and fished out this code to try, but it didn’t work, can you refine it for me please?

    h1.page.title {
        text-align: center;
    }

    Here’s a sample Page for you to inspect:

    https://www.born-again-christian.org/news/lifelines-devotional/

    Thread Starter 1waytoheaven

    (@1waytoheaven)

    Thank you for your help.

    The key change that made it work, was simply lifting the css code to the top of the “Additional CSS” code blocks.

    So the order of blocks of code in Customizer > Additional CSS is significant.

    Thread Starter 1waytoheaven

    (@1waytoheaven)

    Bingo!

    That got it ??

    Now centre justified h1 titles on the Hoempage, and on article inner posts.

    Many thanks for your diligence and patience with me.

    Resolved.

    Thread Starter 1waytoheaven

    (@1waytoheaven)

    Thank you Vytis, well done for taking the trouble to investigate, and illustrate your code works ??

    The screen shot you provided, is of an inner article page, not from the Homepage.

    I confirm that your code does now work on the article pages (after I placed it at the top of the “Additional CSS”) but the same h1 Title is still left justified on the homepage.

    I moved your code to the top of the “Additional CSS”, purged all LiteSpeed caches, and my browser cache, and though the h1 header is now centre justified on the article pages inside, h1 titles on the homepage are still left justified.

    (Homepage is the front page of the site, I think Neve calls it the “Blog”.)

    https://www.born-again-christian.org/news/

    The only code I have in Additional CSS is as follows;

    h1.title.entry-title {
        text-align: center;
    }
    @media only screen and (max-width: 480px){
    
    .is-menu-wrapper {
       display: none !important;
    }
    	
    }
    @media only screen and (min-width: 481px) and (max-width: 910px){
    	
    .is-menu-wrapper {
       display: none !important;
    }

    I don’t see any syntax errors there… can you Sir?

    I’d like to get the Header titles centre justified on the Homepage as well.

    Thank you helping me make progress!

    PS. The CSS code after the h1 code was needed to stop a search box appearing and obscuring the Hamburger icon on mobile size screens. So I still need it in there.

    Thread Starter 1waytoheaven

    (@1waytoheaven)

    Thank you Vytis, I thought I’d been forgotten.

    I removed the previous h1 additional css code, and inserted your suggestion instead;

    h1.title.entry-title {
        text-align: center;
    }

    Purged all LiteSpeed caches, and browser caches, but the Heading is still left justified, on the homepage and on the article pages.

    No idea why these changes don’t have any effect.

    Thread Starter 1waytoheaven

    (@1waytoheaven)

    I noticed the plugin was updated today, so I installed the update, cleared all caches, and reactivated it.

    The bug described above is stillpresent I’m afraid, no change.

    So we had to deactivate it again again.

    Thread Starter 1waytoheaven

    (@1waytoheaven)

    To clarify:
    The error message displayed is what the plugin terms “The Alert”, but it is shown only as plain text at the very bottom of the page, preceded by the word error:

    Meanwhile the protecting features still function.

    I tried Re-activating the plugin, and turned each free option on, one at a time; but they all caused the bug.

    I notice (if it helps solve this), that the error text doesn’t show immediately the page loads, it shows only after the Lazy Load has taken effect on each image on the same page, so maybe there’s a confilct with Lazy Load type plugins.

    Thread Starter 1waytoheaven

    (@1waytoheaven)

    Thank you, I placed the code in “Additional CSS” in the Neve theme, flushed the browser, and the site’s LiteSpeed cache (Purge All), and refreshed the page, but the heading is still left justified. It is the same on the; Homepage, article Posts, and the Pages in the Main menu.

    I don’t understand why this isn’t working.

    In Developer Tools I see the CSS code for this Post Title, for example, as follows:

    <div class="entry-header"><div class="nv-title-meta-wrap"><h1 class="title entry-title ">Quick Prayer Keys</h1></div>

    But even with your suggested “Additional CSS”, I see no change on the live post.

    I am using Neve with the Neve Child theme.

    Thread Starter 1waytoheaven

    (@1waytoheaven)

    Q/
    did you also enable JS Combine External and Inline ?
    /Q

    Yes, and Load Inline JS is set at Default.

    Thread Starter 1waytoheaven

    (@1waytoheaven)

    I used your guide here:

    https://docs.litespeedtech.com/lscache/lscwp/ts-optimize/

    I read and followed it very carefully.

    There’s no mention of using ?LSCWP_CTRL=before_optm on there anywhere yet.

    You will be frustrating further plugin users until you fix your guide.

    I ran the exclude test on the JS files (before optimization) again today with the same negative outcome.

    In addition, I re-tested adding just these excludes, which previously fixed the bug…

    wp-content
    wp-includes

    But today that does not fix the bug!

    This is plainly a waste of time, and so JS Combine is now OFF, until you fix the plugin code, and your Troubleshooting guide.

    “Sigh”

    1waytoheaven

    (@1waytoheaven)

    .nv-page-title-wrap .nv-big-title .nv-page-title {
       
        text-align: center;
    }

    This css didn’t work for me in the latest ‘Neve’ update put in ‘Additional CSS’.

    I then tried inserting it in style.css in the Child theme, but it still made no difference.

    Homepage and article Titles are still Left justified by default.

    Still waiting patiently for a response…

    Thread Starter 1waytoheaven

    (@1waytoheaven)

    Recap:
    When I looked in wp-content/plugins I saw 23 js files.

    After excluding each by full path name, NONE of those was the culprit.

    Further Test:

    When I look at the Homepage in Safari, and use the Developer Tools pane>Network>JS

    I see ten JS files listed as follows:

    
    https://www.born-again-christian.org/news/wp-content/litespeed/cssjs/52c67.js?2898c
    https://www.born-again-christian.org/news/wp-content/litespeed/cssjs/0811b.js?bcbaf
    https://www.born-again-christian.org/news/wp-content/plugins/wp-date-remover/public/js/wp-date-remover-public.js
    https://www.born-again-christian.org/news/wp-content/themes/neve/assets/js/build/modern/frontend.js
    https://www.born-again-christian.org/news/wp-content/litespeed/cssjs/90eda.js?03f7a
    https://www.born-again-christian.org/news/wp-content/litespeed/cssjs/aef86.js?08fde
    https://www.born-again-christian.org/news/wp-content/plugins/add-search-to-menu/public/js/ivory-search.min.js
    https://www.born-again-christian.org/news/wp-content/plugins/wordfence/js/admin.ajaxWatcher.1607007971.js
    https://www.born-again-christian.org/news/wp-content/litespeed/cssjs/6af20.js?8fb63
    

    Excluding ALL of those ten files, Purge All, did NOT cause the Hamburger to function.

    After I reloaded the same homepage in Safari, Dev. Tools>Network>JS

    There are now only five js files listed, as follows;

    
    https://www.born-again-christian.org/news/wp-includes/js/jquery/jquery.min.js
    https://www.born-again-christian.org/news/wp-content/plugins/wordfence/js/admin.ajaxWatcher.1607007971.js
    https://www.born-again-christian.org/news/wp-content/plugins/wp-date-remover/public/js/wp-date-remover-public.js
    https://www.born-again-christian.org/news/wp-content/themes/neve/assets/js/build/modern/frontend.js
    https://www.born-again-christian.org/news/wp-content/plugins/add-search-to-menu/public/js/ivory-search.min.js
    https://www.born-again-christian.org/news/wp-content/litespeed/cssjs/a03f6.js?3dd1a
    

    Excluding that list, purge all, >> No difference. QED.

    That is what I expected, because the test is not logical.

    I already tested them individually, with the same result.

    I have once again had to switch OFF JS Combine to get the Hamburger working on our site Homepage.

    • This reply was modified 4 years ago by Yui. Reason: please use CODE button for proper formatting
    Thread Starter 1waytoheaven

    (@1waytoheaven)

    I’ve just now re-tested Pagespeed with the JSCombine turned ON: 99 on Mobile, 100 on desktop… BUT of course the Hamburger is broken, so mobile visitors cannot access the site menu!

    So I have had to switch OFF JS Combine again, with the PageSpeed score greatly reduced to 83 on Mobile and 99 on Desktop.

    With JSCombine OFF, at least the hamburger works.

    “Sigh”

    You suggest:

    what if you put these 23 sub-dir into the list ?
    
    another way , open dev tool , on network tab , choose JS files
    
    then open your page, dev tool will list out all the JS files this page loads
    
    now save the JS files list , use that list to exclude , see how it goes
    
    if either 23 sub-dirs or all JS list works
    
    you can then try to remove them one by one (or few at the time) to narrow down which one was it

    But that is not logical, I have already tested each item of the 23 individually in the list without ANY of those sub-dirs evoking the problem.

    I copied their names using Developer Tools so there was no “finger-trouble”.

    It is not a logical suggestion Sir.

    Thread Starter 1waytoheaven

    (@1waytoheaven)

    Q/
    so you mean , it needs both to be excluded to make it work ?
    /Q

    Yes.

    I then did as you suggested, with JS Combine ON.

    I removed the wp-content/plugins exclude, and replaced it with one of the 23 sub-dirs in that plugins folder, I purged all and flushed browse after each one…

    However, excluding none of those caused the Hamburegr to work.

    Strangely, I then put back in just the

    wp-content/plugins
    wp-content/themes

    Purged all, and browser cache… BUT the Hamburger no longer works!

    Note: We are testing this is on the site Homepage in FF (the site landing page and most important page on the site), the Hamburger has always worked on the actual article pages (the “blog posts”)

    This is not proceeding according to logic, so unless you have an insight that really will fix it, we better leave it, until you do.

Viewing 15 replies - 61 through 75 (of 102 total)