Same thing here trying to restore previous database
Parse error: syntax error, unexpected ‘<‘, expecting ‘)’ in /hermes/bosnaweb10a/b1621/ipw.itsgaorg/public_html/wp-content/plugins/popup-maker/includes/class-pum-fields.php on line 925
dejudicibus
what files did you remove?
Same problem here. I get the error Parse error: syntax error, unexpected '<' in .../wp-content/plugins/popup-maker/includes/class-pum-fields.php on line 925
Waiting for a soon fix!
I just removed the whole plug-in by FTP waiting for a fix.
restoring the database worked. I’m going to let this one play out some more before updating
@dejudicibus – Dang, you just missed me logging off late this morning. I will get a patch out right away for this. I will be available all day and pushing as many fixes as needed to get things back to normal for you guys. Please bear with me.
Is it possible for anybody to get a full PHP stack trace on that error. I cannot duplicate it as it was reported early yesterday but can’t seem to pin down the exact point of issue.
If possible please email me at support at wppopupmaker.com and reference this ticket if you can install a test version before I push another patch that doesn’t fix it.
@wells100 – Understandable, glad you got it back safely.
@newshop, @wells100 – I will be here all day working on any issues that arise so please bear with me.
If anybody here can test a patch please let me know, I can email it if you message me at support @ wppopupmaker.com
I haven’t been able to find the exact cause of this error but rewrote that code in a different way that will hopefully eliminate this issue, but if not will at least shed more light on exactly where the issue is.
I have to wait for a safe fix be available. The problem occurs on our company site, so I cannot risk to have it off again.
@dejudicibus – Understandable. The problem is that even after having 10 other devs take a look, nobody sees an actual issue with the code that should cause that. I have rewritten it to not use <?php ?> which should eliminate it but also want to make sure another doesn’t come up right afterwards. IE fix one reveals another, easier to have someone test and confirm first.
This will be patched, but don’t want to waste everyones time or release another bug.
Well, I will consider making a test on sunday.
@dejudicibus – Not a problem, we will hopefully have it patched today. I believe I already have it patched but don’t want to push just any update that doesn’t fix the issues or reveals another.
For example lets say I fix this and push it, since I am not able to duplicate it locally anyways all seems great. You install it and yay that error is gone now, but another shows up. The problem with most errors is, once they occur php stops, meaning another error could be there just after the first but not show up till the first is fixed.
Trying to avoid that situation. Do you by chance have access to a staging site through your host?
Hey guys – 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 thoroughly fix it. I will be trying to duplicate it tonight so I can fix all occurances.
​http://php.net/manual/en/ini.core.php#ini.asp-tags
​http://stackoverflow.com/questions/26588014/php-mixing-up-php-underscore-template
@newshop, @wells100, @dejudicibus – This was confirmed solved a few versions ago. Closing this. If you have any further issues please open a new ticket.
Please take a moment to rate and review the plugin and or support once you have updated to the latest version.
I reinstalled the latest version. It works now. The interface for settings is improved too. Good work. I would like also a way to “quick edit” triggers, so that I can trigger all popup at the same way without editing them one by one, but I can live without it. 😉 Thank you.
