This afternoon I finally got round to figuring out why my workaround for changing the Divi projects custom post type to anything you want had broken in Divi 2.5.
In the end it was deceptively simple. I’d set the priority values for the add_action($hook, $function_to_add, $priority) and remove_action($hook, $function_to_add, $priority) functions too low.
WordPress uses the priority value to determine in which order particular actions are run. The default value is 10. The higher the value, the later it will be executed.
With the Chrome Logger extension installed and enabled on the tab I wanted to write to, all I had to do was include the library and log some data. Like this:
ChromePhp::warn('something went wrong!');
Very useful. And as well as a library for PHP there are also libraries for
You can find details on the Chrome Logger website.