Dear customers, our working ours are over for today. Please be patient and wait for your responses.
We are coming back tomorrow at 9AM GMT+2. Thank you! Current hour is: 07:25 PM
Dear customer,

For a while now we have been working on a new, more user-friendly help desk setup so that our users could receive the support they need and make it easy for them to access information about our products. Starting September 1st, 2017 we will no longer accept new tickets on this help desk and more on to our new address: http://help.touchsize.com. We invested time and resources and we'll try to invest even more into briging articles and more information into our knowledgebase. The new help desk will have live search results, a better navigation through the information on our website and of course - more quality information.

Unforunately, we will not be able to migrate the current tickets and information from this help desk, which means that we start on the new help desk from a clean, new setup. All user information, tickets, replies and details will remain available here for a period. Starting September 1, 2017 we will disable the possibility to add new tickets here and from September 10, 2017 we will block the replies as well.

Thank you very much for your support. The TouchSize Team. Great! Close this.
Looking for WordPress & design information? Check out www.shapeofweb.com for more!
TouchSize

Server StatusServer Status

Viewing Article

Why not use WP_DEBUG on a live site.

  • 01/12/2016 11:49 AM
  • Articles
  • 419 views
While executing new functions in WordPress, we face different types of problems and warning signs numerous times. Most of the time, it is very hard to trace the error messages and address every bugs.
In order to find a solution to these, we need to use a debugger. Luckily, WordPress comes with a default debugger system titled ‘WP_DEBUG.’ WordPress codex defines this feature as a PHP constant which can turn on the debug mode for the platform. You can learn more  here .
While enabling WP_DEBUG is important in development, you may have some non-fatal errors and warnings that you can’t avoid for whatever reason that you don’t want to displayed to all of your visitors. Also, there may be errors and warning that you are not aware of as you never triggered them, but your site’s visitors are seeing. For these reasons it’s important to keep in mind that WP_DEBUG should not be used on a live site
While it’s a useful feature during development, it can be dangerous on a live site because text in the PHP notices can reveal details about your code, paths and other information to visitors to your site. Evil minded people could take advantage of these things and try to hack your website.

 

Print Article  Print Article

Share via   Share by Email   Share via Twitter   Share via Facebook   Share via Google Plus

Related Articles

Comments

Add Comment

Replying To  
Full Name
Email Address     Send Email on Replies

Confirm Submission

Please enter the text from the image in the box provided, this helps us to prevent spam.


Register Now

User Log In

  Remember Me
Forgotten Password?
Note: Your mail address will be automatically registered to our newsletter. How to use the help desk