FM / classicpress

/var/softaculous/classicpress

Name	Size	Mode	Actions
images/	-	0755	rm
php53/	-	0755	rm
php56/	-	0755	rm
php71/	-	0755	rm
php81/	-	0755	rm
.htaccess	419	0644	edit dl rm
check_charset.php	1859	0644	edit dl rm
clone.php	16096	0644	edit dl rm
edit.php	5283	0644	edit dl rm
edit.xml	628	0644	edit dl rm
extend.php	4051	0644	edit dl rm
fileindex.php	305	0644	edit dl rm
import.php	5851	0644	edit dl rm
info.xml	2962	0644	edit dl rm
install.js	924	0644	edit dl rm
install.php	19877	0644	edit dl rm
install.xml	1261	0644	edit dl rm
md5	1438	0644	edit dl rm
notes.txt	1733	0644	edit dl rm
sign_on.php	1010	0644	edit dl rm
soft.htaccess	127	0644	edit dl rm
wp-config.php	2752	0644	edit dl rm
_htaccess	271	0644	edit dl rm
_index.php	59	0644	edit dl rm
_wp-config.php	3035	0644	edit dl rm

Edit: /var/softaculous/classicpress/notes.txt (1733B)

1. While manual installation keep root writable and configure .htaccess and _htaccess.

2. The following files _wpconfig.php and .htaccess have to be configured if the user selects to install with Multisite and also the multisite.sql should be made with the new tables that are created after configuring the Multisite Option.

3. (101, 'rewrite_rules', '', 'yes'), Keep it blank, ClassicPress generates it automatically

4. In multisite sql
After Configuring the Network, dump the SQL before logging in.

5. The multisite.sql is the whole SQL file and also remove the INSERTS in the Options table that are made after login i.e from 'CRON' except 
INSERT INTO `[[dbprefix]]options` VALUES
(100, 'rewrite_rules',''), Keep it blank, ClassicPress generates it automatically
(115, 'can_compress_scripts', '0', 'yes'); 
also change the AUTO INCREMENT as it is in the dumped SQL of Original database.

6. (14, 1, 'session_tokens', 'a:1:{s:64:"e5043af8ebbd5602c6df6fca2ab4f7a7f09d80484487b1a1698c449455dc8f9a";i:1416717670;}'), and 
	(17, 1, 'community-events-location', 'a:1:{s:2:"ip";s:11:"";}'), will be created in usermeta table. If doesn't then create token and add it.

7. We detect if the server has capability to use utf8mb4, we have changed define('DB_CHARSET', 'utf8mb4'); to define('DB_CHARSET', '[[utf8]]'); in both config file and updated COLLATE utf8mb4_unicode_ci to [[collate]] in both sql

8. configure [[permalink_structure]] only in classicpress.sql. Not in multisite.sql.

9. _index.php is our file no need to change it.

10. Remove Storage ENGINE "ENGINE=InnoDB" from all the CREATE TABLE queries in classicpress.sql and multisite.sql as ClassicPress sets the storage engine based on the default set in the MySQL Server.

1. While manual installation keep root writable and configure .htaccess and _htaccess. 2. The following files _wpconfig.php and .htaccess have to be configured if the user selects to install with Multisite and also the multisite.sql should be made with the new tables that are created after configuring the Multisite Option. 3. (101, 'rewrite_rules', '', 'yes'), Keep it blank, ClassicPress generates it automatically 4. In multisite sql After Configuring the Network, dump the SQL before logging in. 5. The multisite.sql is the whole SQL file and also remove the INSERTS in the Options table that are made after login i.e from 'CRON' except INSERT INTO `[[dbprefix]]options` VALUES (100, 'rewrite_rules',''), Keep it blank, ClassicPress generates it automatically (115, 'can_compress_scripts', '0', 'yes'); also change the AUTO INCREMENT as it is in the dumped SQL of Original database. 6. (14, 1, 'session_tokens', 'a:1:{s:64:"e5043af8ebbd5602c6df6fca2ab4f7a7f09d80484487b1a1698c449455dc8f9a";i:1416717670;}'), and (17, 1, 'community-events-location', 'a:1:{s:2:"ip";s:11:"";}'), will be created in usermeta table. If doesn't then create token and add it. 7. We detect if the server has capability to use utf8mb4, we have changed define('DB_CHARSET', 'utf8mb4'); to define('DB_CHARSET', '[[utf8]]'); in both config file and updated COLLATE utf8mb4_unicode_ci to [[collate]] in both sql 8. configure [[permalink_structure]] only in classicpress.sql. Not in multisite.sql. 9. _index.php is our file no need to change it. 10. Remove Storage ENGINE "ENGINE=InnoDB" from all the CREATE TABLE queries in classicpress.sql and multisite.sql as ClassicPress sets the storage engine based on the default set in the MySQL Server.