Somebody who has access to all the administration features

Binder member

A binder member is a Site Member who has been given any access permission to a Binder. A binder member is able to view Protected Items, contrary to non members of the binder.


A person who publishes Articles in a Binder.

System requirements

Quam Plures is a web application, and for that it must be installed/hosted on a web server. If you do not have a web server yet, you have to find yourself one. If you already have a web server, here is what you need to check to make sure it can support Quam Plures:

Technical Requirements

Although most people will run Quam Plures on Linux with the [ Apache] web server, those are not required set-ups. It is possible, for example, to run Quam Plures on Windows with the IIS web server. Your web server will also need to have:

  • PHP version 5.x.
  • MySQL version 5.x.

You can install Quam Plures in an already existing database as well as put several Quam Plures installations in one database. If your web server doesn't meet these specifications, we urge you to ask your web hosting provider to upgrade to PHP 5.x and MySQL 5.x. Otherwise, you can always switch to a better host.


Please note some hosting providers act paranoid when hosting PHP applications. As a matter of fact, they may degrade PHP itself, removing essential features such as file access, sockets (for connection to external sites), uploading files, sending emails or other features. Some features of Quam Plures may not work on such hosts. Quam Plures may not even be able to run at all. If your hosting provider shows such problems, we suggest you switch to another host.


PHP Memory Limit

Quam Plures requires more than the default of 8MB of memory. To change it, set the "memory_limit" php.ini value to a proper value, E.g. 16M.
In /conf/_advanced.php add the following line: ini_set('memory_limit', '16M');
Note: It is recommended to set this value in php.ini or .htaccess (for Apache) itself. If PHP is running in '''safe mode''', using ini_set() to bump the memory limit seems to have no effect. In such a situation, you should ask your web hosting provider to provide the correct values.

PHP Version

PHP Version 5.x is required.

PHP Modules

XML-RPC related functions and XHTML validation require the PHP XML module.

PHP Info

Please be sure to run a PHP info command on your server or ask your prospective hosting provider to do it and send you the output of the command. This will give you a variety of useful information, including the version of PHP that is installed on the server. You will also be able to see if you have the necessary PHP modules installed. Sample phpinfo.php file: Create and upload this file to your web server. Once you have uploaded it to your server, you will need to browse to it with your web browser. Your prospective hosting provider can tell you which version of PHP, Zend, or other software is being used on their system.

PHP Related Dependencies

Make sure that *if* (not all hosting providers use it) your PHP info says anything about a Zend Optimizer, that the version is 2.6.2 or newer. That means that 2.6.3 is fine but 2.6.1 is not. You will also want to make sure that your Zend Engine is newer than 1.3. The reason for this is that the older versions have bugs in them which cause this software package not to perform properly in certain circumstances. As of today, January 14, 2008, Zend Core 2.5, Zend Framework 1.0.3 and Zend Optimizer 3.3 are current. Zend Engine is now at version 2 in PHP 5. PHP's current version is 5.2.5.


The back-office uses CSS (style sheets) for layout and display. Older and experimental browsers, which do not handle CSS correctly will have display problems. Quam Plures is tested with the following browsers:

  • Firefox 3.0+
  • Internet Explorer 7.0
  • Chrome 3.5+
  • Safari 4.x

Browsers that are known to have display issues are given below:

  • Safari
  • Internet explorer 6.x
  • Mozilla 1.2
  • Netscape 4

Most of the time these issues can be solved by hacking the CSS file(s). If you come up with such solutions, we would appreciate it if you would please contribute them to the project.


*Quam Plures uses a DB abstraction class, which makes it easier to port the system to another DBMS.


Mostly copy/pasted from WP. Need to be 'rewritten'
Trackback helps you to notify another author that you wrote something related to what he had written on his blog, even if you don't have an explicit link to his article. This improves the chances of the other author sitting up and noticing that you gave him credit for something, or that you improved upon something he wrote, or something similar. With pingback and trackback, blogs are interconnected. Think of them as the equivalents of acknowledgements and references at the end of an academic paper, or a chapter in a textbook. Trackbacks were originally developed by SixApart. It was designed to provide a method of notification between websites: it is a method of person A saying to person B, "This is something you may be interested in." To do that, person A sends a TrackBack ping to person B. A better explanation is this: * Person A writes something on their blog. * Person B wants to comment on Person A's blog, but wants her own readers to see what she had to say, and be able to comment on her own blog * Person B posts on her own blog and sends a trackback to Person A's blog * Person A's blog receives the trackback, and displays it as a comment to the original post. This comment contains a link to Person B's post The idea here is that more people are introduced to the conversation (both Person A's and Person B's readers can follow links to the other's post), and that there is a level of authenticity to the trackback comments because they originated from another weblog. Unfortunately, there is no actual verification performed on the incoming trackback, and indeed they can even be faked. Most trackbacks send to Person A only a small portion (called an "excerpt") of what Person B had to say. This is meant to act as a "teaser", letting Person A (and his readers) see some of what Person B had to say, and encouraging them all to click over to Person B's site to read the rest (and possibly comment). Person B's trackback to Person A's blog generally gets posted along with all the comments. This means that Person A can edit the contents of the trackback on his own server, which means that the whole idea of "authenticity" isn't really solved. (Note: Person A can only edit the contents of the trackback on his own site. He cannot edit the post on Person B's site that sent the trackback.) Take a look at the official trackback specification from SixApart.