Does your SMF config reflect the right paths to templates etc? Maybe you overlooked that?
Like:
Code:
########## Directories/Files ########## # Note: These directories do not have to be changed unless you move things. $boarddir = '/var/www/vhosts/mysite.com/httpdocs/forum';# The absolute path to the forum's folder. (not just '.'!) $sourcedir = '/var/www/vhosts/mysite.com/httpdocs/forum/Sources';# Path to the Sources directory.
My issue has stopped. Did you update your php.ini or only the smf.php files? When you say bbcode how much is a lot?
If you have console to your server try this in the dir that you have your website files in: grep -lir "memory_limit" * In sms.class.php line 339 looks to be allocating memory for an array. Would have to study code to see what it is doing but double check your memory seetings for php.ini and smf.php
hmm. I dont know. Something is wrong. Until the 2.0.2.1 I'm run with memory_limit = 16M. First I tried 24, now I´m @ 32M and still:
PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 126895 bytes) in /home/xxx/components/com_smf/smf.class.php on line 339, referer: http://www.example.com/forum/board,1.0/
it´s looks like Board Threads/Posts with a lot of bbcode increase the memory usage drastical. bevor 2.0.2 this error never occurs
exrace fix brought no improvement for me.
Think I might be running into same thing. Some process is exhausting memory as it will climb to the value I set it to and die.
If I find it I will post but this is a new issue for me.
One thing I did do last night when this all started was tighten down permissions on this site...so permissions to write a file or access to a file might be part of this.
After further discover I have found the issue. In /components/com_smf/smf.php find this code around lines 41
Code:
// no direct access defined( '_VALID_MOS' ) or die( 'Restricted access' );
//1.1.4-5 Increase the allowed memory usage @ini_set('memory_limit', '16M');
Bump this value up a few meg at at time to fix issue. You don't want to make this a real big number due to memory usage. Keep in mind your php.ini or .htaccess settings need to be at or above this number.
I just started getting this messages this morning. Mine is hitting with the file com_smf module within pear.php
Code:
[Tue Aug 07 07:10:10 2007] [error] [client 74.70.180.104] PHP Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 35 bytes) in /var/www/vhosts/myhost.com/httpdocs/administrator/components/com_smf/includes/PEAR.php on line 863
To quick fix you need to bump up the memory allocation in php.ini or .htaccess file for your site. I have been running this site with 16777216 for quite some time so I am not sure if it has something to do with the size of my smf db or possible php update of some sort.
I recently made a new install with Joomla 1.0.13 and SMF 2.0.2.1 and epxerienced problems, i temporarily used the earlier versions of both software for testing and learning.
And now I've done the same setup for the new version(s), though I've followed the instructions as precise i could i still couldn't login correctly and the account i created when installing the forum, i get a blank page.
Blank page means a php error of some sort. You need to look at your php_error log to help troubleshoot.
Might be good idea to make a zip with just the updated files so many will not have to reinstall bridge to update.
I will be doing a file compare to upgrade my setups. If I do this soon I will post the list of files that were modified for this update.
It would be nice if Cowboy would qualify this and place it in the download area of site. I will start checking all the saloons on main street to see if I can find him.
It also helps to make a backup of your DB BEFORE upgrading. Then you can copy and paste from your backup DB to your production DB if you have to back out.
I wish Joomla hadn't released this security "update" like this login hash change as someone on the core team HAD to know it was going to break every single piece of bridge code out that does password sync.
I know it was in interest of security but yet another black-eye for Joomla.
Joomla Hacks is a Joomla Components, Joomla Modules, Joomla Templates, & Joomla Mambots resource portal. None of the text or images in this public website may be copied without the expressed written consent of the authors. Copyright 2005 by JoomlaHacks.com. Powered by Joomla. All rights reserved.
Terms of Use
Show Posts
Forum
