autotutorial

4.9 for php 7.2 PHP 7.2 (WordPress core)

Sorry, first domain.

# Canonical WWW/HTTPS
<IfModule mod_rewrite.c>
	RewriteCond %{HTTP_HOST} ^example\.com [NC,OR]
	RewriteCond %{HTTPS} off
	RewriteRule (.*) https://www.example.com/$1 [L,R=301]
</IfModule>

If start different example.com or not use https, redirect default domain, to https://www.example.com/ ( otherwise https is in use in another domain https://subdomain.example.com/ )

This for http or www.example.com and target https://example.com

# Canonical HTTPS/non-WWW
<IfModule mod_rewrite.c>
	RewriteCond %{HTTPS} off [OR]
	RewriteCond %{HTTP_HOST} ^www\.example\.com [NC]
	RewriteRule (.*) https://example.com/$1 [L,R=301]
</IfModule>

This for http or example.com and target https://www.example.com

# Canonical HTTPS/WWW
<IfModule mod_rewrite.c>
	RewriteCond %{HTTPS} off [OR]
	RewriteCond %{HTTP_HOST} ^example\.com [NC]
	RewriteRule (.*) https://www.example.com/$1 [L,R=301]
</IfModule>

General settings – https://www.example.com

try creating the network with your ip for internet.
secondary sites will take the same path as the network.
Network – http://82.64.xx.xx/WordPress/wp-admin/network/
Secondary site – http://82.64.xx.xx/WordPress/ns1/ (adding ns1 to the creation of secondary sites).
Restrictions

https://network.com/wp/wp-admin/network/site-info.php?id=2 (https://network.com/wp/ns1/ for example) – secondary site.

secondary installaction WordPress – https://network.com/wp2/

It deletes the superfluous contents in the secondary site inside the multisite.
Search and replace to old site into new site, old https://network.com/wp2/ new https://network.com/wp/ns1/ (secondary site)
For Database normally a search is not recommended and replace raw, use a plugin or a php script to do this job.
It is also true that you cannot search and replace that is already used. It means if you have multisite wp/ and single site wp2/ you don’t have to replace with these paths .. Even if in htaccess there is the rule if it is not file go to index.php, at most it replicates the single on a single instance.
Maybe you don’t really need to change the path in the xlm file generated by the import (I hope wordpress translates the old path into the new one automatically into secondary site WordPress multisite)

Plugin or script https://wordpress.org/support/article/moving-wordpress/#changing-your-domain-name-and-urls
obviously you need to create backups of your files and database before deleting (files and databases) the secondary installation.
Import xml into https://network.com/wp/ns1/ (secondary site)

<?php 
function yournamefunction() {
$create = get_post_modified_time('d/m/Y \a\l\l\e g:i A',true );
return $create;
}

add_action('get_the_time','yournamefunction');

does it work for you? With $gmt to true

WordPress 5.3 add supports array for register_post_type() https://make.wordpress.org/core/2019/10/15/miscellaneous-developer-focused-changes-in-5-3/
Add args before wordpress 5.3 supports had no arguments, mistakenly you could use supports with a string value, from WordPress 5.3 must be Array.
Compatibility php 7.4, it is required that the variable is initialized in the type of final data.
This generates a warning

$val = false;
$val[0];

So for theme and plugin make sure they are tested with the current version Tested up to: WordPress version https://make.wordpress.org/plugins/2017/08/29/minimum-php-version-requirement/
WordPress 5.3 core supports php 7.4

WordPress and PHP 7.4

• This reply was modified 6 years, 5 months ago by autotutorial.
• This reply was modified 6 years, 5 months ago by autotutorial.

There are many factors for the management of a multiple site, the secondary sites are functional only with the rewriting of the url (htaccess for APACHE rewriting for ningix) the wp-config.php contains the reference for your network.
If you don’t have support from your hosting, you need to consider moving to another hosting.
Are you with ningix under APACHE or do you only use APACHE?
Does your hosting allow you to disable your cache / CDN if you need it?