New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[2019.03] PHP Warnings #6337
Comments
Moved from #5911 (comment)
Fixed in #6504 |
Fixed in #6728 |
|
|
Yes proc_close is disabled by default and I activated proc_open because it is supposed to be used by Friendica. |
Oh, please enable it as well then if you can. |
Just happened ... |
|
Please run |
|
|
Have you switched storage backend on your node? |
No, just done a git pull today, but i deleted some users |
|
|
For #6337 (comment), can you please attach the relevant lines of the compiled Smarty file? |
first I would try to clear smarty3 compiled files. just to be sure they are up to date... |
I don't think it's a stale cache issue, from my experience files are recompiled immediately after source template files have been changed. |
If this message comes then the page is not accessible. |
Without a full trace this is impossible to debug, unless you have a specific page where this happens all the time. |
Since 3 years I want to report that my php.out is very often full with |
A brand new warning:
Fixed in #6751 |
That's a fatal error, not a warning => #6386 |
Oops. |
But this time it is a warning:
Fixed by #6792 |
I'm pleasantly surprised by your newfound ability to stop trying to put a round peg in a square hole! |
@copiis I don't have the same compiled version of |
Look! A warning.
Fixed by #6789 |
- Improve SQL query for network contacts - Add missing query statement closure - Addresses friendica#6337 (comment)
Here's another one:
Fixed in #6824 |
I'm getting those 'unterminated entity reference' errors pretty often. What's really weird about those errors they are not producing a clean stack trace. Some lines are dropped from PHP error log and sometimes lines are magically overwritten when looking into the issue (it's like a quantum effect: when you look at it the result is changing). :-) But I'm wrong. In fact a Friendica code block itself is making the trouble. The PHP log looks weird because we're dealing with an issue related to an issue someone reported by using a code block. I know that sounds complicated. :-) Have a look at this line of my PHP error log (containing real PHP error data and parts of the post that triggered the warning:
Everything related to '/home/friendica/friendica/...' is part of the post/comment not related to the actual path of my node. I have seached the forum node (yeah! full text search) and could pin it down to that comment: Has the issue something to do with that Is this 'unterminated entity reference' bad? I mean 'unterminated' sounds like a serious issue when a HTML parser is involved. Could this be exploited in a bad way? |
|
Closed for release, open issues have been moved to #6917 |
Illegal string offset 'created' in Worker/Notifier
A non-numeric value encountered in Core/Update
strlen() expects parameter 1 to be string, array given in .../mod/network.php on line 553
count(): Parameter must be an array or an object that implements Countable in .../include/api.php on line 956
Creating default object from empty value in .../mod/match.php on line 83
The text was updated successfully, but these errors were encountered: