Opened 15 years ago
Closed 15 years ago
#12749 closed defect (bug) (invalid)
3.0 catchable fatal error
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | 3.0 |
| Component: | General | Keywords: | |
| Focuses: | Cc: |
Description
normally, this would go in support forum, but not much for 3.0 there and this is something that was working previously in 3.0...
I dont know when it started but we noticed it today... getting these notices and error:
Notice: Object of class WP_Error could not be converted to int in C:\wamp\www\wordpress-dev\wp-includes\functions.php on line 3016
Notice: Object of class WP_Error could not be converted to int in C:\wamp\www\wordpress-dev\wp-includes\functions.php on line 3016
Catchable fatal error: Object of class WP_Error could not be converted to string in C:\wamp\www\wordpress-dev\wp-includes\formatting.php on line 2755
trying to back track this and find where the error is coming from... In this case, we are actually logging in the user but after the error, the user is left logged in as the wp admin, not the account the user was logging in... scary...
This is last nights nightly build of 3.0 and I as I mentioned previously, this area of the plugin had already been updated and tested to work with 3.0
Attachments (1)
Change History (9)
#2
@
15 years ago
happy to, but how do I generate a backtrace?
and I guess I assumed using Westi's beta tester plugin and grabbing the nightly it was from last night... is it older than that? but yes, absint()... probably should just change it over to svn...
#3
@
15 years ago
for grins, move over to svn... now get these
Notice: Object of class WP_Error could not be converted to int in C:\wamp\www\wordpress-dev\wp-includes\functions.php on line 3028
Notice: Object of class WP_Error could not be converted to int in C:\wamp\www\wordpress-dev\wp-includes\functions.php on line 3028
Catchable fatal error: Object of class WP_Error could not be converted to string in C:\wamp\www\wordpress-dev\wp-includes\formatting.php on line 2755
#5
@
15 years ago
If its long for pasting here, You could upload it to this ticket as a .txt if it doesnt contain sensitive information.
In trunk (r13871), functions.php line 3016 is a
die()call. But I did the math, and your nightly has absint() at 3016.The error means that absint() is being passed a WP_Error object instead of a non-object value, usually scalar, from which it is to derive a positive integer.
The error for formatting.php:2755 means that wp_strip_all_tags() is being passed a WP_Error object instead of a string from which it is to strip tags.
We will need additional information such as a backtrace to see how and where wp_strip_all_tags() and absint() are being called from and how they are getting WP_Error objects that are apparently unaccounted for.