-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
3.7: Fatal error due to #11225 #12095
Comments
Looks like it would be solved by using ! instead of empty? I.e.
|
#11225 has been tested on 3.6.x branch not on 3.7 branch I'll look at it On 20 Sep 2016 9:13 am, "infograf768" notifications@github.com wrote:
|
Seriously?
for |
What we have now and causes the Fatal error is:
|
Indeed, should never have been accepted! |
How many people test with PHP 5.3 and 5.4 ? |
My test was on php 5.4.4 |
All you need is the line @sovainfo pointed out, |
yes i understood that because you got the error, |
@infograf768 i'm unable to reproduce on just want to remember that still minimum Requirements for Joomla! 3.x is 5.3.10 and yes should be |
People are known to make mistakes, procedures are in place to avoid mistakes getting into the product. That doesn't mean every mistake is caught! Luckily, this one was. Of the almost 500 $this->state->get statements in the product a few also use escape() around it. Don't know whether it needs it. |
Closing as there is a PR. Thanks! |
Steps to reproduce the issue
Load the articles manager
Fatal error: Can't use method return value in write context in ROOT/administrator/components/com_content/models/articles.php on line 329
The text was updated successfully, but these errors were encountered: