Tutorial Blog | Blogger Tutorial Blogspot Templates, Cara Membuat Blog Networking Tutorials SEO.: how to create a blog

Blog, it is today a web classic "hello world" of web solutions. Let's take a quick look at how to create such a simple blog in the net. Requirements : Understanding the basic principles Nette (relations in the MVP pattern, the basic idea of the presenter and his relationship to the templates) Introduction Creating a simple blog is an evergreen topics tutorials various web frameworks. Unfortunately, most of these tutorials is curtailed to the minimum spanning tree of the task and the main objective is to show the user how to easily Framework, it goes with that. This reduces the complexity of the task at the level at which almost worth a framework to use. So do not take this tutorial as a teaching material. tutorial is used in namespace version Nette. Although the application is so small that namespaces are there more of a nuisance, it's something that every potential user Nette should know and use. If for technical reasons, can not use PHP version => 5.3, use overrefined Nette version for PHP 5.2 and the drain of said source code definition namespaces. Blog for 19 minutes! With RoR or Code Ignite can create a "complete" "blog" for "20" minutes. Dear, it's nothing! We will show you that with Nette's 19 minutes you can too! <h2 id="toc-instance">Installation</h2> We use the skeleton of distribute. Copy it to a folder on the server. In the folder <code>/ libs</code> will copy dibi (sold Nette is located in the folder 3rdParty). We will also need a database, I'll stick to MySQL, but if you want to use SQLite or PostgreSQL, this is not a problem, just read on. Remember that the skeleton is missing Nette in the folder <code>/ libs</code> ! <h2 id="toc-databaze-a-model">Database and model</h2> Let's start with creating the appropriate tables. Their structure is clear from the brief. So run on our database the following commands: <pre class="src-sql" style="overflow: auto; clear: both; font-size: 14px; font-family: Consolas, Monaco, monospace; font-weight: normal; line-height: 1.4; background-color: #f1f7ff; border-top-left-radius: 5px; border-top-right-radius: 5px; border-bottom-right-radius: 5px; border-bottom-left-radius: 5px; box-shadow: #e9eef5 1px 1px 10px inset; padding: 10px; margin: 1.5em 0px; position: relative; z-index: 10; color: #333333; font-style: normal; font-variant: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-position: initial initial; background-repeat: initial initial;"><code style="font-family: Consolas, Monaco, monospace;">CREATE TABLE `posts` ( `id` int ( 11 ) NOT NULL AUTO_INCREMENT, `title` varchar ( 128 ) COLLATE utf8_bin NOT NULL , `body` text COLLATE utf8_bin NOT NULL , `date` datetime NOT NULL , PRIMARY KEY ( `id` ) ) ENGINE = InnoDB DEFAULT CHARSET = utf8 COLLATE = utf8_bin;</code></pre> This will create a table with articles. <blockquote> <pre><code>CREATE TABLE `comments` ( `id` INT NOT NULL AUTO_INCREMENT PRIMARY KEY , `post_id` INT NOT NULL , `author` VARCHAR ( 128 ) NOT NULL , `body` TEXT NOT NULL , `date` DATETIME NOT NULL , INDEX (post_id), FOREIGN KEY (post_id) REFERENCES posts(id) ) ENGINE = INNODB CHARACTER SET utf8 COLLATE utf8_bin;</code></pre> </blockquote> And this (surprisingly) a table of comments. If you are using a different database, create the same table structure, dibi takes care of compatibility on the part of the application itself. When we have a database, you need to connect it through dibi. Configuration files in Nette offer an elegant way to manage data such as information about the database. Open <code>config.ini</code> in the folder <code>/ app</code> and parts <code>[common]</code> Add the appropriate modification of these lines: <blockquote> <pre><code>db.server = localhost db.database = blogtut db.username = blogtut db.password = blogtut db.driver = mysqli db.charset = utf8 db.lazy = TRUE</code> </pre> </blockquote> And now the connection itself. To file <code>bootstrap.php</code> (boot file of the entire application, as you should know), add a line <blockquote> <pre><code>$ Application -> run () / / This line runs our application ...</code></pre> </blockquote> following: <pre><code>dibi :: connect (Environment :: getConfig ( 'db' )) / / ... and connect to need before you start </code></pre> You stop for a moment and give you a minute theory, which deepen knowledge and to answer possible questions. A few key points: <ul> <li>Nette <a href="http://doc.nette.org/cs/nette-loaders">reads the code files (either library or part of the application itself) itself and as needed</a> . Therefore, there is no include or require neither here nor anywhere else in our code.</li> <li>Call the <code>Environment :: getConfig ('db')</code> we obtain from the configuration file field specifies the database settings. Our notation is different representations of associative array</li> </ul> <pre><code>$db = array ( 'server' => 'localhost' , 'database' => 'blogtut' , 'username' => 'blogtut' , 'password' => 'blogtut' , 'driver' => 'mysql' , 'charset' => 'utf8' , 'lazy' => TRUE );</code></pre> <ul> <li>Even if we set the database connection each time the application starts, the connection is real only when it is really needed, thanks to the setting <code>db.lazy = TRUE</code> in <code>config.ini</code> .</li> </ul> We have yet to develop models for both tables. <pre><code><? Php class PostsModel { public static function fetchAll () { return dibi :: fetchAll ( ' SELECT * FROM [posts] ORDER BY [date] ' , dibi :: DESC ); } }</code></pre> <pre><code><? Php class CommentsModel { public static function fetchAll ( $ post_id ) { return dibi :: fetchAll ( ' SELECT * FROM [comments] WHERE [post_id] =% i ' , $ post_id ); } }</code></pre> For clarity, the moment will their methods without undue respects to pull all available data. Both sets of class definitions saved in <code>/ app / models</code> and name them according to the class that contains ( <code>PostsModel.php</code> , <code>CommentsModel.php</code> ). If you are used to terminate scripts brand <code>?></code> and quickly weaned off! end tags are optional and only cause problems with non-printing characters, which then causes the inability to send the HTTP headers. <h2 id="toc-presenter">Presenter</h2> V <code>/ app / presenters /</code> is HomepagePresenter. It will serve as a good basis for our efforts. Add to it a method that takes data from the model and passes them to the template to render. renderDefault method to adjust <pre><code>public function renderDefault () { $ This -> template-> posts = PostsModel :: fetchAll (); }</code></pre> If you are unsure about why working with a default method in the presenter Homepage, look for <a href="http://doc.nette.org/cs/nette-application-route">the routes</a> in the bootstrap.php file. <h2 id="toc-view">View</h2> Well, now we view <code>default</code> on the variable <code>$ posts</code> , which contains all the posts. Let's dump. folder <code>/ app / templates</code> file is <code>@ layout.phtml</code> . It contains the basic framework of all the sites that we create. Therefore, I suggest you look at it. V <code>/ app / templates / Homepage</code> is set <code>default.phtml</code> that contains the block definition <code>content</code> , the content of which will replace the <code>{include} # content</code> in the layout. List of all articles might look like this: <pre><code>{ block content } <h1> My blogísek </h1> <div id= "posts" > { if count( $posts ) } { foreach $posts as $post } <div class= "post" > <h3> { $post [ 'title' ] } </h3> Přidáno { $post [ 'date' ]|date } { $post [ 'body' ] } </div> { / foreach } { else } There was no written article. { / if } </ div></code></pre> Download <a href="http://files.nette.org/git/pla/posts.sql">test data</a> , load them into the database and try to open the root site in your browser.The result should look like this: <pre><code> </code></pre>