|
hoffman
|
February 5, 2015 at 6:37 am
I migrated to 4.6.1 but selected the ‘delete option’ rather than migrating. It’s on a test server but after selecting a ticket and clicking on register the screen remains blank and hangs on the ?ee=process_ticket_selections. If I refresh I get this message http://screencast.com/t/UtiRQaaeV
|
|
Tony
|
February 5, 2015 at 7:14 am
Hi,
Are you running caching on your dev server?
If you enable WP_Debug and retest, is there an error message displayed on when the page was prvious blank?
|
|
hoffman
|
February 5, 2015 at 7:36 am
Hi
No I don’t run any WP caching plugins. I enabled WP debug and had a couple of warnings (both similar just different lines)
WARNING: wp-includes/functions.php:1056 – Cannot modify header information – headers already sent by (output started at /var/sites/t/testserver.nicholaspealldesign.com/public_html/wp-content/themes/dms/dms/header.php:17)
require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), include(‘/themes/dms/index.php’), setup_pagelines_template, get_header, locate_template, load_template, require_once(‘/themes/dms/header.php’), pl_get_core_header, require_once(‘/themes/dms/dms/header.php’), wp_head, do_action(‘wp_head’), call_user_func_array, EED_Single_Page_Checkout::nocache_headers, nocache_headers, header_remove
|
|
Tony
|
February 5, 2015 at 10:09 am
Can you try switching to one of the default themes such as twentyfourteen and retesting this?
|
|
Sidney Harrell
|
February 5, 2015 at 10:20 am
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
That cannot modify header information error is probably being caused by and error in the theme header on line 17. It’s only showing up because you turned on wp_debug, and probably does not have to do with the EE problems you are seeing. If you can instead use the above code in your wp-config file, then it should quiet that warning, and let you see the debug output in the file wp-content/debug.log
|
|
hoffman
|
February 5, 2015 at 11:25 am
I made the change in wp config and now have the debug file. This appears over and over:
[05-Feb-2015 18:22:05 UTC] PHP Notice: wpdb::prepare was called incorrectly. The query argument of wpdb::prepare() must have a placeholder. Please see Debugging in WordPress for more information. (This message was added in version 3.9.) in /var/sites/t/testserver.nicholaspealldesign.com/public_html/wp-includes/functions.php on line 3547
|
|
Sidney Harrell
|
February 5, 2015 at 11:44 am
That shouldn’t be coming from EE. We all run with debugging turned on, and should have noticed that. Can you deactivate EE and all it’s add-ons and see if you are still getting that error? The more straightforward way would be if there was php5-xdebug installed on the server, it would give a stack trace in addition to the error message, with exactly where the wpdb::prepare is being called incorrectly.
|
|
hoffman
|
February 5, 2015 at 11:54 am
The migration/upgrade to EE was the only change I made to this test installation. Note that I deleted the old version of the plugin before installing 4.6.1 then selected the migration with delete all data (it doesn’t delete everything). I can create a login if you want to take a look – I’m not that familiar with detailed debugging.
|
|
hoffman
|
February 5, 2015 at 1:28 pm
BTW I checked with my host and the php5-xdebug isn’t on the cloud hosting platform I use for this.
|
|
Josh
|
February 5, 2015 at 5:56 pm
It may help to update to the current version of EE, and you can also rule these out one by one:
1) A theme conflict. You can rule this out by temporarily switching to the default WordPress theme.
2) A plugin conflict. You can rule this out by temporarily deactivating any other installed WordPress plugins.
|
|
hoffman
|
February 6, 2015 at 2:10 am
Looks like the 4.6.4 fix you pushed out has sorted out the issue (I’ve never suffered from a theme or plugin conflict with EE)
Thanks
|
