From b6a83bd790508576df7cab121cfbad6617a18b0e Mon Sep 17 00:00:00 2001 From: Arhell Date: Wed, 26 Jun 2024 00:26:38 +0300 Subject: [PATCH] update es folder links --- guide/en/structure/package.md | 4 ++-- guide/es/README.md | 2 +- guide/es/concept/di-container.md | 2 +- guide/es/intro/what-is-yii.md | 2 +- guide/es/security/authorization.md | 4 ++-- guide/es/security/best-practices.md | 4 ++-- guide/es/start/hello.md | 2 +- guide/es/start/installation.md | 6 +++--- guide/es/structure/package.md | 4 ++-- guide/es/tutorial/performance-tuning.md | 2 +- guide/id/README.md | 2 +- 11 files changed, 17 insertions(+), 17 deletions(-) diff --git a/guide/en/structure/package.md b/guide/en/structure/package.md index 3b1b0b3..724f74e 100644 --- a/guide/en/structure/package.md +++ b/guide/en/structure/package.md @@ -180,7 +180,7 @@ everything is in good shape. For more details, please refer to the [Testing](../ #### Versioning You should give each release of your extension a version number (e.g. `1.0.1`). We recommend you follow the -[semantic versioning](http://semver.org) practice when determining what version numbers should be used. +[semantic versioning](https://semver.org) practice when determining what version numbers should be used. #### Releasing @@ -197,7 +197,7 @@ In the release of your package, in addition to code files, you should also consi help other people learn about and use your extension: * A readme file in the package root directory: it describes what your extension does and how to install and use it. - We recommend you write it in [Markdown](http://daringfireball.net/projects/markdown/) format and name the file + We recommend you write it in [Markdown](https://daringfireball.net/projects/markdown/) format and name the file as `README.md`. * A changelog file in the package root directory: it lists what changes are made in each release. The file may be written in Markdown format and named as `CHANGELOG.md`. diff --git a/guide/es/README.md b/guide/es/README.md index c391639..f4eba50 100644 --- a/guide/es/README.md +++ b/guide/es/README.md @@ -1,6 +1,6 @@ # La Guía Definitiva de Yii 3.0 -Esta guía se publica bajo los [Términos de documentación de Yii](http://www.yiiframework.com/doc/terms/). +Esta guía se publica bajo los [Términos de documentación de Yii](https://www.yiiframework.com/doc/terms/). Introducción ------------ diff --git a/guide/es/concept/di-container.md b/guide/es/concept/di-container.md index c1a7ee2..b0831f2 100644 --- a/guide/es/concept/di-container.md +++ b/guide/es/concept/di-container.md @@ -96,7 +96,7 @@ So it makes sense to: That's what dependency containers are for. A dependency injection (DI) container is an object that knows how to instantiate and configure objects and -all their dependent objects. [Martin Fowler's article](http://martinfowler.com/articles/injection.html) has well +all their dependent objects. [Martin Fowler's article](https://martinfowler.com/articles/injection.html) has well explained why DI container is useful. Here we will mainly explain the usage of the DI container provided by Yii. Yii provides the DI container feature through the [yiisoft/di](https://github.com/yiisoft/di) package and diff --git a/guide/es/intro/what-is-yii.md b/guide/es/intro/what-is-yii.md index 65ca9f6..168f76b 100644 --- a/guide/es/intro/what-is-yii.md +++ b/guide/es/intro/what-is-yii.md @@ -38,7 +38,7 @@ If you're already familiar with another framework, you may appreciate knowing ho take advantage of Yii's solid extension architecture to use or develop redistributable extensions. - High performance is always a primary goal of Yii. -Yii is not a one-man show, it is backed up by a [strong core developer team](http://www.yiiframework.com/team/), as well as a large community +Yii is not a one-man show, it is backed up by a [strong core developer team](https://www.yiiframework.com/team/), as well as a large community of professionals constantly contributing to Yii's development. The Yii developer team keeps a close eye on the latest Web development trends and on the best practices and features found in other frameworks and projects. The most relevant best practices and features found elsewhere are regularly incorporated into the core framework and exposed diff --git a/guide/es/security/authorization.md b/guide/es/security/authorization.md index 3e86392..30291c4 100644 --- a/guide/es/security/authorization.md +++ b/guide/es/security/authorization.md @@ -46,10 +46,10 @@ so an implementation should be provided in dependency container in order for it ## Role Based Access Control (RBAC) Role-Based Access Control (RBAC) provides a simple yet powerful centralized access control. Please refer to -the [Wikipedia](http://en.wikipedia.org/wiki/Role-based_access_control) for details about comparing RBAC +the [Wikipedia](https://en.wikipedia.org/wiki/Role-based_access_control) for details about comparing RBAC with other more traditional access control schemes. -Yii implements a General Hierarchical RBAC, following the [NIST RBAC model](http://csrc.nist.gov/rbac/sandhu-ferraiolo-kuhn-00.pdf). +Yii implements a General Hierarchical RBAC, following the [NIST RBAC model](https://csrc.nist.gov/rbac/sandhu-ferraiolo-kuhn-00.pdf). Using RBAC involves two parts of work. The first part is to build up the RBAC authorization data, and the second part is to use the authorization data to perform access check in places where it is needed. Since RBAC implements diff --git a/guide/es/security/best-practices.md b/guide/es/security/best-practices.md index e388174..81244c2 100644 --- a/guide/es/security/best-practices.md +++ b/guide/es/security/best-practices.md @@ -109,7 +109,7 @@ If all you need is plain text then escaping is as easy as the following: ``` -If it should be HTML we could get some help from [HtmlPurifier](http://htmlpurifier.org/). +If it should be HTML we could get some help from [HtmlPurifier](https://htmlpurifier.org/). Note that HtmlPurifier processing is quite heavy so consider adding caching. Further reading on the topic: @@ -202,5 +202,5 @@ In such situations you should fix your webserver configuration to serve the site For more information about the server configuration, please refer to the documentation of your webserver: -- Apache 2: +- Apache 2: - Nginx: diff --git a/guide/es/start/hello.md b/guide/es/start/hello.md index 9ee841e..2849abc 100644 --- a/guide/es/start/hello.md +++ b/guide/es/start/hello.md @@ -148,7 +148,7 @@ use Yiisoft\Html\Html; Note that in the above code, the `message` parameter is HTML-encoded before being printed. This is necessary as the parameter comes from an end user, making it vulnerable to -[cross-site scripting (XSS) attacks](http://en.wikipedia.org/wiki/Cross-site_scripting) by embedding +[cross-site scripting (XSS) attacks](https://en.wikipedia.org/wiki/Cross-site_scripting) by embedding malicious JavaScript code in the parameter. Naturally, you may put more content in the `say` view. The content can consist of HTML tags, plain text, and even diff --git a/guide/es/start/installation.md b/guide/es/start/installation.md index dbf107a..930d64a 100644 --- a/guide/es/start/installation.md +++ b/guide/es/start/installation.md @@ -95,7 +95,7 @@ You should see the above "Congratulations!" page in your browser. of deploying it to a production server. The application installed according to the above instructions should work out of the box with either -an [Apache HTTP server](http://httpd.apache.org/) or an [Nginx HTTP server](http://nginx.org/), on +an [Apache HTTP server](https://httpd.apache.org/) or an [Nginx HTTP server](https://nginx.org/), on Windows, Mac OS X, or Linux running PHP 7.2 or higher. On a production server, you may want to configure your Web server so that the application can be accessed @@ -164,7 +164,7 @@ RewriteRule . index.php ### Nginx -To use [Nginx](http://wiki.nginx.org/), you should install PHP as an [FPM SAPI](https://secure.php.net/install.fpm). +To use [Nginx](https://wiki.nginx.org/), you should install PHP as an [FPM SAPI](https://secure.php.net/install.fpm). You may use the following Nginx configuration, replacing `path/to/app/public` with the actual path for `app/public` and `mysite.test` with the actual hostname to serve. @@ -247,7 +247,7 @@ configuration goes to `Web.config`: ### lighttpd -To use [lighttpd](http://www.lighttpd.net/) >= 1.4.24 put `index.php` to webroot and add the following to configuration: +To use [lighttpd](https://www.lighttpd.net/) >= 1.4.24 put `index.php` to webroot and add the following to configuration: ``` url.rewrite-if-not-file = ("(.*)" => "/index.php/$0") diff --git a/guide/es/structure/package.md b/guide/es/structure/package.md index 750f6f9..b19c9e6 100644 --- a/guide/es/structure/package.md +++ b/guide/es/structure/package.md @@ -163,7 +163,7 @@ everything is in good shape. For more details, please refer to the [Testing](../ #### Versioning You should give each release of your extension a version number (e.g. `1.0.1`). We recommend you follow the -[semantic versioning](http://semver.org) practice when determining what version numbers should be used. +[semantic versioning](https://semver.org) practice when determining what version numbers should be used. #### Releasing @@ -179,7 +179,7 @@ In the releases of your package, in addition to code files, you should also cons help other people learn about and use your extension: * A readme file in the package root directory: it describes what your extension does and how to install and use it. - We recommend you write it in [Markdown](http://daringfireball.net/projects/markdown/) format and name the file + We recommend you write it in [Markdown](https://daringfireball.net/projects/markdown/) format and name the file as `README.md`. * A changelog file in the package root directory: it lists what changes are made in each release. The file may be written in Markdown format and named as `CHANGELOG.md`. diff --git a/guide/es/tutorial/performance-tuning.md b/guide/es/tutorial/performance-tuning.md index 23a1f1c..ae37eea 100644 --- a/guide/es/tutorial/performance-tuning.md +++ b/guide/es/tutorial/performance-tuning.md @@ -100,4 +100,4 @@ The following profiling tools may be useful: - [Yii debug toolbar and debugger](https://github.com/yiisoft/yii2-debug/blob/master/docs/guide/README.md) - [Blackfire](https://blackfire.io/) - [XHProf](https://secure.php.net/manual/en/book.xhprof.php) -- [XDebug profiler](http://xdebug.org/docs/profiler) +- [XDebug profiler](https://xdebug.org/docs/profiler) diff --git a/guide/id/README.md b/guide/id/README.md index 4233f29..828481c 100644 --- a/guide/id/README.md +++ b/guide/id/README.md @@ -1,6 +1,6 @@ # Panduan Definitif untuk Yii 3.0 -Panduan ini dirilis di bawah [Ketentuan Dokumentasi Yii](http://www.yiiframework.com/doc/terms/). +Panduan ini dirilis di bawah [Ketentuan Dokumentasi Yii](https://www.yiiframework.com/doc/terms/). Pengenalan + ------------