How can I determine how much memory is allocated to PHP?
1. Navigate to Admin › Utilities › PHP Info
2. Search the page for ‘memory_limit’
3. The value shown in the “Local” column is the memory limit you are working with. If no Local value is set, then the Master value is your memory limit.
1. Using a text editor, create a new file containing only the following single line:
<? phpinfo(); ?>
2. Save the file as ‘phpinfo.php’ and upload it to a publicly accessible directoy on your server
3. Point your browser to the location of the file, e.g. http://yoursite.com/phpinfo.php
4. Search the page for ‘memory_limit’
5. The value shown in the “Local” column is the memory limit you are working with. If no Local value is set, then the Master value is your memory limit.
6. Remove the phpinfo.php file from your server, as leaving it publicly accessible is not recommended.
*User Guide
*Support Forums
*Knowledge Base
*EEHowTo
*So Very Posh - ExpressionEngine - Also has some plugins.
*EE at TextSnippets
*5pieces.com Tutorials
*Boyink.com Tutorials
*web hosting
* Interior Design Online]
*seo services company
*vacations
*web hosting india
*matrimony
*Social Bookmarking Submission
*Blog Posting Service
*Link Building Service
*ACCESSORIES AND THINGS
Category:Offsite Help and Tutorials
*Custom writing
{exp:comment:entries sort="desc" orderby="date" limit="10" dynamic="off"}
{url_or_email_as_author} on <i>
<?php
$PaginatorPage = "";
$query = mysql_query("SELECT comment_id FROM exp_comments WHERE entry_id = {entry_id}");
$comment_total = mysql_num_rows($query);
if ($comment_total > 200)
$PaginatorPage = "/P" . (floor($comment_total / 200) * 200);
?>
<a href="{comment_url_title_auto_path}<?= $PaginatorPage ?>#{comment_id}">{title}</a>
</i>.
<center>———</center>
{/exp:comment:entries}
I have PHP parsing stage set to “output” in the template preferences for this template. On the comments page, where the actual comments are displayed, I have:
{exp:comment:entries limit= "200" paginate="both"}
...matching the “200” in the recent comments list.
]]>I’m trying to turn on error reporting in EE 1.6.8, how do I do that?
The first thing you need to make sure of is that PHP supports display_errors turned on.
Visit Admin › Utilities › PHP Info and ensure that display_errors is On.
NOTE: If your host has disabled the PHP ‘display_errors’ directive, you will need to ask them to enable it, or if the server allows scripts to override the setting, you can add the following to your index.php file:
ini_set('display_errors', 1);
Next, edit the /system/index.php file, and change the value of
"error_reporting(0);"
to
"error_reporting(E_ALL);"
Then visit Admin › System Preferences › Output and Debugging Preferences and set Debug Preference to 1. PHP/SQL error messages show only to Super Admins.
View the front end of your site to see what sort of errors show up.
Additional Note: If you cannot access the Control Panel due to errors on the site or templates not rendering, you can change the system/config.php $conf[‘debug’] value to 2 temporarily which will show PHP errors to everyone. Remember to change this back to 0 or 1 when you’ve resolved your issues.
]]>If all you want to do is create a simple “alternate” version of your site, this post might interest you:
http://erskinelabs.com/post/create-an-alternative-version-of-your-expressionengine-website/
It is possible to run ExpressionEngine so that content can be accessed from more than one location. This is often desired if you want to put different content on different subdomains or simply otherwise want to access your content through more than one location.
In order to allow this, you simply need to follow a few steps:
You must place a copy of the main site path.php and index.php (the ones from your main directory, not from the system directory) files into the directory from which you wish to access ExpressionEngine.
The directory you specify must be able to have files within it be able to access your main installation system directory. You should ensure you don’t have any “open_basedir” or other restrictions in place which could prevent this.
If you want, you may rename the index.php file as described on the Renaming Main Site File page.
Once you’ve copied the files, you must open path.php to edit it.
First, you must ensure that the $system_path variable is set correctly within the file. The variable should contain a relative path from the current directory (in which the path.php file resides) to your site’s system directory. For instance:
$system_path = "../system/";
Second, you must add several new variables to the file:
$template_group = "template_group_name";
$template = "template_name";
$site_url = "http://www.example.com/subdirectory/";
$site_index = "index.php";
$site_404 = "template_group_name/template_name";
The variables are:
$template_group The name of the Template Group you want to be shown by default.
$template The name of the Template that you want to be shown by default.
$site_url The full URL to the current directory in which this path.php file resides.
$site_index This is an optional variable that will let you indicate the name of the index file if you change the name of index.php to something else.
$site_404 This is an optional variable that will allow you to set a specific Template to display as a 404 page for your subsite. This will override the general site setting for this subsite.
You may specify a PHP array containing “global variables” that will be available only to Templates accessed through that path.php file.
$global_vars = array(); // This array must be associative
For instance, let’s say you want to define a weblog name and a Template Group name. You could use this:
$global_vars = array(
"my_weblog" => "news",
"my_template_group" => "display"
); // Last entry must not include the comma at the end
Within your Templates, you would then be able to use the {my_weblog} and {my_template_group} variables.
This is a common practice, if not an official one. The result is not seeing ‘index.php’ anywhere in your urls, provided you make the arrangements properly.
A warning should be given which respects the official position, that if you make a mistake in the setup for removing index.php, the results can be quite confusing to troubleshoot. If you have that problem using the instructions, simply delete or rename all new .htaccess files you have constructed, and prior operation of your site should resume.
With that caveat and fixup out of the way, let’s see a way index.php removal can be done, including smooth operation on subdomains.
The actual method you choose for hiding should come from here, as the ins and outs are discussed: Remove index.php From URLs.
Probably the first method described in the removal article is best, especially if you are concerned about search engine optimization (SEO), as discussed with the second.
The result of each of the methods is that you will have an .htaccess file added, or lines added to the one you already have, for a basic EE site.
The trick to make index.php hiding work smoothly with multiple or subdomains is to also have an .htaccess file with the same index.php hiding rules in each of your new multiple or subdomain root folders, where the copied index.php and modified path.php are.
If you already prefer another index.php removal method on your main site, you can try replicating those rules into your new site’s .htaccess instead, and see if they will do the job as well.
...
]]>
I’m unable to get into my ExpressionEngine backend, and I’m not receiving my password reset email. Can I edit my password via PHPMyAdmin?
You can, but you need to keep in mind that your password is not stored as ascii text, but as a SHA1 encrypted password. However, you can use the following code which is for the password called “password”:
5baa61e4c9b93f3f0682250b6cf8331b7ee68fd8
How do I install plugins in EE 2.0PB? Can I just install them from the Plugins page?
Right now, the items linked in the right column are 1.x addons only. You’ll need to download first party plugins from EE Public Beta Downloads or the site of third-party developers.
To actually install the plugin(s), upload the whole folder to your /system/expressionengine/third_party folder.
NOTE: Don’t put them in the /system/expressionengine/plugins folder.
]]>How can I check whether or not Zend Optimizer is installed, and which version it is?
Create a zendcheck.php file with the following code in it:
<?php
if ( ! function_exists('zend_optimizer_version'))
{
echo 'Install Zend Optimizer';
}
else
{
echo 'Zend Optimizer version: '.zend_optimizer_version();
}
?>
FTP the zendcheck.php file to your server, and open in your browser.
If Zend Optimizer has been installed correctly, it is also mentioned in the output of phpinfo().
]]>Where can I find the Server Wizard for EE2?
You can find the link at: ExpressionEngine 2.0 Public Beta Requirements
]]>