Title: PHP Parse error after new update Last modified: August 31, 2016 --- # PHP Parse error after new update * Resolved [Dave_S](https://wordpress.org/support/users/dave_s/) * (@dave_s) * [10 years, 1 month ago](https://wordpress.org/support/topic/php-parse-error-after-new-update/) * Hi, * I just updated the plugin, now I get this parse error: * Parse error: syntax error, unexpected ‘<‘, expecting ‘)’ in /wordpress/wp-content/ plugins/popup-maker/includes/class-pum-fields.php on line 925 * Hope that helps to get it fixed. * Thanks, * David * [https://wordpress.org/plugins/popup-maker/](https://wordpress.org/plugins/popup-maker/) Viewing 15 replies - 1 through 15 (of 17 total) 1 [2](https://wordpress.org/support/topic/php-parse-error-after-new-update/page/2/?output_format=md) [→](https://wordpress.org/support/topic/php-parse-error-after-new-update/page/2/?output_format=md) * Plugin Author [Daniel Iser](https://wordpress.org/support/users/danieliser/) * (@danieliser) * [10 years, 1 month ago](https://wordpress.org/support/topic/php-parse-error-after-new-update/#post-7301931) * [@dave_s](https://wordpress.org/support/users/dave_s/) – Thanks for the report, we will be rapidly releasing over the next few hours & days to resolve all of the reported issues. I planned to have several days specifically to handle it quickly. That said I just finished pushing v1.4.1 which patched another issue, so look for v1.4.2 in just a bit. * Plugin Author [Daniel Iser](https://wordpress.org/support/users/danieliser/) * (@danieliser) * [10 years, 1 month ago](https://wordpress.org/support/topic/php-parse-error-after-new-update/#post-7301936) * Can you elaborate. Looking at that line I am not quite sure what the issue is. Are you getting that as a PHP error or a JS error. the code in question has no PHP enclosure issues, but maybe a JS one. * Can you try v1.4.1 by deleting the plugin and reinstalling it? Wondering if there was a messed up file or something as I don’t see an issue there currently. * Also any info like PHP version etc would be helpful. * Thread Starter [Dave_S](https://wordpress.org/support/users/dave_s/) * (@dave_s) * [10 years, 1 month ago](https://wordpress.org/support/topic/php-parse-error-after-new-update/#post-7301958) * PHP version is 5-54STABLE-STANDARD and it’s really a php error thrown out by the server. * Sorry I can’t live-test any new version right now. Will try the latest version tonight when there is less traffic on my site. * Cheers, * David * Plugin Author [Daniel Iser](https://wordpress.org/support/users/danieliser/) * (@danieliser) * [10 years, 1 month ago](https://wordpress.org/support/topic/php-parse-error-after-new-update/#post-7301960) * [@dave_s](https://wordpress.org/support/users/dave_s/) – Much appreciated. If you can maybe enable WP_DEBUG_LOG and turn on stacktraces for logging we can find the issue quickly. I cannot duplicate it currently and this is the only report of this issue, though there have been other issues we have gotten resolved quickly, hence 1.4.5 already in less than 12 hours from 1.4 * Thread Starter [Dave_S](https://wordpress.org/support/users/dave_s/) * (@dave_s) * [10 years, 1 month ago](https://wordpress.org/support/topic/php-parse-error-after-new-update/#post-7302050) * Hi Daniel, * I just enabled WP_DEBUG but I still only get the same output as mentioned above. No more enhanced log than the parse error. * I also tried to install the v1.4.5 by ftp, didn’t help neither. * If you have any other idea just let me know. * Plugin Author [Daniel Iser](https://wordpress.org/support/users/danieliser/) * (@danieliser) * [10 years, 1 month ago](https://wordpress.org/support/topic/php-parse-error-after-new-update/#post-7302052) * [@dave_s](https://wordpress.org/support/users/dave_s/) – If you can try this: [http://www.barrykooij.com/white-screen-wordpress](http://www.barrykooij.com/white-screen-wordpress). * That is exactly what we need, it tells me what called the function that called the function that broke, also shows all the variables passed to each function so I can further narrow and test. * Appreciate the help. * Thread Starter [Dave_S](https://wordpress.org/support/users/dave_s/) * (@dave_s) * [10 years, 1 month ago](https://wordpress.org/support/topic/php-parse-error-after-new-update/#post-7302053) * Yea, that’s exactly what I tried. * And as I said there is no other output than the PHP parse error. And what’s actually weird: Even the error log doesn’t get written then (though the error.log dump works fine when the plugin isn’t installed so it isn’t a rights issue or something). * Plugin Author [Daniel Iser](https://wordpress.org/support/users/danieliser/) * (@danieliser) * [10 years, 1 month ago](https://wordpress.org/support/topic/php-parse-error-after-new-update/#post-7302057) * [@dave_s](https://wordpress.org/support/users/dave_s/) – Are you available to test a patch so I don’t have to push it up for everyone without checking it works? If so email me support @ wppopupmaker.com so I can send you a test copy. I think I have it solved but nobody to verify and I can’t keep releasing broken stuff.. * Plugin Author [Daniel Iser](https://wordpress.org/support/users/danieliser/) * (@danieliser) * [10 years, 1 month ago](https://wordpress.org/support/topic/php-parse-error-after-new-update/#post-7302063) * [@dave_s](https://wordpress.org/support/users/dave_s/) – Looks like I found the issue. Seems some obscure PHP builds enable ASP tags which look like <%. Because of that your PHP server is interpreting JS templates as PHP. Now that I know the issue I will be working to get a patch, but I need to patch many sections of code to thouroughly fix it. I will be trying to duplicate it tonight so I can fix all occurances. * ​http://stackoverflow.com/questions/26588014/php-mixing-up-php-underscore-template ​ http://php.net/manual/en/ini.core.php#ini.asp-tags * [Troglos](https://wordpress.org/support/users/troglos/) * (@troglos) * [10 years, 1 month ago](https://wordpress.org/support/topic/php-parse-error-after-new-update/#post-7302064) * This is happening to me too on MAMP, as I told you in the other post with the screenshot. I see ASP tags :0 * Plugin Author [Daniel Iser](https://wordpress.org/support/users/danieliser/) * (@danieliser) * [10 years, 1 month ago](https://wordpress.org/support/topic/php-parse-error-after-new-update/#post-7302065) * [@troglos](https://wordpress.org/support/users/troglos/) – Are you saying you checked and don’t have asp_tags enabled in PHP or that you do? * [probyn](https://wordpress.org/support/users/probyn/) * (@probyn) * [10 years, 1 month ago](https://wordpress.org/support/topic/php-parse-error-after-new-update/#post-7302104) * After a new update ver. 1.4.6 i’ve got this parse error: * Parse error: syntax error, unexpected ‘?’ in /htdocs/public/www/wp-content/plugins/ popup-maker/includes/class-pum-fields.php on line 962 * Plugin Author [Daniel Iser](https://wordpress.org/support/users/danieliser/) * (@danieliser) * [10 years, 1 month ago](https://wordpress.org/support/topic/php-parse-error-after-new-update/#post-7302109) * [@probyn](https://wordpress.org/support/users/probyn/) – See the above replies, your host has enabled a non typical option. I am in the process of patching it now, but the patch is not a simple one as we used <% a lot for rendering forms. Your server is trying to read that as a