It is also a bit faster because you will see the results on-screen, without the need to publish the changes every time. It is a little bit easier to debug AMPscript in Email Studio because the system will show you the errors as soon as you try to preview the email against a subscriber. You will always need to pass the required parameters used in your script, either by adding them to the URL ( ?myparam1=) or by creating a link or a button in an email using the CloudPagesURL function, and previewing that email against a subscriber. Remember that it will only output a nested function, and it won’t work if you try to resolve a single variable, for example last thing worth mentioning is to always remember that the purpose of AMPscript is to personalize a CloudPage for each subscriber, so you cannot expect your CloudPage to resolve correctly from the CloudPage link in the editor. You can also use the Output function to output nested functions at the location where the code block appears in your CloudPage, without having to output them inline later using %%=v()=%%. To get some details about the error behind this, try wrapping your AMPscript with a Server-Side JavaScript try/catch block: There is a problem with the resource you are looking for, and it cannot be displayed.” message without any indication of what went wrong: If you publish the page anyway and later try to access it, you will get the infamous “500 – Internal server error. When you’re working on a script in a CloudPage, the first indication that there is something wrong is the fact that when you try to publish your page, you never get a preview and the throbber just keeps spinning: The idea to add a debugging feature to CloudPages has been hanging in the Traiblazer Community’s “Ideas” section for two years now and haven’t yet reached the point threshold set by Salesforce – so if you’re reading this, visit the Add Debugging Support for CloudPages site and give it a thumb up! Consider the following two scripts: frontend.php and AMPscript in Salesforce Marketing Cloud can be a pain, as there is no built-in feature that would show script errors in CloudPages. However, this will only work for the first script we hit. For our frontend script, we'll do this from the browser using the PhpStorm bookmarklets or a Browser Debugging Extension.īoth debugging engines can start a debugging session on-demand by passing in a request variable ( XDEBUG_SESSION_START=session_name for Xdebug, start_debug=1 for Zend Debugger), which is what the bookmarklets and browser extensions do. While possible, it's good practice to not do this for every request being made but only for those where debugging is desired. The way Xdebug and Zend Debugger work is that they make a connection from the PHP interpreter to the IDE.

Click Open in Editor.Įnsure a debugger session is started for secondary requests In the CLI Interpreters dialog that opens, the Configuration file read-only field shows the path to the active php.ini file. On the PHP page that opens, click next to the CLI Interpreter field. In the Settings dialog ( Control+Alt+S), click PHP. Open the active php.ini file in the editor: To avoid this problem, you need to update the corresponding sections in the php.ini file as described in Configure Xdebug and Configure Zend Debugger. These tools cannot be used simultaneously because they block each other. PhpStorm supports debugging with two most popular tools: Xdebug and Zend Debugger. Before you startīefore you start debugging, make sure that you have a debugging engine installed and configured properly.

This tutorial describes several ways to step from front-end code into back-end code and debug them simultaneously. Often, developers work on both sides of such application at the same time. When building web applications with multiple tiers, you can have frontend PHP code calling into backend PHP code.

Max script debugger