This Disp displays a form where the current User can change his password. This Disp also has an equivalent in the Back-Office; see: Password Tab. This, of course, only applies as long as the particular skin you are using doesn’t completely… more »

Moving b2evolution to a different folder on you server is extremely easy. Suppose you were on http://mydomain.com/b2evolution/ and you now want to be on http://mydomain.com/blog/ or even http://mydomain.com/. All you need to do is move your files on the… more »

Grunt is a very powerful command line tool for processing files on your development machine. For example, it can compile a .less file into .css, then concatenate several .css files into a .bundle.css file, then minify (compress) that bundle into a… more »

If you have a Multi Domain Setup, at some point you might want to log-in on several of your domains at once. First you have to remember that if you log in on www.microsoft.com, the cookie that remembers your session there will never be sent to… more »

Short answer: your $baseurl is not configured properly. (Or you are not using the same URL to connect.) more »

Set up your webserver If you are using [http://b2evolution.net/web-hosting/top-quality-best-webhosting.php shared hosting], check that your hosting plan allows multiple domains and set those up as "Domain Aliases". If your are using a [http:… more »

This man page refers to b2evolution "phoenix" First, when testing a single domain, you should always use localhost and not the IP address of your machine, nor the windows name of your machine. Trust our experience that cookies may act weird on the IP… more »

This Disp is used to display an interface where the current User can change his preferences(s). The settings that the user is allowed to change are controlled through User Settings > Profiles. This, of course, only applies as long as the particular skin… more »

This Disp is used to display a form where the current User can edit the basics of his user profile. The settings that the user is allowed to change are controlled through User Settings > Profiles and User fields. This, of course, only applies as long… more »

This Disp is used to display a form asking the User to confirm he wants to close his account and leave a little bit of feedback. NOTES: The Admin cannot close his account. Regular Users can only close their account if this feature is enabled here:… more »

A list of files and directories to be ignored from backup on automatic upgrade. List on file or directory per line. Here is an example of file contents you could use: more »

This page is intended for integrators / developers, not for regular users. b2evolution supports fully automated installation and fully automated upgrade by calling the regular /install/index.php script with special parameters, either via CURL or via PHP… more »

If you are already logged in to b2evolution in a web browser, you will have a session cookie and you can use this cookie to obtain privileges when calling the REST API. This is particularly useful when you use the REST API in a browser, for example in a… more »

Future versions of b2evolution will include customization through the Back-Office. In version 6.6 you need to manually duplicate and edit some files. The files responsible for displaying the header and the footer can be found in the /skins_site… more »

Very often we want to have several widgets/sections in the footer of our website. By default, if we insert several widgets in the footer container (or any other), they would be placed one below the other, which is usually not what we want. In most… more »

If you feel b2evolution detects spam or security issues too often in what you posts to your own site and you don’t want to hear about it any more, you can disable all the SPAM and Security checks on the Administrators account. See: Blogging… more »

When you develop a new skin, you should check that it matches a set of standards so that it will work effectively in a variety of situations, for a variety of users and so that it is as much future poof as possible (best compatibility with future… more »

This man page refers to b2evolution version 1.6 The easiest way is this: Make a copy of the file _test.plugin.php Rename the new file to _newname.plugin.php (choose whatever newname you want) Open the _newname.plugin.php file. Renam… more »

In order to test LDAP functionality you may use the LDAP Directory Server from the Apache Directory Project. Note: the Apache Directory Server currently doesn’t install properly on Mac OS X El Capitan. Installing the Server You may download the… more »

This is the internal ID of any Item/Post/Page?/Topic in your b2evolution Database. You can find it by editing a post and looking at the top left of your edit form: more »

To be able to moderate content a User must be given Advanced Permissions like this: he must be allowed to edit Posts or Comments other than his own he must also be allowed to create Posts or Comments on at least two different Visibility Statuses from… more »

This Disp is deprecated. It was used in early versions to display the comments for a post in a popup window. more »

The Scheduler is a b2evolution feature that allows to execute Scheduled Jobs without requesting an action from a user to trigger the execution. In other words, Scheduled Jobs are executed asynchronously, at predefined times and/or intervals. See also:… more »

A ScheduledTask that is planned to be executed or which has been executed by the Scheduler. See: Scheduled Task Reference more »

A task (See: Scheduled Task Reference) that can be planned to execute by the scheduler. A planned task is called a Scheduled Job. more »

/conf/sample.htaccess should be renamed to /conf/.htaccess to protect the contents of the /conf folder from prying eyes. This files is NOT to be confused with the Main .htaccess file which has a much more important role. more »

/conf/_upgrade.php is used by the upgrade script only. more »

/conf/_formatting.php sets how b2evolution will parse and format texts (posts, comments, etc.) You typically won’t need to edit this file and you should replace it with each upgrade. more »

/conf/_application.php configure the b2evolution application. You typically shouldn’t edit this file and replace it with the new version at each upgrade. This file especially contains the version number and date used to compare versions during… more »

/conf/_config.php is the "main" configuration file which is called by b2evolution to, in turn, include all the other config files it needs. It also includes some high level initializations. You typically should never edit this file and replace… more »