search

downshiftorg / prophoto7-issues

A current roadmap and bug tracking for ProPhoto 7
1 stars 0 forks source link

P7 activation/initialization fails when test-driving P5 #58

Open mdietsche opened 6 years ago

mdietsche commented 6 years ago

Issue by postmastersteve Tuesday May 29, 2018 at 14:33 GMT Originally opened as https://github.com/downshiftorg/prophoto/issues/3381

This Github issue is synchronized with Zendesk:

Ticket ID: #181387 Priority: high Group: Developers Requester: matt@pro.photo Organization: DownShift Issue escalated by: Matt Dietsche

Original ticket description:

Seems like P7 legacy import is treating P5 like it's P6: 

WordPress database error Table 'kandian1_wrd1.wp_pp_customizations' doesn't exist for query SELECT settings FROM wp_pp_customizations WHERE id= 'site-settings' made by require('wp-blog-header.php'), wp, WP->main, WP->parse_request, do_action_ref_array, WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, rest_api_loaded, WP_REST_Server->serve_request, WP_REST_Server->dispatch, call_user_func, ProPhoto\LegacyImport\Rest\ListDesigns->listDesigns

Matt Dietsche
ProPhoto Support

Follow us for the latest ProPhoto news and updates:
https://www.twitter.com/prophotoblogs/

mdietsche commented 6 years ago

Comment by postmastersteve Tuesday May 29, 2018 at 15:24 GMT

Comment made from Zendesk by Josh Arens on 2018-05-29 at 15:24:

This is happening on sites that never had p6 installed - there's a bad query being run but it will never run on sites that have p6 and is totally harmless on other sites.