Make WordPress Core

Opened 22 years ago

Closed 21 years ago

#326 closed defect (bug) (wontfix)

9/29 nightly prevents selecting images in Exhibit

Reported by: thefreefood's profile thefreefood Owned by: matt's profile matt
Milestone: Priority: normal
Severity: major Version:
Component: General Keywords:
Focuses: Cc:

Description

Upon upgrading to the 9/29 nightly, I found that I was unable to make any new posts with images in Exhibit. When selecting an image or folder, the Javascript that allows selection of images would appear to process briefly, but when I then hit 'save and continue editing,' no images were added to the post. Downgrading to the 9/26 nightly caused Exhibit to function normally again. I am using the newest version of Exhibit.

Change History (4)

#2 @thefreefood
22 years ago

After some sleuthing, I determined that the problem with Exhibit is caused by the change in wp_settings.php, line 81 (in 9/26 nightly), from "include(ABSPATH . 'wp-content/plugins/' . $plugin);" to "include_once(ABSPATH . 'wp-content/plugins/' . $plugin);" Because Exhibit uses a two-pane system with Javascript, the plugin calls more than one instance of itself when adding pictures to a post, causing the problem. I am not familiar enough with the backend of Exhibit to know if Exhibit can be changed to work around this limitation. I also recognize that the coding change in wp_settings.php was designed to prevent potential problems caused by loading a plugin more than once. However, I wonder if it may be better to keep open the possibility so that we have fewer errors in cases like this.

#3 @lstelie
22 years ago

I confirm the problem... and the solution for exhibit use (include instead of include_once)

I don't know how the plugins are named by the system but perhaps is it possible to have a switch :

IF plugin name = exhibit then : include
ELSE : include_once

modifié le : 10-07-04 12:49

#4 @matt
21 years ago

  • Owner changed from anonymous to matt
  • Resolution changed from 10 to 90
  • Status changed from new to closed

We can't have workarounds for specific plugins, I would recommend contacting the plugin author and resolving the issue there.

Note: See TracTickets for help on using tickets.