WordPress Query Page

Saturday, October 6th, 2007 at 6:51 pm

wordpress query page
How can you effectively build the clean URLs?

Most websites nowadays use databases with dynamic pages. That is, a site as http://example.com contain a page to display articles showarticle.php after determining that the item be removed from the base data could be used query strings (http://example.com/showarticle.php?artcileid=523). I recently read about the clean URL and how to convert URL http://example.com/articles/523.html before for example. If you look here, we have not lost the id of the article (523) still in the URL, is the has changed. M question now is: a lot of websites use this technique, but I can not find any unique identifier in the title, such as a http://goodsite.com/articles/how-to-be-an-effective site as leader / I see no reference to the id of the page here, and I do not use the title of the page to be the primary key, as this would be contrary to the rules of optimization. I learned that this technique is used by WordPress. Do you have any idea how establish this?

There is only one way to skin this particular cat. I will provide an idea that based on the Model-View-Controller (MVC). Elements Model application business logic and interaction with files, databases, etc. The controller manages the relationship between incoming requests and responses outgoing. View the items composing responses, usually HTML content. In MVC, the "C" stands for "driver". The traffic controller is Police to implement, may have other duties too, but one of its main responsibilities is to identify the page (see) must be returned in response the prompt. In considering the content of the request, the controller to make decisions about how to direct the request to a view that will of writing HTML code will be sent back to the user. As a simple example of a driver for PHP is based on the HTTP request parameters ... // controller.php implements the Dispatcher View (Controller) pattern / / controller.php only sees relationships: / / controller.php filter.php <---> <---> [Workers view] / / Get the view of the application. $ View = $ _REQUEST ["view"] / / route the request to change the view corresponding ($ View) {case "other": require_once ("other.php") break; / / cause is by default - just passing the case of "major": / / Do nothing here by default: require_once ("main.php");} / / exit the current stack frame, to control the release of filter.php> Applications would look like: http://site.com?view=page_name where page_name be valid values for "other" and "principal" - any other thing would be by default? to provide the main.php. This is the simplest version of a driver, as only decide which views should handle the request. Everyone Check owns a duty to know how to compose their own answer, in the Dispatcher View pattern, the business logic of a model element that is invoked from the View element. What if a foundation is involved, a model element to be managed for the eyes. Descriptive of the URL. $url = $_SERVER['REQUEST_URI'];

$url = Trim ($ url) if ("/" == substr ($ url, 0, 1)) {$ url = substr ($ url, 1, strlen ($ url) -1);} $ url = explode ( "?" $ Url, 2), $ url = array_shift ($ url) if (substr ($ url, -1) == '/') {$ url = substr ($ url, 0, -1);} switch ($ url) {Case "friendly-url-from-another-page": require_once ("other.php") break; case "friendly-url-of-main-page": default: require_once ('main.php ");}> As you can see the relationship of the URL to the view script that actually handle the request can be anything you like. Finally, as to the pages that show names like "some.html" - the name can be anything, regardless of the actual source of the service. That is, the fact that the browser has released a name *. html does not mean that there is a HTML at the other end. The architecture of the MVC application sends all requests to controller. It is entirely the driver to postpone the composition of the light of the answer to another worker, and the apparent name of the result can be anything you want (made configuration files for the server or direct manipulation on the other side - that just use the URL-friendly, 'cousin' is also friendly. That is the vision of twenty thousand feet.

Query Editor preview