Easy code troubleshooting in wordpressPrint WordPress template filename(s) for debuggingDebug 500 Internal...
GeometricMean definition
Is there a frame of reference in which I was born before I was conceived?
What can I substitute for soda pop in a sweet pork recipe?
Exponential growth/decay formula: what happened to the other constant of integration?
Sometimes a banana is just a banana
Why proton concentration is divided by 10⁻⁷?
Compare four integers, return word based on maximum
Book where the good guy lives backwards through time and the bad guy lives forward
Is divide-by-zero a security vulnerability?
Casually inserting sexuality
If nine coins are tossed, what is the probability that the number of heads is even?
It took me a lot of time to make this, pls like. (YouTube Comments #1)
Replacement ford fiesta radiator has extra hose
Called into a meeting and told we are being made redundant (laid off) and "not to share outside". Can I tell my partner?
Second-rate spelling
How can I be pwned if I'm not registered on that site?
What is a term for a function that when called repeatedly, has the same effect as calling once?
Where was Karl Mordo in Infinity War?
How to count words in a line
What is better: yes / no radio, or simple checkbox?
Pure Functions: Does "No Side Effects" Imply "Always Same Output, Given Same Input"?
What do the pedals on grand pianos do?
How to speed up a process
"Murder!" The knight said
Easy code troubleshooting in wordpress
Print WordPress template filename(s) for debuggingDebug 500 Internal Server Error on WordPress blogTroubleshooting white screen when editing specific postsHow to troubleshoot WordPress issues?How to debug a unit test for a WordPress plugin, which uses wordpress-test?WordPress Ajax ProblemsWordpress + Buddpyress - troubleshooting server overloadingIs it possible to display the admin bar while in the Theme Customizer?Always keep a parameter in URL?Finding which functions were called
Is there an easy and standard way to debug our code in wordpress plugins?
I want to print some variables in a function that runs when a certain things happen.
Is there a wordpress way to save this in a file or at least see it?
debug troubleshooting
add a comment |
Is there an easy and standard way to debug our code in wordpress plugins?
I want to print some variables in a function that runs when a certain things happen.
Is there a wordpress way to save this in a file or at least see it?
debug troubleshooting
add a comment |
Is there an easy and standard way to debug our code in wordpress plugins?
I want to print some variables in a function that runs when a certain things happen.
Is there a wordpress way to save this in a file or at least see it?
debug troubleshooting
Is there an easy and standard way to debug our code in wordpress plugins?
I want to print some variables in a function that runs when a certain things happen.
Is there a wordpress way to save this in a file or at least see it?
debug troubleshooting
debug troubleshooting
asked 3 hours ago
AmiritionAmirition
598
598
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
The best way to troubleshoot/debug your PHP code for WordPress is to use the XDEBUG debugger for PHP coupled with an IDE/editor that can leverage XDEBUG.
By far my favorite IDE for PHP/XDEBUG is PhpStorm (best money I have ever spent), but you can use for free on the bleeding edge with their EAP (Early Access Program). You can also use the free VSCode with XDEBUG.
Here is a great video showing what it looks like to use XDEBUG & PhpStorm. You can start at the 18:00
point because everything before that is talking and slides.
You will also need a local development setup that supports XDEBUG. Several years ago I was frustrated with how difficult it was to get XDEBUG configured correctly so I had my team develop WPLib Box which pre-configures XDEBUG and thus makes using XDEBUG trivally easy. You can download WPLib Box from GitHub, use for free, and get help via our Slack.
I like to say using PhpStorm/XDEBUG/WPlib Box gives me WordPress superpowers. How else do you think I answered all the questions here at WPSE that I have? :-)
That said, there are also other local development solutions such as VVV, Trellis, Chassis, Desktop Server, MAMP, DevilBox, LaraDock, Kalabox, Kusanagi and others you might try. But I am not sure how difficult it is to set up XDEBUG to work with any of these others anymore and I know firsthand XDEBUG works without any fuss when using WPLib Box.
Hope this helps.
add a comment |
Just start with the following definitions in your config.php file:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('SCRIPT_DEBUG', true);
define('SAVEQUERIES', true);
The first one sets your system into debug mode, the second one writes every notice into a log file saved into your wp-content
directory. Script debug enables WordPress to use the uncompressed CSS and JS files (Maybe also interesting for writing Plugins). And Savequeries writes HTML-Comments at the bottom of the rendered HTML Output and will be used by Plugins I suggest you next.
See the WordPress Plugin Directory for Debug Bar and extensions. There are a lot and there's a great chance that some of them are providing exactly what you need.
If nothing helps you can write everytime
print_r( $var );
die();
and look into the HTML sourcecode.
add a comment |
Unfortunately there isn't really a standard developer logging API in WordPress. If you want to output your own data to a debug file (to prevent "headers already sent" errors) then you can simply use the standard PHP error_log
function. Something simple like this will record the variable $data
to the file debug.log
in your plugins directory:
$debugline = '['.date('y m d H:i:s', time()).'] '.print_r($data,true);
$debugfilepath = dirname(__FILE__).'/debug.log';
error_log($debugline, 3, $debugfilepath);
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "110"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwordpress.stackexchange.com%2fquestions%2f330654%2feasy-code-troubleshooting-in-wordpress%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
The best way to troubleshoot/debug your PHP code for WordPress is to use the XDEBUG debugger for PHP coupled with an IDE/editor that can leverage XDEBUG.
By far my favorite IDE for PHP/XDEBUG is PhpStorm (best money I have ever spent), but you can use for free on the bleeding edge with their EAP (Early Access Program). You can also use the free VSCode with XDEBUG.
Here is a great video showing what it looks like to use XDEBUG & PhpStorm. You can start at the 18:00
point because everything before that is talking and slides.
You will also need a local development setup that supports XDEBUG. Several years ago I was frustrated with how difficult it was to get XDEBUG configured correctly so I had my team develop WPLib Box which pre-configures XDEBUG and thus makes using XDEBUG trivally easy. You can download WPLib Box from GitHub, use for free, and get help via our Slack.
I like to say using PhpStorm/XDEBUG/WPlib Box gives me WordPress superpowers. How else do you think I answered all the questions here at WPSE that I have? :-)
That said, there are also other local development solutions such as VVV, Trellis, Chassis, Desktop Server, MAMP, DevilBox, LaraDock, Kalabox, Kusanagi and others you might try. But I am not sure how difficult it is to set up XDEBUG to work with any of these others anymore and I know firsthand XDEBUG works without any fuss when using WPLib Box.
Hope this helps.
add a comment |
The best way to troubleshoot/debug your PHP code for WordPress is to use the XDEBUG debugger for PHP coupled with an IDE/editor that can leverage XDEBUG.
By far my favorite IDE for PHP/XDEBUG is PhpStorm (best money I have ever spent), but you can use for free on the bleeding edge with their EAP (Early Access Program). You can also use the free VSCode with XDEBUG.
Here is a great video showing what it looks like to use XDEBUG & PhpStorm. You can start at the 18:00
point because everything before that is talking and slides.
You will also need a local development setup that supports XDEBUG. Several years ago I was frustrated with how difficult it was to get XDEBUG configured correctly so I had my team develop WPLib Box which pre-configures XDEBUG and thus makes using XDEBUG trivally easy. You can download WPLib Box from GitHub, use for free, and get help via our Slack.
I like to say using PhpStorm/XDEBUG/WPlib Box gives me WordPress superpowers. How else do you think I answered all the questions here at WPSE that I have? :-)
That said, there are also other local development solutions such as VVV, Trellis, Chassis, Desktop Server, MAMP, DevilBox, LaraDock, Kalabox, Kusanagi and others you might try. But I am not sure how difficult it is to set up XDEBUG to work with any of these others anymore and I know firsthand XDEBUG works without any fuss when using WPLib Box.
Hope this helps.
add a comment |
The best way to troubleshoot/debug your PHP code for WordPress is to use the XDEBUG debugger for PHP coupled with an IDE/editor that can leverage XDEBUG.
By far my favorite IDE for PHP/XDEBUG is PhpStorm (best money I have ever spent), but you can use for free on the bleeding edge with their EAP (Early Access Program). You can also use the free VSCode with XDEBUG.
Here is a great video showing what it looks like to use XDEBUG & PhpStorm. You can start at the 18:00
point because everything before that is talking and slides.
You will also need a local development setup that supports XDEBUG. Several years ago I was frustrated with how difficult it was to get XDEBUG configured correctly so I had my team develop WPLib Box which pre-configures XDEBUG and thus makes using XDEBUG trivally easy. You can download WPLib Box from GitHub, use for free, and get help via our Slack.
I like to say using PhpStorm/XDEBUG/WPlib Box gives me WordPress superpowers. How else do you think I answered all the questions here at WPSE that I have? :-)
That said, there are also other local development solutions such as VVV, Trellis, Chassis, Desktop Server, MAMP, DevilBox, LaraDock, Kalabox, Kusanagi and others you might try. But I am not sure how difficult it is to set up XDEBUG to work with any of these others anymore and I know firsthand XDEBUG works without any fuss when using WPLib Box.
Hope this helps.
The best way to troubleshoot/debug your PHP code for WordPress is to use the XDEBUG debugger for PHP coupled with an IDE/editor that can leverage XDEBUG.
By far my favorite IDE for PHP/XDEBUG is PhpStorm (best money I have ever spent), but you can use for free on the bleeding edge with their EAP (Early Access Program). You can also use the free VSCode with XDEBUG.
Here is a great video showing what it looks like to use XDEBUG & PhpStorm. You can start at the 18:00
point because everything before that is talking and slides.
You will also need a local development setup that supports XDEBUG. Several years ago I was frustrated with how difficult it was to get XDEBUG configured correctly so I had my team develop WPLib Box which pre-configures XDEBUG and thus makes using XDEBUG trivally easy. You can download WPLib Box from GitHub, use for free, and get help via our Slack.
I like to say using PhpStorm/XDEBUG/WPlib Box gives me WordPress superpowers. How else do you think I answered all the questions here at WPSE that I have? :-)
That said, there are also other local development solutions such as VVV, Trellis, Chassis, Desktop Server, MAMP, DevilBox, LaraDock, Kalabox, Kusanagi and others you might try. But I am not sure how difficult it is to set up XDEBUG to work with any of these others anymore and I know firsthand XDEBUG works without any fuss when using WPLib Box.
Hope this helps.
edited 1 hour ago
answered 1 hour ago
MikeSchinkelMikeSchinkel
34k14104126
34k14104126
add a comment |
add a comment |
Just start with the following definitions in your config.php file:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('SCRIPT_DEBUG', true);
define('SAVEQUERIES', true);
The first one sets your system into debug mode, the second one writes every notice into a log file saved into your wp-content
directory. Script debug enables WordPress to use the uncompressed CSS and JS files (Maybe also interesting for writing Plugins). And Savequeries writes HTML-Comments at the bottom of the rendered HTML Output and will be used by Plugins I suggest you next.
See the WordPress Plugin Directory for Debug Bar and extensions. There are a lot and there's a great chance that some of them are providing exactly what you need.
If nothing helps you can write everytime
print_r( $var );
die();
and look into the HTML sourcecode.
add a comment |
Just start with the following definitions in your config.php file:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('SCRIPT_DEBUG', true);
define('SAVEQUERIES', true);
The first one sets your system into debug mode, the second one writes every notice into a log file saved into your wp-content
directory. Script debug enables WordPress to use the uncompressed CSS and JS files (Maybe also interesting for writing Plugins). And Savequeries writes HTML-Comments at the bottom of the rendered HTML Output and will be used by Plugins I suggest you next.
See the WordPress Plugin Directory for Debug Bar and extensions. There are a lot and there's a great chance that some of them are providing exactly what you need.
If nothing helps you can write everytime
print_r( $var );
die();
and look into the HTML sourcecode.
add a comment |
Just start with the following definitions in your config.php file:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('SCRIPT_DEBUG', true);
define('SAVEQUERIES', true);
The first one sets your system into debug mode, the second one writes every notice into a log file saved into your wp-content
directory. Script debug enables WordPress to use the uncompressed CSS and JS files (Maybe also interesting for writing Plugins). And Savequeries writes HTML-Comments at the bottom of the rendered HTML Output and will be used by Plugins I suggest you next.
See the WordPress Plugin Directory for Debug Bar and extensions. There are a lot and there's a great chance that some of them are providing exactly what you need.
If nothing helps you can write everytime
print_r( $var );
die();
and look into the HTML sourcecode.
Just start with the following definitions in your config.php file:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('SCRIPT_DEBUG', true);
define('SAVEQUERIES', true);
The first one sets your system into debug mode, the second one writes every notice into a log file saved into your wp-content
directory. Script debug enables WordPress to use the uncompressed CSS and JS files (Maybe also interesting for writing Plugins). And Savequeries writes HTML-Comments at the bottom of the rendered HTML Output and will be used by Plugins I suggest you next.
See the WordPress Plugin Directory for Debug Bar and extensions. There are a lot and there's a great chance that some of them are providing exactly what you need.
If nothing helps you can write everytime
print_r( $var );
die();
and look into the HTML sourcecode.
answered 2 hours ago
chrisbergrchrisbergr
635
635
add a comment |
add a comment |
Unfortunately there isn't really a standard developer logging API in WordPress. If you want to output your own data to a debug file (to prevent "headers already sent" errors) then you can simply use the standard PHP error_log
function. Something simple like this will record the variable $data
to the file debug.log
in your plugins directory:
$debugline = '['.date('y m d H:i:s', time()).'] '.print_r($data,true);
$debugfilepath = dirname(__FILE__).'/debug.log';
error_log($debugline, 3, $debugfilepath);
add a comment |
Unfortunately there isn't really a standard developer logging API in WordPress. If you want to output your own data to a debug file (to prevent "headers already sent" errors) then you can simply use the standard PHP error_log
function. Something simple like this will record the variable $data
to the file debug.log
in your plugins directory:
$debugline = '['.date('y m d H:i:s', time()).'] '.print_r($data,true);
$debugfilepath = dirname(__FILE__).'/debug.log';
error_log($debugline, 3, $debugfilepath);
add a comment |
Unfortunately there isn't really a standard developer logging API in WordPress. If you want to output your own data to a debug file (to prevent "headers already sent" errors) then you can simply use the standard PHP error_log
function. Something simple like this will record the variable $data
to the file debug.log
in your plugins directory:
$debugline = '['.date('y m d H:i:s', time()).'] '.print_r($data,true);
$debugfilepath = dirname(__FILE__).'/debug.log';
error_log($debugline, 3, $debugfilepath);
Unfortunately there isn't really a standard developer logging API in WordPress. If you want to output your own data to a debug file (to prevent "headers already sent" errors) then you can simply use the standard PHP error_log
function. Something simple like this will record the variable $data
to the file debug.log
in your plugins directory:
$debugline = '['.date('y m d H:i:s', time()).'] '.print_r($data,true);
$debugfilepath = dirname(__FILE__).'/debug.log';
error_log($debugline, 3, $debugfilepath);
answered 2 hours ago
majickmajick
3,7091622
3,7091622
add a comment |
add a comment |
Thanks for contributing an answer to WordPress Development Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwordpress.stackexchange.com%2fquestions%2f330654%2feasy-code-troubleshooting-in-wordpress%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown