NewsFeaturesDownloadsDevelopmentSupportAbout Us

Users FAQ

From LifeType Wiki

(Redirected from FAQ)


'When trying to run the wizard during installation, it doesn't work and I get lots of messages like "fopen(./tmp/3f4c7de95a680): failed to open stream: Permission denied", "Smarty error: problem writing temporary file './tmp/3f4c7de95a680'" or "touch(): Unable to create file ./tmp/wizard^intro.template because Permission denied". What can I do?

A: LifeType uses a template engine (Smarty) to separate the blog logic from the blog presentation. Due to its design, Smarty needs a temporary folder to be writable by the user that will be running the web server (in Apache that user will normally be the 'apache' or 'httpd' user) By default, LifeType uses the "./tmp" folder in the LifeType folder tree as the temporary folder. This error happens when the directory does not have the correct permissions. Please make sure that it can be written by the web server process, or in the worst case, that can be written by anybody (chmod 777 ./tmp)

If you would like LifeType to write its temporary files to another folder, please check the temp_folder setting in the confiuration file. You can set it to any other folder outside the web server tree, as long as the folder is writable by the web server.

How can I recover my password?

  • A*: As mentioned many before throughout this document, passwords cannot be recovered if forgotten. The technical reason behind that is that LifeType does not store the real value of the password but its MD5 hash representation. The MD5 algorithm cannot be "undone" (see RFC 1321 for more technical details on the MD5 algorithm) and the only way we can get access to our blog again is by directly logging into our database server and setting a new password.

How to use our database server is out of the scope of this document, so we will only see the exact query needed here:

 UPDATE lt_users SET password = MD5('your_new_password') WHERE user = 'your_username';

(If you chose a different database prefix other than "lt_", please replace it in the SQL query above, otherwise leave it as it is) After this operation, we should be able to log in again with our old username and new password.

How can users register a Blog on my System?

The summary.php ( within the root Folder contains all the desired Information like to register a new blog, see the latest posts etc. If you want to set the summary.php as default startpage on your server, please see [How do I set summary.php as the front page of my site?]

Why can't I add new template files?

In order for file uploads to work, you have to make sure that your PHP installation is not configured to use safe mode. If it is, then you won't be able to upload files to the server.

If PHP is not configured in safe mode, then you have to make sure that the temporary folder that has been configured in the "Global Settings" tab is writable by the user running the web server.

I get "There was no resource file uploaded" when adding a new resource

There's nothing that can be done from LifeType's side because the problem is that PHP is most likely too big. The size of the biggest file that can be uploaded to PHP is controlled via the [upload_max_filesize|] and [post_max_size|]. Please make sure that the file you're trying to upload is not bigger than the maximum allowed size.

I cannot see the graphical editor of posts even though I have set _"Enable WYSIWYG edition of texts"_ to yes in my blog settings

The HTMLArea control is a great piece of software but it only works in IE 5.5 or higher and in Mozilla 1.3b or higher. It won't work at all in Konqueror, Safari, Opera, Omniweb amongst others.

When I try to add a link using the graphical editor of posts by clicking the button with the anchor icon, I get a pop-up window asking me for a URL but then nothing is added to the text.

You need to select some text first. HTMLArea will use the text you have selected as the text of the link while what you type in the pop-up window will be the address to which the link is pointing to.

The wizard throws the following error when I move to step number two

Exception message: fopen(/Users/oscar/lifetype/config/ failed to open stream: Permission denied
Error code: 2
-- Backtrace --
/Users/oscar/lifetype/class/file/file.class.php(33): fopen
/Users/oscar/public_html/lifetype/wizard.php(521): configfilestorage.savevalue
/Users/oscar/public_html/lifetype/class/controller/controller.class.php(103): wizardstepone.perform
/home/orchid/public_html/lifetype/wizard.php(1113): controller.process

It means that it was not possible to write the settings to the configuration file. Please make sure that the *config/* file is world-writable *before* starting the installation. If you have shell access to the web server, the following command will do:

chmod 666 config/

Once the installation process is over, please make sure that the file cannot be written anymore:

chmod 644 config/

If you don't have shell access, use your FTP client to the the correct permissions to the file.

How can I use "https://" URLs with LifeType?

The instructions are different depending on whether you have a multi-domain installation or just one domain. (Note, LifeType supports multiple blogs on one domain, both with and without subdomains).

For one blog, all blogs on the same domain, or all blogs on the same subdomain of one domain

You can easily enable https URLs with LifeType doing the following: log into the administration interface of your LifeType and then click the "Site Admin" tab. Once there, click the "Global Settings" tab and you'll be presented with a list containing all the possible configuration parameters supported by LifeType. Look for one called "base_url", since this one is used as the base URL to generate all other URLs in the html code. By default, it should look something like "http://yourlifetypehost/" (depending on where you installed LifeType) If you wish to have secure URLs, modify that field so that it has "https://yourlifetypehost/", scroll down the page and click the "Save" button. Now all URLs should point to your secure site.

Note that if you put https:// in the base_url, the "Use SSL" setting on the blog settings page (only appears when subdomains are enabled) will not have any effect.

For multi-domain installations

If you are using https on all domains in the installation, you can simply use the above instructions.

For versions greater than 1.2.12, you can have some blogs with SSL and some blogs without. Leave the global setting base_url with just http://{blogdomain} or whatever you need.

And then in the blog settings for each blog you wish to make SSL, check the box that says "Use SSL".

Locales with access do not work

First of all, make sure that the default character set of your browser is set to "Auto-Detect". The Spanish locale file uses ISO-8859-1 as the encoding but others may use UTF-8, so it's best to leave it up to the browser and the html code to decide which one to use (all templates in LifeType "announce" which encoding they're using)

If that didn't help, check that your Apache server is not serving UTF-8 content, therefore forcing all content to be UTF-8. Make sure that the AddDefaultCharset Apache directive is disabled:

  ~AddDefaultCharset Off

How can I configure "Search Engine friendly" URLs?

This feature only works on Apache servers and requires that .htaccess files are allowed. If this is the case, make sure that *ForceType* and *ErrorDocument* directives can be used within .htaccess files, as those two directives are the ones upon which the technique is built.

On some Web Hosts, if PHP is running as CGI, ForceType may not be supported. In your .htaccess file replace all instances of:

  ForceType application/x-httpd-php


  SetHandler application/x-httpd-php

Where is the administration panel?

The administration panel is accessed via the *admin.php* script, from the same web folder where LifeType was installed, so that if LifeType was installed in, then the adiministration interface can be reached at

No thumbnail is generated at all when uploading GIF files!

Recent versions of PHP come with a version of the GD library that does not have support for GIF files. From the PHP documentation:

"Versions of GD older than gd-1.6 support GIF format images, and do not support PNG, where versions greater than gd-1.6 support PNG, not GIF."

The solutions are either to build PHP manually to include support for GIFs, or use ImageMagick as the backend for generating previews.

After installing LifeType in my RH9/Fedora Core server the texts are all messed up!

RH9 and Fedora Core ship with the Apache web server configured in a way that it forces clients to use the UTF-8 encoding. According to the HTTP specification, browsers should ignore whathever encoding the HTML page is setting via <meta ...> tags and follow what the web server says.

In order disable this, look for a line that looks like this:

  AddDefaultCharset utf-8

And make it look like this:

  AddDefaultCharset off

For more information, see the

How do I set summary.php as the front page of my site?

If your Apache setup allows the use of .htaccess files, add the following lines to the file .htaccess:

<IfModule mod_dir.c>
        DirectoryIndex summary.php index.html index.php

If .htaccess files are not allowed, the lines above can be added to httpd.conf, the main Apache configuration file.

If it still doesn't work, try removing the <IfModule...> and </IfModule> lines and see if you get an error. If you do - it means Apache needs to have that module installed.

My PHP is running out of memory/I can't see anything in my pages

I am getting an allowed memory size of XXX bytes exhausted error

Might be that you need to increase PHP's memory limit. LifeType can be memory hungry at times and sometimes under certain conditions it will go over the 8Mb limit set by PHP by default.

Edit your .htaccess file and add the following lines:

<IfModule mod_php4.c>
  php_value memory_limit "16M"

Alternatively you can edit your php.ini and set the option memory_limit to 16M or more.

When subdomains are enabled, says that the blog doesn't exist!

That's because when subdomains are enabled, LifeType is trying to load whose user or title is "www" and if it doesn't exist, it will show an error.

The way to get around this limitation is via Apache's mod_rewrite:

RewriteEngine On

# For Redirecting domains like -->
RewriteCond %{HTTP_HOST} ^www\.(.*)\.mysite\.com$ [NC]
RewriteRule ^.*$ [R=301,L]

#For Redirecting -->
#For Redirecting -->
RewriteCond %{HTTP_HOST} ^mysite\.com$ [NC,OR]
RewriteCond %{HTTP_HOST} ^www\.mysite\.com$ [NC]
RewriteCond %{REQUEST_URI} ^/$ [NC]
RewriteRule ^.*$ [R=301,L] 

The rules above should be added to your .htaccess file or to your Apache configuration file for the virtual host where LifeType is installed.

How Can I display my LifeType blog in non-LifeType pages?

Please see Integrating LifeType

How do I configure support for subdomains?

See Support for Subdomains

How do I configure custom URLs?

See Custom URLs

I am using subdomains, can I remove /blog/ from URLs?

Please see Custom URLs#How to customize URLs when we are the only user in the site

I am getting an error in file XXX line YYY right after installation, why do you guys have broken code?

If you are using a released version, I can assure you that the problem is not in the code. It might have to do with your server configuration, or a memory error (see above FAQ on memory exhausted) but what seems to happen a lot is the files get corrupted when FTP'ed to the host. FTP used to work, so I don't know why it is such a problem, but I had it happen to me, with a reliable client, (I suspect the host, as when I FTP to my hosted machine, there aren't any errors). ncftp is a good client to use, as it is smart enough to be able to go through directories recursively looking for files that are different, and upload only those files. So, it is easy to try to reupload the whole tree again, and see if a file was corrupted. If you just reupload all of the files, you might corrupt some other file in the process...

Tables don't exist on Fresh Install

Don't fill in the values in the file if you are installing from scratch. If you do put information in that file, the installer will assume you are upgrading, and since the old tables don't exist, it will complain, and the install will fail.

I get "Request Too Long" when submitting a long post

Some server/brower combinations seem to have trouble with our auto-save mechanism designed to keep your posts stored in cookies in the case that your network connection is lost, your login session times out, etc. See Bug#1600 for technical details, but the short answer is that you can disable the autosaving, by editing /js/ui/autosave.js and set "var maxBackupCookiesPerBlog = 0;"

How can I show more than 15 comments/trackbacks on the Manage->Comments or Manage->Trackbacks page so that I can mark more than 15 as spam at a time?

In order to do this, you are going to have to manually edit the file /class/dao/model.class.php. MAKE A BACKUP OF THE FILE BEFORE MAKING ANY CHANGES! On a linux system, you can use the command:

cp /class/dao/model.class.php /class/dao/model.class.php.bak

Next, open model.class.php in your favorite editor and find the line:

define( "DEFAULT_ITEMS_PER_PAGE", 15 );

(In LT 1.2, it is on line 58) Change the number to any higher number that you like. However, you must be aware of the consequences! Choosing a number that is too high could result in:
- Causing your server to time out during the operation
- LONG waiting times during loading of the page/marking the comments as spam/purging spam.

What is the optimal number? That is hard to say because it depends completely on your server. You can experiment and find what you and your server are comfortable with.

After marking all the comments/trackbacks as spam, don't forget to purge them from Administration->Clean Up->Purge Spam. Once the entire process is complete, set the number for DEFAULT_ITEMS_PER_PAGE back to 15 so that all the other lists on your blog become neatly paginated again and are not unnecessarily long.

In case you made some wrong changes and can't track them down/undo them, revert to the backed up version of your model.class.php and try again.