Dotclear Documentation 2.0:admin

2.0:admin:1-to-2

Wed, 16 Oct 2013 09:55:25 +0200

1220625038		current
Line 13:		Line 13:

	Now that all your entries are imported to your new blog, you still need to import your previous media.		Now that all your entries are imported to your new blog, you still need to import your previous media.
-	Copy your Dotclear 1 media directory (named **img by default) to the root of your webspace, alongside your Dotclear 2 installation. Now, in the sidebar of your administration interface, click on the __about:config__ link and set the public_path and public_url** parameters to the location and URL of your media directory. If Dotclear 2 and your media directory are on the same level, set the parameters as follows :	+	Copy your Dotclear 1 media directory (named **images by default) to the root of your webspace, alongside your Dotclear 2 installation. Now, in the sidebar of your administration interface, click on the __about:config__ link and set the public_path and public_url** parameters to the location and URL of your media directory. If Dotclear 2 and your media directory are on the same level, set the parameters as follows :
-	* public_path : ''../img''	+	* public_path : ''../images''
-	* public_url : ''/img''	+	* public_url : ''/images''
	Change these settings accordingly if you choose to place your media folder somewhere else.		Change these settings accordingly if you choose to place your media folder somewhere else.

2.0:admin:aboutconfig

Thu, 30 Nov 2017 18:31:24 +0200

1512062532		current
Line 87:		Line 87:

	=== use_smilies ===		=== use_smilies ===
-	Enables or disables graphic smilies in entries and comments. The matches between texts and smilies can be found in the file ''dotclear/themes/default/smilies/smilies.txt'' .	+	Enables or disables graphic smilies (smileys) in entries and comments. The matches between texts and smilies can be found in the file ''dotclear/themes/default/smilies/smilies.txt'' .

	=== wiki_comments ===		=== wiki_comments ===
	Allows or prevents using wiki syntax in the comments.		Allows or prevents using wiki syntax in the comments.

2.0:admin:antispam

Wed, 16 Oct 2013 09:55:25 +0200

1216505308		current
Line 32:		Line 32:
	These are links to RSS feeds that let you track spam comments and published comments.		These are links to RSS feeds that let you track spam comments and published comments.

-	===== Configuration des filtres =====	+	===== Filter configuration =====

	Some filters have their own configuration interface accessible via a link {{2.0:controls:bt_edit.png\|}} located on their lines in the filter list.		Some filters have their own configuration interface accessible via a link {{2.0:controls:bt_edit.png\|}} located on their lines in the filter list.

2.0:admin:backup

Wed, 16 Oct 2013 09:55:24 +0200

1308969003		current
Line 54:		Line 54:

	===== Database =====		===== Database =====
-
	==== Backup ====		==== Backup ====

Line 61:		Line 60:
	Several backup options are available depending on the database type you are using.		Several backup options are available depending on the database type you are using.

-	The easiest cas is that of SQLite, where you already have a file containing all of your data in the directory you chose when you installed it.	+	The easiest case is that of SQLite, where you already have a file containing all your data in the directory you specified when you installed.

-	However, this file may become corrupted, therefore it may be useful to export your data regularly.	+	However, this file might become corrupted, therefore it may be useful to export your data regularly.

-	Exporting the data contained in an SQLite file is very straightforward. On a Unix server, in the command prompt type:	+	Exporting the data contained in an SQLite file is very straightforward. On a Unix server, at the command prompt, type:

	<code>		<code>
Line 71:		Line 70:
	</code>		</code>

-	If you are using a MySQL database, you will need to backup your data regularly. If your blog is hosted on a shared server, you will have to use a specific tool such as phpMyAdmin which includes an export tool.	+	If you are using a MySQL database, you will need to backup your data regularly. If your blog is hosted on a shared server, you will need to use a specific tool such as phpMyAdmin, which includes an export tool.

-	If you're lucky and have access to your web server through SSH (or even physically), you can backup your database using the terminal as follows (remember to specify the user and password options):	+	If you're lucky and have access to your web server through SSH (or even physically), you can backup your database using the command line as follows (remember to specify the user and password options):

	<code>		<code>
Line 85:		Line 84:
	pgdump -U db_user database_name > backup.slq		pgdump -U db_user database_name > backup.slq
	</code>		</code>
		+
	==== Restoring ====		==== Restoring ====

2.0:admin:config

Wed, 16 Oct 2013 09:55:24 +0200

1227853882		current
Line 62:		Line 62:
	define('DC_ADMIN_URL','http://mysite/dotclear/admin/');		define('DC_ADMIN_URL','http://mysite/dotclear/admin/');
	</code>		</code>
		+
		+	=== DC_ADMIN_MAILFROM ===
		+
		+	Email address to use as sender of password recovery mails.

	=== DC_SESSION_NAME ===		=== DC_SESSION_NAME ===

2.0:admin:install

Tue, 16 Apr 2024 07:16:58 +0200

1678280332		current
Line 8:		Line 8:
	Before installing Dotclear 2, you should check that your web space features the following technical capabilities:		Before installing Dotclear 2, you should check that your web space features the following technical capabilities:

-	* PHP 7.4 or above, with support for the following extensions:	+	* PHP 8.1 or above, with support for the following extensions:
	* mbstring		* mbstring
	* iconv		* iconv
Line 15:		Line 15:
	* simplexml and domxml		* simplexml and domxml
	* SPL		* SPL
		+	* GMP or BC MATH ( for ipv6 antispam filters)
	* One of the following supported databases:		* One of the following supported databases:
	* PostgreSQL 8.0 minimum		* PostgreSQL 8.0 minimum

2.0:admin:local-install

Wed, 08 Jun 2016 06:17:37 +0200

1465359367		current
Line 96:		Line 96:

	<note>		<note>
-	The root directory of the Apache server that's embedded in MAMP is named htdocs and located in the MAMP directory. This location may be changed via MAMP preferences.	+	The root directory for the Apache server embedded in MAMP is named htdocs and located in the MAMP directory. This location may be changed via MAMP preferences.
	</note>		</note>

Line 105:		Line 105:
	</note>		</note>

-	Once you have installed the servers, you need to create a UTF-8 encoded database. The MAMP package include phpMyAdmin, used to manage the MySQL databases. If you wish to use PostgreSQL, you can download and install [[http://kent.dl.sourceforge.net/sourceforge/phppgadmin/phpPgAdmin-4.1-Beta-1.tar.gz\|phpPgAdmin]] .	+	Once you have installed the servers, you need to create a UTF-8 encoded database. The MAMP package include phpMyAdmin to manage MySQL databases. If you wish to use PostgreSQL, you can download and install [[http://kent.dl.sourceforge.net/sourceforge/phppgadmin/phpPgAdmin-4.1-Beta-1.tar.gz\|phpPgAdmin]] .

	Below are the parameters required to configure phpPGAdmin:		Below are the parameters required to configure phpPGAdmin:
Line 115:		Line 115:
	* pg_dumpall_path : /Library/PostgreSQL8/bin/pg_dumpall		* pg_dumpall_path : /Library/PostgreSQL8/bin/pg_dumpall

-	You should then download and install Dotclear 2 in the root directory of the server (htdocs directory) or in another directory you'll have created for this purpose. Below are the parameters required for the configuration:	+	You should then download and install Dotclear 2 in the root directory of the server (htdocs) or in another directory you created for this purpose. Below are the parameters required for the configuration:

	* MySQL database		* MySQL database

2.0:admin:multiblog

Tue, 05 Jul 2016 04:45:55 +0200

1466456838		current
Line 7:		Line 7:
	FIXME draft		FIXME draft

-	===== Method 1 : one directory per blog =====	+	===== Method 1: one directory per blog =====

	Objective : two blogs on a single installation :		Objective : two blogs on a single installation :
Line 117:		Line 117:

	----		----
-	===== Method 2: one virtual host per blog; all admin via SSL =====

-	FIXME This no longer works in httpd 2.4 as of June 2016. See Method 3 below.	+	===== Method 2: virtual hosts with index.php symlink =====
		+
		+	Step 1: Install Dotclear normally, and make sure it works (both visiting default site and logged-in site admin).
		+
		+	Step 2: Create a virtual host configuration file for each site (''/etc/httpd/conf.d/SITE1.conf'', ''/etc/httpd/conf.d/SITE2.conf'', etc.). Make sure the ''DocumentRoot'' exists and is accessible (although you might get an error because there's no content yet). Customize each virtual host ''.conf'' file with its own ''DC_BLOG_ID'', as in ''SetEnv DC_BLOG_ID SITE1''.
		+
		+	Step 3: In each ''DocumentRoot'' directory, make ''index.php'' a symbolic link back to the master ''index.php'' in the main Dotclear site.
		+
		+	Step 4: For each virtual host, rewrite all URLs to Dotclear. The details depend on the blog's "URL scan method" and where you put the rules -- see the <a href="http://httpd.apache.org/docs/2.4/mod/mod_rewrite.html#rewriterule">mod_rewrite</a> docs for details. ''QUERY_STRING'' is more efficient, because it avoids multiple failed queries before the correct path is requested and served (see <https://forum.dotclear.org/viewtopic.php?pid=315825#p315825> for details).
		+
		+	Step 4a: If using ''QUERY_STRING'', put a redirect block like this into each blog's virtualhost ''.conf'' file:
		+
		+	RewriteEngine On
		+	RewriteCond %{REQUEST_FILENAME} !-f
		+	RewriteCond %{REQUEST_FILENAME} !-d
		+	*RewriteRule ^/(.)$ /index.php?$1**
		+
		+	Step 4b: If using ''PATH_INFO'' you can put something like this in each blog's virtualhost ''.conf'' file:
		+
		+	RewriteEngine On
		+	RewriteCond %{REQUEST_FILENAME} !-f
		+	RewriteCond %{REQUEST_FILENAME} !-d
		+	*RewriteRule (.) /index.php/$1**
		+	RewriteRule ^/index.php$ /index.php/
		+
		+	----
		+
		+	===== Method 3: one virtual host per blog; all admin via SSL =====
		+
		+	FIXME This no longer worked for me in httpd 2.4 as of June 2016.

	Objective: A single secure installation of Dotclear, using SSL to protect all authentication, and multiple blogs -- each with its own domain name, but sharing the same user account database:		Objective: A single secure installation of Dotclear, using SSL to protect all authentication, and multiple blogs -- each with its own domain name, but sharing the same user account database:
Line 272:		Line 300:
	</code>		</code>

-	----
-
-	===== Method 3: VHosts with index.php symlink =====
-
-	Step 1: Install Dotclear normally, and make sure it works (both visiting default site and logged-in site admin).
-
-	Step 2: Create a virtual host (/etc/httpd/conf.d/SITE1.conf, /etc/httpd/conf.d/SITE2.conf, etc.) for each site. Make sure the `DocumentRoot` exists and is accessible (although you might get an error because there's no content yet). Customize each with its own blog ID, as in `SetEnv DC_BLOG_ID SITE1`.
-
-	Step 3: In each `DocumentRoot`, make `index.php` a symbolic link back to the master `index.php` in the main Dotclear site.
-
-	Step 4: Map /posts and other prefixes back to Dotclear (not sure how yet).

2.0:admin:plugins

Wed, 16 Oct 2013 09:55:24 +0200

1216564567		current
Line 25:		Line 25:
	After installing a new plugin, you should systematically go to the Dashboard page. Many plugins need this step to be activated.		After installing a new plugin, you should systematically go to the Dashboard page. Many plugins need this step to be activated.
	</note>		</note>
-
	===== Configuring plugins =====		===== Configuring plugins =====

	The way plugins are managed from the administration interface changes depending on the plugin. The configurable plugins generally have a link of their own in the lower part of the left column, but they may be located elsewhere.		The way plugins are managed from the administration interface changes depending on the plugin. The configurable plugins generally have a link of their own in the lower part of the left column, but they may be located elsewhere.

-	Other plugins simply manage widgets, so they will be accessible via the //Presentation Widgets// link: they will be listed among the ''Available plugins'', and you will be able to drag and drop them to one of the sidebars and access to any display settings available.	+	Other plugins simply provide widgets, so they can be configured via the //Presentation Widgets// link: they will be listed among the ''Available plugins'', and you will be able to drag and drop them to one of the sidebars and configure to any available settings.

-	Finally, there are plugins without any dedicated link nor widget. Please refer to the plugin's documentation (on the author's website) to use the plugin properly.	+	Finally, there are plugins without any dedicated link or widget. Please refer to the plugin's documentation (on the author's website) for information on how to use these plugins.

	<note tip>		<note tip>

2.0:admin:themes

Wed, 16 Oct 2013 09:55:24 +0200

1217420078		current
Line 1:		Line 1:
-	====== Blog aspect ======	+	====== Blog Themes ======

-	A "theme" is a set of elements that define the layout of a blog.	+	A "theme", or "aspect", is a set of elements that define the layout of a blog.

-	You can configure the themes by clicking on the Blog aspect from the Dashboard.	+	You can configure themes by clicking Blog aspect from the Dashboard.

	===== Choosing a theme =====		===== Choosing a theme =====
Line 86:		Line 86:

	Once you have made the necessary changes, click on the Save button.		Once you have made the necessary changes, click on the Save button.
-

2.0:admin:upgrade

Sat, 15 Mar 2014 02:22:55 +0200

1394768475		current
Line 55:		Line 55:
	* To update to the latest version of the current branch use ''hg update''.		* To update to the latest version of the current branch use ''hg update''.
	* To update to a different branch use ''hg update 2.6'' (for example).		* To update to a different branch use ''hg update 2.6'' (for example).
		+	* To update to a specific tag use ''hg update -r 2.6.2'' (for example).

	If you wish to use PHP files instead of gettext language files, create them manually by starting the build-tools/make-l10n.php program from the root of your Dotclear copy. Don't forget to do it after every update if you want to keep a translation updated.		If you wish to use PHP files instead of gettext language files, create them manually by starting the build-tools/make-l10n.php program from the root of your Dotclear copy. Don't forget to do it after every update if you want to keep a translation updated.

2.0:admin:users

Wed, 16 Oct 2013 09:55:25 +0200

1216492549		current
Line 48:		Line 48:


-	===== Permissions de l'utilisateur =====	+	===== User permissions =====

-	Un utilisateur tout seul sans permission particulière ne peut rien faire, pas même se connecter à l'interface d'administration. Pour ce faire, vous allez devoir lui donner des permissions sur un ou plusieurs blogs.	+	A simple user without any permission cannot do anything, not even log into the administration interface. Therefore you need to grant him or her permissions on one or several blogs.

-	Pour ajouter des permissions à un utilisateur, vous pouvez :	+	To give a user permissions, you can:

-	* cliquer sur **Ajouter de nouvelles permissions depuis la page de modification de l'utilisateur ou**	+	* click on **Change permissions from the user modification page, or**
-	* sélectionner des utilisateurs dans la liste et choisir **Définir des permissions dans les actions possibles**.	+	* select users from the user list and choose **Set permissions from the available** actions.

-	Dans les deux cas, vous devrez ensuite choisir un ou plusieurs blogs auxquels l'utilisateur va avoir accès. Une fois les blogs choisis, une page vous donne la liste des blogs sélectionnés et les permissions possibles pour chacun. Vous n'avez plus qu'à cocher les cases et enregistrer.	+	In both cases, you will then need to choose one or more blog to which the user will have access. Once you have selected the blogs, a page shows you the selected blogs and the available permissions for each. All you have to do is tick the boxes and save.

-	Voici un bref détail des permissions possibles :	+	Here is a brief explanation of the available permissions:

-	= administrateur	+	= administrator
-	: Gestion complète du blog.	+	: Full management of the blog.
-	= gérer ses propres billets et commentaires	+	= manages his/her own entries and comments
-	: L'utilisateur a le droit de créer des billets et d'accéder aux commentaires des billets lui appartenant.	+	: The user may create posts and access the comments left on his/her entries.
-	= publier des billets et des commentaires	+	= publishes entries and comments
-	: L'utilisateur peut changer le statut de publication de ses propres billets et des commentaires de ceux-ci.	+	: The user may change the publication status of his/her own posts and related comments.
-	= supprimer des billets et des commentaires	+	= deletes his/her entries and comments
-	: L'utilisateur peut supprimer ses propres billets et les commentaires de ceux-ci.	+	: The user may delete his/her own entries and related comments.
-	= gérer tous les billets et commentaires	+	= manages all entries and comments
-	: L'utilisateur peut gérer complètement les billets du blog, quel qu'en soit l'auteur.	+	: The user may fully manage the blog entries, regardless of their authors.
-	= gérer les catégories	+	= manages categories
-	: L'utilisateur peut créer, modifier, supprimer des catégories.	+	: The user may create, change and delete categories.
-	= gérer ses propres media	+	= manages his/her own media
-	: L'utilisateur peut ajouter des media et modifier ou supprimer les siens.	+	: The user may add media and change or delete his/her own.
-	= gérer tous les media	+	= manages all media
-	: L'utilisateur peut gérer les media de n'importe quel utilisateur.	+	: The user may manage the media of any user.

	<note warning>		<note warning>
-	Pour pouvoir se connecter, l'utilisateur doit avoir au moins une des permissions //administrateur//, //gérer ses propres billets et commentaires// ou //gérer tous les billets et commentaires//.	+	To be able to connect to the administration interface, a user must have at least one of the //administrator// permissions, //manages his/her own entries and comments// or //manages all entries and comments//.
	</note>		</note>