This refers to b2evolution version 0.9.0

To add your own smilie to your toolbar, first you need to open up plugins/_smilies.conf.php in your favourite editor.

Copy one of the existing smilies from the $this->smilies = array( and make sure you paste your code before the closing );.

So, your code will end up looking like this.

'texttobereplaced' => 'my_smilie.gif',

Where texttobereplaced is the text that when typed will be replaced by a smilie, and my_smilie.gif is the name of your new smilie.

Now all you need to do is upload your my_smilie.gif to img/smilies, and upload your changed _smilies.conf.php

To show the smileytoolbar in the backend:

Change the file plugins/toolbars/_smilies.toolbar.php, line 26 (in 0.9.0.11)

var $display = true;

2005-12-10: Relates to version 0.9.1 and earlier

1. b2evo comes with a blacklist. Update that frequently. (This is found in admin/antispam/request abuse update).
2. Change the directory/folder name for your trackback and comments from htsrv to any other valid directory/folder name. Then edit conf/_advanced.php to reflect the change. Change the following line of code:
   $htsrv_subdir = 'htsrv'; This prevents bots that automatically attempt to submit comments and trackbacks using b2evolution's default htsrv installation. You can write a script to automate this for you, or download one (for example from: http://randsco.com/index.php/2005/11/18/anti_spam_script).
   

3. Edit/create an .htaccess file to prevent off-site spamming. The following lines need to go into the .htaccess file (changing yoursite.com to your particular domain):

   # Block remote calls to comments
   RewriteCond? %{HTTP_REFERER} !^http://(www\.)?yoursite.com/.*$ [NC]
   RewriteCond? %{REQUEST_URI} .*comment_post.php$"
   RewriteRule? .* - [F] 
   

For more instructions and updates, see the forum thread ispam techniques in one simple thread.

Historical
Porn sites have found a way to fool blogtools into thinking sites are being referred by them. b2evolution has a built in way to handle this. In versions prior to 0.8.7-beta, you can fix this by adding them to the $block_urls array in the /conf/_antispam.php file. In 0.8.7-beta and later releases, you can click the icon by the spam referer or spam comment to ban the listed domain. You can also ban any keyword directly in the Antispam tab in the back-office. This will ban referrers from domains containing those keywords, and comments with links containing those keywords.

NOTE: The offending sites have been blocked in the central ban list, so all you have to do to be protected is update your ban list from the central ban list, by clicking the link in the Antispam tab of your back-office. By updating your local ban list from the central list, or reporting spammers to the central list, you agree to the Terms of Service.

This man page refers to b2evolution 0.9.2

Let's assume you have a default installation of b2evolution:

• Blog All can be accessed through index.php?blog=1
• Blog A can be accessed through index.php?blog=2
• Blog B can be accessed through index.php?blog=3
• The Linkblog can be accessed through index.php?blog=4

Let's start with Blog A

Let's start with blog A, because it is the easiest. b2evolution ships with an alternative file to call blog A! In your URL, try replacing the end index.php?blog=2 with a_stub.php. You should access the exact same page. That's because b2evolution ships with the file a_stub.php which is preconfigured for acting as if index.php was called with parameter blog=2.

However, if you now click on an internal link on this page, say "Last comments", you will notice that b2evo throws you back to index.php?blog=2 !

That's because b2evo doesn't know (yet) that you want to use a_stub.php instead of index.php?blog=2. You must set this up in the admin, under blogs then Blog A. Under "Preferred access type:", you must select "Explicit reference to stub file (Advanced)" and then name the stub file name in "Stub name:"; here you should enter a_stub.php. Validate your changes.

Now, you can refresh the blog page and click on some links. You will notice that you now stay on a_stub.php and no longer get redirected to index.php?blog=2.

Now with Blog B

Try the same operations as above on blog B (blog number 3) and try to associate it with a stub file named b_stub.php. You will notice that you get a "404 Page not found" error from your webserver!

That is because b2evolution does *not* ship with a file named b_stub.php !

Now try to duplicate the file a_stub.php as b_stub.php on your webserver.

What happens if you acces this page? You will notice that you no longer get an error, *but* b_stub.php displays Blog A just as a_stub.php did! This is not what you wanted!

This happends because b_stub.php contains preset parameters so that you don't have to pass these on the URL. In this case, it contains a hardcoding for blog=2 and blog #2 is blog A, not blog B. (You can see the blog numbers in the admin, under Blogs).

To correct that, you must open the file b_stub.php with a text editor and find the following line:
$blog = 2; // 2 is for "demo blog A" or your upgraded blog (depends on your install)

Replace this line with:
$blog = 3;

Take special care not to forget the $ sign in front of $blog, as well as the semi column ( ; ) at the end of the line. The white space and the comment after // can be omitted.

Save the file (and upload it to your webserver if necessary).

Calling b_stub.php should now work as expected.

The file b_stub.php is what we call a Stub File. You may have noticed that it also lets you set other parameters than just the blog number. For more information on this, see StubFiles.

This refers to b2evolution versions 0.9.0.*

Are you getting traffic from search engines for something that a referer spammer faked into your stats page? Would you like to keep your referer data and stats page visible to visitors but stop the undesirable traffic? If so this is the place for you.

Referrer spammers use a couple of methods to find you, and a big one is using the search engines. They look for "top referrer" and "recent referrer" and "disp=stats" knowing that if you have those then you are a b2evolution user and that they can spam you. The solution is three parts, the first two of which are normal everyday b2evolution stuff.

First always keep your antispam table up to date. In your back office click the antispam tab then click Request abuse update from centralized blacklist. Your antispam table will be compared to the community-based version then updated. You will see some things that are added and some that are already handled, then it will tell you it's done. If this is your first time getting the update you should do it again and again until the update doesn't have any new sites to add (or identify as already handled) so that you get ALL the available updates.

Next you need to clear the existing spammers out of your referrer logs. In your back office click on the stats tab. On the "View stats for blog none and referers tab scroll to the bottom of the page and take a look at the Top referers section. If you see some undesirable site in your Top referers section click the "ban" symbol next to their name. You will be taken to your antispam section. Your hit logs and comments will be searched for undesirable domain names, and if found they will be listed for you. You will then have up to 4 checkboxes for you to (1) delete the hits (if there were any), (2) delete the comments (if there were any), (3) ban the domain locally, and (4) report the domain to the central blacklist.

Do it. Click Perform selected operations to delete them, ban them, and report them.

Now that you've cleaned up your referer data and stats page the next thing to do is to stop the search engines from sending you traffic you don't want. The problem is you can't really do that as long as they have your page indexed. The solution is to control what they index, and this involves editing your _main.php file in your default skin. Open skins/skinname/_main.php in your favorite editor and look for

<meta name="keywords" content="<?php $Blog->disp( 'keywords', 'htmlattr' ); ?>" />
<meta name="generator" content="b2evolution <?php echo $b2_version ?>" /> <!-- Please leave this for stats -->
<link rel="alternate" type="text/xml" title="RDF" href="<?php $Blog->disp( 'rdf_url', 'raw' ) ?>" />
<link rel="alternate" type="text/xml" title="RSS .92" href="<?php $Blog->disp( 'rss_url', 'raw' ) ?>" />

Now you add a "robots noindex nofollow" tag for the stats page by adding a conditional statement about $disp:

<meta name="keywords" content="<?php $Blog->disp( 'keywords', 'htmlattr' ); ?>" />
<meta name="generator" content="b2evolution <?php echo $b2_version ?>" /> <!-- Please leave this for stats -->
<?php if( $disp == 'stats' ) { // stop search engines from indexing the stats page
echo '<meta name="robots" content="noindex, nofollow" />'."\n";
} ?>
<link rel="alternate" type="text/xml" title="RDF" href="<?php $Blog->disp( 'rdf_url', 'raw' ) ?>" />
<link rel="alternate" type="text/xml" title="RSS .92" href="<?php $Blog->disp( 'rss_url', 'raw' ) ?>" />

It will take a while for this to help because you have to wait for the search engines to index your blog again. In the mean time keep your antispam table up to date by getting the updates, and keep your stats clean by checking your stats page for suspicious activity. A domain name that suddenly shows up in the top of your Top referers section is suspicious!

By the way spammers aren't always porn sites. A spammer is someone who fakes referer data to get on your referer list. If you see a suspected spammer you might want to visit the site to make sure before reporting them. Sometimes I do, but only if the name isn't obviously unrelated to the things I blog about.

This man page refers to b2evolution version 0.9.0

The edit screen lets you write new posts or edit existing posts.

Below, you will find a quick rundown of available input fields:

Main Fields

Title

The headline of your post.

Language

This lets you select the Locale? of your post among all locales that have been enabled in the RegionalSettingsScreen?.

Link to url

Turns the title of the post into a hyperlink.

Toolbars

These toolbars will help you in editing your post in the main text area below. They will automatically add code/tags to the main text area below.

Those toolbars are plugins. If one of them is of no interest to you, you can disable it.

Main text area

This is where you enter the text for your post.

• You can enter XHTML tags here, however some tags might get rejected later depending on your SafeXhtmlChecker? and other security settings.

• You can also use alternative markup based on what RendererPlugins? you enable. See below.

• Finally, there are a few pseudo-HTML tags you can use. These will be interpreted by b2evolution when displaying the post:

• <!--more--> will split the post into a teaser (before the more tag) and an extended section (after the mode tag). At display time, only the teaser will be displayed with a link to read more. The whole post will be displayed once the SiteVisitor clicks the more link.

• <!--noteaser--> : if this tag appears in the post, the teaser part of the post will not be repeated when the SiteVisitor clicks the more link.

• <!--nextpage--> will split the post in as many pages as you want. Only the first page will be displayed by default, with links to the others pages.

Action buttons

Click on Blog this! to validate your entry.

Sidebar

Status

Categories

Comments

Renderers

Here you can choose which RendererPlugins? will be applied to your post before display. The list of available plugins can be modified.

Advanced properties

Feedback is displayed by the _feedback template, which is usually included by the _main template.

To display comments, trackbacks and pingbacks UNMIXED, use the following code snippet in the _main template:

<?php
// this includes the comments and a form to add a new comment
$disp_comments = 1; // Display the comments if requested
$disp_comment_form = 1; // Display the comments form if comments requested
$disp_trackbacks = 0; // Display the trackbacks if requested
$disp_trackback_url = 0; // Display the trackbal URL if trackbacks requested
$disp_pingbacks = 0; // Display the pingbacks if requested
include( dirname(__FILE__)."/_feedback.php");

// this includes the trackbacks
$disp_comments = 0; // Display the comments if requested
$disp_comment_form = 0; // Display the comments form if comments requested
$disp_trackbacks = 1; // Display the trackbacks if requested
$disp_trackback_url = 1; // Display the trackbal URL if trackbacks requested
$disp_pingbacks = 0; // Display the pingbacks if requested
include( dirname(__FILE__)."/_feedback.php");

// this includes the pingbacks
$disp_comments = 0; // Display the comments if requested
$disp_comment_form = 0; // Display the comments form if comments requested
$disp_trackbacks = 0; // Display the trackbacks if requested
$disp_trackback_url = 0; // Display the trackbal URL if trackbacks requested
$disp_pingbacks = 1; // Display the pingbacks if requested
include( dirname(__FILE__)."/_feedback.php");
?>

[NL]

This page applies to b2evo 0.9

When you upload files to your webserver by FTP, those files are saved on the server with some specific access permissions. Typically, everyone will be able to "read" the files and subdirectories, that is view them through the webserver, but only you and you alone (when you log into the FTP server) will be able to "write' to these files/subdirectories and modify them.

For some specific actions, b2evolution will need to modify some of its files. b2evo will also need to write new files when you use b2evo to upload an image or generate a static .html file. The problem is: b2evo is not you. More specifically: the PHP process that runs b2evo is not you!

Thus you will most likely need to change the permissions on some files and subdirectories in order to allow b2evo to write there and perform the requested actions.

Note: on somehosts, the default permissions already allow your scripts (b2evo in this cse) to change your files on your account. So you can try b2evo without changing any file permission and come back here only if you get a file permission error.

Most webservers runs some variant of UNIX. On these systems, file permissions can be changed via chmod. If you're not familiar with UNIX file permissions and chmod, check out A quick and dirty chmod Tutorial. If your server is running Windows you probably don't need to change anything.

You can change permissions on files/folder either with an FTP client program (like Filezilla), a Unix shell or a web file manager like the one built into cPanel.

What files/subdirectories do need specific permissions?

Let's assume your b2evo is installed under /blogs. Here's what you need to change:

• chmod 666 /blogs/conf/_config.php if you want the installer to be able to automatically update your config based on your input.

• chmod 777 /blogs to allow creation of blog stub files from the admin interface or to generate static pages for your blogs.

• chmod 777 /blogs/media in order to upload images and other media from b2evo's backoffice.

• chmod 666 /blogs/skins/custom/* if you want to use the template editor for the custom skin.

Deze pagina is van toepassing op b2evo 0.9

Als je files upload naar je webserver met FTP, dan krijgen deze files specifieke beveiligingen mee. Zonder dat je iets doet, zal iedereen ‘lees’ bevoegdheid hebben op je files. Iedereen kan je files dus bekijken, maar enkel jij – en jij alleen – kan ze wijzigen (hebt schrijfbevoegdheid). Jij kan deze files/subdirectories wijzigen of erop schrijven, en dit zelfs enkel indien je via je FTP-pragramme aanlogt.

Voor bepaalde acties, zal b2evolution deze files echter moeten kunnen wijzigen. B2evo dient bvb nieuwe files te kunnen schrijven als je images oplaad via de software in je posts, of als je statische html-files wil generen van je blogs.
Het probleem is echter : b2evo ben jij niet. Of meer specifiek : het proces dat via php opgestart wordt en b2evo runt ben jij niet. Je bent niet aangelogt via ftp, dus de server kan niets controleren.

Dus naar alle waarschijnlijkheid zal je de server moeten instellen opdat een webproces (b2evo dus) wel files kan uploaden of files wijzigen.

PS : Op sommige hosts, laten de standaard instellingen het toe opdat scripts (b2evo in dit geval) files wijzigen in je account. Je kan dus proberen om b2evo te installeren zonder dat je iets veranderd aan de filepermissies en enkel als je file-permissie foutens krijgt, kom je terug naar hier voor meer uitleg.

De meeste webservers werken met een variant van UNIX. Op deze servers kan je filepermissies wijzigen met chmod. Als je niet vertrouwt bent met UNIX file permissies en chmod, kijk dan eens op de pagina A quick and dirty chmod Tutorial. Als je server op Windows draait, dan moet je waarschijnlijk niets veranderen.

File-permissies op files en folders kan je wijzigen met je FTP client programma (zoals bvb ftp-commander), of met de web file manager zoals er een ingebouwd is in cPanel.

Welke files/subdirectories hebben specifieke toestemmingen nodig ?

We veronderstellen voor de onderstaande uitleg dat je b2evo geiпstalleerd hebt in de subdirectory /blogs.
Ga naar de directory waar je de subdirectory blogs ziet staat.
Hieronder zie je dan wat je zou moeten veranderen, en waarom je dat zou moeten doen:

• Wil je via de browser b2evo 'up and running' krijgen, en dus de gegevens over je database en username en zo via een browservenster wil ingeven dan pas je het volgende aan : Typ in de commandoregel (voor elke ftp-programma is dat dus anders) chmod 666 /blogs/conf/_config.php.

• Als je statische pagina’s wil maken of je wil nieuwe blogs automatisch laten generen vanaf een zogenaamde stubfile, dan pas je het volgende aan : chmod 777 /blogs. En dit vanaf de directory net boven diegene waar blogs een subdirectory van is.

• Als je images wil kunnen uploaden, of andere bestanden vanuit de backoffice, dan pas je het volgende aan : chmod 777 /blogs/media

• Wil je de template-editor gebruiken om skins aan te passen dan pas je het volgden aan : chmod 666 /blogs/skins/custom/*.

This was originally written by Isaac in the forums

This is how I learned b2evolution really quickly, without much trouble at all.

1. Log in to the backoffice. (You can do this in most skins with some sort of handy "Login" or "Admin" link tucked away nicely.)

2. Go through each page in the backoffice. There are lots of fields there. Enter data in each one with a description of what field it is. For example, in editing blog A, you could enter this info:
Title: "Blog A Title"
Description: "Blog A Description"
Blogroll: "This is the blogroll for blog A."
etc.

3. Save all your changes.

4. Look at your page using a few different skins.

If you set up a test blog (perhaps running on http://localhost ) and go through all the backoffice items, and look at that test blog in a few different skins, then you'll see right away where every item comes from. You'll look at the page and see "Blog A Blogroll" and know, "Oh, yeah, so that's where that gets set up." If you check out the code for the skins (blogs/skins/skinname/_main.php is always the place to start) you'll be able to see why certain skins look different.

Also, it should be noted that b2evolution is specifically marketed as a blogging app with loads of cool "whiz-bang" features. It's not for everyone, and no one ever said that it was. And really, it works from the same general premise as blogger - you've got a backoffice where you enter data, and skins to display it. As far as I can see, besides having LOADS of additional features the only real issue is that evoSkins are a bit more complicated than blogger's templates (but not much - you just swap some proprietary <&blogger tags&> for php function calls.) Also, you've gotta read the code and play with it to tweak it just how you want it. But all the code is extremely well-commented. Open up blog_a.php, and read what it says in there.

This man page refers to b2evolution version: 0.9.0

Whenever you want to post something, just open a browser and go to /blogs/admin/ to log in and post. On many skins you will also find a link to login and/or administration.

More information about the posting screen.

You can also use a bookmarklet and/or a sidebar (IE5+/NS6+) to post. Use the "Tools" tab in the admin to access these features.

You can also post through the XML-RPC API, for example with w.bloggar.

There's also a beginner's tutorial on phpbuilder.

Dieser Eintrag bezieht sich auf b2evolution Version: 0.8.7

Wenn du einen Eintrag zu deinem Blog hinzu fügen möchtest, öffne einfach ein neues Browser-Fenster und gehe zu /blogs/admin/ um dich ein zu loggen und damit Zutritt zur Backoffice zu erhalten.

Du hast auch die Möglichkeit, ein Bookmarklet und/oder ein Sidebar (IE5+/NS6+) zu benutzen. Um auf diese Möglichkeit zu zu greifen, musst du dich einloggen und "Mein Profil" im Backoffice anklicken.

Ausserdem kannst du Einträge auch mit der Blooger API, zum Beispiel http://www.wbloggar.com, schreiben.

You should use hacks at your own risk. You know that.

However, to make it a little easier, since v 0.8.9, b2evolution will automatically load your hacks if you put them in a file called hacks.php in the conf folder.

This file does not exist in the default distribution in order to make sure you never overwrite it by accident. Moreover, since it's in the conf folder, you'll know you have to take extra care of it when you upgrade, etc.

Look in _main.php (in the directory of your choosen skin) for

<?php $Item->Content(); ?>

this gives a result like:

=>Read more

Change it to

<?php $Item->content( '#', '#', 'Read More', '' ); ?>

for a result like this:

Read more

Change it to

<?php $Item->content( '#', '#', 'Read More', 'Full Post' ); ?>

for a result like this on the first page:

Read more

and this on the permalink page:

first part of post
Full Post
the rest of the post

Or change it to

<?php $Item->content('#','#',$Item->get('title'),'','<p>Read full text of ','...</p>','htmlbody',10); ?>
 

for a result like this:

Read full text of -this is the title of the post-

More technical info if you want to dig into it, you can find on http://doc.b2evolution.net/0.9.1/evocore/Item.html#methodcontent.

This man page refers to b2evolution version: 0.9

(Have you checked the requirements?)

Installation is easy:

1. Download the software package
2. Unzip the package on your computer; this will create a folder called b2evolution and several subfolders with files.
3. Open the index.html file in the b2evolution folder and follow the instructions. This file provides quickstart instructions that will allow you to install or upgrade b2evolution in a matter of 15 minutes. You will be directed back to this online manual for more advanced installation tasks.

so... see you later ;-)

There's also a beginner's tutorial on phpbuilder, based on version 0.9.1

Diese Seite der Dokumentation bezieht sich auf b2evolution Version: 0.8.6.2

(Hast du die Systemanforderungen überprüft?)

Die Installation ist einfach:

1. Downloade das Softwarepaket
2. Entpacke (Unzip) das Paket auf deinem Computer; dies erzeugt ein Verzeichnis namens b2evolution einige Unterverzeichnisse mit Dateien.
3. Öffne die index.html Datei im b2evolution Verzeichnis und folge den Anweisungen. Diese Datei bietet dir eine Schnellstart Anleitung die dir erlaubt b2evolution in rund 15 Minuten zu installieren oder upzugraden. Du wirst dann auf diese Online Dokumentation hingewiesen, die dir eine fortgeschrittenere Installation erlaubt.

Dit is de belangrijkste Categorie, de categorie die het meest zegt over een Item?/Post?. Onder deze categorie zal de post wordt opgeslagen.

bvb. Fotografie.

Zie zeker ook: Extra Categorie

This manual page refers to b2evolution version 0.9.0.12

Lets make a few assuptions :

1. You want to show blog 2/Blog A/ the first blog after the aggragator/the blog where your posts are in if you upgraded from another tool
2. Your linkblog is in blog 4. If you don't have posts in blog 4, nothing will show
3. You want to show your articles 'the blog way', that is the last article entered is shown as first one
4. You will use skins (of course, that is the purpose of this post) and your skin is named 'MySkin'
5. You have your own page, you designed your page the way you want, with css-stylesheet or not, you made the layout with tables or divs.
6. On the place where you want your articles to appear you have a placeholder (you can easily find the place where you want your articles to appear.)

This refers to b2evolution versions 0.9.0.*

The default configuration for b2evolution is to allow comments on posts, and to allow anyone to make a comment. When you make a post you have the option to either close or disable comments, but there is no option to say "only registered members can post a comment... unless you don't mind hacking a file

NOTE: Hacks are not supported parts of b2evolution and may not work when you upgrade to newer versions. ALWAYS backup your files before you hack!

Each skin has a skinname, and each skins/skinname/ folder has a file called _feedback.php. If your skins/skinname/_feedback.php has this at the end of the file:

	/**
	 * We now call the default feedback handler...
	 * However you can replace this file with the full handler (in /blogs) and customize it!
	 */
	require get_path('skins').'/_feedback.php';
?>

then you will need to edit skins/_feedback.php instead.

Open the appropriate _feedback.php file and look for this section:

	if( $disp_comment_form ) 
	{	// We want to display the comments form: 
		if( $Item->can_comment() )
		{ // User can leave a comment
		?>
		<h4><?php echo T_('Leave a comment') ?>:</h4>

Now change it to this:

	if( $disp_comment_form && is_logged_in() ) 
	{	// We want to display the comments form to a registered member: 
		if( $Item->can_comment() )
		{ // User can leave a comment
		?>
		<h4><?php echo T_('Leave a comment') ?>:</h4>

b2evolution supports multiple blogs. The idea is that you will be blogging about a variety of different subjects that will not be of interest to the same groups of readers. Multiple blogs allow you to group subjects for specific audiences. Readers will only read the blog(s) that they are interested in.

Special cases

Blog #1: All blogs aggregation

Blog #1 has a special behaviour: it aggregates ALL categories of ALL blogs on the system.

To hide blog #1 or any other blog from the blog list, uncheck "Include in public blog list" in the Blogs tab.

Blogroll

Many bloggers have a list of blogs they read (and recommend to others) on the side of their blog page. This is often refered to as a BlogRoll. Basically it is a list of links.

b2evolution's approach to the BlogRoll is to use a dedicated blog in which each list entry is simply a blog post with mainly a title and a URL. The only differences with a normal blog is that the posts are displayed in a compact list style and that they are orderred alphabetically and/or by category instead of being displayed chronologically.

Several blog templates (for example _main.php in the "custom" skin) include a specific blog as a BlogRoll next to the main blog's posts.

You will find the code that displays the blogroll in /skins/_blogroll.php. It is actually nothing but a simplified to the max version of a regular blog template.

All the plugins are stored in subfolders of the /plugins folder.

As of version 0.9.0, there are two types of plugins: the toolbar plugins that display on the post edit screen, and the renderer plugins that act as filters when displaying pots. Each type has its own subfolder.

How to enable/disable a plugin

The easiest way to completely disable a renderer plugin is to delete the corresponding .php file from the appropriate plugins subfolder. (This does not work for toolbar plugins in version 0.9.0)

To disable a toolbar plugin, open the file /b2evocore/_class_toolbars and look for:

	function display()
	{
		$this->init();	// Init if not done yet.

		$this->index_Plugins['b2evQTag']->display();
		$this->index_Plugins['b2evSmil']->display();
	}	

Delete (or comment out) the line for the plugin you don't want. b2evQTag is for the QuickTags?. b2evSmil is for the smileys toolbar.

Plugin parameters

If you want to act with a little more control, just open the plugin .php file in a text editor and look for the following settings...

Toolbar plugins

priority

This controls the relative order in which the toolbar will be displayed. Example:

var $priority = 30;

Renderer plugins

priority

This controls the relative order in which the renderer will be applied to the post text. Example:

var $priority = 30;

apply-when

This controls when the renderer should be applied.

Possible values are:

• 'stealth' (renderer will always apply and the post authors won't even know; plugin will be invisible but active)
• 'always' (aka 'forced': renderer will always apply and the post author won't be able to uncheck it)
• 'opt-out' (renderer will be checked by default for new posts, but author can uncheck it to disable it)
• 'opt-in' (renderer will be unchecked by default for new posts, but author can check it to enable it)
• 'lazy' (renderer will only apply to old posts that require it but will not be available for new posts)
• 'never' (renderer will be invisible and inactive)

Example:

var $apply_when = 'opt-out';

You can post news from an email client!

But first you'll have to edit /conf/_advanced.php, filling the appropriate values for your POP3 email account (this interface doesn't support IMAP yet, only POP3, sorry).

Once you have edited the config options, you can make your webserver execute /htsrv/getmail.php every set amount of time (depending on your host's performance, this script can be resource intensive, so don't make it run every minute or you'll be kicked).

You can do it with Cron-jobs, or if your host doesn't support it you can look into the various website-monitoring services, and make them check your b2mail.php URL.

Preliminary advice

It is strongly advised to send your email as text-only (Outlook and Outlook Express default to 'html', which may cause problems), but HTML email could work (the script would strip all your html tags though...).

It is also advised not to use your public email address, but create a new one especially for this script. If you use your public email address and the script goes crazy posting every email on your blog and deleting all your emails, I can't take responsibility for this.

Make sure you delete any email sent to your blog in your 'Sent' folder too, just in case (you don't want someone to find your login and password in the 'Sent' folder).

The script will delete the emails that were used to post stuff on your weblog if it successfully posted your stuff. If it didn't manage to post, the email is not deleted.

How to post

Now to post something, here's how your email should look like:

To: address@domain.com (you set it in the config file)
Subject: blog:the post's title (you can change 'blog:' in the config file)
Body:
login:password (example: Jack:Starwars)
The content of the post, blah blah blah.
More blah blah. 
___

Subject must start with [blog:], or any string you set in the config file (so that the script doesn't check EVERY email in your mailbox).

Body's first line must always be login:password, else the script will just skip the email.

If you don't use [___] (or any body terminator that you set in the config file), the script will post the whole body, which is not what you want if you send email with Yahoo or Hotmail (you don't want their ads on your blog, do you?).

Special cases for mobile phone email

Some mobile phone service providers may allow you to send email with your mobile phone or PDA, but on such devices you can't always include line breaks. In such case, you have to set $use_phoneemail = 1 in /conf/_advanced.php, and then here's how you write the email:

To: address@domain.com
Subject: blog:the post's title :::
Body:
login:password ::: The content of the post, blah blah blah.___

You will have to append ':::' (or whatever string you set in the config file) after the subject, and after the login:password.

Some mobile phone service providers may not allow you to set a subject, and they'll make the subject be the first characters of the body, in which case you would send an email like this:

To: address@domain.com
Body:
blog:the post's title ::: login:password ::: The content of the post, blah blah blah.___

Originally posted by r0nh on the forums

MMS is a way to post messages to a web page by just using your MMS-enabled mobile phone. Entries diary can contain text, images and sound (such as voice recordings or a music file). Messages are posted in a bit of an unorthadox way though by (ab)using the MMS functionality in your phone. The script mms.php pretends to be an MMS Proxy-Relay.

What you need to do to use this is to set the URL to that script (on whatever host you install it) in your phone. So say for instance that you install the script in http://yourdomain.com/mms.php. Then you would insert that address as message server in your phone where you now have the operator's MMS Proxy-Relay. Of course, by doing so you cannot send "real" MMS:es anymore (till you change it back).

On my 7650 it's down in "Messaging -> Options -> Settings -> Multimedia message" and in there there are two options "preferred connection" and "secondary conn." When you choose the primary it gives you a choice of your default access points. You can either edit your provider's one or make a new one (which I did). On making a new one you can create it based on another profile. ("Options --> New Access point --> use existing settings") The setting that you need to edit is called 'home page' on the nokias. Use this new connection as your default MMS connection.

Then all you need to do when you want to make a entry is to compose a message, with images and texts and maybe sounds, with on the first line login and password and send it away and it will appear on the web page. The to-address is not necessary since it won't be transmitted to anyone of course, but most phones complain if you don't write anything there so you need to write at least something there.

Some operators have a very weird view of the mobile internet. They only want to let their users use their parts - parts that give income to the operator. Operator's worst fear is to become a stupid bit-pipe and therefore some have choosen the path to restrict access to the Internet.
So they don't let you run your own MMC and you have to use the one they have provided you with, where you have to pay for whatever they decide an MMS costs.

This refers to b2evolution versions 0.9.0.*

Sometimes you see a skin you like but it has things in the sidebar you don't want. Sometimes you want "just the blog" so you wish the whole sidebar would just go away. Either way, it's very easy to do.

How to remove just one piece of the sidebar?

For the purpose of this article I will pretend that I want to use the 'custom' skin but do not want to have the calendar. No problem! Open up skins/custom/_main.php in your favorite editor and look for the sidebar section. The code is commented nicely - you will see a line that says

<!-- START OF SIDEBAR -->

(Actually it has a lot of equals signs on either side of the text that I had to remove here due to how the renderers the manual uses work.) Since the calendar is near the top of the sidebar the code for it will also be near the top. Looking at the beginning of the sidebar area you will find this:

	<div class="bSideItem">
		<h3><?php $Blog->disp( 'name', 'htmlbody' ) ?></h3>
		<p><?php $Blog->disp( 'longdesc', 'htmlbody' ); ?></p>
		<p class="center"><strong><?php posts_nav_link( ' | ', '< '.T_('Previous'), T_('Next').' >' ); ?></strong></p>
		<!--?php next_post(); // activate this if you want a link to the next post in single page mode ?-->
		<!--?php previous_post(); // activate this if you want a link to the previous post in single page mode ?-->
		<ul>
			<li><a href="<?php $Blog->disp( 'staticurl', 'raw' ) ?>"><strong><?php echo T_('Recently') ?></strong></a> <span class="dimmed"><?php echo T_('(cached)') ?></span></li>
			<li><a href="<?php $Blog->disp( 'dynurl', 'raw' ) ?>"><strong><?php echo T_('Recently') ?></strong></a> <span class="dimmed"><?php echo T_('(no cache)') ?></span></li>
		</ul>
		<?php // -------------------------- CALENDAR INCLUDED HERE -----------------------------
			require( dirname(_FILE_).'/_calendar.php' );
			// -------------------------------- END OF CALENDAR ---------------------------------- ?>
		<ul>
			<li><a href="<?php $Blog->disp( 'lastcommentsurl', 'raw' ) ?>"><strong><?php echo T_('Last comments') ?></strong></a></li>
			<li><a href="<?php $Blog->disp( 'blogstatsurl', 'raw' ) ?>"><strong><?php echo T_('Some viewing statistics') ?></strong></a></li>
		</ul>
	</div>
 

The calendar is in the middle of this particular "bSideItem" div:

		<?php // -------------------------- CALENDAR INCLUDED HERE -----------------------------
			require( dirname(_FILE_).'/_calendar.php' );
			// -------------------------------- END OF CALENDAR ---------------------------------- ?>
 

Delete those three lines and you won't have the calendar anymore. By the way if you're not into php yet here's a little helpful hint: all php statements start with <?php and end with ?>

How to remove the ENTIRE sidebar?

No problem! As you look through the rest of your _main.php file you will see where the sidebar is composed of several different "bSideItem" divs. Delete each of these (including the appropriate /div tag) until you are left with something like this:

<!-- START OF SIDEBAR -->

<div class="bSideBar">

	<?php // -------------------------- LINKBLOG INCLUDED HERE -----------------------------
		require( dirname(_FILE_).'/_linkblog.php' );
		// -------------------------------- END OF LINKBLOG ---------------------------------- ?>

<p class="center">powered by<br />
<a href="http://b2evolution.net/" title="b2evolution home"><img src="../../img/b2evolution_logo_80.gif" alt="b2evolution" width="80" height="17" border="0" class="middle" /></a></p>

</div>
<div id="pageFooter">
	<p class="baseline">
 

Here you still have a sidebar with the linkblog and the "powered by" credit badge. I left them in because 'technically' they are not inside a bSideItem div. The next step is to remove the bSideBar div, it's /div tag, the linkblog, and move the credit badge to the footer.

<!-- START OF SIDEBAR -->
<!-- NO MORE SIDEBAR! -->
<div id="pageFooter">

<p class="baseline">powered by 
<a href="http://b2evolution.net/" title="b2evolution home"><img src="../../img/b2evolution_logo_80.gif" alt="b2evolution" width="80" height="17" border="0" class="middle" /></a></p>

	<p class="baseline">
 

You can remove the two commented lines for "start of sidebar" and "no more sidebar" - I left them here just to illustrate.

Unfortunately your blog will still have space for a sidebar, so now you have to edit your style sheet. Again, working with the 'custom' skin, I will edit skins/skinname/custom.css to let the blog take the full screen. The custom skin uses an image for the background to get the vertical line in place, so you will have to make that go away.

div#wrapper {
	background: #fff url(img/bg_content.gif) repeat-y 0 0;
	width: 740px;
	margin: 0 auto;
	padding: 0;
}

becomes

div#wrapper {
	background: #fff;
	width: 740px;
	margin: 0 auto;
	padding: 0;
}

Finally, tell the bPosts div it's okay to take up as much room as it can.

/* Styles for posts */
.bPosts {
	float: left;
	width: 480px;
	overflow: hidden;
	/* background: #090;*/
}

becomes

/* Styles for posts */
.bPosts {
	float: left;
	/* background: #090;*/
}

That's it - no more sidebar, and no more empty space where the sidebar used to be. The actual work you will need to do depends entirely on your skin. Not all skins use "bSideItem", and some skins have the code for the sidebar before the code for the posts. The same is true for your style sheet: your work will depend entirely on the skin you are editing. Back up frequently, and make small steps towards your goal.

Q: I can log in but b2evolution asks me for my password again and again / my cookies don't hold.

A: In the file /conf/_config.php you have set an URL with a statement like this:

$baseurl = 'http://www.mysite.com';

Cookies will be set only for this URL and "its subfolders". So the trick is: use that URL to access b2evolution, not another one!

In the above, example it means that if your website address is 172.192.45.104 for example, you cannot log in on http://172.192.45.104/admin/, you must use http://www.mysite.com/admin/ !

For local tests, use

$baseurl = 'http://localhost';

If it wasn't working, and then you found and corrected the problem according to what you see here, but it still doesn't work, then in some cases you may have to clear out your cache/cookies/temporary internet files before it starts working.

Q: I am trying to upload files / generate static pages / creating new blogs but I get file permission denied errors.

A: Please make sure you have finished your installation. In particular, have you gone through the TrickyStuff ?

Q: How do I customize my blog pages ?

A: Please read the manual about SkinsAndTemplates?. If you need further assistance, ask in the forums, but please tell us what wasn't clear from the manual so we can improve it

Q: I need further assistance...

A: Please ask in the forums.

[De]

To run b2evolution, you will need a webserver that can run PHP4, and a MySQL database (you can install b2evolution in an already existing database, and you can put several b2evolution's in one database).

Technical requirements

• PHP version 4.1 or above download here (PHP 5 fully supported from version 1.6 "Phoenix")
• mySQL version 3.23 or above download here (MySQL 4.x and InnoDB? fully supported from version 1.6 "Phoenix")

Optional

• Works best with an Apache webserver.
• XML-RPC related functions and XHTML validation require the PHP XML module.

Hosting

Please note some hosting providers act like paranoïd when hosting PHP applications. As a matter of fact, they degrade PHP itself, removing essential features surch as file access, sockets (for connection to external sites), uploading files, sending emails or other features.

Some features of b2evolution may not work on such hosts. b2evolution may even not be able to run at all.

If your hosting provider is a paranoпd, we suggest you switch to another one. (Or you'll probably have to use software with less functionnality than b2evo). Check the list of TestedHosts.

Browsers

The back-office uses CSS (style sheets) to display. Older and experimental browsers that do not handle CSS correctly will have display problems.

b2evolution is tested with these browsers:

• Firefox 1.0
• Internet Explorer 6.0

browsers that are known to have display issues:

• Safari
• Mozilla 1.2
• Netscape 4

Most of the time these issues can be solved by hacking the CSS file. If you come up with such solutions, please contribute them to the project.

Portability

• b2evolution uses a DB abstraction class which will make it easier to port to another DBMS.
• SQL requests are as close to ANSI SQL 92 as possible.
• More info on DB abstraction and portability.

Um b2evolution benutzen zu können, brauchst du einfach nur einen Webserver, auf dem PHP4-Skripte ausgeführt werden können. Außerdem eine MySQL-Datenbank.

b2evolution kann auch in eine schon existierende Datenbank installiert werden. Ebenso wäre es möglich b2evolution mehrfach in eine einzige Datenbank zu installieren - auch wenn dies nicht sehr sinnvoll ist.

Technische Anforderungen

• PHP Version 4.1 oder höher (Download)
• mySQL version 3.23 oder höher (Download)

Optional

• b2evolution läuft am besten auf einem Apache Webserver.
• XML-RPCbezogene Funktionen und die XHTML Validation benötigen das PHP XML Modul.

This is a list of functions you can use in templates. They are sorted by purpose.

Note: There is also an obsolete manual page that may still have some interesting info.

For more information about how to use these functions, see TemplateFunctionsExplained .

Blogs

• **$Blog->dget()** : get a blog property without displaying it (advanced function)
• **$Blog->disp()** : display a blog property (semi advanced function)
• **$Blog->ID()** : display ID of blog
• bloginfo() : deprecated by $Blog->disp()

Comments

• **$Comment->anchor()** : display anchor for permalinks to refer to
• **$Comment->author()** : display author of comment
• **$Comment->author_email()** : display link to comment author's provided email
• **$Comment->author_ip()** : display comment's author's IP
• **$Comment->author_url()** : display link to comment author's provided URL
• $Comment->author_User->...() : display data about the post author, see Users below. WARNING: can be NULL if this is not a member comment.
• **$Comment->content()** : display content of comment
• **$CommentList->display_if_empty()** : display message if no comment available
• **$Comment->date()** : display date (datetime) of comment
• **$Comment->dget()** : get a comment property without displaying it (advanced function)
• **$Comment->disp()** : display a comment property (semi advanced function)
• **$Comment->edit_link()** : display link to edit the comment if user has edit rights
• **$Comment->ID()** : display ID of comment
• **$Comment->permalink()** : display permalink to comment
• **$Comment->msgform_link()** : display link to message the comment's author (added in version 'phoenix')
• $Comment->Item->...() : display data about comment's original post, see Items
• **$Comment->time()** : display time (datetime) of comment
• comment_author() : deprecated by $Comment->author()
• comment_author_email() : deprecated by $Comment->author_email()
• comment_author_email_link() : deprecated by $Comment->author_email()
• comment_author_IP() : deprecated by $Comment->author_ip()
• comment_author_url() : deprecated by $Comment->author_url()
• comment_author_url_basedomain() : deprecated
• comment_author_url_link() : deprecated by $Comment->author_url()
• comment_blog_name() : deprecated
• comment_date() : deprecated by $Comment->date()
• comment_ID() : deprecated by $Comment->ID()
• comment_post_link() : deprecated by $Comment->post_link()
• comment_post_title() : deprecated by $Comment->post_title()
• comment_text() : deprecated by $Comment->content()
• comment_time() : deprecated by $Comment->time()

internationalization (i18n)

• locale_charset() : Returns the charset of the current locale
• locale_datefmt() : Returns the current locale's default date format (advanced function)
• locale_flag() : Displays a flag for the current locale
• locale_lang() : Displays/Returns the current locale
• locale_temp_switch() : Temporarily switch to another locale
• locale_timefmt() : Returns the current locale's default timeformat (advanced function)
• locale_restore_previous() : Restore the locale in use before locale_temp_switch()
• T_() : Returns argument translated to current locale, if translation exists. (advanced function)

Items

• $Item->anchor() : display anchor for permalinks to refer to
• $Item->Author->...() : display data about the post author, see Users
• $Item->can_comment() : Check if user can leave comment on this post or display error
• $Item->categories() : list all the category names for this item
• $Item->content() : display content (text) of item
• $ItemList->date_if_changed() : display the date if it has changed since last call
• $ItemList->display_if_empty() : display message if no post is available for display
• $Item->disp() : display an item parameter (semi advanced function)
• $Item->edit_link() : display link to edit the post if user has edit rights
• **$Item->feedback_link()** : Displays link to feedback page (under some conditions)
• **$Item->msgform_link()** : display link to message the post's author (added in version 'phoenix')
• $Item->gen_permalink() : generate permalink for item (advanced function)
• $Item->get() : get an item parameter without displaying it (advanced function)
• $Item->ID() : display ID of item
• $Item->issue_date() : display issue date (datetime) of item
• $Item->issue_time() : display issue time (datetime) of item
• $Item->lang() : display language code for the item
• $Item->language() : display language name for the item
• $Item->locale() : display locale for the item
• $Item->main_category() : display main category name for item
• $Item->mod_date() : display last mod date (datetime) of item
• $ItemList->mod_date() : display last mod date (datetime) of item list
• $Item->mod_time() : display last mod time (datetime) of item
• $Item->permalink() : display permalink for item
• $Item->status() : display status ('published', 'draft', 'protected'...) of item
• $Item->title() : display title of item
• $Item->trackback_rdf() : displays trackback autodiscovery information for item
• $Item->trackback_url() : displays url to use to trackback this item
• $Item->url_link() : display link to item related url
• **$Item->views()** : Display the number of times the Item has been viewed (Added in version 'phoenix')
• $Item->wordcount() : display the number of words in the post
• comments_link() : deprecated deprecated by Item->feedback_link()
• comments_number() : deprecated deprecated by Item->feedback_link()
• gen_permalink() : deprecated by $Item->gen_permalink()
• permalink_anchor() : deprecated by $Item->anchor()
• permalink_link() : deprecated by $Item->permalink()
• permalink_single() : deprecated by $Item->permalink()
• pingback_link() : deprecated deprecated by Item->feedback_link()
• pingback_number() : deprecated deprecated by Item->feedback_link()
• the_author() : deprecated by $Item->Author->prefered_name()
• the_author_url() : deprecated by $Item->Author->url()
• the_categories() : deprecated by $Item->categories()
• the_category() : deprecated by $Item->main_category()
• the_content() : deprecated by $Item->content()
• the_date() : deprecated by $""ItemList""->date_if_changed()
• the_lang() : deprecated by $Item->lang()
• the_link(): deprecated by $Item->url_link()
• the_time() : deprecated by $Item->time() / $Item->date()
• the_title() : deprecated by $Item->title()
• the_wordcount() : deprecated by $Item->wordcount()
• trackback_link() : deprecated deprecated by Item->feedback_link()
• trackback_number() : deprecated deprecated by Item->feedback_link()
• trackback_rdf() : deprecated by $Item->trackback_rdf()
• trackback_url() : deprecated by $Item->trackback_url()

Page

General

• imgbase() : output base URL to b2evo's image folder
• skinbase() : output base URL to current skin

Title

• arcdir_title() : deprecated by request_title()
• last_comments_title() : deprecated by request_title()
• msgform_title() : deprecated by request_title()
• profile_title() : deprecated by request_title()
• request_title() : Display a global title matching url params
• single_cat_title() : deprecated by request_title()
• single_month_title() : deprecated by request_title()
• single_post_title() : deprecated by request_title()
• stats_title() : deprecated by request_title()

Header

• comments_popup_script() : include the javascript that is required to open comments, trackback and pingback in popup windows.

Footer

• debug_info() : output debug info for this page, if requested
• log_hit() : log the hit on this page

Posts

Posts are Items. See Items.

Users

Authors

• $User->ID() : display ID of user
• $User->disp() : display a user parameter (semi advanced function)
• $User->get() : get a user parameter without displaying it (advanced function)
• $User->level() : display user's level
• $User->login() : display user's login
• **$User->msgform_link()** : display link to message the user (added in version 'phoenix')
• $User->prefered_name() : display user's preferred name
• $User->url() : display user's url

Current user

• user_login_link()
• user_register_link()
• user_admin_link()
• user_profile_link()
• user_logout_link()

<?php the_time() ?>

...which will display the time of the current post, using the default time format.

However, many of these functions can accept optional parameters bewteen the brackets (). For example you could write:

<?php the_time( '%Y-%m-%d %H:%M:%S', 'Posted:' ) ?>

...which would display a full date + time for the current post, preceded by the text 'Posted:'.

How do I know which optional parameters I can use?

The best way for you to learn about available optional parameters, is to look at the the template functions list and follow the link to the technical documentation for any specific function.

Notes about parameters

To add a parameter to a function, simply include it between the brackets (). If it is text (instead of a number), add quotes around the parameter. Examples:

<?php my_tag( 'my text parameter' ); ?>
<?php my_tag( 123 ); ?>

You may have to specify several parameters... In this case, you must separate them with commas, like this:

<?php my_tag( 'first param', 'second param' ); ?>

The order of parameters is important! You must follow the exact order of the parameters as indicated in the technical documentation.

If a function accepts 3 parameters and you only want to set the third one, you still have to provide the first two parameters. In this case, you could simply use the default values for these parameters, as specified in the technical documentation.

<?php my_tag( '', '#', 'second param' ); ?>

Please note: the default value for optional parameters is often '' or '#'.

Some template functions, like the_date(), display something only if in some conditions. They generally accept parameters to display something before and after the output, only when they display something.

<?php the_title( '<h1>', '</h1>' ); ?>

would display <h1>title of the post</h1> only if the post has a title

This explains how to make an evoSkin out of a regular blog template. Of course, you could also start from scratch by editing the custom skin.

The idea is to customize the custom skin by using your previous b2 template.

Here's how to proceed:

1. Go the the /b2evolution/blogs/skins/custom directory

2. Rename _main.php to _bak_main.php (you want to keep this handy for future reference).

3. Copy your previous template (index.php, b2.php, myblog.php or whatever) and rename it to _main.php.

Pay attention: you must copy the file, not move it! We will actually split the contents of your blog template into two files!

4. The original file (the one in /blogs) is to become a simple stub, setting a few parameteres and then letting b2evolution call the desired skin.

Delete the template code from this file in order to just keep the beginning of the file like this:

<?php
/*
* This file is a stub for displaying a blog, using evoSkins.
* This file will fix some display parameters and then let b2evolution handle
* the display by calling an evoSkin. (skins are in the /skins folder.)
*/

# First, select which blog you want to display here!
# You can find thess numbers in the back-office under the Blogs section.
# You can also create new blogs over there. If you do, duplicate this file for the new blog.
$blog = 2; // 2 is for "demo blog A" or your upgraded blog (depends on your install)

# Now, select the default skin you want to display for this blog.
# This setting refers to a subfolder name in the '/skins' folder
$default_skin = 'custom';
# You can *force* a skin with this setting:
# $skin = 'custom';

# This setting retricts posts to those published, thus hiding drafts.
# You should not have to change this.
$show_statuses = "'published'";

# This is the blog to be used as a blogroll (set to 0 if you don't want to use this feature)
$blogroll_blog = 4;

# This is the list of categories to restrict the blogroll to (cats will be displayed recursively)
# Example: $blogroll_cat = '4,6,7';
$blogroll_cat = '';

# This is the array if categories to restrict the blogroll to (non recursive)
# Example: $blogroll_catsel = array( 4, 6, 7 );
$blogroll_catsel = array( );

# Here you can set a limit before which posts will be ignored
# You can use a unix timestamp value or 'now' which will hide all posts in the past
$timestamp_min = '';

# Here you can set a limit after which posts will be ignored
# You can use a unix timestamp value or 'now' which will hide all posts in the future
$timestamp_max = 'now';

# Additionnaly, you can set other values (see URL params in the manual)...
# $order = 'ASC'; // This for example would display the blog in chronological order...

# That's it, now let b2evolution do the rest! :)
include(dirname(__FILE__)."/b2evocore/_blog_main.php");
?> 

• *Attention please:** You need to remove your current $skin=''; and set the default skin to custom.

5. The new file (_main.php in the custom skin folder), on the other hand, is to become a template usable by all blogs. So you need to delete the parametering from the top of this file.

Your _main.php should actually start directly like a regular HTML/XHTML page:

<!DOCTYPE html PUBLIC "-W3CDTD XHTML 1.0 TransitionalEN" "http:">www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="fr" lang="fr">
<head>
<base href="<?php skinbase(); // Base URL for this skin. You need this to fix relative links! ?>" />
<title>... 

6. Make sure you have a <base> tag in your <head> section; right after the <head> tag is best. See above.

7. You may also want to add more features to your main template.

This page is about upgrading from version 0.9.0.x to 0.9.1

The latest documentation for upgrading is included in your blog bundle, in the doc directory, for example doc/upgradefrom_b2evo.en-UK.html. The following documentation refers to that included with version 0.9.1, with some minor changes.

Upgrading from a previous version of b2evolution

Before you begin, please note that some network features of b2evolution require you to agree our simple Terms of service. Also note that there will be some minor downtime to your blog by following these instructions.

1. Backup all your b2evolution files. The easiest way to do this is to rename the b2evolution directory on your server. However you do it, take special care of the files you may have modified, including /conf, skins, blog templates, stubfiles, etc...
2. You should also backup your database if you can. This functionality should be provided by your host.
3. Delete all your existing b2evolution files from your site before uploading the new ones! This will ensure you don't keep unnecessary files on your server after upgrading. It's also better for security.

4. Upload all new b2evolution files from the /blogs folder to your site. We cannot stress this enough: ALL FILES! And that means you can't reuse your customized files, including /conf, skins, blog templates, stubfiles, etc. as they are!
   

   
   
   That means you will have to customize all these files again. We're sorry but, due to the pace of development and adding of new features, we cannot guarantee that anything will work if you keep older files in place. However, since you have backed up all these files in step 1, you can try to partially reuse them once the upgrade process is done. See step 8 below.

5. Run the installation script on your server. It is located in http://yoursite.com/yourblogsfolder/install . Then, simply follow the on screen instructions.
   
   
   The installer will ask you basic configuration settings (unless you have already updated /conf/_config.php before uploading), then allow you to run a database upgrade from any b2evolution version to the new one.
6. Check to make sure the new installation works.
7. On production servers, it is recommended that you delete the /install subfolder. This prevents others overwriting your settings.
8. It's now time to bring back your previous customizations.
   We recommend you get yourself a diff/merge tool like WinMerge. This will allow you to easily compare your old (backuped) files with the new files (even whole directories at once) and report changes accordingly.
   
   
   You can also check the manual or the forums for notes on upgrading specific files from a specific version to another.
9. After basic install is done, there are a few tricky things you may need to take care of (online manual).