background preloader


Facebook Twitter

Stark Digital Media Services Pvt Ltd.

Stark Digital Media Services Pvt. Ltd. is a professional website and mobile app design & development company dedicated to providing a comprehensive web solution for both small business and corporate organizations. We have the right combination of creative and technical expertise to provide a full spectrum of web design, website development, custom web programming. We offer a full range of web solutions for businesses, as well as individuals. Our team of professionals with proven experience in the field of web development can provide high quality, cost-effective complete web solutions including complex database integrated websites, e-commerce portals, intranet development, and maintenance. We are offering a wide range of services as follows: - Website Design/Development - Web Applications Development - Content Management System [CMS] - Search Engine Optimization [SEO] - Mobile app development for Android and iOS Contact Us: Address: Office No.: 13, 1st Floor, Shinde Complex near Maratha Mandir, Shinde Nagar, Bavdhan, Pune, Maharashtra 411021. Mail id: Website: Tell No For India: +91 7757063001 Tell No For USA: +1- (9255)-008-089 Office Tell No: 020 - 22952445

Starkdigital. Using The WordPress Debug Log. Do you ever make mistakes?

Using The WordPress Debug Log

I do. The first step to fixing your mistakes is knowing what the mistake is. I can’t solve all of your problems, but I can help fix those that are generated by PHP code on your WordPress site by helping you work with debug logs. A few weeks ago, when I wrote about customizing your WordPress site’s wp-config.php file, I covered settings for debugging. I covered both how to show errors, and when you might not want to do that. For these reasons, on a live site, its a good idea to leave WP_DEBUG enabled, but to prevent errors from being displayed. Logging errors, even when you’re displaying them is still useful as having a record of your errors is often very useful in development. Setting Up This is a brief review of what I discussed in my wp-config article. In order to enable debugging, prevent errors and warnings from being displayed and log errors, you need these three lines in your wp-config:

Leveraging Chrome Developer Tools for WordPress Development. One of the most common questions I see in forums, and when talking to people one-on-one is “how do you know?”

Leveraging Chrome Developer Tools for WordPress Development

How do you know what style rules a specific element has? How do you know exactly what classes are applied to it? How can you tell that the script isn’t loading properly? There are JavaScript errors? How do you know what the return of an AJAX call is? My answer is Chrome Developer Tools! In this article we take a look at Chrome’s Developer Tools, but the general idea can be applied to all large browsers. If you have Chrome open, go to View > Developer > Developer Tools or press Command + Shift + C on your Mac or Control + Shift + C on Windows to bring up the developer tools.

Inspecting Elements The foundation of any HTML/CSS information is the Elements section and the Element Inspector. By default the inspector will be turned on. The inspector allows you to hover over an element on the page and click to select it. One trick I like is that you can copy/edit/delete nodes. The Console. Query Monitor — WordPress Plugins. Query Monitor is a debugging plugin for anyone developing with WordPress.

Query Monitor — WordPress Plugins

It has some advanced features not available in other debugging plugins, including debugging of AJAX calls, REST API requests, redirects, and the ability to narrow down its output by plugin or theme. For complete information, please see Query Monitor's GitHub repo. Here's an overview of what's shown: Database Queries Shows all database queries performed on the current requestShows affected rows and time for all queriesShows notifications for slow queries, duplicate queries, and queries with errorsFilter queries by query type (SELECT, UPDATE, DELETE, etc)Filter queries by component (WordPress core, Plugin X, Plugin Y, theme)Filter queries by calling functionView aggregate query information grouped by component, calling function, and typeSuper advanced: Supports multiple instances of wpdb on one page (more info in the FAQ) Hooks. Debugging in WordPress.

Languages: English • Español • Français • Hrvatski • Italiano • 日本語 • Português do Brasil • (Add your language) Debugging PHP code is part of any project, but WordPress comes with specific debug systems designed to simplify the process as well as standardize code across the core, plugins and themes.

Debugging in WordPress

This page describes the various debugging tools in WordPress and how to be more productive in your coding as well as increasing the overall quality and interoperativity of your code. NOTE: While it is not mandatory to account for WP_DEBUG in plugins and themes it is highly recommended that plugin and theme developers use WP_DEBUG mode while working on code they plan to release publicly. If your plugin or theme is not compatible then the errors, notices and warnings it throws will make it impossible for other developers to use your plugin/theme while they have WP_DEBUG enabled and your theme will not be eligible for promotion via the official WordPress tools. PHP Errors, Warnings, and Notices. Troubleshooting White Screen of Death Errors in WordPress. Sometimes WordPress just stops working.

Troubleshooting White Screen of Death Errors in WordPress

When you visit your site you’re met with is a stark white page and nothing else. It’s aptly referred to as the “white screen of death.” It can be extremely frustrating and problematic ,to say the least, especially when you don’t see and PHP errors listed to tip you off as to the cause of the error. You could guess what the problem is, but that could take too long. Luckily, there are steps you can take to quickly troubleshoot the problem. In this Weekend WordPress Project, we’ll take a look at the troubleshooting process for white screen errors, which includes a bit of coding or using plugins.

Troubleshooting with Coding Your wp-config.php file in the root of your WordPress install is the key to figuring out what the problem is with your site. If you would like the full details on debugging your site, take a look at our post Debugging WordPress: How to Use WP_DEBUG. Turning on debug mode will effectively display the list of current errors. Conclusion. WordPress Development. Wordpress Website Design & Development Company California USA.