ChristianLifeGroups.com transition from WordPress to CMSbyCW has begun

2026/03/26

- Deployed fresh instance of CMSbyCW at CLG. 

- Created "How To Change Website Colors" tutorial.

- Matthew Chapter 1 to 8

- manual code clean up of video files(applies to all Gospel topics). 

2026/03/27

- Matthew Chapter 9

2026/03/28

- Matthew Chapter 10 to end. 

2026/03/29

- Completed Mark 

2026/03/30

Luke 1 to 11

2026/03/31

- Paused at Luke 11 1-13.  

Current Challenge

While recreating timestamps, I ran into an issue with duplicate entries affecting how posts were displayed.  

Each post uses an index number tied to publish date/time, so the duplicates caused some posts to appear out of order.

So I paused.  I was pissed off, then regrouped. 

No point in recreating the WordPress based timestamps, because it is now being published on CMSbyCW. 

And if I am to post the actual dates they were first published, I wouldn't really know that.  

It's King James Version.  :-) 

So I then decided to let CMSbyCW post the NEW timestamps.  

So, continuing on.... 

Why did I think it will take a while? 

Looking at the source codes of the WP Bible stories, the codes on the audio files got changed.  (I didn't change it, because I knew how I programmed it originally - simple and what would make sense).  

So the "whoever/whatever did the hacks changed the codes to look like this: 

"[audio mp3="https://www.christianlifegroups.com/wp-content/uploads/2021/12/Luke_11_14-23_Jesus_and_Beelzebul.mp3%22][/audio]"

Notice this:

"

and 

3%22 

So it will NOT display on the front end as designed.  It will look and be broken.  Those "automatic" changes (that happen on autoupdates at times) programmatically changed all the "quotation marks".  Grrrrr.

AND THEN, on some posts, on the front end, it displays: 

<p>No items found.</p>

Right?  

What did scripture say about the ant?  

Or the parable of the wheat and tares?  

Well, scrutinizing the source codes, the file paths are still there.  It just got "corrupted, literally".

I just need to fix and tweak and update it.  

About 475 Audio Files of them.  

(And I haven't even told you about the process it took to record those files, to upload as raw audio, then download to convert into mp3s for the web, completed years ago).

That's fine.  

That's what troubleshooting is about.  You fix the trouble that you did not even cause..

That's nothing compared to what Jesus Christ suffered on the cross, getting crucified for all of mankind's sins.  Past, present, and future sins. 

So this tech chaos is indeed agitating, but I thank God that at least He gave me the technical wherewithal to even know how to fix it.   

So off I go.  

Don't sweat the small stuff.  

(It's all small stuff).  :-) 

2026/04/06

- Completed Luke.  

- In the process, well, there were Holy Days, Good Friday up to Easter Sunday .. I rested some.

- I also customized CLG, the header and the footer, I added Search functionality on the dropdown menu.  

- I will keep the WP active until I finish copying the text part of the entire Text and Audio Bible into the CMS. 

- I would have to do that by installments.  Looking at the timestamps above, well, it will take a while too.

This Bible App is intentional, as I have color codes on the fonts as well. The words of the Lord Jesus and God are in RED, the Angels' words are in orange, and the rest is black.  I also capitalize references to the Lord (He , Him , Thou) ... and no, I'm not referring to the types of crazy pronouns these days (LOL!), I did that also on the first go round of my bible text app, but there were some pronouns that escaped capitalization.  This process helps me catch the errors of my typos and ways. 

Typing and  reading God's Words - or Jesus' Words - causes me to pause.  I don't know how many people this Bible app (WordPress version) has helped over the past 5+ years ,,, but I know it has helped at least ONE:  ME. 

Hopefully, with the transition from WP to CMSbyCW, it will be much easier for the next Admin who will inherit this Digital Ministry / Mission, to spread the Gospel of Jesus Christ. With this little time line, I need to post this on the CMS and the Tech Site as well. 

So far, there's  400 web pages on the Text Bible App ... I just counted.  And there's a lot more left to work on.  And yes, wow, no database!  Just guts!  LOL!  

Each individual webpage, that has a text Bible topic. also has its accompanying audio file. 

I think I already typed earlier how I would have to manually fix each page with the correct codes to the file paths of the audio files and also listen to each audio file while going through the steps. 

Like an ant. 

One by one.  And I am amazed at what God can allow us and empower us to do and accomplish. 

A couple of nights ago, I saw a video on You Tube of a teacher, who knew he was going to lose his ability to see - he would be losing his vision, so he prepared his children and taught them how to drive, how to run their little business, in preparation for him going blind. Then he went blind.  

I was in tears. 

He shared his testimony about asking his wife to look for something online that would help him LISTEN to the Bible, since he can no longer READ the Bible.

So yeah, I was in tears. 

There are people who are NEEDING to LISTEN to the bible, so that's why God allowed me to build the Audio Gospels Playlist. 

Faith comes by hearing - God's Words have power indeed. 

And we all need Hope that we can only find in Christ. 

Yes, there are struggles in the world, tech problems, etc., but you know what? 

God always helps those who ask Him for wisdom on what to do next. 

We are all just called to plant seeds of His Words. 

But God makes them grow. 

If the seed I plant is HTML or PHP, so be it.  :-) 

The Gospel According to Luke is complete on the CMS.  :-) 

The Gospel according to John is next...