URI Structures

---

In a project developed with ZN Framework, the request is made to a sample web address as below. Understanding the URL structure used with ZN is very important to understand the use of ZN Framework.

URL
Basic Section		Relative Section		Rotatable Section
http[s]://	yourdomain.com/	[project-name/]	[lang/]	[controller/]	[function/]	[param1/param2 ...]

The URL sections above are reviewed in stages below.

 

 

# Section Headings

---

# HTTP/S

# HTTPS Conversion
# Change Port
# Catching HTTP

# Domain Name

# With HTTP

# Project Name

# Predefined Project Directory
# Use of Aliases
# Catching Project Directory

# Lang

# Change Language
# Catching Active Language

# Controller

# Predefined Controller
# Catching Controller Name

# Function

# Predefined Method
# Catching Method Name

# Parameters

# Catching Parameters

 

 

# HTTP/S

---

The URL::site() method is used to create an on-site URL in the ZN Framework. The http:// prefix of the links created with this method changes to https:// if SSL certificate is activated on the site. This conversion is done automatically. There is no need for an extra setting for this. Therefore, all links used on the site must be made with URL::site(). If the link will point to a local file such as a .css or .js, then URL::base() should be used instead of URL::site().

echo URL::site('product/list');

When you install a security certificate on your site, links automatically convert from http to https.

echo URL::site('product/list');

If a port other than 443 is used for HTTPS in IIS servers, the following arrangement should be made in order for the links to turn into https automatically.

# Before ZN::run() method
$_SERVER['SERVER_PORT'] = 443;

It must be manipulated to ensure the correct match of the SSL port.

You can use the method below to get this value of the URL.

echo Request::scheme();

 

 

# Domain Name

---

You can use the Http::host() method to get this value.

echo Http::host();

You can use the following method to capture the value of http://localhost.

echo URL::host();

 

 

# Project Name

---

It is the section containing the names of the project directories in the Projects/ directory to be run. If the directory to be run is the default (Frontend/) directory, it will not be written. The directory name is written to run directories found outside of it. If the Frontend/ directory is predefined, typing the hostname directly is sufficient to run that directory.

However, if a different project directory is requested to be run, it is specified in the URL.

The above request runs the Projects/Backend/ directory.

The project directory that is run by default is the Projects/Frontend/ directory. To change the default opening project directory, you can make the necessary settings from the configuration file below.

'default' => 'Frontend'

You can give aliases to represent these directory names to access your project directories. Use the following config file to edit this setting.

'panel' => 'Backend'

You can now run the Backend/ directory.

You can find detailed information about what this section is used for in the Multiple Project Development section.

If the project directory name being executed on the URL is required, the corresponding project name is obtained with the CURRENT_PROJECT constant.

echo CURRENT_PROJECT;

 

 

# Lang

---

this section is closed by default. Shows the site's selected language value. In order for the selected language abbreviation to be displayed on the URL, it must be activated from the configuration file. If this is done, the links created with the URL::site() method will also receive this language suffix. In order for the language attachment to be viewable on the URL, it must be activated from the configuration file whose path is specified below.

'lang' => true

Now the URL::site() method produces the following output.

echo URL::site('product/list');

The Lang::set() method is used to change this value.

Lang::set('tr');

echo URL::site('product/list');

this change is also possible by users changing this value and running it through the URL.

The Lang::get() method is used to capture the currently selected language shortening.

echo Lang::get();

The explanation for this section has been made in the File Language Library link.

 

 

# Controller

---

this section determines which controllers in the Controllers/ directory in the ZN Framework will be run. The controller that works by default for requests made without specifying a controller name is the Home controller. The explanation for this section has been made in the Controllers link.

You can use the following configuration file to change the default controller information.

'openController' => 'Home'

The constant CURRENT_CONTROLLER must be used to capture the controller name. Although it can be accessed by different methods, it gives the name of the real controller since it is not affected by fixed routes.

echo CURRENT_CONTROLLER;

 

 

# Function

---

this section refers to the function information of the controller expressed in the previous section. In requests made without specifying a method name, the related controller's main method is activated. Again, the explanation about the use of this section is made in the Controllers link.

You can use the following configuration file to change the default controller method information.

'openFunction' => 'main'

The constant CURRENT_CFUNCTION must be used to capture the method name. This constant gives the name of the actual function currently being executed. This is not affected by fixed routes.

echo CURRENT_CFUNCTION;

 

 

# Parameters

---

It is the part used to send data to the method of the operated controller. This and all of the following sections are used for parameter passing.

The CURRENT_CPARAMETERS constant can be used to capture parameters. Apart from this constant, you can also capture parameters with sequential variables that you define for the parameters of the related method.

output( CURRENT_CPARAMETERS );