Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • @neil T

    Not sure. But they should work fine. I share user & usermeta table and they work in 2.7.
    Have you upgraded both site’s database?
    Have you hack the capabilities.php again after the upgrade? It’s overrided so you have to modify the lines again.

    This is a good idea, but it’s not mine :-). If this is going to be added in Trac, I prefer to let the one who brought this idea to take the credit :-).

    But if others don’t have time to file the ticket, I can help. I think I’ll wait 1-2 weeks. If there is no one to do it, I’ll file it with links to this & some other related threads.

    This won’t make it into 2.7 anyway..

    I hate to edit the core files everytime I upgrade. Should we enroll this lines to the wordpress trac? Any tickets already?

    if (defined ('CUSTOM_CAPABILITIES_PREFIX')) {
    	$this->cap_key = CUSTOM_CAPABILITIES_PREFIX . 'capabilities';
    	}
    	else {	$this->cap_key = $wpdb->prefix . 'capabilities';
    	}

    Thank you. I didn’t noticed it ??
    sorry for this inconvenience..

    Maybe it’s because error_log() function is disabled by your server administrator. Not all server faces this problem.

    And I think it’s a bug in 2.3.2. WordPress should check whether the function is enabled by the server or not before calling it. Try commenting the error_log() call on wp-db.php line 163 until future fixes.

    e.g.:
    /* error_log($error_str, 0); */

Viewing 5 replies - 1 through 5 (of 5 total)