Mods: Automatic Base Detection - Versionsgeschichte

Tm: /* Summary */

2017-11-26T18:46:34Z

Summary

← Nächstältere Version		Version vom 26. November 2017, 18:46 Uhr
Zeile 3:		Zeile 3:
	Sometimes it is difficult to move an application from one subfolder into another or into the root folder. Another problem is moving your applcation to another domain. It would be much simpler if the application use only relative URIs and all the other stuff would be done automatically.		Sometimes it is difficult to move an application from one subfolder into another or into the root folder. Another problem is moving your applcation to another domain. It would be much simpler if the application use only relative URIs and all the other stuff would be done automatically.

	In the most cases there are at least two points in your application you must always have to remember to modify if you move your application around. If you are using redirections with '''mod_rewrite''' you have to modify at least the '''RewriteBase''' and the most frameworks need extra configuration and special code to generate a ~~relative URL~~.		In the most cases there are at least two points in your application you must always have to remember to modify if you move your application around. If you are using redirections with '''mod_rewrite''' you have to modify at least the '''RewriteBase''' and the most frameworks need extra configuration and special code to generate a portable URIs.

	With CodeIgniter for example you have functions like '''base_url()''' or '''site_url()''' which should helps you to built links without to know about your current place. But this not very handy as you have always remember to use these functions in every link and to setup correctly your configuration value in '''$config['base_url']'''. An automatic base url detection is built in, but for security reasons the IP address of the your server will be used to compose the URI instead of your host name ([https://expressionengine.com/blog/http-host-and-server-name-security-issues read more about security concerns of detecting the host name automatically]). This will not work in the most cases of course. Furthermore these functions produce absolute URLs, which is not necessary imo.		With CodeIgniter for example you have functions like '''base_url()''' or '''site_url()''' which should helps you to built links without to know about your current place. But this not very handy as you have always remember to use these functions in every link and to setup correctly your configuration value in '''$config['base_url']'''. An automatic base url detection is built in, but for security reasons the IP address of the your server will be used to compose the URI instead of your host name ([https://expressionengine.com/blog/http-host-and-server-name-security-issues read more about security concerns of detecting the host name automatically]). This will not work in the most cases of course. Furthermore these functions produce absolute URLs, which is not necessary imo.

Tm: /* Relative Links vs Absolute Links */

2017-11-26T18:44:16Z

Relative Links vs Absolute Links

← Nächstältere Version		Version vom 26. November 2017, 18:44 Uhr
Zeile 63:		Zeile 63:
	If you try to search the internet for '''relative links vs absolute links''' you will find only one multiple time copied and translated opinion of SEO people. They say that it is bad to use relative because of two things:		If you try to search the internet for '''relative links vs absolute links''' you will find only one multiple time copied and translated opinion of SEO people. They say that it is bad to use relative because of two things:

	1. Duplicate Content		# Duplicate Content
	2. Scraping		# Scraping

	Some of them mention that developing a big website needs staging and therefore moving the application to different locations, domains and sometimes subfolders, but they come to a result that this should be solved by the programmers "somehow". On one website WordPress was mentioned as examplary because it uses only absolute URLs. I do not think that the author ever had to move a WordPress Website from one domain to another. It' the hell.		Some of them mention that developing a big website needs staging and therefore moving the application to different locations, domains and sometimes subfolders, but they come to a result that this should be solved by the programmers "somehow". On one website WordPress was mentioned as examplary because it uses only absolute URLs. I do not think that the author ever had to move a WordPress Website from one domain to another. It' the hell.
Zeile 72:		Zeile 72:
	The first point is that websites often are not configured well and they are reachable under four URLs:		The first point is that websites often are not configured well and they are reachable under four URLs:

	1. http://www.domain.tld		# http://www.domain.tld
	2. http://domain.tld		# http://domain.tld
	3. https://www.domain.tld		# https://www.domain.tld
	4. https://domain.tld		# https://domain.tld

	The most simple solution is to redirect three of these domains to one final domain with the search engine friendly 301 header. This can be done with some simple lines in the '''htaccess'' file.		The most simple solution is to redirect three of these domains to one final domain with the search engine friendly 301 header. This can be done with some simple lines in the '''htaccess'' file.

Tm am 26. November 2017 um 18:42 Uhr

2017-11-26T18:42:34Z

← Nächstältere Version		Version vom 26. November 2017, 18:42 Uhr
Zeile 1:		Zeile 1:
	== Summary ==		== Summary ==

	Sometimes it is difficult to move an application from one subfolder into another or into the root folder. Another problem is moving your applcation to another domain. It would be much simpler if the application use only relative ~~url's~~ and all the other stuff would be done automatically.		Sometimes it is difficult to move an application from one subfolder into another or into the root folder. Another problem is moving your applcation to another domain. It would be much simpler if the application use only relative URIs and all the other stuff would be done automatically.

	In the most cases there are at least two points in your application you must always have to remember to modify if you move your application around. If you are using redirections with '''mod_rewrite''' you have to modify at least the '''RewriteBase''' and the most frameworks need extra configuration and special code to generate a relative URL.		In the most cases there are at least two points in your application you must always have to remember to modify if you move your application around. If you are using redirections with '''mod_rewrite''' you have to modify at least the '''RewriteBase''' and the most frameworks need extra configuration and special code to generate a relative URL.
Zeile 19:		Zeile 19:
	</syntaxhighlight>		</syntaxhighlight>

	~~So why not using~~ only relative ~~URLs?~~		== Using only relative URIs ==

	CodeCoupler includes a htaccess file that detects and save the current base folder in an environment variable. This variable will be used to set an absolute ~~URL~~ into the configuration variable '''base_url''' in codeigniter. From now on ~~all~~ CodeIgniter functions will produce an URI without a hostname and with the correct subfolder if needed.		CodeCoupler includes an htaccess file that detects and save the current base folder in an environment variable. This variable will be used to set an absolute path into the configuration variable '''base_url''' in codeigniter, including the base folder of your application and excluding any host name. From now on CodeIgniter functions like '''base_url()''' or '''site_url()''' will produce an absolute URI without a hostname and with the correct subfolder if needed.

	In an HTML page you can set your ~~base like this~~:		In an HTML page you can set this base in your header and use only relative links:

	<syntaxhighlight lang="html">		<syntaxhighlight lang="html">
Zeile 47:		Zeile 47:
	== Some Notes ==		== Some Notes ==

	With this modification all the libraries using '''base_url()''', '''site_url()''' or some helpers like '''redirect()''' which call these function will work in the most cases like before. ~~The~~ only limitaion is the usage of the second paramter '''$protocoll''' of the both functions. As we use only absolute paths and not any host name or IP address, we cannot set a protocol. The functions will check if the given protocol is the current protocol (http or https). If not they will show an error.		With this modification all the libraries using '''base_url()''', '''site_url()''' or some helpers like '''redirect()''' which call these function will work in the most cases like before. There are only some point you should notice:

			1.) There is a limitaion in the usage of the second paramter '''$protocoll''' of the both functions. As we use only absolute paths and not any host name or IP address, we cannot set a protocol. The functions will check if the given protocol is the current protocol (http or https). If not they will show an error. As the limitation occur only if you switch the protocol from http to https (or vice versa) you should think about to call all your pages with only one protocol.

			2.) Do not use the function '''current_url()''' for building links to the current controller. The function will return an absolute path to this controller, but the base tag in your header will prepend the absolute path to your application again. Using this function in '''redirect(current_url())''' will work, but for links you should use '''get_instance()->uri->uri_string()'''.

	If you nevertheless should really need this functionality you must set your domain name in the variable '''base_url''' in '''config.php'''. You could of course setup the following code to use your domain name and benefiting from the automatic base detection, The variable {CC_BASE_URL} will be automatically replaced with the detected base:		If you nevertheless should really need this functionality you must set your domain name in the variable '''base_url''' in '''config.php'''. You could of course setup the following code to use your domain name and benefiting from the automatic base detection, The variable {CC_BASE_URL} will be automatically replaced with the detected base:
Zeile 55:		Zeile 59:
	</syntaxhighlight>		</syntaxhighlight>

	As the ~~limitation occur~~ only ~~if you switch~~ the ~~protocol~~ from http to ~~https (or vice versa)~~ you should think ~~about~~ to ~~call all~~ your ~~pages with only one protocol~~.		== Relative Links vs Absolute Links ==

			If you try to search the internet for '''relative links vs absolute links''' you will find only one multiple time copied and translated opinion of SEO people. They say that it is bad to use relative because of two things:

			1. Duplicate Content
			2. Scraping

			Some of them mention that developing a big website needs staging and therefore moving the application to different locations, domains and sometimes subfolders, but they come to a result that this should be solved by the programmers "somehow". On one website WordPress was mentioned as examplary because it uses only absolute URLs. I do not think that the author ever had to move a WordPress Website from one domain to another. It' the hell.

			But let us see what we could do to make our SEO friends happy and not to make our application ugly.

			The first point is that websites often are not configured well and they are reachable under four URLs:

			1. http://www.domain.tld
			2. http://domain.tld
			3. https://www.domain.tld
			4. https://domain.tld

			The most simple solution is to redirect three of these domains to one final domain with the search engine friendly 301 header. This can be done with some simple lines in the '''htaccess'' file.

			The second point is nothing you should worry about. If a scraper copies your site it is an inconsiderable detail if you have used relative or absolute links. I think it is much easier for a scraper to modify an application that uses absolute links, because he have only to search and replace the domainname. It is like you say to him "Hey, look here. This is the place you have to change the code to work my application under your domain!".

	== How this works ==		== How this works ==

Tm: /* Some Notes */

2017-11-22T15:15:44Z

Some Notes

← Nächstältere Version		Version vom 22. November 2017, 15:15 Uhr
Zeile 47:		Zeile 47:
	== Some Notes ==		== Some Notes ==

	With this modification all the libraries using '''base_url()''', '''site_url()''' or some helpers like '''redirect()''' which call these function will work in the most cases like before. The only limitaion is the usage of the second paramter '''$protocoll''' of the both functions. As we use only absolute paths and not any host name or IP address, we cannot set a protocol. The functions will show an error ~~if you try to use the htaccess file and call them with a protocol~~.		With this modification all the libraries using '''base_url()''', '''site_url()''' or some helpers like '''redirect()''' which call these function will work in the most cases like before. The only limitaion is the usage of the second paramter '''$protocoll''' of the both functions. As we use only absolute paths and not any host name or IP address, we cannot set a protocol. The functions will check if the given protocol is the current protocol (http or https). If not they will show an error.

	If you nevertheless should really need this functionality you must set your domain name in the variable '''base_url''' in '''config.php'''. You could of course setup the following code to use your domain name and benefiting from the automatic base detection, The variable {CC_BASE_URL} will be automatically replaced with the detected base:		If you nevertheless should really need this functionality you must set your domain name in the variable '''base_url''' in '''config.php'''. You could of course setup the following code to use your domain name and benefiting from the automatic base detection, The variable {CC_BASE_URL} will be automatically replaced with the detected base:
Zeile 54:		Zeile 54:
	$config['base_url'] = 'http://YOUR_FIXED_DOMAIN/{CC_BASE_URL}'));		$config['base_url'] = 'http://YOUR_FIXED_DOMAIN/{CC_BASE_URL}'));
	</syntaxhighlight>		</syntaxhighlight>

			As the limitation occur only if you switch the protocol from http to https (or vice versa) you should think about to call all your pages with only one protocol.

	== How this works ==		== How this works ==

Tm: /* Summary */

2017-11-22T14:47:09Z

Summary

← Nächstältere Version		Version vom 22. November 2017, 14:47 Uhr
Zeile 3:		Zeile 3:
	Sometimes it is difficult to move an application from one subfolder into another or into the root folder. Another problem is moving your applcation to another domain. It would be much simpler if the application use only relative url's and all the other stuff would be done automatically.		Sometimes it is difficult to move an application from one subfolder into another or into the root folder. Another problem is moving your applcation to another domain. It would be much simpler if the application use only relative url's and all the other stuff would be done automatically.

	In the most cases there are at least two points in your application you must always have to remember to modify if you move your application around. If you are using redirections with '''mod_rewrite''' you have to modify at least the '''RewriteBase''' and the most frameworks need extra configuration and special code to generate relative ~~Url's~~.		In the most cases there are at least two points in your application you must always have to remember to modify if you move your application around. If you are using redirections with '''mod_rewrite''' you have to modify at least the '''RewriteBase''' and the most frameworks need extra configuration and special code to generate a relative URL.

	With CodeIgniter for example you have functions like '''base_url()''' or '''site_url()''' which should helps you to built links without to know about your current place. But this not very handy as you have always remember to use these functions in every link and to setup correctly your configuration value in '''$config['base_url']'''. An automatic base url detection is built in, but for security reasons the IP address of the your server will be used to compose the URI instead of your host name ([https://expressionengine.com/blog/http-host-and-server-name-security-issues read more about security concerns of detecting the host name automatically]). This will not work in the most cases of course. Furthermore these functions produce absolute URLs, which is not necessary imo.		With CodeIgniter for example you have functions like '''base_url()''' or '''site_url()''' which should helps you to built links without to know about your current place. But this not very handy as you have always remember to use these functions in every link and to setup correctly your configuration value in '''$config['base_url']'''. An automatic base url detection is built in, but for security reasons the IP address of the your server will be used to compose the URI instead of your host name ([https://expressionengine.com/blog/http-host-and-server-name-security-issues read more about security concerns of detecting the host name automatically]). This will not work in the most cases of course. Furthermore these functions produce absolute URLs, which is not necessary imo.

Tm am 22. November 2017 um 14:46 Uhr

2017-11-22T14:46:08Z

← Nächstältere Version		Version vom 22. November 2017, 14:46 Uhr
Zeile 1:		Zeile 1:
	== Summary ==		== Summary ==

	Sometimes it is difficult to move an application from one subfolder into another or into the root folder. Another problem is moving your applcation to another domain. It would be much simpler is the application use only relative url's and all the other stuff would be done automatically.		Sometimes it is difficult to move an application from one subfolder into another or into the root folder. Another problem is moving your applcation to another domain. It would be much simpler if the application use only relative url's and all the other stuff would be done automatically.

	In the most cases there are at least two points in your application you must always have to remember to modify if you move your application around. If you are using redirections with '''mod_rewrite''' you have to modify at least the '''RewriteBase''' ~~if you move them from one subfolder into another. And~~ the most frameworks need extra configuration and special code to generate relative Url's. With CodeIgniter for example you have functions like '''base_url()''' or '''site_url()''' which should helps you to built links ~~to ressources your application~~ without to know about your current place. But this not very handy as you have always remember to use these functions in every link and to setup correctly your configuration value in '''$config['base_url']'''. Furthermore these functions produce absolute URLs, which is not necessary imo:		In the most cases there are at least two points in your application you must always have to remember to modify if you move your application around. If you are using redirections with '''mod_rewrite''' you have to modify at least the '''RewriteBase''' and the most frameworks need extra configuration and special code to generate relative Url's.

			With CodeIgniter for example you have functions like '''base_url()''' or '''site_url()''' which should helps you to built links without to know about your current place. But this not very handy as you have always remember to use these functions in every link and to setup correctly your configuration value in '''$config['base_url']'''. An automatic base url detection is built in, but for security reasons the IP address of the your server will be used to compose the URI instead of your host name ([https://expressionengine.com/blog/http-host-and-server-name-security-issues read more about security concerns of detecting the host name automatically]). This will not work in the most cases of course. Furthermore these functions produce absolute URLs, which is not necessary imo.

	Example for HTML:		Example for HTML:
Zeile 17:		Zeile 19:
	</syntaxhighlight>		</syntaxhighlight>

			So why not using only relative URLs?

	~~So why not using only relative URLs?~~		CodeCoupler includes a htaccess file that detects and save the current base folder in an environment variable. This variable will be used to set an absolute URL into the configuration variable '''base_url''' in codeigniter. From now on all CodeIgniter functions will produce an URI without a hostname and with the correct subfolder if needed.

	~~CodeCoupler includes a htaccess file that detects and save the current base folder in a server variable and redirects everything into the '''index.php'''. Now~~ you can set ~~the~~ base ~~in your html page and use only relative URLs~~:		In an HTML page you can set your base like this:

	<syntaxhighlight lang="html">		<syntaxhighlight lang="html">
	<base href="<?= (~~isset($_SERVER['BASE'])?$_SERVER['BASE']:$_SERVER['REDIRECT_BASE']~~) ?>">		<base href="<?= base_url() ?>">
	</syntaxhighlight>		</syntaxhighlight>

	If you are using the template '''html''' it will be set in every page automatically.		By the way: If you are using the template '''html''' it will be already set in every page automatically.

	From now you do not have to bother how to point to ressources anymore ~~or use the '''index.php'''~~. Just start everytime with the name of controller:		From now you do not have to bother how to point to ressources anymore. Just start everytime with the name of controller:

	Example for HTML:		Example for HTML:
Zeile 41:		Zeile 44:
	}		}
	</syntaxhighlight>		</syntaxhighlight>

	~~Remarks:~~

	If you are running PHP in CGI mode then apache will prefix your environment variables with '''REDIRECT_'''. So we have to check first if the index '''$_SERVER['BASE']''' ist set. If not we should use the index '''$_SERVER['REDIRECT_BASE']'''.

	== Some Notes ==		== Some Notes ==

	~~If you nevertheless should really need~~ the ~~function~~ '''base_url()''' ~~of CodeIgniter here a note to the~~ '''~~base_url~~''' ~~variable~~ in '''~~config.php~~''':		With this modification all the libraries using '''base_url()''', '''site_url()''' or some helpers like '''redirect()''' which call these function will work in the most cases like before. The only limitaion is the usage of the second paramter '''$protocoll''' of the both functions. As we use only absolute paths and not any host name or IP address, we cannot set a protocol. The functions will show an error if you try to use the htaccess file and call them with a protocol.

	~~This variable~~ should ~~always be empty to let CodeIgniter automatically detect~~ the ~~protocol the hostname and the subdirectory~~ in ~~functions like~~ '''~~base_url()~~'''. ~~In some cases you have~~ to ~~set this variable~~ and ~~then you have another place to remind if you move your application around. With CodeCoupler you can set this~~ variable ~~in a way that moving~~ the ~~application at least to another folder do not break your links~~:		If you nevertheless should really need this functionality you must set your domain name in the variable '''base_url''' in '''config.php'''. You could of course setup the following code to use your domain name and benefiting from the automatic base detection, The variable {CC_BASE_URL} will be automatically replaced with the detected base:

	<syntaxhighlight lang="php">		<syntaxhighlight lang="php">
	$config['base_url'] = 'http://YOUR_FIXED_DOMAIN/~~'.(is_cli()?'':ltrim($_SERVER['BASE'],'/~~'));		$config['base_url'] = 'http://YOUR_FIXED_DOMAIN/{CC_BASE_URL}'));
	</syntaxhighlight>		</syntaxhighlight>

Zeile 61:		Zeile 60:

	<syntaxhighlight lang="apache">		<syntaxhighlight lang="apache">
	RewriteCond %{ENV:~~URI~~} ^$		RewriteCond %{ENV:CC_TMP_URI} ^$
	RewriteRule ^(.*)$ - [ENV=~~URI~~:$1]		RewriteRule ^(.*)$ - [ENV=CC_TMP_URI:$1]
	</syntaxhighlight>		</syntaxhighlight>

	The first line looks if the variable ~~URI~~ is empty. If yes, the second line stores the path from the location of the htaccess file to the requested file into the variable '''~~URI~~'''.		The first line looks if the variable CC_TMP_URI is empty. If yes, the second line stores the path from the location of the htaccess file to the requested file into the variable '''CC_TMP_URI'''.

	* Example Request: '''<nowiki>http://host/subdir/request-dir/request-file?var=val</nowiki>'''		* Example Request: '''<nowiki>http://host/subdir/request-dir/request-file?var=val</nowiki>'''
Zeile 71:		Zeile 70:

	<syntaxhighlight lang="apache">		<syntaxhighlight lang="apache">
	RewriteCond %{ENV:~~BASE~~} ^$		RewriteCond %{ENV:CC_BASE_URL} ^$
	RewriteCond %{ENV:~~URI~~}::%{REQUEST_URI} ^(.)::(.?)\1$		RewriteCond %{ENV:CC_TMP_URI}::%{REQUEST_URI} ^(.)::(.?)\1$
	RewriteRule ^ - [ENV=~~BASE~~:%2]		RewriteRule ^ - [ENV=CC_BASE_URL:%2]
	</syntaxhighlight>		</syntaxhighlight>

	The first line looks if the variable ~~BASE~~ is empty. The condition of the second line is always true. The only point of this line is saving the some values in two groups. It works as follows:		The first line looks if the variable CC_BASE_URL is empty. The condition of the second line is always true. The only point of this line is saving the some values in two groups. It works as follows:

	Remember:		Remember:
	* Our example Request: '''<nowiki>http://host/subdir/request-dir/request-file?var=val</nowiki>'''		* Our example Request: '''<nowiki>http://host/subdir/request-dir/request-file?var=val</nowiki>'''
	* The variable ~~URI~~ have the value because of the rule above: '''request-dir/request-file'''		* The variable CC_TMP_URI have the value because of the rule above: '''request-dir/request-file'''

	Now the condition is:		Now the condition is:
Zeile 92:		Zeile 91:
	</syntaxhighlight>		</syntaxhighlight>

	Now we have in '''group 2''' the base that we need. The third line save this value into the variable ~~BASE~~. And we are ready for our final rewrite:		Now we have in '''group 2''' the base that we need. The third line save this value into the variable CC_BASE_URL. And we are ready for our final rewrite:

	<syntaxhighlight lang="apache">		<syntaxhighlight lang="apache">
	RewriteCond $1 !^index\.php		RewriteCond $1 !^index\.php
	RewriteRule ^(.*)$ %{ENV:~~BASE~~}index.php [L,QSA]		RewriteRule ^(.*)$ %{ENV:CC_BASE_URL}index.php [L,QSA]
	</syntaxhighlight>		</syntaxhighlight>

Tm: /* Summary */

2017-11-22T08:32:26Z

Summary

← Nächstältere Version		Version vom 22. November 2017, 08:32 Uhr
Zeile 1:		Zeile 1:
	== Summary ==		== Summary ==

	~~In the most applications that are using redirections and rewrites you have~~ to ~~modify at least the '''RewriteBase''' if you~~ move ~~them~~ from one subfolder into another. ~~Some frameworks make our life unnecessarily difficult changing~~ the ~~domain name and some other need extra code to generate~~ relative ~~Url~~'s.		Sometimes it is difficult to move an application from one subfolder into another or into the root folder. Another problem is moving your applcation to another domain. It would be much simpler is the application use only relative url's and all the other stuff would be done automatically.

	With CodeIgniter for example you have functions like '''base_url()''' or '''site_url()''' which should helps you to built links to ressources your application without to know about your current place:		In the most cases there are at least two points in your application you must always have to remember to modify if you move your application around. If you are using redirections with '''mod_rewrite''' you have to modify at least the '''RewriteBase''' if you move them from one subfolder into another. And the most frameworks need extra configuration and special code to generate relative Url's. With CodeIgniter for example you have functions like '''base_url()''' or '''site_url()''' which should helps you to built links to ressources your application without to know about your current place. But this not very handy as you have always remember to use these functions in every link and to setup correctly your configuration value in '''$config['base_url']'''. Furthermore these functions produce absolute URLs, which is not necessary imo:

	Example for HTML:		Example for HTML:
Zeile 17:		Zeile 17:
	</syntaxhighlight>		</syntaxhighlight>

	But this not very handy as you have always remember to modify your configuration value in '''$config['base_url']''' and your '''RewriteBase'''. Furthermore these functions produce absolute URLs, which is not necessary.

	So why not using only relative URLs?		So why not using only relative URLs?
Zeile 24:		Zeile 23:

	<syntaxhighlight lang="html">		<syntaxhighlight lang="html">
	<base href="<?=$_SERVER['BASE']?>">		<base href="<?= (isset($_SERVER['BASE'])?$_SERVER['BASE']:$_SERVER['REDIRECT_BASE']) ?>">
	</syntaxhighlight>		</syntaxhighlight>

	If you are ~~sing~~ the ~~Master Template Library~~ it will be set in every page automatically.		If you are using the template '''html''' it will be set in every page automatically.

	From now you do not have to bother how to point to ressources anymore or use the '''index.php'''. Just start everytime with the name of controller:		From now you do not have to bother how to point to ressources anymore or use the '''index.php'''. Just start everytime with the name of controller:
Zeile 42:		Zeile 41:
	}		}
	</syntaxhighlight>		</syntaxhighlight>

			Remarks:

			If you are running PHP in CGI mode then apache will prefix your environment variables with '''REDIRECT_'''. So we have to check first if the index '''$_SERVER['BASE']''' ist set. If not we should use the index '''$_SERVER['REDIRECT_BASE']'''.

	== Some Notes ==		== Some Notes ==

Tm: /* Some Notes */

2017-11-05T13:38:59Z

Some Notes

← Nächstältere Version		Version vom 5. November 2017, 13:38 Uhr
Zeile 45:		Zeile 45:
	== Some Notes ==		== Some Notes ==

	If you nevertheless should really need the ~~funtion~~ '''base_url()''' of CodeIgniter here a note to the '''base_url''' variable in '''config.php''':		If you nevertheless should really need the function '''base_url()''' of CodeIgniter here a note to the '''base_url''' variable in '''config.php''':

	This variable should always be empty to let CodeIgniter automatically detect the protocol the hostname and the subdirectory in functions like '''base_url()'''. In some cases you have to set this variable and then you have another place to remind if you move your application around. With CodeCoupler you can set this variable in a way that moving the application at least to another folder do not break your links:		This variable should always be empty to let CodeIgniter automatically detect the protocol the hostname and the subdirectory in functions like '''base_url()'''. In some cases you have to set this variable and then you have another place to remind if you move your application around. With CodeCoupler you can set this variable in a way that moving the application at least to another folder do not break your links:

Tm am 5. November 2017 um 13:38 Uhr

2017-11-05T13:38:39Z

← Nächstältere Version		Version vom 5. November 2017, 13:38 Uhr
Zeile 52:		Zeile 52:
	$config['base_url'] = 'http://YOUR_FIXED_DOMAIN/'.(is_cli()?'':ltrim($_SERVER['BASE'],'/'));		$config['base_url'] = 'http://YOUR_FIXED_DOMAIN/'.(is_cli()?'':ltrim($_SERVER['BASE'],'/'));
	</syntaxhighlight>		</syntaxhighlight>

	~~== Thanks ==~~

	~~CodeCoupler adopted the solution published by Jon Lin in a Stack Overflow Answer from here: http://stackoverflow.com/a/21027742~~

	== How this works ==		== How this works ==

Tm: /* Some Notes */

2017-11-05T13:38:15Z

Some Notes

← Nächstältere Version		Version vom 5. November 2017, 13:38 Uhr
Zeile 45:		Zeile 45:
	== Some Notes ==		== Some Notes ==

	A note to the '''base_url''' variable in '''config.php''' ~~of CodeIgniter~~: This variable should always be empty to let CodeIgniter automatically detect the protocol the hostname and the subdirectory in functions like '''base_url()'''. In some cases you have to set this variable and then you have another place to remind if you move your application around. With CodeCoupler you can set this variable in a way that moving the application at least to another folder do not break your links:		If you nevertheless should really need the funtion '''base_url()''' of CodeIgniter here a note to the '''base_url''' variable in '''config.php''':

			This variable should always be empty to let CodeIgniter automatically detect the protocol the hostname and the subdirectory in functions like '''base_url()'''. In some cases you have to set this variable and then you have another place to remind if you move your application around. With CodeCoupler you can set this variable in a way that moving the application at least to another folder do not break your links:

	<syntaxhighlight lang="php">		<syntaxhighlight lang="php">