[_ck_]

By the way, if you are asking yourself if it’s worth this much trouble getting eAccelerator to work, the answer is definitely yes. It will give you a very nice speed boost in bbPress and WordPress.

Since your server is very standardized as Cpanel + PHP 4.4.8 I am virtually positive we can get this going.

[_ck_]

No the zen optimizer is not an opcode cache, it’s just another keyhole optimizer. eAccelerator has a keyhole optimizer too but it doesn’t hurt anything to use them both. I use them both on PHP4 servers, PHP5 doesn’t need it.

I think there are possibly THREE (simple) problems.

One is a leftover corrupted eaccelerator cache left on your drive from a previous attempt that has to be cleared/deleted first.

Two is an old eaccelerator that was built for a different version of PHP, it needs to be rebuilt with that script above.

The last possibility might be the extension load order.

(you can try disabling the zend optimizer altogether as it’s overkill when eaccelerator is running)

So:

1. Try deleting your old eaccelerator disk cache first

rm -rf /tmp/eaccelerator

2. Go into php.ini and look for the Zend section.

It will look something like this but maybe not exactly like this:

[Zend]

zend_extension_manager.optimizer=/usr/local/Zend/lib/Optimizer-3.0.1

zend_extension_manager.optimizer_ts=/usr/local/Zend/lib/Optimizer_TS-3.0.1

zend_optimizer.version=3.0.1

zend_extension=/usr/local/Zend/lib/ZendExtensionManager.so

zend_extension_ts=/usr/local/Zend/lib/ZendExtensionManager_TS.so

3. Make sure that Zend section is ABOVE (before) the eAccelerator section. You can also try commenting it all out with semi-colons before each line to disable it entirely.

Last but not least, you should also delete the entire eAccerator section in PHP.ini and then run that script above.

---

After thinking about this for awhile, I would put my money on the idea that your eAccelerator was built for an earlier version of PHP and MUST be re-compiled by that script.

[_ck_]

If you replaced the semi-colon and it still will not restart, you need to double check for a typo.

Failing that, you can try removing all lines starting with eaccelerator. which should be at the very end of the php.ini or just putting semi-colons in front of them.

I perhaps should have told you to make a copy of php.ini via cp php.ini php.bak but since it’s documented here we should be able too repair it.

Actually, that install script probably made a backup of php.ini for you. Update: no unfortunately it does that when it’s about to copy and it didn’t make it that far. But you may have backup copies from other programs. See what files show up when you do a ls php* -latr

[_ck_]

Please review the 30+ other WPMU questions and answers.

https://bbpress.org/forums/tags/wpmu

[_ck_]

bbpress.org runs 0.9.0.2 here.

[_ck_]

Try these?

http://bbpress.ru/files/plugins/CyrNickname.zip

https://trac.bbpress.org/attachment/ticket/452/usernames_i18n_fix.php

The concept is fairly straightforward.

And “sanitize_user” is still used in bbPress 1.0

[_ck_]

There’s also plugins like this which can easily be modified:

http://bbpress.ru/files/plugins/CyrNickname.zip

https://trac.bbpress.org/attachment/ticket/452/usernames_i18n_fix.php

[_ck_]

You’ll need to find other WPMU users who have successfully done this. 1.0 alpha is brand spanking new and unstable. A bug today may be gone tomorrow.

[_ck_]

OH! You know what my tired eyes missed?

Yes, you have the eAccelerator *settings*,

BUT it’s disabled!

Someone disabled it by putting a semi-colon in front of the actual binary:

;extension="eaccelerator.so"

See that? To enable it, the semi-colon has to be removed, otherwise it’s dormant.

Now if it wasn’t properly installed and the setting were just left in place, then removing the semi-colon may just halt PHP entirely and prevent your apache from working correctly.

So try removing the semi-colon, save php.ini and then restart Apache via: service httpd restart

If apache doesn’t restart, or it does but you can’t access web pages, then you need to go put back the semi-colon or remove the eaccelerator section entirely.

If apache starts but you can’t find an “eaccelerator” section inside phpinfo() then it’s not really installed, or installed incorrectly. If that’s the case, then you need to remove all the existing eaccelerator lines listed above, and then run that install script again.

By the way, if you don’t know what phpinfo() is, just make a file called phpinfo.php and put only this line into it: <?php phpinfo(); ?> and put it somewhere you can access it from the web on your server and then access it via the web.

You will definitely see a speed boost when reloading pages once eAccelerator is properly installed and running.

[_ck_]

I probably made a bad assumption that it was not installed, though it definitely doesn’t come by default on a cpanel setup so that’s a bit unusual. Strange someone would put eaccelerator on there but not enable the mysql cache.

You can look at your phpinfo() to find out if eAccelerator is really installed and active.

That eaccelerator compress and compression level is just a waste of cpu time. I’d either set

eaccelerator.compress="0"

or

eaccelerator.compress_level="1"

By the way, the php configuration is located in

/usr/local/lib/php.ini

and the eAccelerator options are at the very bottom of the file if you ever have to manually edit them.

[_ck_]

This should be put into TRAC

http://trac.bbpress.org

[_ck_]

bbPress would have the same requirements of a host as WordPress. So you can check this or ask your host:

https://bbpress.org/about/requirements/

https://wordpress.org/about/requirements/

If the host already runs WordPress, they can do bbPress.

[_ck_]

Never use an alpha of any product for anything other than testing. Otherwise it’s 100% at your own risk.

bbPress 0.9 is very stable.

There are sometimes daily updates to 1.0 alpha (via the SVN of the trunk) but it will not be “finished” for many weeks.

Who is reviewing 1.0 alpha? You can’t review 1.0 alpha, it’s not finished. That’s like reviewing a car that has no interior.

[_ck_]

That’s a valid, good approach and will allow you to switch between templates very easily while retaining customization.

[_ck_]

Database error: []

SELECT * FROM bb_online WHERE user_id = LIMIT 1

Caller: online_logout

The user_id is empty in this case which causes the error.

The question is why it’s empty.

This could be a cookie problem, this could be an alpha bug.

If you have no plugins running and switching to the default template does not make the error go away, it’s a bug and should be reported on TRAC (along with your configuration if possible, server type, PHP, etc)

[_ck_]

“Cannot modify header information – headers already sent”

is one of those errors that will fool you by distraction because it’s an indication of another error, that happened before it, it’s not the actual primary error.

“headers already sent” means one of the following (among other possibilities)

1. You have whitespace at the start of end of a plugin (or template) BEFORE or AFTER the <?php ?> (usually after the end. Whitespace means new lines or spaces.

OR

2. Another plugin or configuration error has occured and sends a text message, which causes the headers to be sent. To find out what the real problem is, you typically can do a “VIEW SOURCE” on the page (from your browser menus) and you’ll see in plain text at the top of the page the real error before the “headers sent” error.

[_ck_]

Some of mine that you have posted have only been fixed for 1.0 alpha in the past 24-48 hours (like Hidden Forums). Make sure you double check your version numbers.

What changes did you have to do to Post-Count-Plus?

It should have been fixed with the newest version.

I just posted 0.0.3 of reputation which should work now.

I’ll look at the quotes plugin.

[_ck_]

By the way, once you are done with this, we’ll install eAccelerator and that will give your PHP a nice boost too.

Let me know how the MySQL cache mod goes.

If you don’t want to wait and feel comfortable trying it right away, try downloading and using this script to auto-install eAccelerator on Cpanel:

wget http://tutorials.medialayer.com/cPanel/eaccelerator.sh

chmod 700 eaccelerator.sh

./eaccelerator.sh

Once it is done, you might have to restart apache

service httpd restart

and you should definitely notice another speed boost.

[_ck_]

Untested. auto-closes a topic on-the-fly when someone visits it and it’s last post is 90 days old (adjustable)

add_action('bb_head','auto_close_topic');

function auto_close_topic() {

global $topic;

if (is_topic() && $topic->topic_open===1) {

$old=time()-3600*24*90; // 90 days default

if (strtotime($topic->topic_time)<$old) {

bb_close_topic($topic->topic_id);

$topic->topic_open=0;  // just in case the cache doesn't clear

}

}

}

[_ck_]

This would be a very simple plugin.

I’ll try to whip it up for you when I have a moment.

[_ck_]

No, if you have bbpress and wordpress integrated, and you are with bbPress 0.9, you should stick with WordPress 2.5 because that’s the only version that works with bbPress 0.9

There is nothing wrong with WP 2.5 and no need to upgrade to 2.6, because if you do, you’ll need bbPress 1.0 alpha which is unstable and has bugs.

[_ck_]

Okay, carefully edit your /etc/my.cnf (ask if you don’t know how to edit) and REPLACE what’s in there with this:

[mysqld]

max_connections = 400

key_buffer = 16M

myisam_sort_buffer_size = 32M

join_buffer_size = 1M

read_buffer_size = 1M

sort_buffer_size = 2M

table_cache = 1024

thread_cache_size = 286

interactive_timeout = 25

wait_timeout = 1000

connect_timeout = 10

max_allowed_packet = 16M

max_connect_errors = 10

query_cache_limit = 1M

query_cache_size = 16M

query_cache_type = 1

tmp_table_size = 16M

skip-innodb

[mysqld_safe]

open_files_limit = 8192

[mysqldump]

quick

max_allowed_packet = 16M

[myisamchk]

key_buffer = 32M

sort_buffer = 32M

read_buffer = 16M

write_buffer = 16M

[mysqlhotcopy]

interactive-timeout

After you edit it you’ll need to restart the mysql engine by typing this in the ssh:

service mysql restart

(optionally there’s also a mysql restart in cpanel)

Then do a couple of refreshes on your bbPress pages and it should seem a bit zippier.

[_ck_]

Oh they probably changed the bb-config.php so it doesn’t matter where you put it anymore.

bb-config.php used to load another file but now I think they make the other file load bb-config for safety and logic reasons.

[_ck_]

For now you should be okay with cpanel and whm – they do make life much easier running a server. There are things we can fine tune eventually.

However you have one HUGE problem.

You have no mysql cache enabled, at all!

When we get it fixed you will see a big difference in bbpress (and wordpress) performance.

[_ck_]

The cookies in bbPress 1.0 and WordPress 2.6 are based on recommendations from a security whitepaper by a top researcher.

Half of the key used in the cookie is kept in the database and the other half of the key is kept in the configuration file (bb-config.php / wp-config.php)

The idea is to make it harder for an attacker to compromise the system. They may gain file access but not db access or visa versa – therefore the other half is safe.

When I say “half” it’s not literal – but essentially the secret keys are “salted” with the secret salt. “Salting” is a much more complex operation than needs to be explained here (see wikipedia).