| Current File : /home/mmdealscpanel/yummmdeals.com/notes.txt.tar |
var/softaculous/snipeit/notes.txt 0000644 00000002227 15034134747 0013262 0 ustar 00 1. Install Composer and create zip for package use "php composer.phar install --no-dev" command to install.
2. Copy .env.example to .env and fill the database details DB_HOST, DB_DATABASE, DB_USERNAME, DB_PASSWORD, DB_PREFIX and APP_URL
3. Run php artisan key:generate to generate APP_KEY in .env file.
4. Run "php artisan migrate" from command line before creating tables step in manual installation.(confirmed with vendor)
5. Add the following line to the .htaccess file in the root folder :
<IfModule mod_alias.c>
RedirectMatch 301 ^[[relativeurl]]/$ [[softurl]]/public
</IfModule>
6. PHP REQUIREMENT LINK: https://snipe-it.readme.io/docs/requirements
7. We have not added upgrade yet because script provides upgrade/migrate through composer only. https://snipe-it.readme.io/docs/upgrading
check everytime and add if possible
8. delete inserts of oauth_clients and oauth_personal_access_clients tables. It creates after login. (check in every version)
9. Keep the LIVEWIRE_URL_PREFIX=[[relativeurl]]/public parameter as it is required to load the livewire js files.
10. Delete bootstrap/cache/packages.php and bootstrap/cache/services.php files it gets generated on login. var/softaculous/postfix/notes.txt 0000644 00000000630 15034143013 0013261 0 ustar 00 1. set $CONF['configured'] = true; and also enter the database details in config.inc.php file in manual installation
2. PHP REQUIREMENT LINK : requirement display on setup page of installation (check composer.json as well).
3. Release date : https://github.com/postfixadmin/postfixadmin/releases/
4. Kept PHP requirement as 7.4 as mentioned by vendor (https://github.com/postfixadmin/postfixadmin/issues/879) var/softaculous/feng/notes.txt 0000644 00000001302 15034166214 0012511 0 ustar 00 1. Change the location of USING BTREE in the feng.sql file (It should be to the left and not to the end of line).
2. Default database engine InnoDB.
3. comment the php_value in .htaccess (NOT REQUIRED SINCE 3.4.1.1)
4. PHP REQUIREMENT LINK : https://wiki.fengoffice.com/doku.php/installation:server_reqs
5. We have disabled the upgrade in v3.5.1.5 because post upgrade from v3.4.4.1 to v3.5.1.5, the UI is broken and nothing is displayed except the header. Please check in the next version and enable upgrade accordingly. We had contacted vendor as well for the same via email and they said they shall fix it.
6. Tick Checkbox of Core_dimensions, Workspaces, Mail while manual installation (Since 3.8.1.24) var/softaculous/typo7/notes.txt 0000644 00000002703 15035103543 0012657 0 ustar 00 1. Install manually using composer package.
https://docs.typo3.org/m/typo3/reference-coreapi/12.4/en-us/Administration/Installation/ComposerMode/Index.html#installing-typo3-with-composer
2. TCP/IP based connection for manual installation (Database details)
3. check Take me straight to the backend.
4. PHP REQUIREMENT LINK: https://get.typo3.org/version/12#system-requirements
5. We have disabled the upgrade because this gives error when upgraded from 10.4.21. Check in next version and if it supports then enable it again. Aslo they have recommended to Upgrade through CLI which we can not offer.
6. Upgrade Documentation: https://docs.typo3.org/m/typo3/guide-installation/11.5/en-us/Index.html
7. To convert package installation to Composer compatible installation: (To upgrade installation which are installed through source zip package) https://docs.typo3.org/m/typo3/guide-installation/main/en-us/MigrateToComposer/Index.html
8. For Database upgrade through CLI
https://stackoverflow.com/questions/64874179/table-tx-scheduler-task-doesnt-exist-after-composer-typo3-cms-scheduler
https://docs.typo3.org/p/helhum/typo3-console/main/en-us/CommandReference/DatabaseUpdateschema.html
php vendor/bin/typo3cms database:updateschema "*.add,*.change"
9. .htaccess is our file to redirect the script to public directory.
10. We have not given installation based on CLI as the admin panel redirected to the blank page. Try to give CLI based installation from next version onwards. var/softaculous/zikula15/notes.txt 0000644 00000001020 15042070475 0013236 0 ustar 00 1) Please dont change $ZConfig['System']['system.chmod_dir'] = 0777; in config file as it is same i.e. 0777 when installed manually on cPanel also.
2) We have kept config.php bcoz it is required for upgrade from 1.3.x to 1.4.x. Kindly check upgrade process for 1.4.x to 1.4.x in next update and add it.
3) Table menu_items in not generated post upgrade from 1.4.x to 1.4.4 because menu module must be manually installed.(Confirmed with vendor)
4. PHP REQUIREMENT LINK : https://github.com/zikula/core/blob/1.5/INSTALL-Core1.x.md var/softaculous/whmcs82/notes.txt 0000644 00000003620 15044003424 0013064 0 ustar 00 1. data.zip is made by zipping the following folders from the package:
/downloads/
/templates_c/
/attachments/
2. Languages are seperate for admin account and enduser site. The files are there in the /lang/ folder for enduser and /admin/lang/ folder for admin languages.
Check if the languages we provide the files exists in the respective folders.
3. In sql keep 'SMTPPassword', 'FTPBackupPassword' and 'License' fields blank in `tblconfiguration` table.
4. We have disabled 5.3.10 on windows as it gives "Admin Directory Conflict" error even on manual installation. We have opened ticket to WHMCS for the same. Check in next version if it works then remove the check.(removed from 5.3.11)
5. In SQL `tbladmins` table we set only one password since we do not know the password hash. WHMCS creates the other password hash on 1st login.
6. Use config.php from crons/config.php.new. We explicitly do this to set Custom Crons Directory
7. Do not change uuid from tbladmins table as it is same for all installations.
8. We have removed below sql inserts from v7.2.1 and have confirmed with the WHMCS team via ticket, no need longer
INSERT INTO `tbltransientdata` VALUES
(1, 'RewriteBackup', '[{"before":[],"whmcs":[],"after":[]}]', 1525758986),
(2, 'detect-route-environment', 'El9q4', [[timestamp]]),
9. Also set the value for "InstanceID" to ''{blank} in "tblconfiguration" table since v7.2.1.
10. PHP REQUIREMENT LINK: https://docs.whmcs.com/System_Requirements
11. The below entries were added from 7.6.0 under tblconfiguration table. Check this in next version as well.
('domainLookupProvider', 'WhmcsDomains', '[[regtime]]', '[[regtime]]'),
('ReCAPTCHAForms', '{"checkoutCompletion":false}', '[[regtime]]', '[[regtime]]'),
('MDEFromTime', '[[regtime]]', '[[regtime]]', '[[regtime]]')
12. Value for "EulaAgreementAccepted" hash in `tblconfiguration` table is same for all installations. Hence we have kept it as it is. (Since 7.7.0) var/softaculous/whmcs83/notes.txt 0000644 00000003620 15044452646 0013103 0 ustar 00 1. data.zip is made by zipping the following folders from the package:
/downloads/
/templates_c/
/attachments/
2. Languages are seperate for admin account and enduser site. The files are there in the /lang/ folder for enduser and /admin/lang/ folder for admin languages.
Check if the languages we provide the files exists in the respective folders.
3. In sql keep 'SMTPPassword', 'FTPBackupPassword' and 'License' fields blank in `tblconfiguration` table.
4. We have disabled 5.3.10 on windows as it gives "Admin Directory Conflict" error even on manual installation. We have opened ticket to WHMCS for the same. Check in next version if it works then remove the check.(removed from 5.3.11)
5. In SQL `tbladmins` table we set only one password since we do not know the password hash. WHMCS creates the other password hash on 1st login.
6. Use config.php from crons/config.php.new. We explicitly do this to set Custom Crons Directory
7. Do not change uuid from tbladmins table as it is same for all installations.
8. We have removed below sql inserts from v7.2.1 and have confirmed with the WHMCS team via ticket, no need longer
INSERT INTO `tbltransientdata` VALUES
(1, 'RewriteBackup', '[{"before":[],"whmcs":[],"after":[]}]', 1525758986),
(2, 'detect-route-environment', 'El9q4', [[timestamp]]),
9. Also set the value for "InstanceID" to ''{blank} in "tblconfiguration" table since v7.2.1.
10. PHP REQUIREMENT LINK: https://docs.whmcs.com/System_Requirements
11. The below entries were added from 7.6.0 under tblconfiguration table. Check this in next version as well.
('domainLookupProvider', 'WhmcsDomains', '[[regtime]]', '[[regtime]]'),
('ReCAPTCHAForms', '{"checkoutCompletion":false}', '[[regtime]]', '[[regtime]]'),
('MDEFromTime', '[[regtime]]', '[[regtime]]', '[[regtime]]')
12. Value for "EulaAgreementAccepted" hash in `tblconfiguration` table is same for all installations. Hence we have kept it as it is. (Since 7.7.0) var/softaculous/whmcs81/notes.txt 0000644 00000003620 15044453143 0013072 0 ustar 00 1. data.zip is made by zipping the following folders from the package:
/downloads/
/templates_c/
/attachments/
2. Languages are seperate for admin account and enduser site. The files are there in the /lang/ folder for enduser and /admin/lang/ folder for admin languages.
Check if the languages we provide the files exists in the respective folders.
3. In sql keep 'SMTPPassword', 'FTPBackupPassword' and 'License' fields blank in `tblconfiguration` table.
4. We have disabled 5.3.10 on windows as it gives "Admin Directory Conflict" error even on manual installation. We have opened ticket to WHMCS for the same. Check in next version if it works then remove the check.(removed from 5.3.11)
5. In SQL `tbladmins` table we set only one password since we do not know the password hash. WHMCS creates the other password hash on 1st login.
6. Use config.php from crons/config.php.new. We explicitly do this to set Custom Crons Directory
7. Do not change uuid from tbladmins table as it is same for all installations.
8. We have removed below sql inserts from v7.2.1 and have confirmed with the WHMCS team via ticket, no need longer
INSERT INTO `tbltransientdata` VALUES
(1, 'RewriteBackup', '[{"before":[],"whmcs":[],"after":[]}]', 1525758986),
(2, 'detect-route-environment', 'El9q4', [[timestamp]]),
9. Also set the value for "InstanceID" to ''{blank} in "tblconfiguration" table since v7.2.1.
10. PHP REQUIREMENT LINK: https://docs.whmcs.com/System_Requirements
11. The below entries were added from 7.6.0 under tblconfiguration table. Check this in next version as well.
('domainLookupProvider', 'WhmcsDomains', '[[regtime]]', '[[regtime]]'),
('ReCAPTCHAForms', '{"checkoutCompletion":false}', '[[regtime]]', '[[regtime]]'),
('MDEFromTime', '[[regtime]]', '[[regtime]]', '[[regtime]]')
12. Value for "EulaAgreementAccepted" hash in `tblconfiguration` table is same for all installations. Hence we have kept it as it is. (Since 7.7.0) var/softaculous/whmcs89/notes.txt 0000644 00000003620 15044454033 0013101 0 ustar 00 1. data.zip is made by zipping the following folders from the package:
/downloads/
/templates_c/
/attachments/
2. Languages are seperate for admin account and enduser site. The files are there in the /lang/ folder for enduser and /admin/lang/ folder for admin languages.
Check if the languages we provide the files exists in the respective folders.
3. In sql keep 'SMTPPassword', 'FTPBackupPassword' and 'License' fields blank in `tblconfiguration` table.
4. We have disabled 5.3.10 on windows as it gives "Admin Directory Conflict" error even on manual installation. We have opened ticket to WHMCS for the same. Check in next version if it works then remove the check.(removed from 5.3.11)
5. In SQL `tbladmins` table we set only one password since we do not know the password hash. WHMCS creates the other password hash on 1st login.
6. Use config.php from crons/config.php.new. We explicitly do this to set Custom Crons Directory
7. Do not change uuid from tbladmins table as it is same for all installations.
8. We have removed below sql inserts from v7.2.1 and have confirmed with the WHMCS team via ticket, no need longer
INSERT INTO `tbltransientdata` VALUES
(1, 'RewriteBackup', '[{"before":[],"whmcs":[],"after":[]}]', 1525758986),
(2, 'detect-route-environment', 'El9q4', [[timestamp]]),
9. Also set the value for "InstanceID" to ''{blank} in "tblconfiguration" table since v7.2.1.
10. PHP REQUIREMENT LINK: https://docs.whmcs.com/System_Requirements
11. The below entries were added from 7.6.0 under tblconfiguration table. Check this in next version as well.
('domainLookupProvider', 'WhmcsDomains', '[[regtime]]', '[[regtime]]'),
('ReCAPTCHAForms', '{"checkoutCompletion":false}', '[[regtime]]', '[[regtime]]'),
('MDEFromTime', '[[regtime]]', '[[regtime]]', '[[regtime]]')
12. Value for "EulaAgreementAccepted" hash in `tblconfiguration` table is same for all installations. Hence we have kept it as it is. (Since 7.7.0) var/softaculous/symfony3/notes.txt 0000644 00000000517 15044474404 0013374 0 ustar 00 1. Download using composer command for zip
php composer.phar create-project symfony/website-skeleton symfony425 {version}
2. PHP REQUIREMENT LINK: https://symfony.com/doc/current/reference/requirements.html
3. Empty the contents of /var/cache/ folder while making zip, as it contains cache files made by composer which have softpaths.
var/softaculous/ostic14/notes.txt 0000644 00000001132 15044630747 0013071 0 ustar 00 1. schema_signature same for every install
2. Make script where Database ENGINE is InnoDB
3. Don't convert ostic.sql and languages files to utf8
4. PHP REQUIREMENT LINK : https://docs.osticket.com/en/latest/Getting%20Started/Installation.html
5. Download and update language from "https://osticket.com/download/#ostLang"
6. Check language update in next version(In 1.14.2 languages weren't properly updated)
7. If language packs doesn't download from site. Try to download using following URL depending upon script version.
https://s3.amazonaws.com/downloads.osticket.com/lang/1.14.x/[[LANG_CODE]].phar var/softaculous/ostic17/notes.txt 0000644 00000001205 15044631536 0013072 0 ustar 00 1. schema_signature same for every install
2. Make script where Database ENGINE is InnoDB
3. Don't convert ostic.sql and languages files to utf8
4. PHP REQUIREMENT LINK : https://osticket.com/download/ and also check include/class.setup.php
5. Download and update language from "https://osticket.com/download/#ostLang"
6. Check language update in next version(In 1.14.2 languages weren't properly updated)
7. If language packs doesn't download from site. Try to download using following URL depending upon script version.
https://s3.amazonaws.com/downloads.osticket.com/lang/1.14.x/[[LANG_CODE]].phar (languages are not available for 1.15, 1.16) var/softaculous/loaded7/notes.txt 0000644 00000000742 15044710540 0013116 0 ustar 00 1) Before manual installation provide proper writable permissions to directories(refer install.php or pre-install steps on loaded7 site).
2) For manual installation install twice i.e. with SSL and without SSL. and check for difference in each installed files and SQL.
3) Install with sample data.
4) Please create function to check required PHP Settings of enduser PHP binary.
5) Choose Database type : MySQL-InnoDB(Transaction-Safe)
6) Move images/ images to package and make zip. var/softaculous/ojs33/notes.txt 0000644 00000002460 15044737311 0012544 0 ustar 00 1. While installing on webuzo give writable permission to cache
2. Choose password encryption method sha1 (Not Required since 3.1.0.0)
3. Upgrade requires old installation to be deleted and have to safe guard config file and public folder. (confirmed by vendor). Everytime change version in upgrade.php __pre_unzip function. or remove condition of version in next update. (Added in 3.0.2.0) (REMOVED)
4. PHP REQUIREMENT LINK: https://docs.pkp.sfu.ca/admin-guide/3.3/en/requirements
5. Select MySQLi in manual installation.
6) Please check symlinks every time by checking difference in the original zip and ground zip and update in install.php, upgrade.php and clone.php.
7) Tick on all addition languages except English in manual installation.
8) We have made change in lib/pkp/classes/install/form/UpgradeForm.inc.php because on upgrading 3.2.1.3 version to 3.3.0.3 version was giving error. https://github.com/pkp/pkp-lib/issues/6703
9) Table "subscription_types" -> Column "non_expiring" this was not removed after upgrade from v3.3.0.8 to v3.3.0.9. Please check in the next version. (Not gets deleted in 3.3.0.10 version as well)
10) We have kept MYSQL 5.7.22 in info.xml to maintain compatibility with the later 3.4.x branch
https://forum.pkp.sfu.ca/t/omp-3-4-0-0-throws-syntax-error-sqlstate-42000-while-installation/79262 var/softaculous/4images/notes.txt 0000644 00000000164 15045027272 0013132 0 ustar 00 1. PHP REQUIREMENT LINK : docs/Installation.english.txt
1. RELEASE DATE : https://www.4homepages.de/forum/index.php
var/softaculous/elgg4/notes.txt 0000644 00000001573 15045374000 0012602 0 ustar 00 1) Add the elggdata folder to data.zip BUT delete all files of root folders of that elggdata
2) Take the data.zip after logging in the manual installation.
3) Timezone = America/New_York
4) PHP REQUIREMENT LINK: http://learn.elgg.org/en/stable/intro/install.html#requirements
5) Upgrade Documents http://learn.elgg.org/en/3.x/admin/upgrading.html (Try to add in next version)
6) Since there is no diff in sql from version 3.0.x to 3.0.x versions we have disabled third link i.e (setupcontinue='') in upgrade.php. Check this in next version and comment this to enable third link.(Added in Elgg 3.0.5)
7)We have enabled upgrade for Elgg versions 3.0.x (with minimum requirement 3.0.1). We haven't enabled upgrade for versions 2.3.x to 3.0.x, We have commented the code for the same in upgrade.php as we need to check for utf8mb4 collation conversion issue post upgrade.(Note added since 3.0.5) var/softaculous/lime5/notes.txt 0000644 00000003251 15045375043 0012616 0 ustar 00 1. (NOT REQUIRED NOW) We have added few variables in config.php so add them even if they are not in the current file (Now these variables are added in Database).
2. Keep MyISAM in MySQL database engine type while installing manually.
3. After installation if you get update notification then add
('updateavailable', '0'),
('updatelastcheck', '[[regtime]]'); In [[dbprefix]]settings_global table
4. We have removed auto upgrade for minor version. i.e when there is no change in Db we will display 3rd link.
5. PHP REQUIREMENT LINK : https://manual.limesurvey.org/Installation#Make_sure_you_can_use_LimeSurvey_on_your_website
6. We have disabled upgrade to version 3.x.x from previous versions i.e from 2.x.x and 1.x.x ,as 'Plugin manager' breaks after upgrade.(Please check and enable upgrade in next version if it works 2.x.x and 1.x.x and change minimum requirement accordingly.)(Since version 3.1.1+).
7. Upgrade enabled with minimum version 3.1.1+.
8. Important : Every time check and change the value of $DBVersion variable in upgrade.php by checking value of DBVersion from `".$__settings['dbprefix']."settings_global` table when there is a change in it.
9. Since 4.1.6+ installer asks for custom dbprefix during installation but takes default prefix (lime_) to populate database. Hence we have removed from install.xml Check in next version.(Checked in 4.1.8+ as well, not yet fixed) (re-enabled from 4.1.18+)
10. After 4.3.15+, we don't provide any further update to LimeSurvey 4.x , since those releases are labelled as 'Unstable' on their website. We have reverted to 3.x latest stable(i.e 3.25.3+) release post 4.3.15+. Provide update to 4.x only when the releases are mentioned as 'Stable'. var/softaculous/lime3/notes.txt 0000644 00000003251 15045375544 0012622 0 ustar 00 1. (NOT REQUIRED NOW) We have added few variables in config.php so add them even if they are not in the current file (Now these variables are added in Database).
2. Keep MyISAM in MySQL database engine type while installing manually.
3. After installation if you get update notification then add
('updateavailable', '0'),
('updatelastcheck', '[[regtime]]'); In [[dbprefix]]settings_global table
4. We have removed auto upgrade for minor version. i.e when there is no change in Db we will display 3rd link.
5. PHP REQUIREMENT LINK : https://manual.limesurvey.org/Installation#Make_sure_you_can_use_LimeSurvey_on_your_website
6. We have disabled upgrade to version 3.x.x from previous versions i.e from 2.x.x and 1.x.x ,as 'Plugin manager' breaks after upgrade.(Please check and enable upgrade in next version if it works 2.x.x and 1.x.x and change minimum requirement accordingly.)(Since version 3.1.1+).
7. Upgrade enabled with minimum version 3.1.1+.
8. Important : Every time check and change the value of $DBVersion variable in upgrade.php by checking value of DBVersion from `".$__settings['dbprefix']."settings_global` table when there is a change in it.
9. Since 4.1.6+ installer asks for custom dbprefix during installation but takes default prefix (lime_) to populate database. Hence we have removed from install.xml Check in next version.(Checked in 4.1.8+ as well, not yet fixed) (re-enabled from 4.1.18+)
10. After 4.3.15+, we don't provide any further update to LimeSurvey 4.x , since those releases are labelled as 'Unstable' on their website. We have reverted to 3.x latest stable(i.e 3.25.3+) release post 4.3.15+. Provide update to 4.x only when the releases are mentioned as 'Stable'. var/softaculous/elgg3/notes.txt 0000644 00000001573 15045375645 0012621 0 ustar 00 1) Add the elggdata folder to data.zip BUT delete all files of root folders of that elggdata
2) Take the data.zip after logging in the manual installation.
3) Timezone = America/New_York
4) PHP REQUIREMENT LINK: http://learn.elgg.org/en/stable/intro/install.html#requirements
5) Upgrade Documents http://learn.elgg.org/en/3.x/admin/upgrading.html (Try to add in next version)
6) Since there is no diff in sql from version 3.0.x to 3.0.x versions we have disabled third link i.e (setupcontinue='') in upgrade.php. Check this in next version and comment this to enable third link.(Added in Elgg 3.0.5)
7)We have enabled upgrade for Elgg versions 3.0.x (with minimum requirement 3.0.1). We haven't enabled upgrade for versions 2.3.x to 3.0.x, We have commented the code for the same in upgrade.php as we need to check for utf8mb4 collation conversion issue post upgrade.(Note added since 3.0.5) var/softaculous/ocart23/notes.txt 0000644 00000000776 15046307326 0013071 0 ustar 00 1. Change the value of config_error_display to "0" in ocart.sql
2. Have disabled upgrade in 2.1.0.1 due to Errors in 2.0.3.1 to 2.1.0.1 upgarde and few tables are not generating after upgrade. ( same issue for 2.1.0.2, In next release plz check upgrade from 2.0.3.1 and check DB changes. ). Have mailed vendor.
3. Try to add upgrade from 2.2.0.0 to 2.3.X.X. We have disabled it in 2.3.0.2 because front link is not loading due to change in extention path. http://forum.opencart.com/viewtopic.php?f=183&t=165958 var/softaculous/net2ftp/notes.txt 0000644 00000000444 15050412440 0013153 0 ustar 00 1. change "use_database" to "true" to use database
2. PHP REQUIREMENT LINK : https://www.net2ftp.com/index.php?state=homepage&state2=4b
3. The script is throwing syntax error on PHP 8.0 onwards and no specific information is given on website for PHP requiremenet. Hence we have restricted it. var/softaculous/soplanning/notes.txt 0000644 00000000474 15054076141 0013754 0 ustar 00 1)We have changed PHP requirements to 5.3.0 , since there was an issue on PHP 5.2.0 (in version 1.40).
2)PHP REQUIREMENT LINK : http://www.soplanning.org/en/download/
3) Timezone is hard coded in "sql\planning_mysql.sql" file
4) change SOPLANNING_API_KEY_VALUE's value with UUID() function in planning_config table. var/softaculous/classicpress/notes.txt 0000644 00000003413 15054140363 0014274 0 ustar 00 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.
11. PHP REQUIREMENT LINK: https://www.classicpress.net/requirements/ var/softaculous/x2/notes.txt 0000644 00000002356 15054142072 0012133 0 ustar 00 1. Manual Installation works on a suPHP server
2. Always make x2.zip file on Linux by zip command. Bcoz in js/ folder there are two files with same name. i.e x2chart.js & X2Chart.js. In windows it overwrites and keeps only x2chart.js in zip. So, Create zip on linux (not required any more)
3. Make `unique_id` in INSERT in table `x2_admin` as 'none' (script vendor asked us to make it 'none').
4. Timezone US/Pacific
5. No sample data while manual installation
6. If you get error on webuzo manual install then disable tokenizer, sqlite, pdo_sqlite, PDO, iconv, ctype
7. PHP REQUIREMENT LINK : https://www.x2crm.com/download/
8.Always make x2.zip file on Linux by zip command. Bcoz in /js/X2Flow folder there are two files with same name. i.e x2flowEditor.js & X2FlowEditor.js. In windows it overwrites and keeps only x2flowEditor.js in zip. So, Create zip on linux. since 6.9
email has been done to venfor for the same. Check this in next update.
9. Added restriction for less than PHP 7.1.0 due to non-compatibility over PHP 7.1 and 7.2 (mcrypt used in the script).
Max PHP restriction, mcrypt and openssl check removed in X2CRM 7.1, because installer doesn't configure "encryption.key" and "encryption.iv" file if openssl is not installed while manual install var/softaculous/wp/notes.txt 0000644 00000014116 15054142222 0012222 0 ustar 00 1. Download the language files from :
http://codex.wordpress.org/L10n:Localization_Teams (https://nl.wordpress.org/)
and copy them to the /var/softaculous/wp/languages/LANGUAGE_CODE.zip
2. The language files for the following languages have been updated to 6.8.1 :
<option value="bg_BG">Bulgarian</option>
<option value="ca">Catalan</option>
<option value="da_DK">Danish</option>
<option value="de_DE">German</option>
<option value="el">Greek</option>
<option value="es_ES">Spanish</option>
<option value="fa_IR">Persian</option>
<option value="fi">Finnish</option>
<option value="fr_FR">French</option>
<option value="hr">Croatian</option>
<option value="hu_HU">Hungarian</option>
<option value="id_ID">Indonesian</option>
<option value="it_IT">Italian</option>
<option value="ja">Japanese</option>
<option value="ko_KR">Korean</option>
<option value="nb_NO">Norwegian</option>
<option value="nl_NL">Dutch</option>
<option value="pl_PL">Polish</option>
<option value="pt_BR">Portuguese-BR</option>
<option value="pt_PT">Portuguese</option>
<option value="ro_RO">Romanian</option>
<option value="ru_RU">Russian</option>
<option value="sk_SK">Slovak</option>
<option value="sl_SI">Slovenian</option>
<option value="sq">Albanian</option>
<option value="sv_SE">Swedish</option>
<option value="tr_TR">Turkish</option>
<option value="vi">Vietnamese</option>
<option value="zh_CN">Chinese(Simplified)</option>
<option value="zh_TW">Chinese(Traditional)</option>
3. Please try to update these languages if they are available for 6.8.1
<option value="ar">Arabic</option>
<option value="cs_CZ">Czech</option>
<option value="he_IL">Hebrew</option>
<option value="th">Thai</option>
<option value="uk">Ukrainian</option>
<option value="zh_HK">Chinese (Hong Kong)</option>
4. To activate footer link add this
<!--SOFTACULOUS-->
in the following file in wp.zip
wp-content/themes/twentytwentyfive/patterns/footer.php
wp-content/themes/twentytwentyfour/patterns/footer.php
wp-content/themes/twentytwentythree/patterns/footer-default.php
NOTE : When a new theme is added in WordPress do the following tasks :
- add the line in install.xml and upgrade.xml as well
- add condition in upgrade.php ( in __pre_unzip function )
- update extend.php $templates['list']['wp-default'] array
- update new default theme screenshots in website/www/images/wp-default
5. 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.
The guide to install Multisite Manually :
https://wordpress.org/support/article/create-a-network/
6. (101, 'rewrite_rules', '', 'yes'), Keep it blank, WordPress generates it automatically
7. In multisite sql
After Configuring the Network, dump the SQL before logging in.
8. 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, WordPress generates it automatically
(115, 'can_compress_scripts', '0', 'yes');
also change the AUTO INCREMENT as it is in the dumped SQL of Original database.
9. Remove inserts in the sitemeta table after "active_sitewide_plugins" in MU
10. Remove the language files related to particular theme from languages/ if a theme is deleted by WordPress.
11. (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.
12. From 4.5.1 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 from 4.2.2
13. In case of major update please update the popularfx database.
14. While manual installation keep root writable and configure .htaccess as _htaccess.
15. configure [[permalink_structure]] only in wp.sql. Not in multisite.sql.
16. _index.php is our file no need to change it.
17. Remove Storage ENGINE "ENGINE=InnoDB" from all the CREATE TABLE queries in wp.sql and multisite.sql as WordPress sets the storage engine based on the default set in the MySQL Server.
18. when we add/delete a plugin update the edit.php and edit.xml file.
19. The language is configured in database under 'options' and 'sitemeta' tables for normal and multi site respectively. We use to manage language in version.php however this use to get reverted in case of persian language as observed. Hence we have now started handling in database and for multi site it was handled default in database. Also version.php is now removed because of this. (Since v4.8.1)
20. Boldgrid download link :
http://repo.boldgrid.com/boldgrid-inspirations.zip
21. We have added classic-editor plugin since 5.0.0 and we need to check in manual installation for extra insert classic-editor-replace under
options table. If any changes, change in install, edit, upgrade.
22. Remove __update_themes() and __update_plugins() functions only from the extend.php from the existing branch whenver you add a new branch. This means that this function shall only be a part of the current wp and not the old one's like wp50.
23. The WP_AUTO_UPDATE_CORE setting in wp-contig.php and _wp-config.php is added because when we install old version of WordPress we do not want it to auto upgrade to latest version because since WordPress 5.6 WordPress auto updates itself for major versions as well. When making the latest version as an old branch do not forget to add changes related to WP_AUTO_UPDATE_CORE in
install.php
wp-config.php
_wp-config.php
24. Do not encode wp-cli file. Keep it as it is.
25. Check the "[[punycode_softurl]]/?p=4" Auto Draft entry in post table. IN MULTISITE and remove that entry from both the sqls.
26. PHP REQUIREMENT LINK: https://wordpress.org/about/requirements/
var/softaculous/e107/notes.txt 0000644 00000001355 15054164524 0012262 0 ustar 00 1. Download full package and upgrade package from sourceforge i.e http://e107.org/get-started
2. Upgrade is allowed for all 1.x to 2.1. Check the files and folders that needs to be deleted in next version. This can be checked while logging into admin after upgrade.
3. kindly check and add upgrade method when there is update in 2.x branch. (Current upgrade method support only 1.x to 2.x)
4. PHP REQUIREMENT LINK : http://e107.org/get-started
5. Since e107 2.3.0 version list of files to be deleted can be checked from /e107_system/{{RAND_FOLDER_NAME}}/logs/fileinspector/deprecatedFiles.log. Since post upgrade the script does not ask to delete any folders, we have commented the code to delete folders in upgrade.php. Check this in every version. var/softaculous/jcow/notes.txt 0000644 00000001146 15054167457 0012556 0 ustar 00 1.If the download link does not appear on their site you can download the community edition from Sourceforge:
http://sourceforge.net/projects/jcow/files/jcow8/
(Also we have confirmed with vendor that the releases on sourceforge are stable releases)
2. After Upgrade few tables are not getting created i.e jcow_topics_followed, jcow_topic_ids etc
We have discussed with script vendor regarding this and they said that these tables are not required for CE. It will get created if client upgrades to PAID version.
3. Release date : https://sourceforge.net/p/jcow/activity/?page=0&limit=100#59627546e88f3d1360a402b9 var/softaculous/layerbb/notes.txt 0000644 00000000176 15054171772 0013231 0 ustar 00 1. PHP REQUIREMENT LINK: https://github.com/AndyRixon/LayerBB
2. MYSql 5.6 is required but it is working fine with Mysql 5.5. var/softaculous/wp55/notes.txt 0000644 00000012712 15054206007 0012376 0 ustar 00 1. Download the language files from :
http://codex.wordpress.org/L10n:Localization_Teams (https://nl.wordpress.org/)
and copy them to the /var/softaculous/wp/languages/LANGUAGE_CODE.zip
2. The language files for the following languages have been updated to 5.5.16 :
<option value="ar">Arabic</option>
<option value="ca">Catalan</option>
<option value="cs_CZ">Czech</option>
<option value="da_DK">Danish</option>
<option value="de_DE">German</option>
<option value="el">Greek</option>
<option value="es_ES">Spanish</option>
<option value="fa_IR">Persian</option>
<option value="fi">Finnish</option>
<option value="fr_FR">French</option>
<option value="he_IL">Hebrew</option>
<option value="hr">Croatian</option>
<option value="hu_HU">Hungarian</option>
<option value="id_ID">Indonesian</option>
<option value="it_IT">Italian</option>
<option value="ja">Japanese</option>
<option value="ko_KR">Korean</option>
<option value="nb_NO">Norwegian</option>
<option value="nl_NL">Dutch</option>
<option value="pl_PL">Polish</option>
<option value="pt_BR">Portuguese-BR</option>
<option value="pt_PT">Portuguese</option>
<option value="ro_RO">Romanian</option>
<option value="ru_RU">Russian</option>
<option value="sk_SK">Slovak</option>
<option value="sq">Albanian</option>
<option value="sv_SE">Swedish</option>
<option value="th">Thai</option>
<option value="tr_TR">Turkish</option>
<option value="uk">Ukrainian</option>
<option value="vi">Vietnamese</option>
<option value="zh_CN">Chinese(Simplified)</option>
<option value="zh_HK">Chinese (Hong Kong)</option>
<option value="zh_TW">Chinese(Traditional)</option>
3. Please try to update these languages if they are available for 5.5.16
<option value="bg_BG">Bulgarian</option>
<option value="sl_SI">Slovenian</option>
4. To activate footer link add this
<!--SOFTACULOUS-->
in the following file in wp.zip
wp-content/themes/twentytwenty/footer.php
wp-content/themes/twentynineteen/footer.php
wp-content/themes/twentyseventeen/template-parts/footer/site-info.php
wp-content/themes/twentysixteen/footer.php
NOTE : When a new theme is added in WordPress do the following tasks :
- add the line in install.xml and upgrade.xml as well
- add condition in upgrade.php ( in __pre_unzip function )
- update extend.php $templates['list']['wp-default'] array
- update new default theme screenshots in website/www/images/wp-default
5. 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.
The guide to install Multisite Manually :
https://wordpress.org/support/article/create-a-network/
6. (101, 'rewrite_rules', '', 'yes'), Keep it blank, WordPress generates it automatically
7. In multisite sql
After Configuring the Network, dump the SQL before logging in.
8. 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, WordPress generates it automatically
(115, 'can_compress_scripts', '0', 'yes');
also change the AUTO INCREMENT as it is in the dumped SQL of Original database.
9. Remove inserts in the sitemeta table after "active_sitewide_plugins" in MU
10. Remove the language files related to particular theme from languages/ if a theme is deleted by WordPress.
11. (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.
12. From 4.5.1 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 from 4.2.2
13. In case of major update please update the popularfx database.
14. While manual installation keep root writable and configure .htaccess as _htaccess.
15. configure [[permalink_structure]] only in wp.sql. Not in multisite.sql.
16. _index.php is our file no need to change it.
17. Remove Storage ENGINE "ENGINE=InnoDB" from all the CREATE TABLE queries in wp.sql and multisite.sql as WordPress sets the storage engine based on the default set in the MySQL Server.
18. when we add/delete a plugin update the edit.php and edit.xml file.
19. The language is configured in database under 'options' and 'sitemeta' tables for normal and multi site respectively. We use to manage language in version.php however this use to get reverted in case of persian language as observed. Hence we have now started handling in database and for multi site it was handled default in database. Also version.php is now removed because of this. (Since v4.8.1)
20. Boldgrid download link :
http://repo.boldgrid.com/boldgrid-inspirations.zip
21. We have added classic-editor plugin since 5.0.0 and we need to check in manual installation for extra insert classic-editor-replace under
options table. If any changes, change in install, edit, upgrade.
22. Remove __update_themes() and __update_plugins() functions only from the extend.php from the existing branch whenver you add a new branch. This means that this function shall only be a part of the current wp and not the old one's like wp50. var/softaculous/wp66/notes.txt 0000644 00000014131 15054206037 0012400 0 ustar 00 1. Download the language files from :
http://codex.wordpress.org/L10n:Localization_Teams (https://nl.wordpress.org/)
and copy them to the /var/softaculous/wp/languages/LANGUAGE_CODE.zip
2. The language files for the following languages have been updated to 6.6.3 :
<option value="bg_BG">Bulgarian</option>
<option value="ca">Catalan</option>
<option value="da_DK">Danish</option>
<option value="de_DE">German</option>
<option value="el">Greek</option>
<option value="es_ES">Spanish</option>
<option value="fa_IR">Persian</option>
<option value="fi">Finnish</option>
<option value="fr_FR">French</option>
<option value="hr">Croatian</option>
<option value="hu_HU">Hungarian</option>
<option value="id_ID">Indonesian</option>
<option value="it_IT">Italian</option>
<option value="ja">Japanese</option>
<option value="ko_KR">Korean</option>
<option value="nb_NO">Norwegian</option>
<option value="nl_NL">Dutch</option>
<option value="pl_PL">Polish</option>
<option value="pt_BR">Portuguese-BR</option>
<option value="pt_PT">Portuguese</option>
<option value="ro_RO">Romanian</option>
<option value="ru_RU">Russian</option>
<option value="sk_SK">Slovak</option>
<option value="sl_SI">Slovenian</option>
<option value="sq">Albanian</option>
<option value="sv_SE">Swedish</option>
<option value="tr_TR">Turkish</option>
<option value="vi">Vietnamese</option>
<option value="zh_CN">Chinese(Simplified)</option>
<option value="zh_TW">Chinese(Traditional)</option>
3. Please try to update these languages if they are available for 6.6.3
<option value="ar">Arabic</option>
<option value="cs_CZ">Czech</option>
<option value="he_IL">Hebrew</option>
<option value="th">Thai</option>
<option value="uk">Ukrainian</option>
<option value="zh_HK">Chinese (Hong Kong)</option>
4. To activate footer link add this
<!--SOFTACULOUS-->
in the following file in wp.zip
wp-content/themes/twentytwentyfour/patterns/footer.php
wp-content/themes/twentytwentythree/patterns/footer-default.php
wp-content/themes/twentytwentytwo/inc/patterns/footer-default.php
NOTE : When a new theme is added in WordPress do the following tasks :
- add the line in install.xml and upgrade.xml as well
- add condition in upgrade.php ( in __pre_unzip function )
- update extend.php $templates['list']['wp-default'] array
- update new default theme screenshots in website/www/images/wp-default
5. 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.
The guide to install Multisite Manually :
https://wordpress.org/support/article/create-a-network/
6. (101, 'rewrite_rules', '', 'yes'), Keep it blank, WordPress generates it automatically
7. In multisite sql
After Configuring the Network, dump the SQL before logging in.
8. 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, WordPress generates it automatically
(115, 'can_compress_scripts', '0', 'yes');
also change the AUTO INCREMENT as it is in the dumped SQL of Original database.
9. Remove inserts in the sitemeta table after "active_sitewide_plugins" in MU
10. Remove the language files related to particular theme from languages/ if a theme is deleted by WordPress.
11. (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.
12. From 4.5.1 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 from 4.2.2
13. In case of major update please update the popularfx database.
14. While manual installation keep root writable and configure .htaccess as _htaccess.
15. configure [[permalink_structure]] only in wp.sql. Not in multisite.sql.
16. _index.php is our file no need to change it.
17. Remove Storage ENGINE "ENGINE=InnoDB" from all the CREATE TABLE queries in wp.sql and multisite.sql as WordPress sets the storage engine based on the default set in the MySQL Server.
18. when we add/delete a plugin update the edit.php and edit.xml file.
19. The language is configured in database under 'options' and 'sitemeta' tables for normal and multi site respectively. We use to manage language in version.php however this use to get reverted in case of persian language as observed. Hence we have now started handling in database and for multi site it was handled default in database. Also version.php is now removed because of this. (Since v4.8.1)
20. Boldgrid download link :
http://repo.boldgrid.com/boldgrid-inspirations.zip
21. We have added classic-editor plugin since 5.0.0 and we need to check in manual installation for extra insert classic-editor-replace under
options table. If any changes, change in install, edit, upgrade.
22. Remove __update_themes() and __update_plugins() functions only from the extend.php from the existing branch whenver you add a new branch. This means that this function shall only be a part of the current wp and not the old one's like wp50.
23. The WP_AUTO_UPDATE_CORE setting in wp-contig.php and _wp-config.php is added because when we install old version of WordPress we do not want it to auto upgrade to latest version because since WordPress 5.6 WordPress auto updates itself for major versions as well. When making the latest version as an old branch do not forget to add changes related to WP_AUTO_UPDATE_CORE in
install.php
wp-config.php
_wp-config.php
24. Do not encode wp-cli file. Keep it as it is.
25. Check the "[[punycode_softurl]]/?p=4" Auto Draft entry in post table. IN MULTISITE and remove that entry from both the sqls.
26. PHP REQUIREMENT LINK: https://wordpress.org/about/requirements/
var/softaculous/fcms/notes.txt 0000644 00000000244 15054214335 0012526 0 ustar 00 1. PHP REQUIREMENT LINK : http://www.familycms.com/
2. We have restricted the script on Mysql >= 5.7 and PHP >= 7.4 because it throws error. (Confirmed over email) var/softaculous/qtoa/notes.txt 0000644 00000000613 15054214601 0012536 0 ustar 00 1) add the following line to sql in option table( To give default site name otherwise it will take domain as Sitename by default)
INSERT INTO `[[dbprefix]]options` VALUES('site_title', '[[site_name]]');
2) If any problem occurs regarding login please check the install.php (in "__mysql()" function)and the manual code for reference.
3) PHP REQUIREMENT LINK : https://www.question2answer.org/ var/softaculous/espo/notes.txt 0000644 00000001665 15054214705 0012555 0 ustar 00 1. PHP REQUIREMENT LINK : https://docs.espocrm.com/administration/installation/
2. Uncheck 'Auth' , 'Is Shared' as well as set 'From Name' to blank in SMTP settings for outgoing emails() while manual installation) since we don't use smtp configuration.(No such option since 9.1.0, hence we explicitly keep, 'outboundEmailIsShared' => false and 'smtpAuth' => false in config.php)
3. Mysql 5.5 doesn't support full-text search for InnoDB tables. 5.6.4 and later versions do support. ( https://github.com/espocrm/documentation/blob/master/user-guide/text-search.md#full-text-search )
4. Keep "timeZone": "America\\/New_York" in sql for `preferences` table even though entry is blank in manual installation's sql(i.e "timeZone": "").
5. Select Espo theme while installing manually.
6. We have not given the upgrade utility because the script supports CLI and admin UI based upgrades only. They do not advise to upgrade manually hence we have not given. var/softaculous/pier/notes.txt 0000644 00000000705 15054214760 0012541 0 ustar 00 Its only for users if they ask how to add project :
Error on Add Project: You don't have permission to access the requested page
1. Hover on "Administration" on Top -> Select "Company".
2. In "Contacts" Section, select "Edit user account" of "admin".
3. In "Options" section, For "Can manage his/her own projects" select "Yes"
Don't follow this steps for making package.
4. Release date : https://github.com/Project-Pier/ProjectPier-Core/releases var/softaculous/traq/notes.txt 0000644 00000000221 15054216210 0012532 0 ustar 00 1. PHP REQUIREMENT LINK : https://traq.io/downloads And in readme.md
2. We have kept requirement to 8.2 because the installer asks for the same. var/softaculous/ossn/notes.txt 0000644 00000001102 15054220004 0012540 0 ustar 00 1. PHP REQUIREMENT LINK : https://www.opensource-socialnetwork.org/wiki/view/706/how-to-install-open-source-social-network OR https://www.opensource-socialnetwork.org/discussion/view/6017/ossn-v63-lts-has-been-released
2. Take database dump on login page.
3. We have commented code in /installation/pages/check.php to disable code which was checking if the cache folder is to be created by user. For this manual installation was asking root directory writable to create cache folder. (Confirmed with vendor over email)
(Same is checked and code is commented in OSSN 8.x as well) var/softaculous/ruko/notes.txt 0000644 00000001027 15054222707 0012560 0 ustar 00 1. Check upgrade procedure everytime and change upgrade files accordingly.
2. Check there release blog everytime and if there are no database changes present in that particular version, empty "$setupcontinue" in upgrade.php (Change the condition accordingly)
2. PHP REQUIREMENT LINK : https://www.rukovoditel.net/download.php
3. Important : Always copy latest .htaccess from the package to _htaccess file in our package + make our changes i.e remove Options -Indexes from the file. This is to enable the file listing for upgrade files. var/softaculous/peel/notes.txt 0000644 00000001346 15054227307 0012532 0 ustar 00 1. We rename admin folder as it is strongly recommended to do so and it is mentioned at the last step of installation. Also we do not save admin_folder name in install.xml because we do not want admin url to update. (Added since 8.0.5).
2. Keep default values in Genreral Settings.
3. We have set PHP requirement to 5.5 because since version 9.0.0 script uses PHP 5.5's syntax.
4. We install with non-sample data(So keep Fill the database option : 'No' while manual installation) and we have removed sample data option from install.xml, Since sample data has issues while loading some frontend links,after renaming admin folder(in manual install as well).
5. PHP REQUIREMENT LINK : https://github.com/advisto/peel-shopping#ce-quil-vous-faut var/softaculous/less/notes.txt 0000644 00000000276 15054230722 0012547 0 ustar 00 1. We have kept version number in info as 3.13.0 and less.js is of 3.12.2 because vendor have kept the same.
2. Rename less.min.js to less.js from dist folder and make our package from that. var/softaculous/pyro/notes.txt 0000644 00000001670 15054231036 0012570 0 ustar 00 1. Manual install with Application Reference = softaculous_ref.
2. Check and move public/app/default/assets folder from manual to zip.
3. Check and move public/app/softaculous_ref folder from manual to zip.
4. Check and move storage/streams/softaculous_ref folder from manual to zip.
5. Exclude the following files while moving the above folders from manual to zip :
public/app/default/assets/admin/theme.css
public/app/softaculous_ref/assets/admin/theme.css
public/app/softaculous_ref/assets/public/theme.css
storage/streams/softaculous_ref/search/zend/default/{All .cfs, .sti and .del files}
6. Remove the following entry from composer.json
anomaly/installer-module
This is to disable the warning that the installer still exists.
Guide to install Composer :
https://getcomposer.org/doc/00-intro.md
curl -sS https://getcomposer.org/installer | php
php composer.phar install
7. Update from 2.2.x is not possible as confirmed by vendor via email. var/softaculous/flat/notes.txt 0000644 00000001724 15054234613 0012531 0 ustar 00 1. PHP REQUIREMENT LINK : https://github.com/flatpressblog/flatpress
2. We offer incremental upgrade i.e for example 1.1 to 1.2 but not from previous versions to 1.2 as vendor provides upgrade zip for upgrading incremental versions. change minimum required version in <min_require> tag in info.xml and make relevant changes in upgrade.php in every update. Download upgrade package from here https://www.flatpress.org/download
3. We have explicitely added "en-us" in settings-defaults.php file before starting curl_call because the installer takes "cs-cz" only despite of adding en-us in the post parameter. (Check in next version)
4. Ignore the .git and .github folders while making our zip. (If any)
5. We have made a manual change in fp-includes/core/core.utils.php file to make it work on PHP 7.1 since 1.4 upgrade as suggested by vendor.
https://github.com/flatpressblog/flatpress/issues/630(not needed since 1.4.1)
6. Upgrade documentation: https://www.flatpress.org/download var/softaculous/cftp/notes.txt 0000644 00000000462 15054235100 0012525 0 ustar 00 1. We have Given upgrade from version r180.
2. Use default dbprefix while manual installation. (Suggested by vendor)
3. Release date : https://www.projectsend.org/change-log/
4. PHP REQUIREMENT LINK: https://www.projectsend.org/how-to-install-projectsend/ and also check /vendor/composer/platform_check.php var/softaculous/spip/notes.txt 0000644 00000002213 15054235107 0012547 0 ustar 00 1. Choose MySQL for type of database.
2. Do not remove sha256.inc.php file we use it for password encryption.
3. In /config/connect.php file in manual installation it doesnt takes "_" for dbprefix and database has it.
4. Check for _jobs 'date' entries. In 3.0.11 we have used regtime. before it was [[queue_watch_date]] etc.
5. PHP REQUIREMENT LINK : https://www.spip.net/en_article6659.html
6. Blank plugin entry "meta" table. It generates after login.
7. In "meta" keep value of langue_site as [[language]], to keep frontend as well in the user selected language.
8. Keep [[language]] in "auteurs" table.
9. `backup_cles` entry generates post login.
10. Kept sha256.inc.php file to add backup compatibility in edit.
11. We have deleted all the folders(except config and IMG) in upgrade as keeping old files results in error when uploading a document in "Edit-->Document" section. Discussion is mentioned here. https://discuter.spip.net/t/error-uploading-documents-post-upgrade/162884/7
12. Keep 'vendor' folder writable as well while manual installation, to avoid warning of 'inoperative .htaccess'.
13. cache_signature and secret_du_site generates on it's own. var/softaculous/mt/notes.txt 0000644 00000001335 15054272517 0012226 0 ustar 00
1) Include these two lines in mt.cgi it contains the path of packages.
use lib '/hsphere/shared/lib/perl5';
use lib '/hsphere/shared/lib/perl5/site_perl';
2) If You still get error after doing above step that only follow this step
If movabletype is not running that please rename mt-config.cgi to another name and run mt-check.cgi file it will show you missing plugins.
If DBD:mysql is not installed than install it using following command :
perl -MCPAN -e 'install Bundle::DBD::mysql'
3) After Installation create one page under website. Give title home and publish it. then dump sql
4) .htaccess is required so do not remove .htaccess even if it is not created by MT.
5) Make script where MySQL engine is InnoDB var/softaculous/qcms/notes.txt 0000644 00000000105 15054342024 0012532 0 ustar 00 1. PHP REQUIREMENT LINK : https://opensolution.org/docs/?p=en-install var/softaculous/sidu/notes.txt 0000644 00000001637 15054342360 0012551 0 ustar 00
The following problem has been resolved in SIDU 3.7-----------------------------------
If you get errors when you click on 'User' tab in menu then
Solutions (Recommended by Script Vendor):
1 - open file: user.php
========================
<?php
//0id 1tab 2user@host 3db 4table
include 'inc.page.php';
$SIDU['page']['nav']='defa';
uppe();
echo "<div class='web'>";
main($SIDU,$user,$acs,$acs2,$grant,$cmd);
echo '</div>';
down();
...
=========================
Above is the top part of user.php.
simply add "@" before uppe() and main(...) and down()
so it will look like the following:
========================
<?php
//0id 1tab 2user@host 3db 4table
include 'inc.page.php';
$SIDU['page']['nav']='defa';
@uppe();
echo "<div class='web'>";
@main($SIDU,$user,$acs,$acs2,$grant,$cmd);
echo '</div>';
@down();
...
=========================
2)We have changed the php requirement to 5.4 due to syntax error in version 6.0.
var/softaculous/bugs/notes.txt 0000644 00000000601 15054342750 0012536 0 ustar 00 1. select timezone America/New_York
2. install/get_updates_list needs permissions to render the frontend,else it throws error.
3. We don't delete the install folder as it is required for further use.(confirmed with vendor in email).
4. We exclude the config-setup.php as it is unlinked by the installer after installation and keeping it throws error.
5. PHP REQUIREMENT LINK: README.md var/softaculous/doku/notes.txt 0000644 00000001716 15054352236 0012550 0 ustar 00 1. Add [[language]] in local.php
2. Choose License type 'Do not show any license information'.
3. Install three times i.e in Open Mode, Public mode & closed mode to check ACL values in install.php
4. <vr search="2013-05-10a">2013-05-10+</vr> added for force upgrade by softaculous. So remove it in next version if not needed (Already removed)
5. PHP REQUIREMENT LINK : https://www.dokuwiki.org/requirements
6. "lib/exe/indexer.php?id=wiki%3Awelcome&timstamp" is ajax call made by "doku.php?id=wiki:welcome" link, provide in dokuwiki installer to visit after install, check if files are getting created in "data/index" after visit of link. ( added since 2017-02-19e )
7. We have set min PHP version to 7.4 because since 2024.02.06 version script's composer requires PHP 7.4
8. For our reference : The blank file data/cache/autosubmit.txt is created by visiting admin panel under Admin -> Popularity Feedback -> Automatically send data once a month(Keep checked)-> Send data. var/softaculous/lime/notes.txt 0000644 00000003251 15054352307 0012527 0 ustar 00 1. (NOT REQUIRED NOW) We have added few variables in config.php so add them even if they are not in the current file (Now these variables are added in Database).
2. Keep MyISAM in MySQL database engine type while installing manually.
3. After installation if you get update notification then add
('updateavailable', '0'),
('updatelastcheck', '[[regtime]]'); In [[dbprefix]]settings_global table
4. We have removed auto upgrade for minor version. i.e when there is no change in Db we will display 3rd link.
5. PHP REQUIREMENT LINK : https://manual.limesurvey.org/Installation#Make_sure_you_can_use_LimeSurvey_on_your_website
6. We have disabled upgrade to version 3.x.x from previous versions i.e from 2.x.x and 1.x.x ,as 'Plugin manager' breaks after upgrade.(Please check and enable upgrade in next version if it works 2.x.x and 1.x.x and change minimum requirement accordingly.)(Since version 3.1.1+).
7. Upgrade enabled with minimum version 3.1.1+.
8. Important : Every time check and change the value of $DBVersion variable in upgrade.php by checking value of DBVersion from `".$__settings['dbprefix']."settings_global` table when there is a change in it.
9. Since 4.1.6+ installer asks for custom dbprefix during installation but takes default prefix (lime_) to populate database. Hence we have removed from install.xml Check in next version.(Checked in 4.1.8+ as well, not yet fixed) (re-enabled from 4.1.18+)
10. After 4.3.15+, we don't provide any further update to LimeSurvey 4.x , since those releases are labelled as 'Unstable' on their website. We have reverted to 3.x latest stable(i.e 3.25.3+) release post 4.3.15+. Provide update to 4.x only when the releases are mentioned as 'Stable'. var/softaculous/elgg/notes.txt 0000644 00000001015 15054352564 0012520 0 ustar 00 1) Add the elggdata folder to data.zip BUT delete all files of root folders of that elggdata
2) Take the data.zip after logging in the manual installation.
3) We have disabled auto upgrade in 1.9.1 because it requires datadir upgrade when upgrading from 1.8.x, please check auto upgrade from 1.8.x if you enable auto upgrade in future
4) Add a trailing slash '/' for datadir path in manual installation. (Not required now since 1.12.11)
5) PHP REQUIREMENT LINK: http://learn.elgg.org/en/stable/intro/install.html#requirements var/softaculous/tine/notes.txt 0000644 00000002655 15054367121 0012547 0 ustar 00 1. Make manual installation where MySQL is >= 5.7.7
2. While manual installation : "Config Manager" -> Save Config and then move to Authentication/Accounts
3. Create data directory with "tmp" and "files" directory and add respective paths during manual installation.
4. Check and compare data directory everytime with Addressbook/Export/templates/*, Sales/Export/templates/*, Crm/Export/templates/*, Timetracker/Export/templates/*, Calendar/Export/templates/* of original zip. These files should match with "tmp" and "files" directory files.
5. PHP REQUIREMENT LINK: Setup\essentials.xml
MySQL requirement since 2019.02.2 https://github.com/tine20/tine20/releases https://github.com/tine20/tine20/wiki/EN%3ASystem-requirements
6. We have set MySQL requirement to 5.6.4 because Some features are not available for MySQL < 5.6. Vendor has recommended to use MySQL 5.6.4 https://www.tine20.org/forum/viewtopic.php?f=8&t=18724&p=68100#p68100
7. Setup.php was not accessible via web browser in tine 2018.8.3/4/5 hence we have made manual installation through command line with following command given by vendor. https://github.com/tine20/tine20/issues/6906
php setup.php --config /home/soft/public_html/manual/tine202085/config.inc.php --install
8. Download 2022.01.08-f54711b-nightly.tar.gz Package from github. i.e https://github.com/tine20/tine20/releases/download/2022.01.08.4/2022.01.08-f54711b-nightly.tar.gz
9. Language can be changed from login page var/softaculous/yeti/notes.txt 0000644 00000002234 15054367160 0012556 0 ustar 00 1. [IMP] Before starting manual installation, make app_data/installSource.txt file with "Softaculous" in it. Since 7.0.4 version vendor has requested us to make this file and keep it in our package.
2. Select Currency as "USA, Dollars" and Time zone as "(UTC-05:00) Eastern Time (US & Canada)"
3. Keep Company name "YetiForce" in manual Installation. We can change from admin panel.
4. PHP Requirement Link: https://yetiforce.com/pl/component/zoo/item/web-server-requirements and also check vendor/composer/platform_check.php(Its PHP > = 7.4.15 in platform_check.php)
5. Release date : https://github.com/YetiForceCompany/YetiForceCRM/releases (released xx days ago)
6. We have moved few folders in config, app_data and user_privileges from manual to zip because it does not create after install. (Since 5.0.0)
7. Remove COLLATE=utf8mb4_0900_ai_ci From sql file if we have installed manually on Mysql 8. Because it gives error on installing with MariaDB. Besides this script itself doesn't use any collation and hence it takes server's default collation. (confirmed with vendor over email)
8. Take the dumps using CLI.
mysqldump --routines -u root -ppass yetiforce > yetiforce.sql var/softaculous/fork/notes.txt 0000644 00000004317 15054367203 0012547 0 ustar 00 *** It cannot be installed on Webuzo. CSS dosnt work. (Do not prefer Webuzo for Manual Installation). It works from 3.9.3
1) Install Composer and create zip for package and delete extra content of var folder from package (v5.8.0 check for the vendor folder in next version)
2) Install with Sample data
3) Install in www folder i.e rename your www folder and create new blank www and install in that www because Fork is installed only in root dir
4) Add these files from manual www to zip
check and move /bundles and its sub files and folders to zip
frontend/files/Users/avatars/32x32/god.jpg to frontend/files/Users/avatars/32x32
frontend/files/Users/avatars/64x64/god.jpg to frontend/files/Users/avatars/64x64
frontend/files/Users/avatars/128x128/god.jpg to frontend/files/Users/avatars/128x128
frontend/files/Users/avatars/source/god.jpg to frontend/files/Users/avatars/source
5) The version in the __requirements() in Upgrade.php should be increased when there is a Major Upgrade because it is not possible to upgrade to a Major version. This is now handled by info.xml <min_require> tag so we do not need to make changes in upgrade.php
6) check and update version in upgrade.php if it upgrade requires to delete appProdProjectContainer.php (Not required since version 4.0.0)
7) <requirement check="php" type="extension" name="pcre" version="8" operator="ge"><![CDATA[ PCRE Library Version => (.*?)\s ]]></requirement> Add this entry in info.xml once softaculous bug is fixed and launched. Also update <softversion>
8) PHP REQUIREMENT LINK : https://github.com/forkcms/forkcms/blob/master/docs/01.%20installation/03.%20minimum_requirements.md and also check composer.json
9) ckfinder_license_key in modules_settings table is hardcoded in src\Backend\Core\Installer\CoreInstaller.php files no need to configure
10)Check and change scopy code if required for i.e @scopy($__settings['softpath'].'/src/Backend/Core/Installer/Data/images/1.jpg', $__settings['softpath'].'/src/Frontend/Files/Pages/images/source/'.$__settings['timestamp'].'.jpg');.as the image created with timestamp name might be either of
/src/Backend/Core/Installer/Data/images/1.jpg or src/Backend/Core/Installer/Data/images/2.jpg, or src/Backend/Core/Installer/Data/images/3.jpg. var/softaculous/hesk/notes.txt 0000644 00000002215 15054367524 0012541 0 ustar 00 1. For next release kindly check upgrade method.
2. From 2.5.2 we have given update from just previous version i.e. 2.5.0. For next release kindly check if it gets upgraded by normal process.
3. Auto upgrade might need some changes when there is a new version with changes in database. Add the steps accordingly in upgrade.php
4. PHP REQUIREMENT LINK : install/install_functions.inc.php
5. Select Timezone = America/New_York in manual installation.
6. for adding new language download language from https://www.hesk.com/language/ link and open text.php and get values of "LANGUAGE" ,"EMAIL_HR" and language file name ex. "ar" from ar.zip ( FILENAME = ar ) and arrange in this format and add in $hesk_settings array
'{{FILENAME}}' => array ( '{{LANGUAGE}}' => array('folder' => '{{FILENAME}}', 'hr' => '{{EMAIL_HR}}'), ),
7. Since 3.5.0 version we have removed auto upgrade because the script was using ajax to migrate the customers.
8. We have appplied a patch given by vendor in 3.6.0 version as the script was throwing error on accessing customer module.
(This patch fix was added to 3.6.1 as mentioned by vendor in email, and it's mentioned in changelog as well) var/softaculous/cube/notes.txt 0000644 00000001445 15054367573 0012535 0 ustar 00 1. Add following code in global.inc.php file
$glob['install_source'] = 'softaculous';
2. Default Currency : GBP -British Pound
3. Update the value for $tmp and $Contact_Form in install.php with the updated value in manual SQL file
4. Always check setup/index.php and change accordingly in our package. Keep our changes intact. This is for upgrade
5. update "$tmp['store_copyright']" if any change in manual
6. PHP REQUIREMENT LINK : https://www.cubecart.com/hosting-requirements and also check with setup/index.php
(Kept PHP requirement 7.1.0 in info.xml due to issue on PHP 5.5 (min req) and 7.0 in version 6.4.6. Change requirement accordingly in info.xml if vendor fixes the same)
(Vendor has asked us to keep PHP 7.1 as minimal PHP version and has updated the same in setup/index.php in version 6.4.7) var/softaculous/cake/notes.txt 0000644 00000001756 15054370744 0012521 0 ustar 00 1. PHP REQUIREMENT LINK: https://book.cakephp.org/5/en/installation.html and also check /vendor/composer/platform_check.php
2. Set "DEBUG" true in "config/app.php"
3. We have copied logs folder from older version inside our package. As it throws error.(Log folder added in version 4.0.2)
4. We have added database settings in app.php file explicitly in version 4.0.0 i.e,
'host' => '[[softdbhost]]',
'username' => '[[softbuser]]',
'password' => '[[softdbpass]]',
'database' => '[[softdb]]',
as they were not present in version 4.0.0, and they are needed to connect to database. Please check in next version.(If not present add them below the line 'persistent' => false, under ORM settings in app.php file).(Not needed since 4.0.2 as script now uses app_local.php for configuration and provides way to configure database settings.)
5. Use app_local.php and not app.php for configuring database settings in manual installation(As settings in app_local.php override settings in app.php)(Since version 4.0.2)
var/softaculous/wp65/notes.txt 0000644 00000014121 15054520104 0012370 0 ustar 00 1. Download the language files from :
http://codex.wordpress.org/L10n:Localization_Teams (https://nl.wordpress.org/)
and copy them to the /var/softaculous/wp/languages/LANGUAGE_CODE.zip
2. The language files for the following languages have been updated to 6.5.6 :
<option value="bg_BG">Bulgarian</option>
<option value="ca">Catalan</option>
<option value="cs_CZ">Czech</option>
<option value="da_DK">Danish</option>
<option value="de_DE">German</option>
<option value="el">Greek</option>
<option value="es_ES">Spanish</option>
<option value="fa_IR">Persian</option>
<option value="fi">Finnish</option>
<option value="fr_FR">French</option>
<option value="hr">Croatian</option>
<option value="hu_HU">Hungarian</option>
<option value="id_ID">Indonesian</option>
<option value="it_IT">Italian</option>
<option value="ja">Japanese</option>
<option value="ko_KR">Korean</option>
<option value="nb_NO">Norwegian</option>
<option value="nl_NL">Dutch</option>
<option value="pl_PL">Polish</option>
<option value="pt_BR">Portuguese-BR</option>
<option value="pt_PT">Portuguese</option>
<option value="ro_RO">Romanian</option>
<option value="ru_RU">Russian</option>
<option value="sk_SK">Slovak</option>
<option value="sl_SI">Slovenian</option>
<option value="sq">Albanian</option>
<option value="sv_SE">Swedish</option>
<option value="tr_TR">Turkish</option>
<option value="vi">Vietnamese</option>
<option value="zh_CN">Chinese(Simplified)</option>
<option value="zh_TW">Chinese(Traditional)</option>
3. Please try to update these languages if they are available for 6.5.6
<option value="ar">Arabic</option>
<option value="he_IL">Hebrew</option>
<option value="th">Thai</option>
<option value="uk">Ukrainian</option>
<option value="zh_HK">Chinese (Hong Kong)</option>
4. To activate footer link add this
<!--SOFTACULOUS-->
in the following file in wp.zip
wp-content/themes/twentytwentyfour/footer.php
wp-content/themes/twentytwentythree/patterns/footer-default.php
wp-content/themes/twentytwentytwo/inc/patterns/footer-default.php
NOTE : When a new theme is added in WordPress do the following tasks :
- add the line in install.xml and upgrade.xml as well
- add condition in upgrade.php ( in __pre_unzip function )
- update extend.php $templates['list']['wp-default'] array
- update new default theme screenshots in website/www/images/wp-default
5. 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.
The guide to install Multisite Manually :
https://wordpress.org/support/article/create-a-network/
6. (101, 'rewrite_rules', '', 'yes'), Keep it blank, WordPress generates it automatically
7. In multisite sql
After Configuring the Network, dump the SQL before logging in.
8. 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, WordPress generates it automatically
(115, 'can_compress_scripts', '0', 'yes');
also change the AUTO INCREMENT as it is in the dumped SQL of Original database.
9. Remove inserts in the sitemeta table after "active_sitewide_plugins" in MU
10. Remove the language files related to particular theme from languages/ if a theme is deleted by WordPress.
11. (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.
12. From 4.5.1 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 from 4.2.2
13. In case of major update please update the popularfx database.
14. While manual installation keep root writable and configure .htaccess as _htaccess.
15. configure [[permalink_structure]] only in wp.sql. Not in multisite.sql.
16. _index.php is our file no need to change it.
17. Remove Storage ENGINE "ENGINE=InnoDB" from all the CREATE TABLE queries in wp.sql and multisite.sql as WordPress sets the storage engine based on the default set in the MySQL Server.
18. when we add/delete a plugin update the edit.php and edit.xml file.
19. The language is configured in database under 'options' and 'sitemeta' tables for normal and multi site respectively. We use to manage language in version.php however this use to get reverted in case of persian language as observed. Hence we have now started handling in database and for multi site it was handled default in database. Also version.php is now removed because of this. (Since v4.8.1)
20. Boldgrid download link :
http://repo.boldgrid.com/boldgrid-inspirations.zip
21. We have added classic-editor plugin since 5.0.0 and we need to check in manual installation for extra insert classic-editor-replace under
options table. If any changes, change in install, edit, upgrade.
22. Remove __update_themes() and __update_plugins() functions only from the extend.php from the existing branch whenver you add a new branch. This means that this function shall only be a part of the current wp and not the old one's like wp50.
23. The WP_AUTO_UPDATE_CORE setting in wp-contig.php and _wp-config.php is added because when we install old version of WordPress we do not want it to auto upgrade to latest version because since WordPress 5.6 WordPress auto updates itself for major versions as well. When making the latest version as an old branch do not forget to add changes related to WP_AUTO_UPDATE_CORE in
install.php
wp-config.php
_wp-config.php
24. Do not encode wp-cli file. Keep it as it is.
25. Check the "[[punycode_softurl]]/?p=4" Auto Draft entry in post table. IN MULTISITE and remove that entry from both the sqls.
26. PHP REQUIREMENT LINK: https://wordpress.org/about/requirements/
var/softaculous/wp59/notes.txt 0000644 00000013502 15054520456 0012407 0 ustar 00 1. Download the language files from :
http://codex.wordpress.org/L10n:Localization_Teams (https://nl.wordpress.org/)
and copy them to the /var/softaculous/wp/languages/LANGUAGE_CODE.zip
2. The language files for the following languages have been updated to 5.9.11 :
<option value="ar">Arabic</option>
<option value="bg_BG">Bulgarian</option>
<option value="ca">Catalan</option>
<option value="cs_CZ">Czech</option>
<option value="da_DK">Danish</option>
<option value="de_DE">German</option>
<option value="el">Greek</option>
<option value="es_ES">Spanish</option>
<option value="fa_IR">Persian</option>
<option value="fi">Finnish</option>
<option value="fr_FR">French</option>
<option value="he_IL">Hebrew</option>
<option value="hr">Croatian</option>
<option value="hu_HU">Hungarian</option>
<option value="id_ID">Indonesian</option>
<option value="it_IT">Italian</option>
<option value="ja">Japanese</option>
<option value="ko_KR">Korean</option>
<option value="nb_NO">Norwegian</option>
<option value="nl_NL">Dutch</option>
<option value="pl_PL">Polish</option>
<option value="pt_BR">Portuguese-BR</option>
<option value="pt_PT">Portuguese</option>
<option value="ro_RO">Romanian</option>
<option value="ru_RU">Russian</option>
<option value="sk_SK">Slovak</option>
<option value="sl_SI">Slovenian</option>
<option value="sq">Albanian</option>
<option value="sv_SE">Swedish</option>
<option value="tr_TR">Turkish</option>
<option value="vi">Vietnamese</option>
<option value="zh_CN">Chinese(Simplified)</option>
<option value="zh_HK">Chinese (Hong Kong)</option>
<option value="zh_TW">Chinese(Traditional)</option>
3. Please try to update these languages if they are available for 5.9.11
<option value="th">Thai</option>
<option value="uk">Ukrainian</option>
4. To activate footer link add this
<!--SOFTACULOUS-->
in the following file in wp.zip
wp-content/themes/twentytwentytwo/inc/patterns/footer-default.php
wp-content/themes/twentytwentyone/footer.php
wp-content/themes/twentytwenty/footer.php
NOTE : When a new theme is added in WordPress do the following tasks :
- add the line in install.xml and upgrade.xml as well
- add condition in upgrade.php ( in __pre_unzip function )
- update extend.php $templates['list']['wp-default'] array
- update new default theme screenshots in website/www/images/wp-default
5. 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.
The guide to install Multisite Manually :
https://wordpress.org/support/article/create-a-network/
6. (101, 'rewrite_rules', '', 'yes'), Keep it blank, WordPress generates it automatically
7. In multisite sql
After Configuring the Network, dump the SQL before logging in.
8. 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, WordPress generates it automatically
(115, 'can_compress_scripts', '0', 'yes');
also change the AUTO INCREMENT as it is in the dumped SQL of Original database.
9. Remove inserts in the sitemeta table after "active_sitewide_plugins" in MU
10. Remove the language files related to particular theme from languages/ if a theme is deleted by WordPress.
11. (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.
12. From 4.5.1 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 from 4.2.2
13. In case of major update please update the popularfx database.
14. While manual installation keep root writable and configure .htaccess as _htaccess.
15. configure [[permalink_structure]] only in wp.sql. Not in multisite.sql.
16. _index.php is our file no need to change it.
17. Remove Storage ENGINE "ENGINE=InnoDB" from all the CREATE TABLE queries in wp.sql and multisite.sql as WordPress sets the storage engine based on the default set in the MySQL Server.
18. when we add/delete a plugin update the edit.php and edit.xml file.
19. The language is configured in database under 'options' and 'sitemeta' tables for normal and multi site respectively. We use to manage language in version.php however this use to get reverted in case of persian language as observed. Hence we have now started handling in database and for multi site it was handled default in database. Also version.php is now removed because of this. (Since v4.8.1)
20. Boldgrid download link :
http://repo.boldgrid.com/boldgrid-inspirations.zip
21. We have added classic-editor plugin since 5.0.0 and we need to check in manual installation for extra insert classic-editor-replace under
options table. If any changes, change in install, edit, upgrade.
22. Remove __update_themes() and __update_plugins() functions only from the extend.php from the existing branch whenver you add a new branch. This means that this function shall only be a part of the current wp and not the old one's like wp50.
23. The WP_AUTO_UPDATE_CORE setting in wp-contig.php and _wp-config.php is added because when we install old version of WordPress we do not want it to auto upgrade to latest version because since WordPress 5.6 WordPress auto updates itself for major versions as well. When making the latest version as an old branch do not forget to add changes related to WP_AUTO_UPDATE_CORE in
install.php
wp-config.php
_wp-config.php
var/softaculous/wp67/notes.txt 0000644 00000014116 15054520555 0012410 0 ustar 00 1. Download the language files from :
http://codex.wordpress.org/L10n:Localization_Teams (https://nl.wordpress.org/)
and copy them to the /var/softaculous/wp/languages/LANGUAGE_CODE.zip
2. The language files for the following languages have been updated to 6.7.3 :
<option value="bg_BG">Bulgarian</option>
<option value="ca">Catalan</option>
<option value="cs_CZ">Czech</option>
<option value="da_DK">Danish</option>
<option value="de_DE">German</option>
<option value="el">Greek</option>
<option value="es_ES">Spanish</option>
<option value="fa_IR">Persian</option>
<option value="fi">Finnish</option>
<option value="fr_FR">French</option>
<option value="hr">Croatian</option>
<option value="hu_HU">Hungarian</option>
<option value="id_ID">Indonesian</option>
<option value="it_IT">Italian</option>
<option value="ja">Japanese</option>
<option value="ko_KR">Korean</option>
<option value="nb_NO">Norwegian</option>
<option value="nl_NL">Dutch</option>
<option value="pl_PL">Polish</option>
<option value="pt_BR">Portuguese-BR</option>
<option value="pt_PT">Portuguese</option>
<option value="ro_RO">Romanian</option>
<option value="ru_RU">Russian</option>
<option value="sk_SK">Slovak</option>
<option value="sl_SI">Slovenian</option>
<option value="sq">Albanian</option>
<option value="sv_SE">Swedish</option>
<option value="tr_TR">Turkish</option>
<option value="vi">Vietnamese</option>
<option value="zh_CN">Chinese(Simplified)</option>
<option value="zh_TW">Chinese(Traditional)</option>
3. Please try to update these languages if they are available for 6.7.3
<option value="ar">Arabic</option>
<option value="he_IL">Hebrew</option>
<option value="th">Thai</option>
<option value="uk">Ukrainian</option>
<option value="zh_HK">Chinese (Hong Kong)</option>
4. To activate footer link add this
<!--SOFTACULOUS-->
in the following file in wp.zip
wp-content/themes/twentytwentyfive/patterns/footer.php
wp-content/themes/twentytwentyfour/patterns/footer.php
wp-content/themes/twentytwentythree/patterns/footer-default.php
NOTE : When a new theme is added in WordPress do the following tasks :
- add the line in install.xml and upgrade.xml as well
- add condition in upgrade.php ( in __pre_unzip function )
- update extend.php $templates['list']['wp-default'] array
- update new default theme screenshots in website/www/images/wp-default
5. 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.
The guide to install Multisite Manually :
https://wordpress.org/support/article/create-a-network/
6. (101, 'rewrite_rules', '', 'yes'), Keep it blank, WordPress generates it automatically
7. In multisite sql
After Configuring the Network, dump the SQL before logging in.
8. 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, WordPress generates it automatically
(115, 'can_compress_scripts', '0', 'yes');
also change the AUTO INCREMENT as it is in the dumped SQL of Original database.
9. Remove inserts in the sitemeta table after "active_sitewide_plugins" in MU
10. Remove the language files related to particular theme from languages/ if a theme is deleted by WordPress.
11. (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.
12. From 4.5.1 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 from 4.2.2
13. In case of major update please update the popularfx database.
14. While manual installation keep root writable and configure .htaccess as _htaccess.
15. configure [[permalink_structure]] only in wp.sql. Not in multisite.sql.
16. _index.php is our file no need to change it.
17. Remove Storage ENGINE "ENGINE=InnoDB" from all the CREATE TABLE queries in wp.sql and multisite.sql as WordPress sets the storage engine based on the default set in the MySQL Server.
18. when we add/delete a plugin update the edit.php and edit.xml file.
19. The language is configured in database under 'options' and 'sitemeta' tables for normal and multi site respectively. We use to manage language in version.php however this use to get reverted in case of persian language as observed. Hence we have now started handling in database and for multi site it was handled default in database. Also version.php is now removed because of this. (Since v4.8.1)
20. Boldgrid download link :
http://repo.boldgrid.com/boldgrid-inspirations.zip
21. We have added classic-editor plugin since 5.0.0 and we need to check in manual installation for extra insert classic-editor-replace under
options table. If any changes, change in install, edit, upgrade.
22. Remove __update_themes() and __update_plugins() functions only from the extend.php from the existing branch whenver you add a new branch. This means that this function shall only be a part of the current wp and not the old one's like wp50.
23. The WP_AUTO_UPDATE_CORE setting in wp-contig.php and _wp-config.php is added because when we install old version of WordPress we do not want it to auto upgrade to latest version because since WordPress 5.6 WordPress auto updates itself for major versions as well. When making the latest version as an old branch do not forget to add changes related to WP_AUTO_UPDATE_CORE in
install.php
wp-config.php
_wp-config.php
24. Do not encode wp-cli file. Keep it as it is.
25. Check the "[[punycode_softurl]]/?p=4" Auto Draft entry in post table. IN MULTISITE and remove that entry from both the sqls.
26. PHP REQUIREMENT LINK: https://wordpress.org/about/requirements/
var/softaculous/mw35/notes.txt 0000644 00000003311 15054526252 0012373 0 ustar 00 ################ Untar downloaded tar.gz package on linux server and then make a ground zip. ################
1) Use Storage Engine Innodb.
2) Use binary database character set.
3) Use the License as "No license footer"
4) Check the language files exists in the /languages/classes/ & /languages/messages/ it should be there with the downloaded zip.
5) We have added "tmpdir" in order to save cache at different locations for each installation to avoid conflicts between them. (v1.27.1)
https://www.mediawiki.org/wiki/Manual_talk:Upgrading#Shared_server_.2B_multiple_Mediawiki_installations
https://phabricator.wikimedia.org/T127127
We have added the following in LocalSettings.php
$wgTmpDirectory = "[[tmpdir]]";
6) PHP REQUIREMENT LINK: https://www.mediawiki.org/wiki/MediaWiki_1.35
7) check "I'm bored already, just install the wiki." and continue in manual install
8) Check visual editor and other extension options in every major update. By clicking "ask me more questions" option. (Just to check)
9) removed inserts from "job" table because it creates entry after page access
10) Keep `content_sha1` value as it is in "content" table because it is same for all installations.
11)we have disable cross upgrade because we were getting following error post upgrading. eb786298294aef346a4e8c9b] 2020-03-27 11:45:10: Fatal exception of type "MWException"
(Reported issue to vendor as well) Check in next version if it resolves.(Got this error while upgrading from 1.31.12 to 1.35.1 so have disabled cross upgrade(i.e changed 'min_require' in info.xml as 1.35.0), check whether cross upgrade works in next version and also change 'min_require'.(Enabled in 1.35.4 and changed minimum requirement to 1.31.0 since cross upgrade is working) var/softaculous/wp57/notes.txt 0000644 00000013557 15054555632 0012423 0 ustar 00 1. Download the language files from :
http://codex.wordpress.org/L10n:Localization_Teams (https://nl.wordpress.org/)
and copy them to the /var/softaculous/wp/languages/LANGUAGE_CODE.zip
2. The language files for the following languages have been updated to 5.7.13 :
<option value="ar">Arabic</option>
<option value="bg_BG">Bulgarian</option>
<option value="ca">Catalan</option>
<option value="cs_CZ">Czech</option>
<option value="da_DK">Danish</option>
<option value="de_DE">German</option>
<option value="el">Greek</option>
<option value="es_ES">Spanish</option>
<option value="fa_IR">Persian</option>
<option value="fi">Finnish</option>
<option value="fr_FR">French</option>
<option value="he_IL">Hebrew</option>
<option value="hr">Croatian</option>
<option value="hu_HU">Hungarian</option>
<option value="id_ID">Indonesian</option>
<option value="it_IT">Italian</option>
<option value="ja">Japanese</option>
<option value="ko_KR">Korean</option>
<option value="nb_NO">Norwegian</option>
<option value="nl_NL">Dutch</option>
<option value="pl_PL">Polish</option>
<option value="pt_BR">Portuguese-BR</option>
<option value="pt_PT">Portuguese</option>
<option value="ro_RO">Romanian</option>
<option value="ru_RU">Russian</option>
<option value="sk_SK">Slovak</option>
<option value="sq">Albanian</option>
<option value="sv_SE">Swedish</option>
<option value="th">Thai</option>
<option value="tr_TR">Turkish</option>
<option value="uk">Ukrainian</option>
<option value="vi">Vietnamese</option>
<option value="zh_CN">Chinese(Simplified)</option>
<option value="zh_HK">Chinese (Hong Kong)</option>
<option value="zh_TW">Chinese(Traditional)</option>
3. Please try to update these languages if they are available for 5.7.13
<option value="sl_SI">Slovenian</option>
4. To activate footer link add this
<!--SOFTACULOUS-->
in the following file in wp.zip
wp-content/themes/twentytwenty/footer.php
wp-content/themes/twentynineteen/footer.php
wp-content/themes/twentyseventeen/template-parts/footer/site-info.php
wp-content/themes/twentysixteen/footer.php
NOTE : When a new theme is added in WordPress do the following tasks :
- add the line in install.xml and upgrade.xml as well
- add condition in upgrade.php ( in __pre_unzip function )
- update extend.php $templates['list']['wp-default'] array
- update new default theme screenshots in website/www/images/wp-default
5. 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.
The guide to install Multisite Manually :
https://wordpress.org/support/article/create-a-network/
6. (101, 'rewrite_rules', '', 'yes'), Keep it blank, WordPress generates it automatically
7. In multisite sql
After Configuring the Network, dump the SQL before logging in.
8. 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, WordPress generates it automatically
(115, 'can_compress_scripts', '0', 'yes');
also change the AUTO INCREMENT as it is in the dumped SQL of Original database.
9. Remove inserts in the sitemeta table after "active_sitewide_plugins" in MU
10. Remove the language files related to particular theme from languages/ if a theme is deleted by WordPress.
11. (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.
12. From 4.5.1 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 from 4.2.2
13. In case of major update please update the popularfx database.
14. While manual installation keep root writable and configure .htaccess as _htaccess.
15. configure [[permalink_structure]] only in wp.sql. Not in multisite.sql.
16. _index.php is our file no need to change it.
17. Remove Storage ENGINE "ENGINE=InnoDB" from all the CREATE TABLE queries in wp.sql and multisite.sql as WordPress sets the storage engine based on the default set in the MySQL Server.
18. when we add/delete a plugin update the edit.php and edit.xml file.
19. The language is configured in database under 'options' and 'sitemeta' tables for normal and multi site respectively. We use to manage language in version.php however this use to get reverted in case of persian language as observed. Hence we have now started handling in database and for multi site it was handled default in database. Also version.php is now removed because of this. (Since v4.8.1)
20. Boldgrid download link :
http://repo.boldgrid.com/boldgrid-inspirations.zip
21. We have added classic-editor plugin since 5.0.0 and we need to check in manual installation for extra insert classic-editor-replace under
options table. If any changes, change in install, edit, upgrade.
22. Remove __update_themes() and __update_plugins() functions only from the extend.php from the existing branch whenver you add a new branch. This means that this function shall only be a part of the current wp and not the old one's like wp50.
23. The WP_AUTO_UPDATE_CORE setting in wp-contig.php and _wp-config.php is added because when we install old version of WordPress we do not want it to auto upgrade to latest version because since WordPress 5.6 WordPress auto updates itself for major versions as well. When making the latest version as an old branch do not forget to add changes related to WP_AUTO_UPDATE_CORE in
install.php
wp-config.php
_wp-config.php var/softaculous/wp56/notes.txt 0000644 00000013557 15054555643 0012424 0 ustar 00 1. Download the language files from :
http://codex.wordpress.org/L10n:Localization_Teams (https://nl.wordpress.org/)
and copy them to the /var/softaculous/wp/languages/LANGUAGE_CODE.zip
2. The language files for the following languages have been updated to 5.6.15 :
<option value="ar">Arabic</option>
<option value="bg_BG">Bulgarian</option>
<option value="ca">Catalan</option>
<option value="cs_CZ">Czech</option>
<option value="da_DK">Danish</option>
<option value="de_DE">German</option>
<option value="el">Greek</option>
<option value="es_ES">Spanish</option>
<option value="fa_IR">Persian</option>
<option value="fi">Finnish</option>
<option value="fr_FR">French</option>
<option value="he_IL">Hebrew</option>
<option value="hr">Croatian</option>
<option value="hu_HU">Hungarian</option>
<option value="id_ID">Indonesian</option>
<option value="it_IT">Italian</option>
<option value="ja">Japanese</option>
<option value="ko_KR">Korean</option>
<option value="nb_NO">Norwegian</option>
<option value="nl_NL">Dutch</option>
<option value="pl_PL">Polish</option>
<option value="pt_BR">Portuguese-BR</option>
<option value="pt_PT">Portuguese</option>
<option value="ro_RO">Romanian</option>
<option value="ru_RU">Russian</option>
<option value="sk_SK">Slovak</option>
<option value="sq">Albanian</option>
<option value="sv_SE">Swedish</option>
<option value="th">Thai</option>
<option value="tr_TR">Turkish</option>
<option value="uk">Ukrainian</option>
<option value="vi">Vietnamese</option>
<option value="zh_CN">Chinese(Simplified)</option>
<option value="zh_HK">Chinese (Hong Kong)</option>
<option value="zh_TW">Chinese(Traditional)</option>
3. Please try to update these languages if they are available for 5.6.15
<option value="sl_SI">Slovenian</option>
4. To activate footer link add this
<!--SOFTACULOUS-->
in the following file in wp.zip
wp-content/themes/twentytwenty/footer.php
wp-content/themes/twentynineteen/footer.php
wp-content/themes/twentyseventeen/template-parts/footer/site-info.php
wp-content/themes/twentysixteen/footer.php
NOTE : When a new theme is added in WordPress do the following tasks :
- add the line in install.xml and upgrade.xml as well
- add condition in upgrade.php ( in __pre_unzip function )
- update extend.php $templates['list']['wp-default'] array
- update new default theme screenshots in website/www/images/wp-default
5. 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.
The guide to install Multisite Manually :
https://wordpress.org/support/article/create-a-network/
6. (101, 'rewrite_rules', '', 'yes'), Keep it blank, WordPress generates it automatically
7. In multisite sql
After Configuring the Network, dump the SQL before logging in.
8. 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, WordPress generates it automatically
(115, 'can_compress_scripts', '0', 'yes');
also change the AUTO INCREMENT as it is in the dumped SQL of Original database.
9. Remove inserts in the sitemeta table after "active_sitewide_plugins" in MU
10. Remove the language files related to particular theme from languages/ if a theme is deleted by WordPress.
11. (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.
12. From 4.5.1 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 from 4.2.2
13. In case of major update please update the popularfx database.
14. While manual installation keep root writable and configure .htaccess as _htaccess.
15. configure [[permalink_structure]] only in wp.sql. Not in multisite.sql.
16. _index.php is our file no need to change it.
17. Remove Storage ENGINE "ENGINE=InnoDB" from all the CREATE TABLE queries in wp.sql and multisite.sql as WordPress sets the storage engine based on the default set in the MySQL Server.
18. when we add/delete a plugin update the edit.php and edit.xml file.
19. The language is configured in database under 'options' and 'sitemeta' tables for normal and multi site respectively. We use to manage language in version.php however this use to get reverted in case of persian language as observed. Hence we have now started handling in database and for multi site it was handled default in database. Also version.php is now removed because of this. (Since v4.8.1)
20. Boldgrid download link :
http://repo.boldgrid.com/boldgrid-inspirations.zip
21. We have added classic-editor plugin since 5.0.0 and we need to check in manual installation for extra insert classic-editor-replace under
options table. If any changes, change in install, edit, upgrade.
22. Remove __update_themes() and __update_plugins() functions only from the extend.php from the existing branch whenver you add a new branch. This means that this function shall only be a part of the current wp and not the old one's like wp50.
23. The WP_AUTO_UPDATE_CORE setting in wp-contig.php and _wp-config.php is added because when we install old version of WordPress we do not want it to auto upgrade to latest version because since WordPress 5.6 WordPress auto updates itself for major versions as well. When making the latest version as an old branch do not forget to add changes related to WP_AUTO_UPDATE_CORE in
install.php
wp-config.php
_wp-config.php var/softaculous/wp64/notes.txt 0000644 00000014015 15054555657 0012416 0 ustar 00 1. Download the language files from :
http://codex.wordpress.org/L10n:Localization_Teams (https://nl.wordpress.org/)
and copy them to the /var/softaculous/wp/languages/LANGUAGE_CODE.zip
2. The language files for the following languages have been updated to 6.4.6 :
<option value="ar">Arabic</option>
<option value="bg_BG">Bulgarian</option>
<option value="ca">Catalan</option>
<option value="cs_CZ">Czech</option>
<option value="da_DK">Danish</option>
<option value="de_DE">German</option>
<option value="el">Greek</option>
<option value="es_ES">Spanish</option>
<option value="fa_IR">Persian</option>
<option value="fi">Finnish</option>
<option value="fr_FR">French</option>
<option value="hr">Croatian</option>
<option value="hu_HU">Hungarian</option>
<option value="id_ID">Indonesian</option>
<option value="it_IT">Italian</option>
<option value="ja">Japanese</option>
<option value="ko_KR">Korean</option>
<option value="nb_NO">Norwegian</option>
<option value="nl_NL">Dutch</option>
<option value="pl_PL">Polish</option>
<option value="pt_BR">Portuguese-BR</option>
<option value="pt_PT">Portuguese</option>
<option value="ro_RO">Romanian</option>
<option value="ru_RU">Russian</option>
<option value="sk_SK">Slovak</option>
<option value="sl_SI">Slovenian</option>
<option value="sq">Albanian</option>
<option value="sv_SE">Swedish</option>
<option value="tr_TR">Turkish</option>
<option value="uk">Ukrainian</option>
<option value="zh_CN">Chinese(Simplified)</option>
<option value="zh_TW">Chinese(Traditional)</option>
3. Please try to update these languages if they are available for 6.4.6
<option value="he_IL">Hebrew</option>
<option value="th">Thai</option>
<option value="vi">Vietnamese</option>
<option value="zh_HK">Chinese (Hong Kong)</option>
4. To activate footer link add this
<!--SOFTACULOUS-->
in the following file in wp.zip
wp-content/themes/twentytwentyfour/footer.php
wp-content/themes/twentytwentythree/patterns/footer-default.php
wp-content/themes/twentytwentytwo/inc/patterns/footer-default.php
NOTE : When a new theme is added in WordPress do the following tasks :
- add the line in install.xml and upgrade.xml as well
- add condition in upgrade.php ( in __pre_unzip function )
- update extend.php $templates['list']['wp-default'] array
- update new default theme screenshots in website/www/images/wp-default
5. 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.
The guide to install Multisite Manually :
https://wordpress.org/support/article/create-a-network/
6. (101, 'rewrite_rules', '', 'yes'), Keep it blank, WordPress generates it automatically
7. In multisite sql
After Configuring the Network, dump the SQL before logging in.
8. 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, WordPress generates it automatically
(115, 'can_compress_scripts', '0', 'yes');
also change the AUTO INCREMENT as it is in the dumped SQL of Original database.
9. Remove inserts in the sitemeta table after "active_sitewide_plugins" in MU
10. Remove the language files related to particular theme from languages/ if a theme is deleted by WordPress.
11. (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.
12. From 4.5.1 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 from 4.2.2
13. In case of major update please update the popularfx database.
14. While manual installation keep root writable and configure .htaccess as _htaccess.
15. configure [[permalink_structure]] only in wp.sql. Not in multisite.sql.
16. _index.php is our file no need to change it.
17. Remove Storage ENGINE "ENGINE=InnoDB" from all the CREATE TABLE queries in wp.sql and multisite.sql as WordPress sets the storage engine based on the default set in the MySQL Server.
18. when we add/delete a plugin update the edit.php and edit.xml file.
19. The language is configured in database under 'options' and 'sitemeta' tables for normal and multi site respectively. We use to manage language in version.php however this use to get reverted in case of persian language as observed. Hence we have now started handling in database and for multi site it was handled default in database. Also version.php is now removed because of this. (Since v4.8.1)
20. Boldgrid download link :
http://repo.boldgrid.com/boldgrid-inspirations.zip
21. We have added classic-editor plugin since 5.0.0 and we need to check in manual installation for extra insert classic-editor-replace under
options table. If any changes, change in install, edit, upgrade.
22. Remove __update_themes() and __update_plugins() functions only from the extend.php from the existing branch whenver you add a new branch. This means that this function shall only be a part of the current wp and not the old one's like wp50.
23. The WP_AUTO_UPDATE_CORE setting in wp-contig.php and _wp-config.php is added because when we install old version of WordPress we do not want it to auto upgrade to latest version because since WordPress 5.6 WordPress auto updates itself for major versions as well. When making the latest version as an old branch do not forget to add changes related to WP_AUTO_UPDATE_CORE in
install.php
wp-config.php
_wp-config.php
24. Do not encode wp-cli file. Keep it as it is.
25. Check the "[[punycode_softurl]]/?p=4" Auto Draft entry in post table. IN MULTISITE and remove that entry from both the sqls.
var/softaculous/wp49/notes.txt 0000644 00000012246 15054555667 0012426 0 ustar 00 1. Download the language files from :
http://codex.wordpress.org/L10n:Localization_Teams (https://nl.wordpress.org/)
and copy them to the /var/softaculous/wp/languages/LANGUAGE_CODE.zip
2. The language files for the following languages have been updated to 4.9.27 :
<option value="ar">Arabic</option>
<option value="bg_BG">Bulgarian</option>
<option value="ca">Catalan</option>
<option value="cs_CZ">Czech</option>
<option value="da_DK">Danish</option>
<option value="de_DE">German</option>
<option value="el">Greek</option>
<option value="es_ES">Spanish</option>
<option value="fa_IR">Persian</option>
<option value="fi">Finnish</option>
<option value="fr_FR">French</option>
<option value="he_IL">Hebrew</option>
<option value="hr">Croatian</option>
<option value="hu_HU">Hungarian</option>
<option value="id_ID">Indonesian</option>
<option value="it_IT">Italian</option>
<option value="ja">Japanese</option>
<option value="ko_KR">Korean</option>
<option value="nb_NO">Norwegian</option>
<option value="nl_NL">Dutch</option>
<option value="pl_PL">Polish</option>
<option value="pt_BR">Portuguese-BR</option>
<option value="pt_PT">Portuguese</option>
<option value="ro_RO">Romanian</option>
<option value="ru_RU">Russian</option>
<option value="sk_SK">Slovak</option>
<option value="sl_SI">Slovenian</option>
<option value="sq">Albanian</option>
<option value="sv_SE">Swedish</option>
<option value="th">Thai</option>
<option value="tr_TR">Turkish</option>
<option value="uk">Ukrainian</option>
<option value="vi">Vietnamese</option>
<option value="zh_CN">Chinese(Simplified)</option>
<option value="zh_HK">Chinese (Hong Kong)</option>
<option value="zh_TW">Chinese(Traditional)</option>
3. Please try to update these languages if they are available for 4.9.27
4. To activate footer link add this
<!--SOFTACULOUS-->
in the following file in wp.zip
wp-content/themes/twentyseventeen/template-parts/footer/site-info.php
wp-content/themes/twentysixteen/footer.php
wp-content/themes/twentyfifteen/footer.php
NOTE : When a new theme is added in WordPress do the following tasks :
- add the line in install.xml and upgrade.xml as well
- add condition in upgrade.php ( in __pre_unzip function )
- update extend.php $templates['list']['wp-default'] array
- update new default theme screenshots in website/www/images/wp-default
5. 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.
The guide to install Multisite Manually :
https://wordpress.org/support/article/create-a-network/
6. (101, 'rewrite_rules', '', 'yes'), Keep it blank, WordPress generates it automatically
7. In multisite sql
After Configuring the Network, dump the SQL before logging in.
8. 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, WordPress generates it automatically
(115, 'can_compress_scripts', '0', 'yes');
also change the AUTO INCREMENT as it is in the dumped SQL of Original database.
9. Remove inserts in the sitemeta table after "active_sitewide_plugins" in MU
10. Remove the language files related to particular theme from languages/ if a theme is deleted by WordPress.
11. (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.
12. From 4.5.1 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 from 4.2.2
13. In case of major update please update the popularfx database.
14. While manual installation keep root writable and configure .htaccess as _htaccess.
15. configure [[permalink_structure]] only in wp.sql. Not in multisite.sql.
16. _index.php is our file no need to change it.
17. Remove Storage ENGINE "ENGINE=InnoDB" from all the CREATE TABLE queries in wp.sql and multisite.sql as WordPress sets the storage engine based on the default set in the MySQL Server.
18. when we add/delete a plugin update the edit.php and edit.xml file.
19. The language is configured in database under 'options' and 'sitemeta' tables for normal and multi site respectively. We use to manage language in version.php however this use to get reverted in case of persian language as observed. Hence we have now started handling in database and for multi site it was handled default in database. Also version.php is now removed because of this. (Since v4.8.1)
20. Boldgrid download link :
http://repo.boldgrid.com/boldgrid-inspirations.zip
21. Always check for the default akismet and hello dolly plugin's latest version in all branches of wordpress. If there is old package in minor versions, manually replace with the latest one in our package.
var/softaculous/wp54/notes.txt 0000644 00000012654 15054555704 0012415 0 ustar 00 1. Download the language files from :
http://codex.wordpress.org/L10n:Localization_Teams (https://nl.wordpress.org/)
and copy them to the /var/softaculous/wp/languages/LANGUAGE_CODE.zip
Please update the notes :
2. The language files for the following languages have been updated to 5.4.17 :
<option value="ar">Arabic</option>
<option value="bg_BG">Bulgarian</option>
<option value="ca">Catalan</option>
<option value="cs_CZ">Czech</option>
<option value="da_DK">Danish</option>
<option value="de_DE">German</option>
<option value="el">Greek</option>
<option value="es_ES">Spanish</option>
<option value="fa_IR">Persian</option>
<option value="fi">Finnish</option>
<option value="fr_FR">French</option>
<option value="he_IL">Hebrew</option>
<option value="hr">Croatian</option>
<option value="hu_HU">Hungarian</option>
<option value="id_ID">Indonesian</option>
<option value="it_IT">Italian</option>
<option value="ja">Japanese</option>
<option value="ko_KR">Korean</option>
<option value="nb_NO">Norwegian</option>
<option value="nl_NL">Dutch</option>
<option value="pl_PL">Polish</option>
<option value="pt_BR">Portuguese-BR</option>
<option value="pt_PT">Portuguese</option>
<option value="ro_RO">Romanian</option>
<option value="ru_RU">Russian</option>
<option value="sk_SK">Slovak</option>
<option value="sq">Albanian</option>
<option value="sv_SE">Swedish</option>
<option value="th">Thai</option>
<option value="tr_TR">Turkish</option>
<option value="uk">Ukrainian</option>
<option value="vi">Vietnamese</option>
<option value="zh_CN">Chinese(Simplified)</option>
<option value="zh_HK">Chinese (Hong Kong)</option>
<option value="zh_TW">Chinese(Traditional)</option>
3. Please try to update these languages if they are available for 5.4.17
<option value="sl_SI">Slovenian</option>
4. To activate footer link add this
<!--SOFTACULOUS-->
in the following file in wp.zip
wp-content/themes/twentytwenty/footer.php
wp-content/themes/twentynineteen/footer.php
wp-content/themes/twentyseventeen/template-parts/footer/site-info.php
wp-content/themes/twentysixteen/footer.php
NOTE : When a new theme is added in WordPress do the following tasks :
- add the line in install.xml and upgrade.xml as well
- add condition in upgrade.php ( in __pre_unzip function )
- update extend.php $templates['list']['wp-default'] array
- update new default theme screenshots in website/www/images/wp-default
5. 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.
The guide to install Multisite Manually :
https://wordpress.org/support/article/create-a-network/
6. (101, 'rewrite_rules', '', 'yes'), Keep it blank, WordPress generates it automatically
7. In multisite sql
After Configuring the Network, dump the SQL before logging in.
8. 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, WordPress generates it automatically
(115, 'can_compress_scripts', '0', 'yes');
also change the AUTO INCREMENT as it is in the dumped SQL of Original database.
9. Remove inserts in the sitemeta table after "active_sitewide_plugins" in MU
10. Remove the language files related to particular theme from languages/ if a theme is deleted by WordPress.
11. (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.
12. From 4.5.1 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 from 4.2.2
13. In case of major update please update the popularfx database.
14. While manual installation keep root writable and configure .htaccess as _htaccess.
15. configure [[permalink_structure]] only in wp.sql. Not in multisite.sql.
16. _index.php is our file no need to change it.
17. Remove Storage ENGINE "ENGINE=InnoDB" from all the CREATE TABLE queries in wp.sql and multisite.sql as WordPress sets the storage engine based on the default set in the MySQL Server.
18. when we add/delete a plugin update the edit.php and edit.xml file.
19. The language is configured in database under 'options' and 'sitemeta' tables for normal and multi site respectively. We use to manage language in version.php however this use to get reverted in case of persian language as observed. Hence we have now started handling in database and for multi site it was handled default in database. Also version.php is now removed because of this. (Since v4.8.1)
20. Boldgrid download link :
http://repo.boldgrid.com/boldgrid-inspirations.zip
21. We have added classic-editor plugin since 5.0.0 and we need to check in manual installation for extra insert classic-editor-replace under
options table. If any changes, change in install, edit, upgrade.
22. Always check for the default akismet plugin's latest version in all branches of wordpress. If there is old package in minor versions, manually replace with the latest one in our package. var/softaculous/mw14/notes.txt 0000644 00000003652 15054555740 0012404 0 ustar 00 ################ Untar downloaded tar.gz package on linux server and then make a ground zip. ################
1) Use Storage Engine Innodb.
2) Use binary database character set.
3) Use the License as "No license footer"
4) Check the language files exists in the /languages/messages/ it should be there with the downloaded zip.
5) We have added "tmpdir" in order to save cache at different locations for each installation to avoid conflicts between them. (v1.27.1)
https://www.mediawiki.org/wiki/Manual_talk:Upgrading#Shared_server_.2B_multiple_Mediawiki_installations
https://phabricator.wikimedia.org/T127127
We have added the following in LocalSettings.php
$wgTmpDirectory = "[[tmpdir]]";
6) PHP REQUIREMENT LINK: https://www.mediawiki.org/wiki/Manual:Installation_requirements
7) check "I'm bored already, just install the wiki." and continue in manual install
8) Check visual editor and other extension options in every major update. By clicking "ask me more questions" option. (Just to check)
9) removed inserts from "job" table because it creates entry after page access
10) Keep `content_sha1` value as it is in "content" table because it is same for all installations.
11)we have disable cross upgrade because we were getting following error post upgrading. eb786298294aef346a4e8c9b] 2020-03-27 11:45:10: Fatal exception of type "MWException"
(Reported issue to vendor as well) Check in next version if it resolves.(Got this error while upgrading from 1.31.12 to 1.35.1 so have disabled cross upgrade(i.e changed 'min_require' in info.xml as 1.35.0), check whether cross upgrade works in next version and also change 'min_require'. Cross upgrade re-enabled in version 1.36.0 with minimum version 1.31.0 in info.xml.
12) Since 1.43.0 searchindex entry default charset is set to utf8mb4 (maintenance\tables-generated.sql) hence we have not handled it.
13) Uncheck "Share data about this installation with MediaWiki developers" during manual installation. var/softaculous/mw28/notes.txt 0000644 00000001705 15054556032 0012401 0 ustar 00 ################ Untar downloaded tar.gz package on linux server and then make a ground zip. ################
1) Use Storage Engine Innodb.
2) Use binary database character set.
3) Use the License as "No license footer"
4) Check the language files exists in the /languages/classes/ & /languages/messages/ it should be there with the downloaded zip.
5) We have added "tmpdir" in order to save cache at different locations for each installation to avoid conflicts between them. (v1.27.1)
https://www.mediawiki.org/wiki/Manual_talk:Upgrading#Shared_server_.2B_multiple_Mediawiki_installations
https://phabricator.wikimedia.org/T127127
We have added the following in LocalSettings.php
$wgTmpDirectory = "[[tmpdir]]";
6) PHP REQUIREMENT LINK: https://www.mediawiki.org/wiki/Manual:Installation_requirements
7) check "I'm bored already, just install the wiki." and continue in manual install
8) removed inserts from "job" table because it creates entry after page access var/softaculous/wp61/notes.txt 0000644 00000013526 15054556047 0012413 0 ustar 00 1. Download the language files from :
http://codex.wordpress.org/L10n:Localization_Teams (https://nl.wordpress.org/)
and copy them to the /var/softaculous/wp/languages/LANGUAGE_CODE.zip
2. The language files for the following languages have been updated to 6.1.8 :
<option value="ar">Arabic</option>
<option value="bg_BG">Bulgarian</option>
<option value="ca">Catalan</option>
<option value="cs_CZ">Czech</option>
<option value="da_DK">Danish</option>
<option value="de_DE">German</option>
<option value="el">Greek</option>
<option value="es_ES">Spanish</option>
<option value="fa_IR">Persian</option>
<option value="fi">Finnish</option>
<option value="fr_FR">French</option>
<option value="he_IL">Hebrew</option>
<option value="hr">Croatian</option>
<option value="hu_HU">Hungarian</option>
<option value="id_ID">Indonesian</option>
<option value="it_IT">Italian</option>
<option value="ja">Japanese</option>
<option value="ko_KR">Korean</option>
<option value="nb_NO">Norwegian</option>
<option value="nl_NL">Dutch</option>
<option value="pl_PL">Polish</option>
<option value="pt_BR">Portuguese-BR</option>
<option value="pt_PT">Portuguese</option>
<option value="ro_RO">Romanian</option>
<option value="ru_RU">Russian</option>
<option value="sk_SK">Slovak</option>
<option value="sl_SI">Slovenian</option>
<option value="sq">Albanian</option>
<option value="sv_SE">Swedish</option>
<option value="tr_TR">Turkish</option>
<option value="uk">Ukrainian</option>
<option value="vi">Vietnamese</option>
<option value="zh_CN">Chinese(Simplified)</option>
<option value="zh_HK">Chinese (Hong Kong)</option>
<option value="zh_TW">Chinese(Traditional)</option>
3. Please try to update these languages if they are available for 6.1.8
<option value="th">Thai</option>
4. To activate footer link add this
<!--SOFTACULOUS-->
in the following file in wp.zip
wp-content/themes/twentytwentythree/patterns/footer-default.php
wp-content/themes/twentytwentytwo/inc/patterns/footer-default.php
wp-content/themes/twentytwentyone/footer.php
NOTE : When a new theme is added in WordPress do the following tasks :
- add the line in install.xml and upgrade.xml as well
- add condition in upgrade.php ( in __pre_unzip function )
- update extend.php $templates['list']['wp-default'] array
- update new default theme screenshots in website/www/images/wp-default
5. 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.
The guide to install Multisite Manually :
https://wordpress.org/support/article/create-a-network/
6. (101, 'rewrite_rules', '', 'yes'), Keep it blank, WordPress generates it automatically
7. In multisite sql
After Configuring the Network, dump the SQL before logging in.
8. 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, WordPress generates it automatically
(115, 'can_compress_scripts', '0', 'yes');
also change the AUTO INCREMENT as it is in the dumped SQL of Original database.
9. Remove inserts in the sitemeta table after "active_sitewide_plugins" in MU
10. Remove the language files related to particular theme from languages/ if a theme is deleted by WordPress.
11. (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.
12. From 4.5.1 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 from 4.2.2
13. In case of major update please update the popularfx database.
14. While manual installation keep root writable and configure .htaccess as _htaccess.
15. configure [[permalink_structure]] only in wp.sql. Not in multisite.sql.
16. _index.php is our file no need to change it.
17. Remove Storage ENGINE "ENGINE=InnoDB" from all the CREATE TABLE queries in wp.sql and multisite.sql as WordPress sets the storage engine based on the default set in the MySQL Server.
18. when we add/delete a plugin update the edit.php and edit.xml file.
19. The language is configured in database under 'options' and 'sitemeta' tables for normal and multi site respectively. We use to manage language in version.php however this use to get reverted in case of persian language as observed. Hence we have now started handling in database and for multi site it was handled default in database. Also version.php is now removed because of this. (Since v4.8.1)
20. Boldgrid download link :
http://repo.boldgrid.com/boldgrid-inspirations.zip
21. We have added classic-editor plugin since 5.0.0 and we need to check in manual installation for extra insert classic-editor-replace under
options table. If any changes, change in install, edit, upgrade.
22. Remove __update_themes() and __update_plugins() functions only from the extend.php from the existing branch whenver you add a new branch. This means that this function shall only be a part of the current wp and not the old one's like wp50.
23. The WP_AUTO_UPDATE_CORE setting in wp-contig.php and _wp-config.php is added because when we install old version of WordPress we do not want it to auto upgrade to latest version because since WordPress 5.6 WordPress auto updates itself for major versions as well. When making the latest version as an old branch do not forget to add changes related to WP_AUTO_UPDATE_CORE in
install.php
wp-config.php
_wp-config.php
var/softaculous/wp63/notes.txt 0000644 00000014012 15054556114 0012377 0 ustar 00 1. Download the language files from :
http://codex.wordpress.org/L10n:Localization_Teams (https://nl.wordpress.org/)
and copy them to the /var/softaculous/wp/languages/LANGUAGE_CODE.zip
2. The language files for the following languages have been updated to 6.3.6 :
<option value="ar">Arabic</option>
<option value="bg_BG">Bulgarian</option>
<option value="ca">Catalan</option>
<option value="cs_CZ">Czech</option>
<option value="da_DK">Danish</option>
<option value="de_DE">German</option>
<option value="el">Greek</option>
<option value="es_ES">Spanish</option>
<option value="fa_IR">Persian</option>
<option value="fi">Finnish</option>
<option value="fr_FR">French</option>
<option value="hr">Croatian</option>
<option value="hu_HU">Hungarian</option>
<option value="id_ID">Indonesian</option>
<option value="it_IT">Italian</option>
<option value="ja">Japanese</option>
<option value="ko_KR">Korean</option>
<option value="nb_NO">Norwegian</option>
<option value="nl_NL">Dutch</option>
<option value="pl_PL">Polish</option>
<option value="pt_BR">Portuguese-BR</option>
<option value="pt_PT">Portuguese</option>
<option value="ro_RO">Romanian</option>
<option value="ru_RU">Russian</option>
<option value="sk_SK">Slovak</option>
<option value="sl_SI">Slovenian</option>
<option value="sq">Albanian</option>
<option value="sv_SE">Swedish</option>
<option value="tr_TR">Turkish</option>
<option value="zh_CN">Chinese(Simplified)</option>
<option value="zh_TW">Chinese(Traditional)</option>
3. Please try to update these languages if they are available for 6.3.6
<option value="he_IL">Hebrew</option>
<option value="th">Thai</option>
<option value="uk">Ukrainian</option>
<option value="vi">Vietnamese</option>
<option value="zh_HK">Chinese (Hong Kong)</option>
4. To activate footer link add this
<!--SOFTACULOUS-->
in the following file in wp.zip
wp-content/themes/twentytwentythree/patterns/footer-default.php
wp-content/themes/twentytwentytwo/inc/patterns/footer-default.php
wp-content/themes/twentytwentyone/footer.php
NOTE : When a new theme is added in WordPress do the following tasks :
- add the line in install.xml and upgrade.xml as well
- add condition in upgrade.php ( in __pre_unzip function )
- update extend.php $templates['list']['wp-default'] array
- update new default theme screenshots in website/www/images/wp-default
5. 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.
The guide to install Multisite Manually :
https://wordpress.org/support/article/create-a-network/
6. (101, 'rewrite_rules', '', 'yes'), Keep it blank, WordPress generates it automatically
7. In multisite sql
After Configuring the Network, dump the SQL before logging in.
8. 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, WordPress generates it automatically
(115, 'can_compress_scripts', '0', 'yes');
also change the AUTO INCREMENT as it is in the dumped SQL of Original database.
9. Remove inserts in the sitemeta table after "active_sitewide_plugins" in MU
10. Remove the language files related to particular theme from languages/ if a theme is deleted by WordPress.
11. (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.
12. From 4.5.1 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 from 4.2.2
13. In case of major update please update the popularfx database.
14. While manual installation keep root writable and configure .htaccess as _htaccess.
15. configure [[permalink_structure]] only in wp.sql. Not in multisite.sql.
16. _index.php is our file no need to change it.
17. Remove Storage ENGINE "ENGINE=InnoDB" from all the CREATE TABLE queries in wp.sql and multisite.sql as WordPress sets the storage engine based on the default set in the MySQL Server.
18. when we add/delete a plugin update the edit.php and edit.xml file.
19. The language is configured in database under 'options' and 'sitemeta' tables for normal and multi site respectively. We use to manage language in version.php however this use to get reverted in case of persian language as observed. Hence we have now started handling in database and for multi site it was handled default in database. Also version.php is now removed because of this. (Since v4.8.1)
20. Boldgrid download link :
http://repo.boldgrid.com/boldgrid-inspirations.zip
21. We have added classic-editor plugin since 5.0.0 and we need to check in manual installation for extra insert classic-editor-replace under
options table. If any changes, change in install, edit, upgrade.
22. Remove __update_themes() and __update_plugins() functions only from the extend.php from the existing branch whenver you add a new branch. This means that this function shall only be a part of the current wp and not the old one's like wp50.
23. The WP_AUTO_UPDATE_CORE setting in wp-contig.php and _wp-config.php is added because when we install old version of WordPress we do not want it to auto upgrade to latest version because since WordPress 5.6 WordPress auto updates itself for major versions as well. When making the latest version as an old branch do not forget to add changes related to WP_AUTO_UPDATE_CORE in
install.php
wp-config.php
_wp-config.php
24. Do not encode wp-cli file. Keep it as it is.
25. Check the "[[punycode_softurl]]/?p=4" Auto Draft entry in post table. IN MULTISITE and remove that entry from both the sqls. var/softaculous/wp58/notes.txt 0000644 00000013556 15054601512 0012410 0 ustar 00 1. Download the language files from :
http://codex.wordpress.org/L10n:Localization_Teams (https://nl.wordpress.org/)
and copy them to the /var/softaculous/wp/languages/LANGUAGE_CODE.zip
2. The language files for the following languages have been updated to 5.8.11 :
<option value="ar">Arabic</option>
<option value="bg_BG">Bulgarian</option>
<option value="ca">Catalan</option>
<option value="cs_CZ">Czech</option>
<option value="da_DK">Danish</option>
<option value="de_DE">German</option>
<option value="el">Greek</option>
<option value="es_ES">Spanish</option>
<option value="fa_IR">Persian</option>
<option value="fi">Finnish</option>
<option value="fr_FR">French</option>
<option value="he_IL">Hebrew</option>
<option value="hr">Croatian</option>
<option value="hu_HU">Hungarian</option>
<option value="id_ID">Indonesian</option>
<option value="it_IT">Italian</option>
<option value="ja">Japanese</option>
<option value="ko_KR">Korean</option>
<option value="nb_NO">Norwegian</option>
<option value="nl_NL">Dutch</option>
<option value="pl_PL">Polish</option>
<option value="pt_BR">Portuguese-BR</option>
<option value="pt_PT">Portuguese</option>
<option value="ro_RO">Romanian</option>
<option value="ru_RU">Russian</option>
<option value="sk_SK">Slovak</option>
<option value="sl_SI">Slovenian</option>
<option value="sq">Albanian</option>
<option value="sv_SE">Swedish</option>
<option value="th">Thai</option>
<option value="tr_TR">Turkish</option>
<option value="uk">Ukrainian</option>
<option value="vi">Vietnamese</option>
<option value="zh_CN">Chinese(Simplified)</option>
<option value="zh_HK">Chinese (Hong Kong)</option>
<option value="zh_TW">Chinese(Traditional)</option>
3. Please try to update these languages if they are available for 5.8.11
4. To activate footer link add this
<!--SOFTACULOUS-->
in the following file in wp.zip
wp-content/themes/twentytwenty/footer.php
wp-content/themes/twentynineteen/footer.php
wp-content/themes/twentyseventeen/template-parts/footer/site-info.php
wp-content/themes/twentysixteen/footer.php
NOTE : When a new theme is added in WordPress do the following tasks :
- add the line in install.xml and upgrade.xml as well
- add condition in upgrade.php ( in __pre_unzip function )
- update extend.php $templates['list']['wp-default'] array
- update new default theme screenshots in website/www/images/wp-default
5. 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.
The guide to install Multisite Manually :
https://wordpress.org/support/article/create-a-network/
6. (101, 'rewrite_rules', '', 'yes'), Keep it blank, WordPress generates it automatically
7. In multisite sql
After Configuring the Network, dump the SQL before logging in.
8. 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, WordPress generates it automatically
(115, 'can_compress_scripts', '0', 'yes');
also change the AUTO INCREMENT as it is in the dumped SQL of Original database.
9. Remove inserts in the sitemeta table after "active_sitewide_plugins" in MU
10. Remove the language files related to particular theme from languages/ if a theme is deleted by WordPress.
11. (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.
12. From 4.5.1 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 from 4.2.2
13. In case of major update please update the popularfx database.
14. While manual installation keep root writable and configure .htaccess as _htaccess.
15. configure [[permalink_structure]] only in wp.sql. Not in multisite.sql.
16. _index.php is our file no need to change it.
17. Remove Storage ENGINE "ENGINE=InnoDB" from all the CREATE TABLE queries in wp.sql and multisite.sql as WordPress sets the storage engine based on the default set in the MySQL Server.
18. when we add/delete a plugin update the edit.php and edit.xml file.
19. The language is configured in database under 'options' and 'sitemeta' tables for normal and multi site respectively. We use to manage language in version.php however this use to get reverted in case of persian language as observed. Hence we have now started handling in database and for multi site it was handled default in database. Also version.php is now removed because of this. (Since v4.8.1)
20. Boldgrid download link :
http://repo.boldgrid.com/boldgrid-inspirations.zip
21. We have added classic-editor plugin since 5.0.0 and we need to check in manual installation for extra insert classic-editor-replace under
options table. If any changes, change in install, edit, upgrade.
22. Remove __update_themes() and __update_plugins() functions only from the extend.php from the existing branch whenver you add a new branch. This means that this function shall only be a part of the current wp and not the old one's like wp50.
23. The WP_AUTO_UPDATE_CORE setting in wp-contig.php and _wp-config.php is added because when we install old version of WordPress we do not want it to auto upgrade to latest version because since WordPress 5.6 WordPress auto updates itself for major versions as well. When making the latest version as an old branch do not forget to add changes related to WP_AUTO_UPDATE_CORE in
install.php
wp-config.php
_wp-config.php var/softaculous/mw19/notes.txt 0000644 00000003323 15054602623 0012375 0 ustar 00 ################ Untar downloaded tar.gz package on linux server and then make a ground zip. ################
1) Use Storage Engine Innodb.
2) Use binary database character set.
3) Use the License as "No license footer"
4) Check the language files exists in the /languages/classes/ & /languages/messages/ it should be there with the downloaded zip.
5) We have added "tmpdir" in order to save cache at different locations for each installation to avoid conflicts between them. (v1.27.1)
https://www.mediawiki.org/wiki/Manual_talk:Upgrading#Shared_server_.2B_multiple_Mediawiki_installations
https://phabricator.wikimedia.org/T127127
We have added the following in LocalSettings.php
$wgTmpDirectory = "[[tmpdir]]";
6) PHP REQUIREMENT LINK: https://www.mediawiki.org/wiki/Manual:Installation_requirements
7) check "I'm bored already, just install the wiki." and continue in manual install
8) Check visual editor and other extension options in every major update. By clicking "ask me more questions" option. (Just to check)
9) removed inserts from "job" table because it creates entry after page access
10) Keep `content_sha1` value as it is in "content" table because it is same for all installations.
11)we have disable cross upgrade because we were getting following error post upgrading. eb786298294aef346a4e8c9b] 2020-03-27 11:45:10: Fatal exception of type "MWException"
(Reported issue to vendor as well) Check in next version if it resolves.(Got this error while upgrading from 1.31.12 to 1.35.1 so have disabled cross upgrade(i.e changed 'min_require' in info.xml as 1.35.0), check whether cross upgrade works in next version and also change 'min_require'. Cross upgrade re-enabled in version 1.36.0 with minimum version 1.31.0 in info.xml. var/softaculous/soho/notes.txt 0000644 00000000700 15054647405 0012553 0 ustar 00 1. Please make the zip from manual.
2. Please export the soho.sql after login. It should contain "site_pages" table.
3. Please delete the file sohoadmin/filebin/eula.lic from the manual while zipping
4. Download the installer from here:
http://www.soholaunch.com/Install_Soholaunch.php (Not valid form v4.9.4 r43)
5. Get the link to download the package from here (Full package):
http://update.securexfer.net/public_builds/api-build_info-latest.php var/softaculous/presta8/notes.txt 0000644 00000004630 15054663037 0013176 0 ustar 00 1. Download the package from Github because the website packages contains additional modules which isn't working in a sub directory as they are for commercial purpose. https://www.prestashop.com/forums/topic/1085022-unable-to-install-prestashop-81x-in-a-subdirectory/
2. Keep root writable while installing manually.
3. Unzip prestashop files on server only. Let UI unzip the files. Before starting the installation make the zip on server and download.
4. [IMP] TAKE SQL DUMP WHEN INSTALLATION COMPLETES AND FILE DUMP ON ADMIN PANEL
5. check and
copy /translations/* [Not required anymore]
copy config/themes/* (Except config/themes/classic/shop1.json, need to configure this file) (Not required from 1.7.1.0)
copy img/*
copy mails/en/* except files which uses softurl
copy modules/* except files which uses softurl
Delete /var/cache/prod
6. Copy bootstrap.php from config folder and create _bootstrap.php and make following changes to get new_cookie_key :
"echo '<new_cookie_key>'.$key.'</new_cookie_key>';"
This is our change to generate the new_cookie_key, Also create clone_bootstrap.php and make changes to unset new_cookie_key>
7. If it is asked for country choose "United States" and Shop timezone as "US/Eastern"
8. Keep demo data "enabled" and SSL entry "blank" in manual installation.
9. While manual install - installation of modules : Install all modules (recommended)
10. PHP REQUIREMENT LINK: https://devdocs.prestashop-project.org/8/basics/installation/system-requirements/#php-requirements
11. No Documentation provided to upgrade prestashop 1.7.x.x hence we have not provided the same. http://doc.prestashop.com/dashboard.action
12. We have removed mcrypt extension because a user reported this via ticket.
13. [NA] config.php generates on visiting frontlink in manual installation.
14. [NA] Under [[dbprefix]]configuration table keep 'value' column blank for the following 'name' columns i.e : PS_ACCOUNTS_RSA_PRIVATE_KEY, PS_ACCOUNTS_RSA_PUBLIC_KEY and PS_ACCOUNTS_RSA_SIGN_DATA blank , as they are made again after logging into the admin panel.
15. [NA] For our reference : Since Presta 8.0.1, while manual installation Prestashop is installed in maintenance mode and demo data isnt displayed . We have kept the same. To enable store users will have to go to admin panel -> click maintenance mode icon and check 'Enable Store' to enable store and display demo data content on frontend. (Requires in Prestashop commercial package) var/softaculous/wbce/notes.txt 0000644 00000001001 15054747751 0012523 0 ustar 00 1. Some images are created in media folder which does not generate after install, We copied it in our install.php. change and update install.php if new images are created. (Not needed since 1.4.0)
2. Select GMT -4 in install its America/New_York Time Zone
3. PHP REQUIREMENT LINK: https://help.wbce-cms.org/pages/installation/system-requirements.php
4. Remove inserts from [[dbprefix]]blocking,[[dbprefix]]dbsessions table as entries are made after logging in.
5. Move USING BTREE entries to the left in sql file. var/softaculous/glpi/notes.txt 0000644 00000000612 15054751021 0012526 0 ustar 00 1. PHP REQUIREMENT LINK : http://glpi-install.readthedocs.io/en/latest/prerequisites.html#php
2. For our note if any users see the warning of 'utf8mb4 support requires additional migration' after upgrade ask them to run
"php bin/console glpi:migration:utf8mb4" and "php bin/console glpi:migration:unsigned_keys". This is shown inside admin panel as well.
(While upgrading from 9.5.x to 10.0.1) var/softaculous/mybb/notes.txt 0000644 00000003121 15055027020 0012516 0 ustar 00 1) For Languages add [[language]] in SQL and in settings.php
2) We add /language/[[language]].zip for all language
* Download the language files from:
http://community.mybb.com/mods.php?action=browse&category=translations
check for exact structure of language, if it match then only update the language pack.
Remove the install/ directory from language pack
3) Database Engine MySQL Improved
4) Leave ACP Pin blank
5) Copy the cache/theme/theme1 and cache/theme/theme2 folder from manual (if css is not generated) (Not required since 1.8.33)(Required again in 1.8.34)
6) Verify the steps in manual upgrade and auto upgrade (debug mode) and confirm the steps are correct. The auto upgrade is complicated.
7) Update the file org_upgrade.php (from original zip /install/upgrade.php) and mod_upgrade.php (from original zip + our changes) of the new version. This change is for auto upgrade.
We have commented the login part and added the following lines :
// Softaculous Change
echo '<softupdate_ver>'.$candidates[0].'</softupdate_ver>';
8) Update the file index.php (from original zip /admin/index.php) and _index.php (from original zip + our changes) of the new version. This change is for auto upgrade from version less than 1.8
We have added if statements for login part
9) PHP REQUIREMENT LINK: https://docs.mybb.com/1.8/install/requirements/ ( We have kept requirement to 7.0.0 bcoz it was throwing error on PHP < 7.0 , https://github.com/mybb/mybb/issues/4705 ). Check if this is fixed in next version, check and change version accordingly. Reverted to PHP 5.5.0 in 1.8.35, as it works fine now on PHP < 7.0.