Hi Charles,
Are you getting this error from the wpdadiehard shortcode? Or the wpdataaccess shortcode? Shortcode wpdadiehard Can you add a screenshot?
Best regards,
Peter
Hi Peter,
I getting this error from the wpdadiehard shortcode.
“order_list” is table’name.
https://prnt.sc/qsoppr
I currently don’t have an active wpdadiehard shortcode in use. I suspended work on a project front-end as I was in the middle of site migration and had a work around using old code. I intend to implement when your next release comes out.
Sorry I can’t help.
But…I had a similar error show up a week ago when I used two standard wpdataaccess short codes on the same page. I redesigned to avoid the problem.
BTW I’ll be offline until Sunday
Hi Charles,
The plugin runs into this error when output is directly echoed to the screen. With the new editor this is no longer allowed. Output must be returned. I tought this error was fixed. I cannot reproduce it on my computer with the latest version of WP and the plugin.
Which version of the plugin are you using? And which WordPress version? Does the page show the expected shortcode output?
Best regards,
Peter
I’m using WP 5.3.2 and WPDA 2.1 and, when possible, the block editor. It is working for me with single short code on a page. It does not like two of your shortcodes on a page. But I am not relying on that at the moment.
I will be offline for a few days starting later today.
Hello Peter,
I am having the same problem, even with one single [wpdadiehard] shortcode on a page.
I receive the same error message (of course in German):
“Aktualisierung fehlgeschlagen. Fehlermeldung: Die Antwort ist keine gültige JSON-Antwort.”
[wpdataaccess], however, is working fine.
Best regards
Michael
Hi Michael,
You are on the latest releases and you’re still having this error. Can you give me some more info? Which Theme and editor are you using? I cannot reproduce this error and my computer. I would be grateful if you could give me some more info so that I can reproduce the error and fix it. Thanks in advance!
BTW, in the next version you add as many wpda shortcodes to a page as you like. You can even add two jQuery DataTables to a page using the same base table.
But let’s fix this fist… 🤔
Best regards,
Peter
Hi Peter,
thanks for your fast response and apologies for my late answer – just arrived back from today’s business trip…
I am using “Pure Simple” theme as a child version. Straight forward with my own functions.php and a style.css also referring to the theme’s own one.
I have >40 registered choir members with different roles, a number of plugins including a partially self-written kind of “Doodle®” version and other databases in use. I am using jQuery and AJAX to replace just part of some pages, even by use of shortcode returns – everything working just fine.
So, in a way, I know what I am doing…
I have just tried everything (static, parent/child, table) with nothing else but trying wpdadiehard as a single shortcode on a new page instead of the wpdataaccess, which comes from the publisher.
(By the way, I have not yet been able to make static pages work in posts like you do in one of your videos – I am getting just a white page…).
So, when using the wpdadiehard shortcode I get the JSON error…
With or without having it in the backend menu…
If I nevertheless open the page, I receive a PHP error message:
call to undefined function …/wpdadiehard_convert_to_screen()
Is there eventually any prerequisite I forgot?
Best regards
Michael
Here is it:
Fatal error: Uncaught Error: Call to undefined function WPDataAccess\Wordpress_Original\wpdadiehard_convert_to_screen() in …/wp-content/plugins/wp-data-access/WPDataAccess/Wordpress_Original/WP_List_Table.php:160 Stack trace: #0 …/wp-content/plugins/wp-data-access/WPDataAccess/List_Table/WPDA_List_Table.php(350): WPDataAccess\Wordpress_Original\WP_List_Table->__construct(Array) #1 …/wp-content/plugins/wp-data-access/WPDataProjects/List_Table/WPDP_List_Table_Lookup.php(53): WPDataAccess\List_Table\WPDA_List_Table->__construct(Array) #2 …/wp-content/plugins/wp-data-access/WPDataProjects/List_Table/WPDP_List_Table.php(43): WPDataProjects\List_Table\WPDP_List_Table_Lookup->__construct(Array) #3 …/wp-content/plugins/wp-data-acc in …/wp-content/plugins/wp-data-access/WPDataAccess/Wordpress_Original/WP_List_Table.php on line 160
Hi Michael,
Thank you for the detailed information! I now understand it is missing the wpdadiehard_convert_to_screen() function. Not sure yet what the cause of the error is, but at least I know where to look at… 👀
I see what I can do and come back to you asap…
Best regards,
Peter
Hi Michael,
Your info might have helped me to solve the issue very quickly… I hope!
I patched the current version (2.7.3). Can you try to update?
You need to delete the plugin first. Before you do make sure you first unselect the checkboxes under “Uninstall” on the plugin settings page. Otherwise the plugin repository will be deleted when you uninstall.
Let me know if the problem is solved…
Best regards,
Peter
Hi Peter,
thanks a lot!
The json error is gone ;-))).
Now I do have the same (incorrect) behavior as in my other 1:n relation issue posted above…
There are a few other things:
1. There is obviously some CSS behind your wpdadiehard-shortcode, which changes most (not all) of my …a href=… links to a blueish color.
2. It will not work (editing and next-page) in page draft mode, the page needs to be published.
3. Like in the back-end, even if you say no-delete, which works for the very table, you will be able to delete the entries in the tables referred to by 1:n.
4. If the table referred to by 1:n has more than one page, sometimes, next page doesn’t word there (like in the backend).
Best regards
Michael
Hi Peter,
and one thing:
In the wpdadiehard frontend appearance, I see functional interference with another plugin called “WP Photo Album Plus” (uses often wppa in its names).
I am using a running filmonly-slideshow in the Banner of my theme, which is influenced by your shortcode (won’t move any more and the Lightbox behavior is different).
Maybe a typo somewhere (wpda vs. wppa)?
Best regards
Michael
Hi Michael,
I checked the project files, there is no wppa string in WP Data Access. Might still be a typo! In wppa… 😉
Best regards,
Peter
