Aportación realizada por Howard Miller

Moodle in English -> General developer forum -> Exception that always produces full trace

de Howard Miller -
Imagen de Core developers Imagen de Documentation writers Imagen de Particularly helpful Moodlers Imagen de Peer reviewers Imagen de Plugin developers

Is there any way to call moodle_exception (or similar) and always get a full "developer" trace returned for the error regardless of site debug settings. 

I want to do this in a new plugin we have developed but don't want to enable full debugging for the rest of the site. 

To make it more interesting, all the exceptions are inside web service calls - so I want the trace to come back in the web service error exception. 

If this makes any sense...

Promedio de valoraciones: -

Moodle in English -> Installing and upgrading help -> A full Moodle backup -> A full Moodle backup

de Howard Miller -
Imagen de Core developers Imagen de Documentation writers Imagen de Particularly helpful Moodlers Imagen de Peer reviewers Imagen de Plugin developers
I'm not sure what problem you are trying to fix. If you just want a backup in case an upgrade goes wrong - so that you can roll back - then Site_backup

You should be doing those anyway, I would hope.

As Ken says, we get this Wordpress thing quite a lot. But Wordpress is the equivalent of one Moodle plugin. It's not in the same league at all.
Promedio de valoraciones: -

Moodle in English -> Installing and upgrading help -> Switching to updating plugins from using git to using Moodle web interface -> Switching to updating plugins from using git to using Moodle web interface

de Howard Miller -
Imagen de Core developers Imagen de Documentation writers Imagen de Particularly helpful Moodlers Imagen de Peer reviewers Imagen de Plugin developers
What I do (and this is not a recommendation, particularly)... when I am upgrading say from 4.4 to 4.5 is to simply copy ALL the optional plugins from 4.5 to 4.5 which gives me a baseline. I can then run the GUI upgrade script, which will pick up some of them. I then print off a list and work through them one by one to make sure they are "Ok". It's quite a lot of work but I can't see any way to avoid doing something like this, however you cut it.
Promedio de valoraciones:Useful (1)

Moodle in English -> Installing and upgrading help -> Plugins overview: undefined function mlbackend_python\exec() -> Plugins overview: undefined function mlbackend_python\exec()

de Howard Miller -
Imagen de Core developers Imagen de Documentation writers Imagen de Particularly helpful Moodlers Imagen de Peer reviewers Imagen de Plugin developers

Firstly, I've never used the analytics stuff and I'd never heard of the python backend. What concerns me is that I'm struggling to find any recent documentation. Is it definitely still a "thing" in Moodle 5?

Failing that, it would help to enable Debugging and get a trace for that error.
 
In fact, I'm tempted to move this to the Analytics and reporting forum.
Promedio de valoraciones: -

Moodle in English -> General help -> Error message when attempting to get lost password -> Error message when attempting to get lost password

de Howard Miller -
Imagen de Core developers Imagen de Documentation writers Imagen de Particularly helpful Moodlers Imagen de Peer reviewers Imagen de Plugin developers
In which case, it's logging to a file called 'error_log'. I think I'd be happier if that was a complete path. For example, mine is /var/log/php-fpm/www-error.log

Then you know for sure where it is.
Promedio de valoraciones: -