teckinno

I just did a quick debug page, to see what admin_page_access_denied() reads:

/**
	 * Ititializes the admin menu settings.
	 *
	 * @return	void
	 */
	public function adminMenu()
	{
		add_menu_page(__('vB Bridge', self::SLUG), __('vB Bridge', self::SLUG), 'manage_options', self::SLUG_MENU, array($this, 'settings'));
		add_submenu_page(self::SLUG_MENU, __('vBulletin Bridge Settings', self::SLUG), __('Settings', self::SLUG), 'manage_options', self::SLUG_MENU, array($this, 'settings'));
		add_submenu_page(self::SLUG_MENU, __('vBulletin Bridge Usergroups', self::SLUG), __('Usergroups', self::SLUG), 'edit_users', self::SLUG_USER, array($this, 'usergroups'));
		add_filter('plugin_action_links', array($this, 'adminLinks'), 10, 2);
		add_action('admin_init', array($this, 'adminInit'));
		add_action('admin_page_access_denied', array($this, 'adminDebug'));
	}

	public function adminDebug()
	{
		global $pagenow;
		global $menu;
		global $submenu;
		global $_wp_menu_nopriv;
		global $_wp_submenu_nopriv;
		global $plugin_page;
		global $_registered_pages;

		$parent = get_admin_page_parent();
		$hookname = get_plugin_page_hookname($plugin_page, $parent);

		$output = array(
			'pagenow'		=> $pagenow,
			'parent'		=> $parent,
			'hookname'		=> $hookname,
			'menu'			=> $menu,
			'submenu'		=> $submenu[$parent],
			'menu_nopriv'		=> $_wp_menu_nopriv,
			'submenu_nopriv'	=> $_wp_submenu_nopriv[$parent][$plugin_page],
			'plugin_page'		=> $plugin_page,
			'registered_pages'	=> $_registered_pages[$hookname]
		);
		foreach ($output AS $key => $value)
		{
			print('<div>' . $key . ' = ' . $value . '</div>');
		}
	}

This is the output:

pagenow = admin.php
parent =
hookname = admin_page_0
menu = Array
submenu =
menu_nopriv = Array
submenu_nopriv =
plugin_page = 0
registered_pages =
You do not have sufficient permissions to access this page.

I have experience with coding, but I’m learning WordPress. ??
Thanks for pointing the small mistake I made.

Just in case you wonder about perms… I deal with Linux for years.
chown -R fpm:root ${DIR}
find ${DIR} -type d -print | xargs chmod 0755
find ${DIR} -type f -print0 | xargs -0 chmod 0644

The above steps did not work for me. It is obviously a WordPress issue.
I installed WordPress on a brand new dedicated server, using the exact same setup as I have on my current 2 servers. On the new server, the MCE works perfectly with 2.9.1 version.

Wgetting the WP tarball, extracting it locally deleting the /wp-includes dir and copying the new files into live site did absolutely nothing (as I was expecting), beside that it made me waste 20min. ??
I said, it was worth a try. I’m glad at least it worked for some of you. I had MCE working perfectly on WP 2.9 version.

What is shocking for me is the fact that installing a fresh version (empty db) will work perfectly. Go figure…

Never mind, I ran a repair/optimize on comment table and it fixed the problem.

Thanks for the info. I upgraded to 2.5.1 and I have even more problem. Now, I cannot see at all the comments. How do I create the index?

I just ran a query:
SELECT * FROM comments

This is the error I get:
1030 – Got error 127 from storage engine

The only way I managed to solve the issue is:
Go to Manage > Posts and you will see there the blue’ed Comments icon, for each post that contains comments in moderation queue. Once you click on the Comment icon, you will be able to see the moderated comments.

However, this is not a solution.
I will upgrade to WP 2.5.1 and see if the problem was solved.