. .
ShallHelp

×


| Home | home
| Consumers |
| Quote |
| Licensed Professionals |
| Clients |

| EXPLORE |
| Community / Forum |
| Articles / Blogs |
| Members Chat |

| MY ACCOUNT | person
| Sign In or Register |
| Missions |
| Tech Team |

18 thoughts on “Session: Sept. 04 2020, Friday

  1. I am finding PHP Warning: strpos(): Empty needle errors on lines 558 still. Earlier I tried using old codes but error showed on Line 550 so reverted back. I’ll check the functions files next. I’m enabling disabling chat for now until I find out what’s causing it.

  2. This is what’s causing the issue:

    Lines 559 – 573

    if (strpos($current_url, $needle) !== false) {

    wp_register_script('sac', $resource_url, array('jquery'), $sac_version, true);
    wp_enqueue_script('sac');

    }

    }

    } else {

    wp_register_script('sac', $resource_url, array('jquery'), $sac_version, true);
    wp_enqueue_script('sac');

    }
    }

    Comparing codes with CLG. Tried renaming, but the quick fix I think would be to revert back to an earlier version. With the WP update, not all scripts can catch up. So, last resort is to just use same version as CLG. More stable.

  3. I’ll just remove it and install the same from CLG. I can’t keep it here because each & every chat post will trigger the error. Heavy load on our error logs.

  4. Finished reverting to CLG version, and then reconfigured everything from default. I ended up causing errors in CLG too. Arrggggg … It’s fixed now. Hopefully. Will just see when it actually auto-refreshes.

  5. Also for CLG, the chat URLs are only on 2 pages, for SH it is four, since I included an custom chat html on the forum widget. On CLG, I did not. (lesser distraction for those wanting to read scripture, since the chat has a bell sound, so I kept that on a page or just the pop up instead.

    1. I have specified which URLs because if I don’t, then when a user clicks submit, it shows a javascript error. Also specifying specific URLs where the chat is allowed is important so that it’s not loading on ALL the pages (affects load time, as it is) At CLG we have a couple of thousand pages and posts already, that’s how we keep average load speeds a little bit faster. (Fact Check today – Fast (1.219 Seconds), 72% of sites are slower
      Average Load Time)

    2. Also here at SH, we have a whole lot of screenshots of our old products high resolution images we need to just backup and remove from the server.

  6. Clearing all the error logs again since I must have generated and triggered 100 warnings / errors while testing what works and what doesn’t. 99 failures before I got to the 100th that worked!

  7. ADMINS, DO NOT UPDATE ANYTHING! or before you do, do a backup first.

    CLG is fully backed up so I can easily restore. \o/ (backed up by God too! LOL! )

  8. I completed the following on the CLG Main Site

    2 Chronicles = 73 Webpages
    Link 2 Chronicles added to Menu added on the Top Menu

    Links to 1 Chronicles added to Drop Down Menu
    Links to 2 Chronicles added to Drop Down Menu

    Had to go back to all the first 70 pages because I noticed the “Next” buttons added manually were not in BOLD.

    Okay, coffee break and time to eat.

    Fasting really helps in FOCUS! Thank you Jesus! 🙂 I am breaking my fast. Time for BRUNCH!

    1. Don’t get distracted by that other site. You have your own ministry to work on. 😀

  9. 5:30 to 10:00am = 4.5 hours (270 minutes) = average 3.70 mins per webpage. (completion of the 73 webpages earlier)

    Ezra 21
    Nehemiah 27
    Esther 17
    Job 50
    Psalms 151
    Proverbs 37
    Ecclesiastes 24
    Song of Solomon 20
    Isaiah 107
    Jeremiah 90
    Lamentations 6
    Ezekiel 84
    Daniel 29
    Hosea 29
    Joel 9
    Amos 17
    Obadiah 5
    Jonah 8
    Micah 14
    Nahum 5
    Habbakuk 10
    Zephaniah 8
    Haggai 6
    Zechariah 24
    Malachi 11

    809 more webpages to go …

    809wp X 3.70mins = 2993.30 / 60mins = 49.89 hours

    “I can do all things through Christ who strengthens me.”

Comments are closed.