WordPress.org

Make WordPress Core

Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#14070 closed defect (bug) (fixed)

admin.php tries to read $plugin_page from the wrong directory

Reported by: bigsmoke Owned by:
Milestone: 3.0.1 Priority: normal
Severity: major Version: 3.0
Component: Administration Keywords:
Focuses: Cc:

Description

2.9 did this right. It should do

include(WP_PLUGIN_DIR . "/$plugin_page");

instead of

include(ABSPATH . PLUGINDIR . "/$plugin_page");

on line 155 of wp-admin/admin.php

It looks like a bug that got introduced by merging WPMU code.
This breaks the features introduced in 2.6 that let you keep WordPress in its own directory separate from wp-content (if WP_CONTENT_DIR != ABS_PATH . '/wp-content')

Attachments (1)

14070.diff (437 bytes) - added by wojtek.szkutnik 6 years ago.

Download all attachments as: .zip

Change History (7)

#1 @scribu
6 years ago

  • Milestone changed from Unassigned to 3.1

#2 @ocean90
6 years ago

  • Summary changed from 3.0 admin.php tries to read $plugin_page from the wrong directory to admin.php tries to read $plugin_page from the wrong directory
  • Version set to 3.0

Related changeset: [12712]

#3 @bigsmoke
6 years ago

  • Cc bigsmoke added

#4 @nacin
6 years ago

  • Milestone changed from 3.1 to 3.0.1

#5 @ryan
6 years ago

  • Resolution set to fixed
  • Status changed from new to closed

(In [15346]) Use WP_PLUGIN_DIR. Props bigsmoke, wojtek.szkutnik. fixes #14070 for 3.1

#6 @automattor
6 years ago

(In [15347]) Use WP_PLUGIN_DIR. Props bigsmoke, wojtek.szkutnik. fixes #14070 for 3.0.1

Note: See TracTickets for help on using tickets.