Support

Home Forums Event Espresso Premium Payment Settings Not Available

Payment Settings Not Available

Posted: March 17, 2014 at 2:31 pm

Viewing 19 reply threads


Rob Orr

    March 17, 2014 at 2:31 pm

    I’m trying to finish loading my payment settings and for some reason, I can get every screen for EE except for the payment settings screens. What’s going on here?

    Here is what I see.

    https://www.evernote.com/shard/s34/sh/53b14255-9a7c-4268-9839-d25fb65ae1b4/2c8738a5db7afdf23df97fd1483d2a56

    WP 3.8.1
    EE version: Version 3.1.36.4.P
    No problems with the site at all.

    Nothing has been changed/upgraded or otherwise adjusted. I’ve also tried this in two different browsers – FF and Chrome – with the same result. I need to get this knocked out, so I hope to hear from you soon!


    Rob Orr

      March 17, 2014 at 2:34 pm

      https://www.evernote.com/shard/s34/sh/21cdae3d-02e3-47e6-927a-03756a3fdeec/ba342973980febe20d862cf01e1c87ac


      Josh

        March 17, 2014 at 2:43 pm

        Hi Rob,

        Whenever all the payment options disappear like this it is usually a JavaScript error happening somewhere early on the page. A quick way to find what’s causing the JavaScript error is by checking the page in Firebug or the Chrome Inspector. From there you should be able to determine if the script that’s throwing the error is from a plugin or the theme.


        Rob Orr

          March 17, 2014 at 6:26 pm

          BTW – this is the error that Chrome is showing:

          Failed to load resource: net::ERR_INCOMPLETE_CHUNKED_ENCODING


          Rob Orr

            March 17, 2014 at 6:29 pm

            BTW – nothing has changed with teh site – no new plugins, no new updates, nothing. it was fine a few days ago, this is rather bizarre.


            Dean

            • Support Staff

            March 18, 2014 at 2:14 am

            Hi,

            A Google search suggests this is a broad Chrome issue. Have you tried using an alternative browser?

            It’s weird why it is affecting you but hasn’t come up for us as the majority of the support and development team use Chrome on iOS and Windows, so we would have come across this by now.

            Out of interest is your server IIS (Windows) or Linux?


            Rob Orr

              March 18, 2014 at 6:36 am

              I’ve tried in Firefox and Chrome – using a 6 month old Mac w/ 10.9 Mavericks


              Rob Orr

                March 18, 2014 at 6:38 am

                oops – sorry . The server is on Rackspace Cloud linux


                Rob Orr

                  March 18, 2014 at 6:42 am

                  I just tried it in Opera and Safari too, to see if it was browser related, and I’m still getting the same thing.


                  Josh

                    March 18, 2014 at 8:40 am

                    Hi Rob,

                    Can you check the PHP error log or enable WP_DEBUG and check to see if any errors get logged or display when you view the Payment Settings page?


                    Rob Orr

                      March 25, 2014 at 11:55 am

                      There are no errors in the error log. WP_DEBUG is reporting this:

                      [25-Mar-2014 17:52:58 UTC] PHP Warning: session_start() [<a href='function.session-start'>function.session-start</a>]: Cannot send session cache limiter - headers already sent (output started at /mnt/stor2-wc1-dfw1/redacted/www.MYSITE.com/web/content/wp-includes/functions.php:2908) in /mnt/stor2-wc1-dfw1/redacted/www.redacted.com/web/content/wp-content/plugins/event-espresso/espresso.php on line 55


                      Josh

                        March 25, 2014 at 3:06 pm

                        Hi Rob,

                        It may help narrow down what’s causing this by temporarily deactivating all the non – Event Espresso plugins and possibly switching to the default twenty* WordPress theme. All it takes to throw a session error like this one is some white space or an empty line that got accidentally added somewhere before an opening


                        Rob Orr

                          March 25, 2014 at 5:33 pm

                          I can’t do that – this is a live site. Let me reiterate that I was able to view the payment settings a couple weeks ago with no problem. Nothing has been added or changed since then. Does that EE specific error message not help?


                          Lorenzo Orlando Caum

                          • Support Staff

                          March 25, 2014 at 7:33 pm

                          Hi there Rob,

                          We do appreciate you sharing the session start warning message. Unfortunately it does not help us pinpoint why your payment settings page is not loading as expected. We also can’t duplicate this issue on a test site.

                          If you aren’t seeing any other messages in the site error_log, then it would be best to test on defaults during off hours. This takes just a few minutes especially if you open up a couple tabs like so:

                          1) Open your WordPress admin in a browser tab and go to Appearance –> Themes
                          2) Launch a new tab (tab two) and go to WordPress admin –> Plugins
                          3) Open up a third tab and go to the Event Espresso payment settings page

                          Now in tab one, activate a default theme. Then in tab two, deactivate all plugins and reactivate only Event Espresso.

                          At this point, your site is running in defaults so refresh tab three which is the payment settings page.

                          Does anything load on the page?

                          If it does, restore your original theme in tab one and refresh tab three.

                          Does it still load?

                          If so, begin re-activating your plugins to find the source of the conflict.


                          Lorenzo


                          Josh

                            March 25, 2014 at 7:34 pm

                            Hi Rob,

                            It certainly does help, which is why I said that a plugin or theme is likely the cause of the error. Let’s break down the warning message and interpret what it’s actually saying:

                            If the error message says:

                            PHP Warning: session_start() Cannot send session cache limiter – headers already sent by (output started at /wp-includes/functions.php:2908) in /wp-content/plugins/event-espresso/espresso.php on line 55

                            Then the problem is at line #2908 of /wp-includes/functions.php, not line #55 of espresso.php. In this scenario, line #55 of espresso.php is the victim. It is being affected by something triggering some WordPress error output from line #2908 of functions.php of WordPress core.

                            Line #2908 of functions.php reads:

                            trigger_error( sprintf( __('%1$s is <strong>deprecated</strong> since version %2$s! Use %3$s instead.'), $function, $version, $replacement ) );

                            So from that, it looks like there’s a deprecated function being called (likely from another plugin or a theme), WordPress is trying to throw an error (because wp-debug is turned on), but it cannot because there’s also a session issue.

                            I mentioned before it doesn’t take much to throw an error like this one. (A single space in the wrong place will do). If any files were edited on the server, which includes any updates or modifications to any files that WordPress loads up, it could be the cause of the issue you are seeing.

                            More troubleshooting info here:

                            http://codex.wordpress.org/FAQ_Troubleshooting#How_do_I_solve_the_Headers_already_sent_warning_problem.3F


                            Rob Orr

                              March 28, 2014 at 6:02 am

                              Ok – not sure what the problem is here, but it is STILL not working. I deactivated EVERY PLUGIN except for the EE plugins – still no payment settings availabe. I changed the theme – not sure at all why changning the theme would have anything at ALL to do with something in the WP admin dashboard, but I did just in case. STILL nothing.

                              You guys mentioned that this is potentially a js/jquery issue. Is the payment settings tab in the WP dashboard the only place where you’re using js/jquery? Why would it have worked a couple weeks back, but not work now? NOTHING NOTHING NOTHING is different on this site than the last time I was able to successfully access the payments tab.

                              We need to figure out what’s going on here ASAP. We’ve paid for a professional license, and a working one at that and we need a solution. this has already dragged on way too long. If you guys need access to the site to see what’s going on, I’ll be happy to get you in, we just HAVE to get this resolved NOW.


                              Rob Orr

                                March 28, 2014 at 6:13 am

                                BTW – just in case I didn’t mention it before, since we’re looking in wp-includes/functions.php we’re running the latest version of WP – 3.8.1. Nothing has been changed in wp-includes/functions.php.

                                Here is the section of code that the error is in reference to in the functions.php file covering lines 2904-2918:

                                <code>	// Allow plugin to filter the output error trigger
                                	if ( WP_DEBUG &amp;&amp; apply_filters( &#039;deprecated_function_trigger_error&#039;, true ) ) {
                                		if ( function_exists( &#039;__&#039; ) ) {
                                			if ( ! is_null( $replacement ) )
                                				trigger_error( sprintf( __(&#039;%1$s is &lt;strong&gt;deprecated&lt;/strong&gt; since version %2$s! Use %3$s instead.&#039;), $function, $version, $replacement ) );
                                			else
                                				trigger_error( sprintf( __(&#039;%1$s is &lt;strong&gt;deprecated&lt;/strong&gt; since version %2$s with no alternative available.&#039;), $function, $version ) );
                                		} else {
                                			if ( ! is_null( $replacement ) )
                                				trigger_error( sprintf( &#039;%1$s is &lt;strong&gt;deprecated&lt;/strong&gt; since version %2$s! Use %3$s instead.&#039;, $function, $version, $replacement ) );
                                			else
                                				trigger_error( sprintf( &#039;%1$s is &lt;strong&gt;deprecated&lt;/strong&gt; since version %2$s with no alternative available.&#039;, $function, $version ) );
                                		}
                                	}</code>

                                Line 2908 specifically is:

                                trigger_error( sprintf( __('%1$s is <strong>deprecated</strong> since version %2$s! Use %3$s instead.'), $function, $version, $replacement ) );


                                Rob Orr

                                  March 28, 2014 at 6:18 am

                                  Here are the EE plugins we’re using, per your recommendations to do what we need to do, from our plugin dashboard:

                                  http://bit.ly/1dztMFH

                                  And also just for the record, we’re using a Genesis theme, not that that’s really important as the error was still present when we switched it to twenty ten.


                                  Dean

                                  • Support Staff

                                  March 28, 2014 at 7:00 am

                                  Is it possible to get your login details in order to look into this?

                                  If so, please send them via http://staging.eventespresso.com/send-login-details/

                                  NOTE: login details need to be Admin level and FTP details are appreciated.


                                  Rob Orr

                                    March 28, 2014 at 7:20 am

                                    Thanks Dean – I’ve sent all the pertinent login info to you. Let me know if you have any trouble.


                                    Josh

                                      March 28, 2014 at 10:50 am

                                      Hi Rob,

                                      I spent a fair amount of time troubleshooting this and this looks like a server issue to me. Which makes sense because nothing has changed in the Event Espresso software since the time this was working for you. The good news is I’m pretty sure I found which function was affected.

                                      Whatever did change on the server affected a function in Event Espresso that checks for whether an SSL certificate is installed for the domain. I added a little “Espresso overrides plugin” that disables the function and the payment settings page loads up fine.

                                      If anyone else starts experiencing the same issue they can make a little snippets plugin and add this function to it as a work around:

                                      if (!function_exists('espresso_check_ssl')) {
                                      	function espresso_check_ssl(){
                                      		return false;
                                      	}
                                      }
                                      Viewing 19 reply threads

                                      The support post ‘Payment Settings Not Available’ is closed to new replies.

                                      Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

                                      Event Espresso - Staging Server