Opened 17 years ago
Closed 16 years ago
#6482 closed defect (bug) (worksforme)
WP 2.5: Can't insert gallery into post
Reported by: | prwood | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 2.5 |
Component: | General | Keywords: | |
Focuses: | Cc: |
Description
I am running Wordpress 2.5 with:
Operating system Linux
Linux kernel version 2.6.9-67.0.4.ELsmp
Apache version 1.3.37 (Unix)
PHP version PHP/4.4.6
MySQL version 4.1.22-standard-log
When creating a new post, I am able to use the "add an image" button in the "add media" section to select multiple images from my local disk and upload them to the server. However, when I click "insert gallery into post", it takes me to a blank screen and stops. Upon further inspection, the gallery was not successfully inserted. This doesn't seem to throw any errors into my Apache server's error log or the PHP error log.
Attachments (1)
Change History (6)
#2
@
17 years ago
Is the fresh copy that works running on the same server with the same environment as the upgraded one that is broken?
Try adding this line to your wp-config.php (before the require_once() line):
define('WP_DEBUG', true);
Does the gallery problem result in any error messages in your log files after adding that?
@
17 years ago
This is a walkthrough showing the actions I took, and the error log messages that were produced.
#3
@
17 years ago
Yep, that produces error messages in my logs. I've attached a walkthrough, with the actions I take followed by the error messages produced.
Also, I should note that on the server that is working properly, the add image window shows up as a inline popup, where in the non-working installation, I am taken to a completely separate page when clicking the add image button. Perhaps this is why when it is finished it takes me to a blank page - if it normally is supposed to appear within an inline popup, it would make sense for the script to do nothing else. Maybe the real issue is, why does it not appear in an inline popup?
Note: I installed a fresh copy of WP 2.5 on a new blog, and I don't have this problem. So it seems to have something to do with having upgraded from a previous version of WP (2.3.3).