Dotkernel Admin PHP Application version 3 was launched.
-
Dotkernel is a Collection of PSR-7 Middleware applications built on top of Mezzio microframework and using Laminas components
@@ -15,7 +15,7 @@You can clone it from github
-Live demo: admin.dotkernel.net
+Live demo: admin7.dotkernel.net
Changelog:
@@ -51,7 +51,7 @@Where can you see a live demo of version 3? +
-
At admin.dotkernel.net.
+At admin7.dotkernel.net.
diff --git a/src/Blog/templates/page/blog-resource/dotkernel3/dotkernel-frontend-version-3-launched.html.twig b/src/Blog/templates/page/blog-resource/dotkernel3/dotkernel-frontend-version-3-launched.html.twig
index afb4fb61..8303f27c 100644
--- a/src/Blog/templates/page/blog-resource/dotkernel3/dotkernel-frontend-version-3-launched.html.twig
+++ b/src/Blog/templates/page/blog-resource/dotkernel3/dotkernel-frontend-version-3-launched.html.twig
@@ -3,7 +3,7 @@
{% block body %}
Dotkernel Frontend PHP Application version 3 was launched.
-
Using an ORM in production without any sort of cache strategy is a very bad move. The Database server chokes; lots of CPU cycles wasted only to generate metadata and queries over and over again at each request; the system slows down and so on.
-Following Doctrine documentation [ +
Following Doctrine documentation [ 'orm_default' => [ // it is recommended to disable doctrine cache on development // just comment any type of cache you dont want to be applied on development @@ -174,9 +174,9 @@ class MyCollection extends Paginator
References
-- Doctrine Advanced Configuration + diff --git a/src/Blog/templates/page/blog-resource/how-to/migrating-dotkernel-3-from-zend-expressive-2-to-zend-expressive-3.html.twig b/src/Blog/templates/page/blog-resource/how-to/migrating-dotkernel-3-from-zend-expressive-2-to-zend-expressive-3.html.twig index 363d3c4e..ad71d155 100644 --- a/src/Blog/templates/page/blog-resource/how-to/migrating-dotkernel-3-from-zend-expressive-2-to-zend-expressive-3.html.twig +++ b/src/Blog/templates/page/blog-resource/how-to/migrating-dotkernel-3-from-zend-expressive-2-to-zend-expressive-3.html.twig @@ -24,7 +24,7 @@ If your project only contains controller-based middleware it can be migrated by
Dotkernel3 Migration - Expressive 2.0 -> 3.0
-Packages
+Packages
Incomposer.json replace the matching repositories with the following:
"dotkernel/dot-authentication-service":"^1.0",
"dotkernel/dot-authentication-service":"^1.0",
@@ -74,8 +74,8 @@ Remove packages:
http-interop/http-middleware
webimpress/http-middleware-compatibility
-Configurations
-Main Configuration
+Configurations
+Main Configuration
In config/config.php add the following config providers:
// zend expressive & middleware factory
@@ -92,7 +92,7 @@ In config/config.php add the following config providers:
\Zend\HttpHandlerRunner\ConfigProvider::class,
Make sure they are the first ConfigProviders or before cached config (ArrayProvider)
-Routing
+Routing
Wrap routing from config/routes.php in a callable with the following format:
return function (Application $app, MiddlewareFactory $factory, ContainerInterface $container) : void {
@@ -106,7 +106,7 @@ add the following use statements and make sure the names are not duplicate:
use Zend\Expressive\Application;
use Zend\Expressive\MiddlewareFactory;
-Pipeline
+Pipeline
Wrap routing from config/pipeline.php in a callable with the following format:
return function (Application $app, MiddlewareFactory $factory, ContainerInterface $container) : void {
@@ -120,7 +120,7 @@ add the following use statements and make sure the names are not duplicate:
use Zend\Expressive\Application;
use Zend\Expressive\MiddlewareFactory;
-Routing middleware migration
+Routing middleware migration
add the following use statements
use Zend\Expressive\Router\Middleware\RouteMiddleware;
@@ -136,7 +136,7 @@ You can check the complete guides and example files from the following links
Migration guide for Dotkernel Frontend: github.com/dotkernel/frontend/tree/master/docs
-Migration guide for Dotkernel Admin: github.com/dotkernel/admin/tree/master/docs
+Migration guide for Dotkernel Admin: docs.dotkernel.org/admin-documentation (the old github.com/dotkernel/admin/tree/master/docs folder has since moved to this documentation site)
Frequently Asked Questions
diff --git a/src/Blog/templates/page/blog-resource/how-to/what-is-psr-7-and-how-to-use-it.html.twig b/src/Blog/templates/page/blog-resource/how-to/what-is-psr-7-and-how-to-use-it.html.twig
index eaf99fc3..4315f240 100644
--- a/src/Blog/templates/page/blog-resource/how-to/what-is-psr-7-and-how-to-use-it.html.twig
+++ b/src/Blog/templates/page/blog-resource/how-to/what-is-psr-7-and-how-to-use-it.html.twig
@@ -62,7 +62,7 @@ $body->write($contents); // stream contains "efabcd"
Note: getContents() seeks the stream while reading it, therefore if the second rewind() method call was not present the stream would have resulted in abcdefabcd because the write() method appends to stream if not preceeded by rewind() or seek(0).
Prepending by using contents as a string
$body = $response->getBody();
$body->rewind(); // or $body->seek(0);
$bodyText = $body->getContends();
-
More information can be found in the PSR-7 article in Dotkernel3 documentation portal.
Sources: PSR-7: HTTP messages zend-diactoros
+More information can be found in the PSR-7 article in Dotkernel3 documentation portal.
Sources: PSR-7: HTTP messages zend-diactoros
Frequently Asked Questions
diff --git a/src/Blog/templates/page/blog-resource/middleware/replacing-controllers-with-psr-15-compliant-handlers-in-dotkernel-light.html.twig b/src/Blog/templates/page/blog-resource/middleware/replacing-controllers-with-psr-15-compliant-handlers-in-dotkernel-light.html.twig
index 264be730..b7a2274d 100644
--- a/src/Blog/templates/page/blog-resource/middleware/replacing-controllers-with-psr-15-compliant-handlers-in-dotkernel-light.html.twig
+++ b/src/Blog/templates/page/blog-resource/middleware/replacing-controllers-with-psr-15-compliant-handlers-in-dotkernel-light.html.twig
@@ -161,7 +161,5 @@ class GetPageViewHandler implements RequestHandlerInterface
-Single Action Handlers in PHP Frameworks
-
{% endblock %}
diff --git a/src/Blog/templates/page/blog-resource/php-development/mezzio-app-development-in-wsl2.html.twig b/src/Blog/templates/page/blog-resource/php-development/mezzio-app-development-in-wsl2.html.twig
index d524f678..f0f2e1ce 100644
--- a/src/Blog/templates/page/blog-resource/php-development/mezzio-app-development-in-wsl2.html.twig
+++ b/src/Blog/templates/page/blog-resource/php-development/mezzio-app-development-in-wsl2.html.twig
@@ -11,11 +11,11 @@
Step 2:
-Install Ubuntu 20.0 LTS inside WLS2 as described here.
+Install Ubuntu 20.0 LTS inside WLS2 as described here (the current version of this guide covers AlmaLinux 9, the distro the WSL setup has since moved to).
Step 3:
-Create a virtualhost for your project using this guide.
+Create a virtualhost for your project using this guide.
Step 4:
@@ -25,7 +25,7 @@
Install Dotkernel API, by following this guide.
-Make sure your data and log directories are writable by changing their permissions, as described here.
+Make sure your data and log directories are writable by changing their permissions, as described here.
Step 5:
diff --git a/src/Blog/templates/page/blog-resource/php-development/php-environment-development-staging-production.html.twig b/src/Blog/templates/page/blog-resource/php-development/php-environment-development-staging-production.html.twig
index b02c81cb..b50819eb 100644
--- a/src/Blog/templates/page/blog-resource/php-development/php-environment-development-staging-production.html.twig
+++ b/src/Blog/templates/page/blog-resource/php-development/php-environment-development-staging-production.html.twig
@@ -13,7 +13,7 @@ It is the “live” environment, where the final application goes out
To switch from one environment to another use the Subversion source code.
-Using SVN on Aptana is an article that explains how to set your development environment on your local computer and then to change it on your staging environment.
+Using SVN on Aptana is an article that explains how to set your development environment on your local computer and then to change it on your staging environment.
To better understand the development of an application using environments, check this helpful article http://dltj.org/article/software-development-practice/
diff --git a/src/Blog/templates/page/blog-resource/php-development/protection-against-sql-injection-using-pdo-and-zend-framework-part-2.html.twig b/src/Blog/templates/page/blog-resource/php-development/protection-against-sql-injection-using-pdo-and-zend-framework-part-2.html.twig
index 19550888..9491ff9a 100644
--- a/src/Blog/templates/page/blog-resource/php-development/protection-against-sql-injection-using-pdo-and-zend-framework-part-2.html.twig
+++ b/src/Blog/templates/page/blog-resource/php-development/protection-against-sql-injection-using-pdo-and-zend-framework-part-2.html.twig
@@ -5,25 +5,25 @@ Following the preview article about query (mixed $sql, [mixed $bind = array()])
+ query (mixed $sql, [mixed $bind = array()])
- use prepare statements internally
- but SQL Injection is still possible if $sql is dynamically created
- fetchAll (string|Zend_Db_Select $sql, , )
+ fetchAll (string|Zend_Db_Select $sql, , )
- all the fetch methods are using prepared statements internally
- but SQL Injection is still possible if $sql is dynamically created
- insert (mixed $table, $bind)
+ insert (mixed $table, $bind)
- use prepare statements internally
- so, SQL Injection is not possible
- update (mixed $table, $bind, [mixed $where = ''])
+ update (mixed $table, $bind, [mixed $where = ''])
- use prepare statements internally
@@ -31,7 +31,7 @@ What you should know about their methods is:
but SQL Injection may be possible if $where is created dynamically
- delete (mixed $table, [mixed $where = ''])
+ delete (mixed $table, [mixed $where = ''])
- SQL Injection may be possible if $where is created dynamically
@@ -41,7 +41,7 @@ What you should know about their methods is:
For more details see Stefan Esser slides.
-PS. A short tip, you can use cast type to avoid SQL Injection in WHERE clause where is possible.
+PS. A short tip, you can use cast type to avoid SQL Injection in WHERE clause where is possible.
$sql= 'SELECT * FROM table WHERE id = ' . (int)$_POST['id'];
diff --git a/src/Blog/templates/page/blog-resource/php-development/protection-against-sql-injection-using-pdo-and-zend-framework.html.twig b/src/Blog/templates/page/blog-resource/php-development/protection-against-sql-injection-using-pdo-and-zend-framework.html.twig
index ed99b3d3..f5354eb1 100644
--- a/src/Blog/templates/page/blog-resource/php-development/protection-against-sql-injection-using-pdo-and-zend-framework.html.twig
+++ b/src/Blog/templates/page/blog-resource/php-development/protection-against-sql-injection-using-pdo-and-zend-framework.html.twig
@@ -20,12 +20,6 @@ It may also occur a problem in Zend Framework when you have SQL injection in
Zend_Db has two escaping methods which can be used: quote() and quoteIdentifier(). Note that these two methods are handling strings by putting them between single quotes.
-For more details see:
-
-http://ezinearticles.com/?SQL-Injection-Protection-in-PHP-With-PDO&id=1815110
-
-http://www.zend.com/webinar/Framework/70170000000bEs9-webinar-secure-application-development-with-the-ZF-20100505.flv
-
Frequently Asked Questions
diff --git a/src/Blog/templates/page/blog-resource/php-troubleshooting/where-is-the-intl-php-extension-problem-solved.html.twig b/src/Blog/templates/page/blog-resource/php-troubleshooting/where-is-the-intl-php-extension-problem-solved.html.twig
index 7dfa4846..1e50d1c3 100644
--- a/src/Blog/templates/page/blog-resource/php-troubleshooting/where-is-the-intl-php-extension-problem-solved.html.twig
+++ b/src/Blog/templates/page/blog-resource/php-troubleshooting/where-is-the-intl-php-extension-problem-solved.html.twig
@@ -4,7 +4,7 @@
Problem
PHP packages/frameworks/libraries/scripts we work with might require different PHP extensions. In this case the Intl extension is needed to work with using Internationalization Functions.
-What is Internationalization?
+What is Internationalization?
Got any of these error messages?
@@ -18,7 +18,7 @@ This happened because the PHP Intl extension isn't installed or enabled.
Parts of this tutorial can be also a guide for installing or enabling other extensions.
What is PHP Intl?
Internationalization extension (further is referred as Intl) is a wrapper for » ICU library, enabling PHP programmers to perform various locale-aware operations including but not limited to formatting, transliteration, encoding conversion, calendar operations
-Source: PHP Documentation
+Source: PHP Documentation
This extension may be installed using the bundled version as of PHP 5.3.0, or as a PECL extension as of PHP 5.2.0. In other words, there are two methods to install the intl extension.
Source: PHP Documentation
Cause
diff --git a/src/Blog/templates/page/blog-resource/zend-framework/sunsetting-pear-channel-for-zend-framework-1.html.twig b/src/Blog/templates/page/blog-resource/zend-framework/sunsetting-pear-channel-for-zend-framework-1.html.twig
index 4b2955b8..5214a3e4 100644
--- a/src/Blog/templates/page/blog-resource/zend-framework/sunsetting-pear-channel-for-zend-framework-1.html.twig
+++ b/src/Blog/templates/page/blog-resource/zend-framework/sunsetting-pear-channel-for-zend-framework-1.html.twig
@@ -3,7 +3,7 @@
{% block body %}
Sunsetting PEAR Channel for Zend Framework 1
-The unofficial PEAR channel for Zend Framework 1 was created in 2016 , at the time when PEAR was still used a lot.
+The unofficial PEAR channel for Zend Framework 1 was created in 2016 , at the time when PEAR was still used a lot.
diff --git a/src/Page/templates/page/frontend.html.twig b/src/Page/templates/page/frontend.html.twig
index e8e7e646..05bfab01 100644
--- a/src/Page/templates/page/frontend.html.twig
+++ b/src/Page/templates/page/frontend.html.twig
@@ -331,7 +331,7 @@
exactly those.