As this has security implications, we recommend you disable this behavior inside any folders you allow file uploads via ExpressionEngine if you are running Apache.  The following .htaccess file will generally work.

1) Create a file called “.htaccess” (exactly like that, no additional file extensions). 

2) Place the following into its contents.

3) Upload this file into the each upload folder within your ExpressionEngine installation, or if your upload folders are all contained inside a common parent folder, you can place one copy of it there.

Notes:
- We always recommend you work with your webhost when working with server configuration.

- If you already have an .htaccess file in your installation, simply add the “SetHandler” line to it.

- Some users have trouble with this file name, and you may want to create “htaccess.txt” and rename it after you’ve uploaded it to your webserver.

Answer: This problem is caused by a changed setting in your config.php file:

instead of

You can edit your config.php to put back the original setting, or you can add that setting to your individual site’s path.php file.

Example:

(You can also copy the admin.php file from the /system/utilities folder into the root of your ExpressionEngine install.)

NOTE: Before editing your config.php and/or path.php files(s), back them up first.

In order for this fix to work, you may need to clear your site wide cookies. Information on how to do this will be in your browser’s documentation.

cPanel subdomains are a bit different then standard subdomains done via htaccess.  Here are the steps to make a forum work as a subdomain with cPanel.

1) Go into cPanel, and “Create a Subdomain”.  Set it to forum.yourdomain.com.  cPanel will want to create a directory for you at home/public_html/forum.  This is a good thing.
2) FTP into this newly created directory, and follow the directions for Running Multiple Domains or Subdomains or Subsites the “classic” way.
3) You should now have identical sites at http://www.yoursite.com and forum.yoursite.com.  The trick now is to point all the subdomain requests to http://www.yoursite.com/index.php/forum.  There are many techniques you could use for URL rewriting, but here’s a simple .htaccess file that will move all requests

Here’s the problem with time.  Imagine you and your buddies are trying to meet up at a set time, and you’ve all given me your watches so I can phone you at exactly 7 to tell you to be there.  When I get your watches, some of them are set 1 hour behind everyone elses (DST).  OK, confusing, but as long as I know that are observing DST I can account for this.  Now imagine that each one is set for a different time zone.  OK, also confusing, but I can figure that out also.  Now suddenly some of the watches stop observing DST (many hosts do), or start observing at different times.  Now I’m scratching my head.  I get a bunch of new watches, and I don’t know if they are observing DST or not.  Now some of the watches are simply set to the wrong time.  There’s also a master watch with the official time used for each day you want to meet your friends, and every day there’s a new way of officially adding and removing that hour.

Here’s how I have my system setup to give me accurate time on EngineHosting.  I’m in Toronto, so Eastern Standard Time.  Both my personal local time (under My Account > Localization) and my system time (Admin > System Preferences> Localization Settings) are set to Eastern time.  My “Daylight Saving Time” and also my “Honor the Daylight Saving Time setting associated with each weblog entry?” are set to “no”.  Partly this is to avoid the DST problem all together, but also I had originally set it this way as I was moving between hosts, and wanted fine control without needing to worry about what setup they had.  Without DST, this puts me an hour “behind”, so I set my “Server Offset (in minutes)” to 60 to make up for it.

When I post, the date and time under “date” is the exact same as my local time, and it posts to screen with that time.  When DST ends, I’ll probably have to go in and remove that server offset.

If you wanted the time an entry was posted without any reference to the localization of the author, {gmt_entry_date} is what you want. 

The date the entry was submitted in GMT. This variable is not localized for each user’s date settings.

This most often happens when mis-setting the cookie value and leaving off the leading period.  You can add this line into /system/config.php to change it:

This should allow you to enter the control panel.  You will want to head to the appropriate setting and submit it in the control panel to force the update to the database.  Once that is done, remove the over-ride from config.php.

Of course, you are free to use a Commercial licensed Site for personal and non-profit use, but you are not allowed to run commercial/for-profit websites from a Personal License. 

Instructions for updating Mark Huot’s Pages module to the newer version (now named “Tome") can be found here: http://docs.markhuot.com/ee/modules/tome/

Note to Developers: This scenario demonstrates the importance of giving unique class and table names to your add-ons, and avoiding unchecked file dependencies.  The suggested naming convention is to use identifying prefixes for all class, file, and table names.  In so doing, you will avoid potential collisions with ExpressionEngine native classes, conflicts with other third party developers’ add-ons, and even potential conflicts with non-ExpressionEngine based PHP scripts that users may be running on their sites.

Warning: If you do this, anyone with access to edit that template will be able to view your login information for that feed, so use this trick with extreme caution.

See this feature request where Paul explains that the best way to have high-ascii case insensitive searches is through your MySQL settings.  On MySQL versions 4.1 and above, setting your collation to match your language should resolve the issue.

It’s also possible for searches to be case sensitive if your MySQL collation setting is one that is by nature case insensitive, such as utf8_bin.

There are a few global forum variables, however, following is a list:

{charset}
{include:head_extra}
{include:body_extra}
{include:spellcheck_js}
{path:spellcheck_iframe}
{screen_name}
{path:logout}
{path:image_url}
{path:forum_home}
{path:your_control_panel}
{path:your_profile}
{path:login}
{path:register}
{path:memberlist}
{path:forgot}
{path:private_messages}
{path:recent_poster}
{path:advanced_search}
{path:view_new_topics}
{path:view_active_topics}
{path:view_pending_topics}
{path:mark_all_read}
{path:do_search}
{path:smileys}
{path:rss}
{path:atom}
{recent_poster}
{forum_name}
{forum_url}
{page_title}
{module_version}
{forum_build}
{error_message}
{path:theme_css}
{site_url}

License issues aside, ExpressionEngine does not currently have a management system in place that permits a user to sign up and receive a totally configured weblog.  You’d have to manually set-up each weblog and assign it to a user.  Templates have to be created, member groups have to be assigned, etc.  While ExpressionEngine supports multiple weblogs, a blogging service requires a lot of extra backend functionality in order to permit easy management (or more appropriately, self management), which means ExpressionEngine is not a suitable fit for the task.