Title: Error on clicking Register button Last modified: March 12, 2021 --- # Error on clicking Register button * Resolved [Ambyomoron](https://wordpress.org/support/users/josiah-s-carberry/) * (@josiah-s-carberry) * [5 years, 2 months ago](https://wordpress.org/support/topic/error-on-clicking-register-button/) * Using WP 5.6.2 After upgrading to plugin ver. 2.1.113 the following unexpected behavior occurs: 1. Visitor registers for an event requiring payment 2. Immediately after clicking on Register button, the message “An error has occurred” is displayed. 3. The page on which the payment method is selected is never displayed. * Disabling all other plugins has no effect on this issue. * The browser console shows the following message: jquery.min.js?ver=3.5.1:2 POST [https://mysite.com/wp-admin/admin-ajax.php](https://mysite.com/wp-admin/admin-ajax.php) 500 (Internal Server Error) * No other unexpected behavior occurs on the site. Viewing 10 replies - 1 through 10 (of 10 total) * Plugin Author [Franky](https://wordpress.org/support/users/liedekef/) * (@liedekef) * [5 years, 2 months ago](https://wordpress.org/support/topic/error-on-clicking-register-button/#post-14174888) * Sorry about that, there’s a typo that accidentally made it to the released version. I’m releasing a new version with the fix now. (and I hope wordpress gets rid of this torbrowser spammer) * Moderator [Steven Stern (sterndata)](https://wordpress.org/support/users/sterndata/) * (@sterndata) * Volunteer Forum Moderator * [5 years, 2 months ago](https://wordpress.org/support/topic/error-on-clicking-register-button/#post-14174915) * [@liedekef](https://wordpress.org/support/users/liedekef/) When you see a spammer, please use the “report” button over on the right and select “spam” from the dropdown. * Thread Starter [Ambyomoron](https://wordpress.org/support/users/josiah-s-carberry/) * (@josiah-s-carberry) * [5 years, 2 months ago](https://wordpress.org/support/topic/error-on-clicking-register-button/#post-14175060) * That upgrade resolves the problem of the error on clicking the register button. * I regret, though, that the new version requires an ‘unsafe-inline’ value for the content security policy directives style-src-attr and style-src-elem * Plugin Author [Franky](https://wordpress.org/support/users/liedekef/) * (@liedekef) * [5 years, 2 months ago](https://wordpress.org/support/topic/error-on-clicking-register-button/#post-14175128) * I indeed use inline styling in a number of cases, but that’s no different from previous versions of EME. If you find some inline styling to be problematic, feel free to report that (but it is more of a feature request, so maybe use the EME forum at [https://www.e-dynamics.be/wordpress](https://www.e-dynamics.be/wordpress) then) * Thread Starter [Ambyomoron](https://wordpress.org/support/users/josiah-s-carberry/) * (@josiah-s-carberry) * [5 years, 2 months ago](https://wordpress.org/support/topic/error-on-clicking-register-button/#post-14176520) * Something changed between the current version and the previous version such that visitors can no longer register for an event, so I hope you will be able to treat this issue as a bug, not an enhancement. * I know that the issue concerns the content security policies, because everything works fine if I disable them. I also suppose that the issue concerns the two directives mentioned above: style-src-attr and style-src-elem. * Regarding the fact that eme may have been using inline styles previously, let me just say that I have never had any issues with the CSP impacting any EME functionality in previous versions. * Here is what appears on the front end: * The shortcode [eme_events] no longer appears at all. However, if I disable CSP, it appears correctly. * In the browser console, a large number of CSP-related messages appear, such as: * ``` Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'self' 'strict-dynamic' https://ajax.googleapis.com https://checkout.stripe.com http://code.ionicframework.com https://code.ionicframework.com https://fonts.googleapis.com https://mysite.com 'nonce-Q1BTLzOnfLriMOMIMnqmQNhOD0wD0ITxP0xkZq6lXvMduSdUqksEockMlPWdVmIleHs3DeLa01pPTLmBS4KcWjspmQ6oNjapYIy7h9wEEmZKUlZNwDEVVZUrzmsfuf3U'". Either the 'unsafe-inline' keyword, a hash ('sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU='), or a nonce ('nonce-...') is required to enable inline execution. ``` * I recognize that the problem might well be in my CSP directives, but it would help me enormously if you were able to tell me what changed in the last version such that—all of a sudden—the directives that used to work fine are causing the page to fail. Do you have any intuition about that? * Plugin Author [Franky](https://wordpress.org/support/users/liedekef/) * (@liedekef) * [5 years, 2 months ago](https://wordpress.org/support/topic/error-on-clicking-register-button/#post-14176571) * [eme_events] hasn’t changed at all. However, it uses your defined settings and templates (not even inline styling by default), so maybe something there is provoking this? If you can tell me how you apply CSP-styling (I’m a newbie in that), I can try on my end too … Is this a theme functionality? Or a plugin? * Edit: maybe an example url might help too (not blocked by csp of course)? Don’t forget that you can have reports sent for csp violations, so that can give you a clue on what’s going on exactly. - This reply was modified 5 years, 2 months ago by [Franky](https://wordpress.org/support/users/liedekef/). * Thread Starter [Ambyomoron](https://wordpress.org/support/users/josiah-s-carberry/) * (@josiah-s-carberry) * [5 years, 2 months ago](https://wordpress.org/support/topic/error-on-clicking-register-button/#post-14176794) * The basic reference for Content Security Policy is at [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy) * Policies may be defined either at the web server level, for example, in .htaccess, or in the code that generates web pages. For WordPress sites, this is typically done via a plugin. I am not aware of any themes having CSP functionality. * As an example, the directive style-src determines valid sources for stylesheets. If an attempt to made to load a stylesheet that is not authorized, the web server will refuse to do so and the browser will see the error in its console. In addition, errors can be logged and a report is sent to a definable point so you can see what errors might occur. * Since this can be a complicated business, CSP allows you to either enforce the policies or not and to log and report the errors or not. A typical approach is to log, but not enforce, the policies so you can analyze what is happening and decide what should be allowed; what should be denied. When you are comfortable with the policy configurations, you can then turn on enforcement. * The console message I included in my previous message contains the exact contents of one of the directives, as an example. I would be happy to share with you more details, but not in this semi-public place. Let me know how you wish to proceed. * Plugin Author [Franky](https://wordpress.org/support/users/liedekef/) * (@liedekef) * [5 years, 2 months ago](https://wordpress.org/support/topic/error-on-clicking-register-button/#post-14176850) * None of the urls [https://ajax.googleapis.com](https://ajax.googleapis.com) [https://checkout.stripe.com](https://checkout.stripe.com) [http://code.ionicframework.com](http://code.ionicframework.com) [https://code.ionicframework.com](https://code.ionicframework.com) [https://fonts.googleapis.com](https://fonts.googleapis.com) are used by EME in code. The stripe-url is used after booking (if stripe is configured in EME), but since you talk about eme_events not working, it is not even related to that. Maybe your theme or another plugin is causing this, but not EME. Since I only debug EME, you need to figure out which plugins/themes are using those urls and act accordingly. Feel free to email me on my known email mentioned at [https://www.e-dynamics.be](https://www.e-dynamics.be) * [karinafic](https://wordpress.org/support/users/karinafic/) * (@karinafic) * [5 years ago](https://wordpress.org/support/topic/error-on-clicking-register-button/#post-14320103) * Hi [@liedekef](https://wordpress.org/support/users/liedekef/), * I have the same errors and use the same platform as thread started; however, I am on WP.com free site. How can I resolve this issue? * Thank you, karinafic * Plugin Author [Franky](https://wordpress.org/support/users/liedekef/) * (@liedekef) * [5 years ago](https://wordpress.org/support/topic/error-on-clicking-register-button/#post-14321072) * The typo which caused the initial problem has been long fixed in the released version. So please open a new thread for your problem, also post an example url and describe what you already tried to resolve it (e.g. look at the browser javascript console, your logfiles, disabling other plugins, etc …). Viewing 10 replies - 1 through 10 (of 10 total) The topic ‘Error on clicking Register button’ is closed to new replies. * ![](https://ps.w.org/events-made-easy/assets/icon-256x256.png?rev=1856035) * [Events Made Easy](https://wordpress.org/plugins/events-made-easy/) * [Frequently Asked Questions](https://wordpress.org/plugins/events-made-easy/#faq) * [Support Threads](https://wordpress.org/support/plugin/events-made-easy/) * [Active Topics](https://wordpress.org/support/plugin/events-made-easy/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/events-made-easy/unresolved/) * [Reviews](https://wordpress.org/support/plugin/events-made-easy/reviews/) * 10 replies * 4 participants * Last reply from: [Franky](https://wordpress.org/support/users/liedekef/) * Last activity: [5 years ago](https://wordpress.org/support/topic/error-on-clicking-register-button/#post-14321072) * Status: resolved