Opened 5 years ago
Closed 5 years ago
#5921 closed defect (bug) (fixed)
fatal error trying write new post
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | General | Version: | |
| Severity: | normal | Keywords: | has-patch |
| Cc: |
Description
after last "svn update blog", to revision 6914, I can't open page "post-new.php", I receiving error:
Fatal error: Call to undefined function wp_get_current_user() in /(...)/blog/wp-includes/user.php on line 87
Attachments (1)
Change History (11)
comment:1
lloydbudd
— 5 years ago
- Milestone 2.3.4 deleted
- Resolution set to invalid
- Status changed from new to closed
comment:2
techcookies
— 5 years ago
- Resolution invalid deleted
- Status changed from closed to reopened
well, i'm having the same problem: branch is trunk, revision is 6937. The problem seems to be a collision with some plugins. I had Simple Tags version 1.3 activated and had the same problem. I first commented the plugin-inclusion code (wp-settings, 334-342), then i deactivated the plugin and reincluded the lines and it works.. Now i don't know at which point the plugin collides with the system but this seems a viable work-around.
comment:3
DD32
— 5 years ago
Sounds like an incompatible plugin that causes the problem then?
Re-close as invalid if thats the case, as its a plugin issue rather than a WordPress issue i believe.
comment:4
matheuseduardo
— 5 years ago
- Resolution set to invalid
- Status changed from reopened to closed
when I disable all plugins "post-new.php" worked!..
it's really some plugin incompatible! I'll try to find it.
thx for all
comment:6
ryan
— 5 years ago
wp_default_editor is being used in the script loader again. That's the problem.
comment:8
ryan
— 5 years ago
- Owner changed from anonymous to ryan
- Status changed from reopened to new
comment:10
ryan
— 5 years ago
- Resolution set to fixed
- Status changed from new to closed
You didn't include what branch you are on.
2.3/wp-includes/pluggable.php includes that function.
Closing as invalid for now. (PS. Please don't update the milestone, leave that to a core member of the team.)