jcmplastics

My project transfer from test to production domain was done manually as follows:

1. Copied Wp_Contents.
2. Copied Wp-config – modified with new schema and password.
3. Exported complete site SQL in phpMyAdmin.
4. Fresh WP Install at production site.
5. Delete New and install Old Wp_Contents file.
6. Replaced wp-config with modified Wp-config.
7. Dropped new schema tables and uploaded transferred schema tables.
8. Modified wp-options with the two domain url fields and the uploads folder domain.

Upon opening new site, schema error came up.
To Resolve issue:
1. Exported in phpMyAdmin all the wpdataaccess tables.
2. Opened in Notepad and did a find and replace all old schema to new schema.
3. Dropped existing wpdataaccess tables and imported modified wpdataaccess tables.
Issue resolved.

If there was and option to “Set” the schema when manually transferring from a test to production domain, or copy install to new project, that would be really helpful. A lot of my projects may have a similar or reusable data structures – why reinvent the wheel? Your current process is nice if you just want to export one or two processes and data, but too time consuming for a complete migration or fresh install with data transfer.

– Jack

I wanted to do a follow-up.

Peter has been so helpful and responsive on any technical issues I’ve had – he’s a rare breed and truly appreciate all his help.

Result and Resolution:
1. The Where clause does not work on “parent” pages – Only on Child pages.
2. Parent/Child pages were created and on page 2 (the child page) where clause was entered and worked.
3. At front-end web page level using the “[wpdataaccess “”] shortcode (Viewing only) – the where statement codes work fine.
4. At front-end web page level using the “[wpdadiehard “”] shortcode (Edit Mode) – the where statement codes are not working. Peter said he will fix and next release.

Hope this helps.

A huge thanks to Peter for his commitment and dedication to this project! He’s an Awesome person.

I’m going to leave this open for now in case Peter wants to make any final comments before closing…

– Jack

• This reply was modified 5 years, 10 months ago by jcmplastics.

I can’t show you the result set screenshot because it has some client data (PID data), but I can get a full result recordset using the above code you are using, and I also get a full result using the shortcode I posted, just doesn’t implement the where clause.

If I add the Where clause at the page level, I get an “empty” recordset on both the front-end and back-end.

Maybe I can post some screen shots with the PID data cropped off…

– Jack

Hi Peter,

I went to:
Wp Data Access > Data Projects
Under Manage Projects > Edit Proj 1
Pages > Edit Page 1
Enter Where Clause at the Bottom
Result: Empty Dataset

I even tried at the front-end page level for editing with:
[wpdadiehard project_id=”1″ page_id=”1″ filter_field_name=”Client_Approved” filter_field_value=”approved”]
Result: Full dataset result and “Pending” record appears in the recordset.

However, using the following at the front-end page level, I get a proper result with only approved records – but no editing capabilities:
[wpdataaccess pub_id=”1″ table=”Wp_Client_CRM” filter_field_name=”Client_Lead_Approved” filter_field_value=”approved” sql_orderby=”Entry_Date,desc”]
Note: I get no order by result – not sure if statement is properly coded for the result.

– Jack

• This reply was modified 5 years, 10 months ago by jcmplastics.

Resolved

I figured it out, Peter. I “fat brained” reading the instructions.

For “displaying” the data tables, use [wpdataaccess table=””]
For “editing” data tables, use [wpdadiehard table_name=””]

Following this, everything works as designed… And noting there are different arguments you can use depending on which statement and purpose above that you are needing.

Thanks for your quick response and amazing work and dedication on the plugin. By the way, your videos excellent and very well presented and informative. Keep up the great work you do!

Best Regards,

– Jack