|
Jonathan Martin
|
October 31, 2012 at 11:50 am
Hi, I am having an issues that seems common on the forums. I’ve followed all the steps I can find, but to no avail:
When I try to log in via the mobile app (on Android), I get a message saying “Fetching Events” and it just hangs.
I have upgraded Event Espresso to 3.1.27.1.P, upgraded the Ticketing Add-On to version 2.0.7, Uploaded the newest version of the /event-services/ folder to the root of the site and set the permissions to 755 (also tried 777 on folder and all files, with no luck).
I noticed that if I go to /event-espresso/index.php in the browser, I do get the message showing, but /event-espresso/events.php just gives me a 500 error.
Not sure what to do next 🙁 Any help would be amazing!
|
|
Josh
|
October 31, 2012 at 12:01 pm
Hi Jonathan,
Is this a multi-site installation?
What happens if you navigate your browser to yoursite.com/espresso-services/ ?
|
|
Jonathan Martin
|
October 31, 2012 at 12:10 pm
Nope, just a single-site installation.
At yoursite.com/espresso-services/ I get a message:
This site is being powered by Event Espresso’s mobile ticketing application!
Seems to be correct?
|
|
Josh
|
October 31, 2012 at 2:34 pm
Yes, that’s what should happen. Can you verify that the xml-rpc publishing feature is enabled in WordPress>Settings>Writing?
|
|
Jonathan Martin
|
October 31, 2012 at 2:50 pm
Yeah, I have that checked. Enabling that allowed me to at least log in via the Android App, just not getting any activity after log-in. Just the “Fetching Events” message.
🙁
|
|
Josh
|
November 1, 2012 at 7:48 am
Hi Jonathan,
We will need access to the site to investigate this further.
Can you send WordPress admin level and FTP log in credentials via the contact form on this page?
https://eventespresso.com/contact/
If so, please select the “I am sending login info as requested” department form when you send this.
|
|
Josh
|
November 1, 2012 at 3:59 pm
Hi Jonathan,
The credentials you sent did not include FTP credentials, so I wasn’t able to access the espresso-services directory. The only thing I could find by logging into the WordPress site that could be an issue is it’s forcing the admin to load in SSL, but there are problems with the certificate.
Clicking on the pad lock revealed this:
The identity of this website has not been verified. • Server’s
certificate does not match the URL. • Server’s certificate is not
trusted.
So this may or may not be a factor, but should be addressed either way.
In order to investigate further, we’ll need FTP credentials. Is it possible for you to send that via the same form?
|
|
Josh
|
November 2, 2012 at 2:43 pm
Hi Jonathan,
The FTP credentials that you sent were read-only, so while I could verify that the espresso-services files were in the correct location, I could not try to make any adjustments to the mobile app files.
My recommendation at this point is to try disabling the force admin SSL directive in wp-config.php for the time being until you can get the SSL certificate domain issue sorted out. This issue may be affecting the mobile app.
So if you have FTP write acces to the server you can change this line in wp-config.php from this:
define('FORCE_SSL_ADMIN', true);
to:
#define('FORCE_SSL_ADMIN', true);
Then you can try logging into the mobile app again to see if that makes a difference.
|
|
Jonathan Martin
|
November 5, 2012 at 9:50 am
Hey Josh, thanks for the response!
I tried commenting out the FORCE_SSL_ADMIN line, still stuck on ‘Fetching Events’ in the app 🙁 I’m now just getting a white screen when I go to /espresso-services/events.php.
I did notice one thing: I turned on PHP error reporting in events.php and get the following:
“Deprecated: Assigning the return value of new by reference is deprecated in /usr/share/wordpress/wp-settings.php on line 646 Deprecated: Assigning the return value of new by reference is deprecated in /usr/share/wordpress/wp-settings.php on line 661 Deprecated: Assigning the return value of new by reference is deprecated in /usr/share/wordpress/wp-settings.php on line 668 Deprecated: Assigning the return value of new by reference is deprecated in /usr/share/wordpress/wp-settings.php on line 675 Deprecated: Assigning the return value of new by reference is deprecated in /usr/share/wordpress/wp-settings.php on line 711 Deprecated: Function set_magic_quotes_runtime() is deprecated in /usr/share/wordpress/wp-settings.php on line 18 Fatal error: Cannot redeclare class wpdb in /var/www/www.cafemox.com/wp-includes/wp-db.php on line 52”
The final error seems to be the one crashing the script…Not sure what is causing it however. It seems strange that I would be getting such an error with the standard api package, but maybe it could give you an idea?
|
|
Josh
|
November 5, 2012 at 4:20 pm
“Cannot redeclare class” would suggest that it’s already declared elsewhere in the core WordPress files. Was there a recent core upgrade that may not have completed successfully?
You could try manually updating WordPress:
http://codex.wordpress.org/Updating_WordPress#Manual_Update
|
|
Jonathan Martin
|
November 5, 2012 at 5:54 pm
Aha!
I noticed some out of date lines in the wp-config file during the upgrade. I just overwrote some of the standard settings with ones out of the new wp-config file and it works!
Not sure which specific setting it was that did the trick, but I’m not complaining… 🙂
|
