Merge pull request #257 from dotkernel/dead-link-check-v2

fix dead link

Author: bidi47

public/md-articles/android/multiple-broadcast-receivers-in-the-same-app-for-the-same-action.md

@@ -29,4 +29,4 @@ A: This can happen when you use 3rd party libraries that already define their ow
 
 ## Resources
 
-- [Admob App Download Tracking documentation](http://developer.admob.com/wiki/Android_App_Download_Tracking)
+- [Admob App Download Tracking documentation](https://developer.admob.com/wiki/Android_App_Download_Tracking)

public/md-articles/best-practice/aptana-set-svn-keywords.md

@@ -10,7 +10,7 @@ language: "en"
 
 # Aptana - set SVN keywords
 
-In Aptana it's very simple to set the [svn:keywords](http://svnbook.red-bean.com/en/1.4/svn.advanced.props.special.keywords.html) property for a file.
+In Aptana it's very simple to set the [svn:keywords](https://svnbook.red-bean.com/en/1.4/svn.advanced.props.special.keywords.html) property for a file.
 
 For example if you want to set the svn keyword property ***Id***:
 
@@ -44,4 +44,4 @@ A: After the SVN commit of the file, the $Id$ keyword is replaced with text cont
 
 ## Resources
 
-- [svn:keywords property documentation](http://svnbook.red-bean.com/en/1.4/svn.advanced.props.special.keywords.html)
+- [svn:keywords property documentation](https://svnbook.red-bean.com/en/1.4/svn.advanced.props.special.keywords.html)

public/md-articles/best-practice/golden-rules-of-professional-php-coding.md

@@ -31,7 +31,7 @@ ini_set('display_errors', 1);
 
 6. Use a version control system. **SVN is NOT dead.**
 
-7. Use an **[IDE](http://en.wikipedia.org/wiki/Integrated_development_environment)**. [Aptana 2](http://www.aptana.com/products/studio2/download), [Aptana 3](http://www.aptana.com/products/studio3/download), Eclipse, even [Zend Studio](http://www.zend.com/en/products/studio/).
+7. Use an **[IDE](https://en.wikipedia.org/wiki/Integrated_development_environment)**. [Aptana 2](https://www.aptana.com/products/studio2/download), [Aptana 3](https://www.aptana.com/products/studio3/download), Eclipse, even [Zend Studio](https://www.zend.com/en/products/studio/).
 
 8. Know your **IDE**: code snippets, code assist, integration with Zend Framework, SVN integration, bug tracker integration, and so on
 
@@ -55,7 +55,7 @@ A: It recommends using a version control system (noting that SVN is not dead) an
 
 ## Resources
 
-- [Integrated development environment (Wikipedia)](http://en.wikipedia.org/wiki/Integrated_development_environment)
-- [Aptana 2 download](http://www.aptana.com/products/studio2/download)
-- [Aptana 3 download](http://www.aptana.com/products/studio3/download)
-- [Zend Studio](http://www.zend.com/en/products/studio/)
+- [Integrated development environment (Wikipedia)](https://en.wikipedia.org/wiki/Integrated_development_environment)
+- [Aptana 2 download](https://www.aptana.com/products/studio2/download)
+- [Aptana 3 download](https://www.aptana.com/products/studio3/download)
+- [Zend Studio](https://www.zend.com/en/products/studio/)

public/md-articles/best-practice/htaccess-301-redirect-non-www-to-www.md

@@ -10,14 +10,14 @@ language: "en"
 
 # htaccess 301 redirect non-www to www
 
-To always redirect users to the www site (for example: http://dotboost.com to http://www.dotboost.com), add the following lines to .htaccess, right after **RewriteEngine On**:
+To always redirect users to the www site (for example: https://dotboost.com to https://www.dotboost.com), add the following lines to .htaccess, right after **RewriteEngine On**:
 
 ```shell
 RewriteCond %{HTTP_HOST} ^dotboost.com
 RewriteRule ^(.*)$ http://www.dotboost.com/$1 [L,R=301]
 ```
 
-If, on the other hand, you want to redirect http://www.dotboost.com to http://dotboost.com, add the following lines instead:
+If, on the other hand, you want to redirect https://www.dotboost.com to https://dotboost.com, add the following lines instead:
 
 ```shell
 RewriteCond %{HTTP_HOST} ^www.dotboost.com
@@ -29,7 +29,7 @@ Replace dotboost.com with your site's domain.
 ## FAQ
 
 **Q: How do I redirect a non-www domain to www using .htaccess?**
-A: Add RewriteCond %{HTTP_HOST} ^dotboost.com and RewriteRule ^(.*)$ http://www.dotboost.com/$1 to your .htaccess file, right after RewriteEngine On, replacing dotboost.com with your own domain.
+A: Add RewriteCond %{HTTP_HOST} ^dotboost.com and RewriteRule ^(.*)$ https://www.dotboost.com/$1 to your .htaccess file, right after RewriteEngine On, replacing dotboost.com with your own domain.
 
 **Q: How do I redirect a www domain to non-www instead?**
-A: Add RewriteCond %{HTTP_HOST} ^www.dotboost.com and RewriteRule ^(.*)$ http://dotboost.com/$1 instead, again replacing dotboost.com with your own domain.
+A: Add RewriteCond %{HTTP_HOST} ^www.dotboost.com and RewriteRule ^(.*)$ https://dotboost.com/$1 instead, again replacing dotboost.com with your own domain.

public/md-articles/best-practice/insert-update-delete-statements-with-zend-db.md

@@ -15,7 +15,7 @@ language: "en"
 DML (Data Manipulation Language) statements change data values in database tables.
 This article, continuing the Zend_Db series, shows how the three primary DML statements - INSERT, UPDATE, and DELETE - are written in raw SQL and translated into Zend_Db method calls.
 
-Continuing the Zend_DB article [series](http://www.dotkernel.com/dotkernel/sql-queries-using-zend-db-select/), we are stopping now at DML statements. DML (Data Manipulation Language) statements are statements that change data values in database tables. There are 3 primary DML statements:
+Continuing the Zend_DB article [series](https://www.dotkernel.com/best-practice/sql-queries-using-zend-db-select/), we are stopping now at DML statements. DML (Data Manipulation Language) statements are statements that change data values in database tables. There are 3 primary DML statements:
 
 - INSERT - Inserting new rows into database tables.
 - UPDATE - Updating existing rows in database tables.
@@ -94,4 +94,4 @@ A: Call $db->delete('user', 'id = '.$id), which is equivalent to the SQL stateme
 
 ## Resources
 
-- [Zend_Db series](http://www.dotkernel.com/dotkernel/sql-select-zend-db/)
+- [Zend_Db series](https://www.dotkernel.com/best-practice/sql-queries-using-zend-db-select/)

public/md-articles/best-practice/sql-queries-using-zend-db-select.md

@@ -126,6 +126,6 @@ A: Before fetching it, echo the query to visualize it: echo $select->__toString(
 ## Resources
 
 - [Zend_Db](https://docs.laminas.dev/laminas-db/adapter/)
-- [What are returning the FETCH functions from Zend_Db](http://www.dotkernel.com/best-practice/what-are-returning-the-fetch-functions-from-zend-db/)
-- [Subqueries with Zend_Db](http://www.dotkernel.com/best-practice/subqueries-with-zend-db/)
-- [INSERT, UPDATE, DELETE statements with Zend_Db](http://www.dotkernel.com/best-practice/insert-update-delete-statements-with-zend-db/)
+- [What are returning the FETCH functions from Zend_Db](https://www.dotkernel.com/best-practice/what-are-returning-the-fetch-functions-from-zend-db/)
+- [Subqueries with Zend_Db](https://www.dotkernel.com/best-practice/subqueries-with-zend-db/)
+- [INSERT, UPDATE, DELETE statements with Zend_Db](https://www.dotkernel.com/best-practice/insert-update-delete-statements-with-zend-db/)

public/md-articles/best-practice/subqueries-with-zend-db.md

@@ -14,7 +14,7 @@ language: "en"
 
 Continuing the Zend_Db series, this article shows a more complex query - combining COUNT(), LEFT JOIN, and GROUP BY across 3 tables, with a count taken from 2 different tables - and how to build it, including a nested subquery, using Zend_Db.
 
-Continuing the Zend_DB article [series](http://www.dotkernel.com/dotkernel/sql-queries-using-zend-db-select/), we are stopping now at subqueries.
+Continuing the Zend_DB article [series](https://www.dotkernel.com/best-practice/sql-queries-using-zend-db-select/), we are stopping now at subqueries.
 
 As you note, the below is a complicate query, with *COUNT()*, *LEFT JOIN()*, *GROUP BY* - select from 3 tables, and make a count from 2 different tables:
 
@@ -69,4 +69,4 @@ A: Use ->joinLeft(array('b'=>'track_courses'), 'a.id = b.track_id', array('count
 
 ## Resources
 
-- [Zend_Db series](http://www.dotkernel.com/dotkernel/sql-select-zend-db/)
+- [Zend_Db series](https://www.dotkernel.com/best-practice/sql-queries-using-zend-db-select/)

public/md-articles/best-practice/svn-export-in-a-virtual-host.md

@@ -38,7 +38,7 @@ where:
 | Parameter | Meaning |
 |---|---|
 | `-r revisionNumber` | Optional. Exports a specific revision. By default, the latest revision is used. |
-| `repositoryUrl` | The repository URL (e.g. `http://example.com/repos/project-name/trunk/`). Remember to add `/trunk/`, or change it appropriately for a branch or tag. |
+| `repositoryUrl` | The repository URL (e.g. `https://example.com/repos/project-name/trunk/`). Remember to add `/trunk/`, or change it appropriately for a branch or tag. |
 | `targetDirectory` - `./` | The current directory. |
 | `targetDirectory` - `./project-name` | Exports to the `project-name` subdirectory. |
 | `targetDirectory` - `/var/www/vhosts/example.com/httpdocs` | Exports to an absolute path. |

public/md-articles/best-practice/svn-keywords-setup-in-php-ide-zend-studio.md

@@ -73,7 +73,7 @@ A: They provide better integration of SVN, your PHP IDE (Zend Studio), and a bug
 A: It tells SVN to ignore local settings files such as *.project, *.prefs, .project, cache, .settings, .buildpath, and *.ini, since you don't want to commit your local settings to the main repository.
 
 **Q: How do you set up basic bug tracker integration?**
-A: Set the bugtracq:label property to "Tracker ID:" and bugtraq:message; if you have a public bug tracker such as Mantis, also set bugtraq:url to a URL pattern like http://www.dotkernel.net/view.php?id=%BUGID%.
+A: Set the bugtracq:label property to "Tracker ID:" and bugtraq:message; if you have a public bug tracker such as Mantis, also set bugtraq:url to a URL pattern like https://www.dotkernel.net/view.php?id=%BUGID%.
 
 **Q: Should these properties be applied recursively?**
 A: No. For the properties above, apply them only to the project folder, not recursively.

public/md-articles/best-practice/using-like-wildcards-with-zend-db.md

@@ -16,7 +16,7 @@ The LIKE condition allows pattern matching in the WHERE clause of SELECT, INSERT
 The `_` wildcard matches a single character, and `%` matches any string of any length (including zero).
 This article shows how to use LIKE and NOT LIKE with both wildcards in Zend_Db.
 
-Continuing the Zend_Db article series (http://www.dotkernel.com/dotkernel/sql-queries-using-zend-db-select/), let's discuss the LIKE condition.
+Continuing the Zend_Db article [series](https://www.dotkernel.com/best-practice/sql-queries-using-zend-db-select/), let's discuss the LIKE condition.
 
 The **LIKE** condition allows you to use wildcards in the *WHERE* clause of an SQL statement. This allows pattern matching. It can be used in any valid SQL statement (*SELECT*, *INSERT*, *UPDATE* or *DELETE*).