error reporting
Permalink 1 user found helpful
Any chance we can get rid of this in 5.7? Seems like the perfect moment to clean this up. I'm monitoring all logs files on my server except for concrete5 projects, would love to get a clean solution there.
/** * ---------------------------------------------------------------------------- * concrete5 depends on some more forgiving error handling. * ---------------------------------------------------------------------------- */ error_reporting(E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED);
Definitely yes to the deprecated errors; possible for the others. I'll make an issue for this in the emerging issues system for 5.7 and people who'd like to fix this are very welcome to. I have fixed quite a number of these issues in 5.7 but as you imagine there are lots.
FYI: $this should no longer be used in themes. Instead we inject a $view parameter into themes that functions as the current View object. Same with $controller (which we always did for blocks.) So we're getting closer.
FYI: $this should no longer be used in themes. Instead we inject a $view parameter into themes that functions as the current View object. Same with $controller (which we always did for blocks.) So we're getting closer.
Where is the best place to contribute to these sort of fixes? 5.7-WIP branch or elsewhere?
Right now just a pull request to the 5.7.0-wip branch – but very soon we may be moving that out to its own repository. We want to keep it in the same repository but Github's tooling isn't great about separating issues between branches, and it makes it really difficult to work on 5.6.x and 5.7 at the same time.
Sounds like a good plan to me.
If you ever look at alternatives, atlassian has some pretty sweet products. We use Jira / Confluence / Bamboo for many of our internal projects and it works really great. Not sure if it would be a good fit for Concrete5 but it's definately a great management tool. Looks like they also have some examples of public JIRA instances.https://confluence.atlassian.com/display/JIRADL/Examples+of+Public+J...
Just food for thought. I realize there's a substantial amount of effort already invested into the way things are currently working and efforts are most likely better spent elsewhere.
If you ever look at alternatives, atlassian has some pretty sweet products. We use Jira / Confluence / Bamboo for many of our internal projects and it works really great. Not sure if it would be a good fit for Concrete5 but it's definately a great management tool. Looks like they also have some examples of public JIRA instances.https://confluence.atlassian.com/display/JIRADL/Examples+of+Public+J...
Just food for thought. I realize there's a substantial amount of effort already invested into the way things are currently working and efforts are most likely better spent elsewhere.
I'm quite concerned with the latest deprecated features that are coming out in PHP 5.6. Specifically the calls to incompatible contexts. I really think that this needs to be tackled sooner than later to prevent other c5 developers from following bad examples and then causing plugins to break when C5 has to change their function calls because PHP no longer supports them.
http://docs.php.net/manual/en/migration56.deprecated.php...