ÿØÿà JFIF    ÿÛ „ ( %!1!%*+...983,7(-.- var/softaculous/conc85/Notes.txt000075500000004726152345554540012663 0ustar00*******Select System Time Zone as "New York" in manual installation ******* 1) Install twice i.e with and without sampledata and give the name of sql file accordingly. 2) Copy the whole application/files folder from manual installed with sampledata and then make data.zip (DONT FORGET TO EMPTY the contents of cache folder) 3) Add following line for language in concrete.php (Not required since 8.3.0 as they can now be downloaded during installation or through the dashboard from the site as required by the user confirmed with vendor) "locale" => "[[language]]", and "i18n" => array( "choose_language_login" => null ) 4) Include /application/config/doctrine/ from manual with sample data to the zip (Make sure that there is proxies folder and php files inside it) 5) If user forgets to login before upgrade then Login can be disabled by adding following code in concrete.php ( This is only for our knowledge) return array( 'updates' => array( 'enable_permissions_protection' => false ) ); 6) Table 'ExpressForm170ExpressSearchIndexAttributes' is not getting generated after upgrading from 5.7.5.11. (Confirmed with Vendor) 7) Changes in Constraints of "ExpressEntities" table were not reflected post upgrade from 8.0.3 to 8.1.0. Do check this in next version. (Confirmed by vendor) 8) PHP REQUIREMENT LINK: https://documentation.concretecms.org/developers/introduction/system-requirements We have set PHP to 7.1 since 8.5.10 because it throws error below that.(Reverted to PHP 5.5.9 as it is working since 8.5.12) 9) We have applied upgrade fix given by vendor in this release i.e 8.4.1 as we were getting error on testing cross upgrade from 5.7.x.x to 8.4.1. Vendor shall update the same patch in next release. https://github.com/concrete5/concrete5/commit/0379b0cb3f32b798cd62599589d51afe426052ba 10) We are excluding all files and folders in upgrade because only the concrete folder needs to be updated. Also we have confirmed this with vendor via email and they said we need to delete concrete folder first, then unzip the updated folder. Please check if any new folders/files are added in future version in root folder then we will have to add it to exclude. Since (8.4.1). 11) "mcrypt" php extension removed from requirements as is does not work in php 7.2. 12) Ignore the Mysql upgrade warning in manual installation. Confirmed with vendor. 13) we have disabled upgrade from 5.7.x.x because it is giving error. We have emailed this issue to the vendor. (Enabled from 8.5.2)var/softaculous/conc56/Notes.txt000075500000002102152345707360012643 0ustar001) Install twice i.e with and without sampledata and give the name of sql file accordingly. 2) Copy the whole /files folder from manual installed with sampledata and then make data.zip (DONT FORGET TO EMPTY the contents of cache folder) 3) Please do not replace timestamp in FileVersions table in sql. (There is no timestamp in FileVersions table) 4) Remove ENVIRONMENT_CACHE from the Config table. Concrete5 generates it. 5) We have excluded the file "config/site_theme_paths.php" during upgrade becuase it has the user's customization and should not be overwritten. 6) Add this line in Config table of both sql for language ('SITE_LOCALE', '[[date_gmt]]', '[[language]]', 0, 0); ( Not required since 5.6.4.0 as languages are not vailable in package itself ) 7) PHP7 support was added in version 5.6.4.0 and its mentioned here https://documentation.concrete5.org/developers/introduction/version-history/5640 . So we have removed PHP7 lt condition from info.xml and mcrypt as well to make script compatible with PHP 7.4. Script works on PHP 7.4 ,tested manually as well as with Softaculous.var/softaculous/sitemagic/Notes.txt000075500000001311152346026570013512 0ustar001. Take dump after login and changing password from Admin->Settings 2. From next version for demo , no need to replace the file base/SMEnvironment.class.php(patched one) if vendor has patched the process in next version for file attachments.(which generated warnings).it shall be done by post_install hook. (Not required since 4.2.3) 3. PHP REQUIREMENT LINK : https://sitemagic.org/Download.html 4. upgrade.php is not excluded from package because it's password protected and not delete automatically by script 5. Release date : Official Facebook page - https://www.facebook.com/SitemagicCMS 6. We have given the package for v4.4.1 with __MACOSX directory. Please check and remove if needed in the next version.var/softaculous/magento17/Notes.txt000075500000000521152346211270013342 0ustar001) Select Database for saving session storage while insatllation on manual 2) Just check that "USING BTREE" is not there in the MySQL file. 3) Always check the file permissions 4) Release date : https://magento.com/tech-resources/download 5) PHP REQUIREMENT LINK: http://docs.magento.com/m1/ce/user_guide/magento/system-requirements.htmlvar/softaculous/nucleus/Notes.txt000064400000000274152346611010013214 0ustar001) Download 'upgrades' folder and put it in zip - 'nucleus/upgrades' (Not needed, it is included in the default package itself from 3.70) 2) $CONF['alertOnSecurityRisk'] = 0; in config.phpvar/softaculous/conc8/Notes.txt000064400000006560152347132460012564 0ustar00******* Select System Time Zone as "New York" in manual installation ******* ******* Select Atomik theme in sample data manual installation ******* 1) Install twice i.e with and without sampledata and give the name of sql file accordingly. 2) Copy the whole application/files folder from manual installed with sampledata and then make data.zip (DONT FORGET TO EMPTY the contents of cache folder, except index.html) 3) Add following line for language in concrete.php (Not required since 8.3.0 as they can now be downloaded during installation or through the dashboard from the site as required by the user confirmed with vendor) "locale" => "[[language]]", and "i18n" => array( "choose_language_login" => null ) 4) Include /application/config/doctrine/ from manual with sample data to the zip (Make sure that there is proxies folder and php files inside it) 5) If user forgets to login before upgrade then Login can be disabled by adding following code in concrete.php ( This is only for our knowledge) return array( 'updates' => array( 'enable_permissions_protection' => false ) ); 6) Table 'ExpressForm170ExpressSearchIndexAttributes' is not getting generated after upgrading from 5.7.5.11. (Confirmed with Vendor) 7) Changes in Constraints of "ExpressEntities" table were not reflected post upgrade from 8.0.3 to 8.1.0. Do check this in next version. (Confirmed by vendor) 8) PHP REQUIREMENT LINK: https://documentation.concretecms.org/developers/introduction/system-requirements 9) We have applied upgrade fix given by vendor in this release i.e 8.4.1 as we were getting error on testing cross upgrade from 5.7.x.x to 8.4.1. Vendor shall update the same patch in next release. https://github.com/concrete5/concrete5/commit/0379b0cb3f32b798cd62599589d51afe426052ba 10) We are excluding all files and folders in upgrade because only the concrete folder needs to be updated. Also we have confirmed this with vendor via email and they said we need to delete concrete folder first, then unzip the updated folder. Please check if any new folders/files are added in future version in root folder then we will have to add it to exclude. Since (8.4.1). 11) "mcrypt" php extension removed from requirements as is does not work in php 7.2. 12) Ignore the Mysql upgrade warning in manual installation. Confirmed with vendor. 13) we have disabled upgrade from 5.7.x.x because it is giving error. We have emailed this issue to the vendor. (Enabled from 8.5.2) 14) Few "OAuth....." tables are not genereted when upgraded from 8.5.6 to 9.0.1 Vendor said to igonre them as these tables are only used when concrete is being used as a login provider for another external concrete site (chat done via email) 15) Under `Config` table keep 'marketplace.key.private' and 'marketplace.key.public' values blank . These keys are generated again when user connects to the Marketplace.(For extra plugins and themes first Connect to marketplace Dashboard {System & Settings>Basics>Marketplace}) 16) [IMP] Check 'ptComposerControlObject' id's every time in normmal and sample data sql if there is a change in id's, change in clone.php as well. 17) Delete inserts from `BoardInstanceLogEntries` and `BoardInstanceLogs` from sample_data.sql(These are generated in sample_data.sql only). These Logs can be regenerated via admin panel under 'Dashboard->Boards->{{BOARD_NAME}}(ex: Blog)->Board Instances->Instance Details->Regenerate'. var/softaculous/magento18/Notes.txt000075500000004757152350751450013366 0ustar001) Install twice manually, with and without sample data. Always check the difference between packages of with and without sample data and make sampledata.zip accordingly. 2) Select "Db" for saving session storage while installation on manual.(we have changed session storage to "Files" from magento 2.2.4 as it was giving error on accessing System -> Tools -> Web Setup Wizard) Changed to db since 2.2.10 3) Select Timezone America/NewYork 4) Just check that "USING BTREE" should be on the left i.e. not at the end 5) Always check the file permissions 6) Check and copy pub/media/theme folder from manual to zip and check name of the images. It should match with entry in SQL.(without sample data) 7) Check and copy pub/media/* folder from manual to sampledata.zip and check name of the images. It should match with entry in SQL. (with sample data) 8) Take dump using mysql command /usr/local/apps/mysql56/bin/mysqldump --routines -u root -ppass soft_mage282 > mage282.sql 9) set WRITEABLE_DIRECTORY_MODE = 0755; and WRITEABLE_FILE_MODE = 0644; in vendor/magento/framework/Filesystem/DriverInterface.php and then start with manual installation. (NOT REQUIRED FROM 2.0.7) 10) "hash_config" values in indexer_state table is same for all installation from 2.1.0, hence no need to change this values. 11) We have disabled magento 2.x on windows because icons are not loading properly post login. This is happening because it redirects to symlinks to load all the icons and on windows symlinks are not created and also as per their requirement, magento 2.x is not supported on windows OS. 12) PHP REQUIREMENT LINK: http://devdocs.magento.com/guides/v2.2/install-gde/system-requirements-tech.html 13) Magento 2.2.2 requires Apache mod_version to be enabled. 14) Upgrade is not possible at present because magento2 uses either system's upgrade utility or the command line upgrade. http://devdocs.magento.com/guides/v2.2/comp-mgr/bk-compman-upgrade-guide.html 15) Change "Magento\Framework\App\View\Asset\MaterializationStrategy\Symlink" from di.xml "Magento\Framework\App\View\Asset\MaterializationStrategy\Copy" to disable symlink, it copies file to required place instead of making symlinks. 16) In version 2.2.11 post installing manually it gives following warning on success page. "Something went wrong while installing sample data" It seems that downloaded sample data zip itself contains one missing product and hence giving error.var/softaculous/magento246/Notes.txt000064400000006760152351004640013433 0ustar001) Install twice manually, with and without sample data. Always check the difference between packages of with and without sample data and make sampledata.zip accordingly. 2) Always check the file permissions 3) Magento 2.4.2 supports only root directory installation. Check next version if it supports sub directory installation. If it does, make the changes accordingly in install as well as clone. 4) Use following command to install Magento 2.4 keeping elasticsearch service on. Check parameters if anything needs to be added or removed. https://devdocs.magento.com/guides/v2.4/install-gde/install/cli/install-cli.html ./bin/magento setup:install --base-url=http://abc.com --db-host=localhost --db-name=magento242sd --db-user=root --db-password=mysql --db-prefix=prmg_ --admin-firstname=admin --admin-lastname=lastname --admin-email=a@a.com --admin-user=admin --admin-password=password --language=en_US --currency=USD --timezone=America/New_York --use-rewrites=1 --session-save=db --use-secure=1 --use-secure-admin=1 --cleanup-database 5) Check and copy pub/media/theme folder from manual to zip and check name of the images. It should match with entry in SQL.(without sample data) 6) Check and copy pub/media/* folder from manual to sampledata.zip and check name of the images. It should match with entry in SQL. (with sample data) 7) Take dump using mysql command mysqldump --routines -u root -ppass soft_mage282 > mage282.sql 8) "hash_config" values in indexer_state table is same for all installation from 2.1.0, hence no need to change this values. 9) We have disabled magento 2.x on windows because icons are not loading properly post login. This is happening because it redirects to symlinks to load all the icons and on windows symlinks are not created and also as per their requirement, magento 2.x is not supported on windows OS. 10) PHP REQUIREMENT LINK: https://devdocs.magento.com/guides/v2.4/install-gde/system-requirements-tech.html ( IN 2.4.4 We have kept MariDB req to 10.2 as one of our user ( fatfingers ) wanted and req in di.xml allows MariaDB 10.3) 11) Magento 2.2.2 requires Apache mod_version to be enabled. 12) Upgrade is not possible at present because magento2 uses either system's upgrade utility or the command line upgrade. http://devdocs.magento.com/guides/v2.4/comp-mgr/bk-compman-upgrade-guide.html 13) Change "Magento\Framework\App\View\Asset\MaterializationStrategy\Symlink" from di.xml "Magento\Framework\App\View\Asset\MaterializationStrategy\Copy" to disable symlink, it copies file to required place instead of making symlinks. 14) Move all Triggers and DELIMITERS to the end of sql. 15) Remove DEFINER=`root`@`localhost` from SQL file. 16) [NA] Keep extra entries in "core_config_data" table and adjust it's auto increment accordingly. 17) Sample data sub-category products loads only when ES service is ON. 18) Delete /var/cache/* /var/composer_home/cache/* and /var/log/* while making sampledata.zip ############## MAGENTO 2.4.5 ############## https://devdocs.magento.com/guides/v2.4/install-gde/install-flow-diagram.html 1 Download the package using following command. php composer.phar create-project --repository-url=https://repo.magento.com/ magento/project-community-edition [[path]] add sample data to it using following command. bin/magento sampledata:deploy 2. Login to https://repo.magento.com/ and get access keys use public key as username and private key as password for downloading package.var/softaculous/magento/Notes.txt000075500000002051152351054150013170 0ustar001) Select Database for saving session storage while installation on manual 2) Select Timezone America/NewYork 3) Just check that "USING BTREE" should be on the left i.e. not at the end 4) Always check the file permissions 5) take mysqldump from command line 6) Following three files are deleted in upgrade.php becuase SUPEE-8788 patch is applied since v1.9.3.0 package by magento. However the below mentioned guide says that these three files are not deleted and need to be deleted. /skin/adminhtml/default/default/media/flex.swf, uploader.swf, uploaderSingle.swf Guide is mentioned here : http://devdocs.magento.com/guides/m1x/ce19-ee114/ce1.9_release-notes.html#ce19-1930 https://support.hypernode.com/knowledgebase/magento-patch-supee-8788-release-1-9-3/ The installation can be checked if the patch was applied successfully here : https://www.magereport.com (This issue was reported by a user via ticket who found this vulnerability at http://magereport.com) 7) PHP REQUIREMENT LINK: http://docs.magento.com/m1/ce/user_guide/magento/system-requirements.htmlvar/softaculous/conc/Notes.txt000075500000002515152360152330012464 0ustar001) Install twice i.e with and without sampledata and give the name of sql file accordingly. 2) Copy the whole application/files folder from manual installed with sampledata and then make data.zip (DONT FORGET TO EMPTY the contents of cache folder) 3) Please do not replace timestamp in fileversion table in sql. (There is no timestamp in fileversion table) 4) Remove ENVIRONMENT_CACHE from the Config table. Concrete5 generates it. 5) We have excluded the file "config/site_theme_paths.php" during upgrade becuase it has the user's customization and should not be overwritten. 6) Add folowing line for language in concrete.php "locale" => "[[language]]", and "i18n" => array( "choose_language_login" => null ) 7) 5.6 to 5.7 Upgarde is not possible at the moment. ( Confimed with vendor ). 8) Remove 'seen_introduction' => true from concrete.php 9) Include /application/config/doctrine/ from manual with sample data to the zip (Make sure that there is proxies folder and php files inside it) 10) If user forgets to login before upgrade then Login can be disabled by adding folliwing code in concrete.php ( This is only for our knowledge) return array( 'updates' => array( 'enable_permissions_protection' => false ) ); 10) PHP REQUIREMENT LINK: https://documentation.concrete5.org/developers/introduction/system-requirementsvar/softaculous/bolt/Notes.txt000075500000003337152360641770012520 0ustar001. Add following entries before starting for manual installation in $datadir/app/config/config.yml take it from vendor/bolt/bolt/app/config/config.yml.dist driver: mysql username: root password: mysql databasename: bolt host: localhost 2. create data.zip without public folder and create bolt.zip from public folder This structure is changed since 3.2.6 because a user had pointed out this error in ticket. https://docs.bolt.cm/3.6/howto/troubleshooting-outside-webroot https://docs.bolt.cm/3.6/installation/manual-download-and-extraction 3. Rename following files composer.json.dist to composer.json, composer.lock.dist to composer.lock, .bolt.yml.dist to .bolt.yml, and /src/Site/CustomisationExtension.php.dist to /src/Site/CustomisationExtension.php in manual installation and add this renamed files in our zip package also. 3. PHP REQUIREMENT LINK : https://docs.bolt.cm/3.6/getting-started/requirements 4.Please note that since version 3.3.1 , '.bolt.yml' was removed from the Bolt's package. So before starting manual installation create .bolt.yml in $datadir($datadir/.bolt.yml) manually and add following entry to it. paths: web: [[softpath]] (This is needed since we keep $datadir outside the webroot , It's needed for mapping webroot files. Confirmed with vendor in mail). Also add [[softdatadir]] path in index.php in softpath. 5. Added __pre_settings function in install.php becuase first character as special character is not allowed in config.yml in datadir. (Since 3.3.5) 6. Take SQL dump before login and after login add dummy content and check diff and make SQL accordingly. 7. move all the placeholder_xxx.jpg files inside 'files' folder(in softpath) from manual to zip as they are not made.(Since version 3.6.3)