I'm brand new to Lyceum and I'm feeling more than a little overwhelmed. I have Lyceum installed and I can login as the administrator and navigate the system admin areas. However, any operation that requires further processing (e.g. creating a blog) yields a "Your tokens have timed out" error. I have no idea as to why. I've read the ticket on the main page regarding this error, but this error was supposedly fixed in the most recent release (which I'm running). Below is my wp-config.php file (deleted some comments for brevity):
*** Begin wp-config.php ***
<?php // ** MySQL settings ** // define('DB_NAME', 'lyceum'); // The name of the database define('DB_USER', 'XXXXXX'); // Your MySQL username define('DB_PASSWORD', 'XXXXXXX'); // ...and password define('DB_HOST', 'localhost'); // hostname or IP of database server (possibly 'localhost')
// You can have multiple installations in one database if you give each a unique prefix $table_prefix = ''; // Only numbers, letters, and underscores please!
// The IP address or equivalent domain name of the server (MUST have 1 or more periods - 'localhost' will not work!) define('MAINDOMAIN', 'webblog.davenport.edu'); define('DEFAULTBLOG', false);
define('SESSIONPATH', '/tmp/webblog.davenport.edu'); // *nix // define('SESSIONPATH', '\\TEMP\blogs.example.com'); // Windows // // Database sessions will be fully supported in Lyceum 1.1 and are currently experimental // define('DBSESSIONS', true);
//you probably want to leave these as they are define('DEFAULT_PS', '/%year%/%monthnum%/%day%/%postname%/'); define('DEFAULT_TEMPLATE', 'default');
// Subdomain options // See doc/Installation.txt and doc/Subdomains.txt for more info define('SUBDOMAINS', false);
//log files define('USELOGS', true); //If you are having problems installing on windows, make this 'false' define('LOGDIR', '/tmp/'); //path MUST have trailing slash. example: /tmp/ define('SECURITYLOG', LOGDIR . 'lyceum_security_log'); define('TRACELOG', LOGDIR . 'lyceum_trace_log'); define('ERRORLOG', LOGDIR . 'lyceum_error_log'); define('QUERYLOG', LOGDIR . 'lyceum_query_log'); define('TOKENLOG', LOGDIR . 'lyceum_token_log');
// Change this to localize WordPress. A corresponding MO file for the // chosen language must be installed to wp-includes/languages. // For example, install de.mo to wp-includes/languages and set WPLANG to 'de' // to enable German language support. define ('WPLANG', '');
//should lyceum NOT create an obfuscated filename for wp-comments-post.php at install time? (if you don't know what this means just leave it set to true) define('SAVEWPCOMMENTS', true);
//////////////////////////////////////////////////////////////////////////////// // Debug options. If you aren't a developer or a tester, leave them as they are.
//this should be set to false for production define('LYCEUMDEBUG', false); define('LOGQUERIES', LYCEUMDEBUG);
// Allow installation to be overwritten from the web? (this is handy for developers who do frequent re-installs) // THIS MUST BE FALSE FOR PRODUCTION define('WEBREINSTALL', false);
//define('SITETITLE', 'Davenport University Blogs'); //define('ADMINEMAIL', 'jonathan.wyse@davenport.edu');
/* That's all, stop editing! Happy blogging. */
require_once(PRIVATEROOT . 'wp-settings.php');
*** End wp-config.php ***
I'm reasonably certain it is some kind of configuration mix up. This project has been one misconfiguration after another. In addition, we're using virtual hosting for the Lyceum domain.
I'd appreciate any help the community here can give.
It's not a great idea to put it as a subdirectory inside /tmp, because /tmp gets cleared with every reboot, and so the directory will be deleted. all your users will have to log in again because all the sessions will be cleared, AND, lyceum won't work in the first place, because the directory won't exist.
this behavior might vary slightly from system to system.
as an experiment, set it to /tmp and see if things start to work. but it's a bad idea to leave it set to /tmp, because of the reasons described above, and also because then it might share the session directory with (hundreds of?) other php applications on the same server.
John, I'm confused by your comment above. You say it's a bad idea to use a subdirectory inside of /tmp but doesn't your example of how to set SESSIONPATH do exactly that?
Also, are there any security concerns with having the sessionpath directory in a publicly readable location?