Hi Kyle,
This might be related to an issue with version 4.2.6. Can you please updated to 4.2.7 to see if this fixes your problem?
Thanks,
Peter
Hello Peter,
Thank you for the quick response. I have updated to version 4.2.7 and the problem persists. Any idea why only the published version of the page (not logged into a wordpress account) is the only part that does not load all the tables? I have done some developer tools troubleshooting and it appears that only the first (5) tables pass any JSON while the remaining pass nothing. If I change the order of the tables in the page, it continues to only load the first (5) of the (9) tables. The website otherwise loads and works perfectly as expected while one is logged into the wordpress account…
Thank you for you time,
Kyle
Hi Kyle,
Are you using any environment variables in the default where clause of those publications?
Thanks,
Peter
Hi Peter,
If I am understanding correctly, we only use the following in the data publisher for each table:
WHERE Clause: dw_literary_lions = ‘$100,000 Carnegie’
Table Options: `{ “dom”: “ftip”,
“language”: {
“info”: “Showing _START_ to _END_ of _TOTAL_ donors”,
“infoFiltered”: “”
},
“serverSide”:false
}`
For the (9) tables the Table Options are the same, the WHERE Clause is slightly different in each; “$100,000 Carnegie”/”$50,000 Carnegie”/”$25,000 Cranegie”/etc
Thank you,
Kyle
Thanks Kyle!
Can you please enable debug mode?
> Go to Settings > WP Data Access > Plugin
> Enabled debug mode and save
After that you can view the response in your browser to see the query that is actually performed.
Please let me know…
Peter
Hi Peter,
I have made the change to enable Debug Mode, what/where is the information we are exactly looking for?
Thank you,
Kyle
Hi Kyle,
Please open the inspector in your browser and click on the Network tab. Then refresh the page and look for the response starting with admin-ajax.php.
When you look into the response you’ll see that the plugin debugger adds a debug node. The debug node contains a query node. Please check the query to see what’s wrong.
I can’t reproduce this error anymore. The publication returning an error are now gone when I view the page.
Please let know…
Peter