RossMitchell

You are correct, the posts are stored in a database, as are other aspects of your website content.
The answer is to backup the database, and then restore it in the new hosting account.
You do not mention if you will be changing the website’s domain.
There is a plugin called DUPLICATOR that helps with this.
Suggest you ask your hosting support to assist with this.
This article also covers various issues:

Moving WordPress

I did a google on:
phpmailer_init action hook example
(it was google that suggested adding example)
Among the links is:
https://developer.wordpress.org/reference/hooks/phpmailer_init/
With an example:

function my_phpmailer_example( $phpmailer ) {
    $phpmailer->isSMTP();     
    $phpmailer->Host = 'smtp.example.com';
    $phpmailer->SMTPAuth = true; // Ask it to use authenticate using the Username and Password properties
    $phpmailer->Port = 25;
    $phpmailer->Username = 'yourusername';
    $phpmailer->Password = 'yourpassword';
 
    // Additional settings…
    //$phpmailer->SMTPSecure = 'tls'; // Choose 'ssl' for SMTPS on port 465, or 'tls' for SMTP+STARTTLS on port 25 or 587
    //$phpmailer->From = "you@yourdomail.com";
    //$phpmailer->FromName = "Your Name";
}
add_action( 'phpmailer_init', 'my_phpmailer_example' );

So you are able to develop your website on localhost as long as you use the root login with no password. Then just do that.
Yes there is a curious problem as to what is wrong with your mcsga_user login, not sure it is worth sorting that out. Have you asked in the XAMPP support forum ?

Myself I use the gui of phpmyadmin to setup my localhost databases, suggest that you try that.

Something like:

.banner .slider .swiper-content p {
 color: black;
}

Suggest disabling the slider animation temporarily as the animation disrupts watching the css in your browser inspector.

Firstly restore your original httpd.conf file. There are no changes necessary for your original website.

You need to load a new set of WordPress files for the new website, it is best tyo keep them out of the “Program Files” space, the var directory will do. Make a sub directory for site2, also create a logs directory.

Add a new virtualhost block to your restored httpd.conf file like this:
(Note that it is on port 80 of 127.0.0.1)

#A new VirtualHost
<VirtualHost *:80>
	<Directory "C:/var/site2">
		Options FollowSymLinks Indexes
		AllowOverride All
		Order deny,allow
		allow from All
	</Directory>
	ServerName mynewhostname
	ServerAlias www.mynewhostname
	DocumentRoot "C:/var/site2"
	ErrorLog "C:/var/site2/logs/error.log"
	CustomLog "C:/var/site2/logs/access.log" combined
</VirtualHost>

Now add these two lines to your hosts file:

www.mynewhostname 127.0.0.1
mynewhostname 127.0.0.1

Then if you want to access your site2 from elsewhere on your LAN you do this:
– find the IP address that your server PC uses, something like 192.168.0.27
whatever it is say it is a.b.c.d
– On every computer that want to access your site2 that is on the LAN, add these lines to its hosts file:

mynewhostname a.b.c.d
www.mynewhostname a.b.c.d

Of course this requires that the IP address of the server never changes, there are ways to do this.

I do this by configuring my webserver using VirtUalHost technique, details here:
https://httpd.apache.org/docs/current/vhosts/
Then I put the domain names into my hosts file, details here:
https://en.wikipedia.org/wiki/Hosts_(file)

Sorry I don’t see any code.
Can you copy/paste it ? Or get a screenshot.
Suggest that you try different browsers and different computers.