| Apache - PHP Switcher! | |
| https://getgrav.org/blog/macos-sierra-apache-multiple-php-versions | |
| SQL - DNSMASQ | |
| https://getgrav.org/blog/macos-sierra-apache-mysql-vhost-apc |
| 1 – Go to ‘shell’ folder in your Magento installation: | |
| cd shell | |
| 2 – Execute reindex using this command: | |
| php -f indexer.php reindexall | |
| It is possible to get full list of Magento indexer commands using this command: | |
| php -f indexer.php help | |
| To get a list of available indexes, execute this command: |
| Locate This File: /app/code/core/Mage/Checkout/controllers/OnepageController.php | |
| Go to Mage_Checkout_OnepageController::successAction() | |
| Comment the line $session->clear();. | |
| Now you can make one order and refresh the page as often as you like for styling the success page, | |
| simply put through a test order and once you are on the success page just change the url | |
| from /checkout/onepage/success/ to /checkout/onepage/failure/ |
This Gist is a collection of configuration files that can be used to easily setup a Homebrew-based LEMP stack on Mac OS X.
Files in this repository are numbered and named for ordering purposes only. At the top of each file is a section of metadata that denote what component the file belongs to and the default name & location of the file. Feel free to implement it however you want.
Note: some configuration files have hard-coded paths to my user directory -- fix it for your setup
| # --------------------------------------------------------------------------- | |
| # | |
| # Description: This file holds all my BASH configurations and aliases | |
| # | |
| # Sections: | |
| # 1. Environment Configuration | |
| # 2. Make Terminal Better (remapping defaults and adding functionality) | |
| # 3. File and Folder Management | |
| # 4. Searching | |
| # 5. Process Management |
| nginx and Go Daddy SSL certificates | |
| Generate the CSR: | |
| 1 openssl genrsa 2048 > yourhost.com.key | |
| 2 openssl req -new -key yourhost.com.key > yourhost.com.csr | |
| Enter in whatever you want - you NEED the "Common Name" everything else is not really required for it to work. | |
| 01 Country Name (2 letter code) [AU]:US | |
| 02 State or Province Name (full name) [Some-State]:. | |
| 03 Locality Name (eg, city) []:. | |
| 04 Organization Name (eg, company) [Internet Widgits Pty Ltd]:Something Here | |
| 05 Organizational Unit Name (eg, section) []:. |
| chown -R www-data:www-data wp-content |
| UPDATE `wp_posts` | |
| SET `post_content` = replace(post_content, '/testing/', '/') | |
| WHERE `post_content` LIKE '%/testing/%' | |
| In this example we find any text named '/testing/' and replace it with '/' within table wp_posts in column post_content |
| Make sure your in develop | |
| git flow hotfix start [Release Number] | |
| git add -A | |
| git commit *** Commit the change and give description | |
| git flow hotfix finish [Release Number] *** Be sure to label Tags | |
| git push *** When you push it will push to both branches that were setup in git flow init | |
| git push --tags *** These will appear in the Releases link on GitHub |