Title: Table empty after editting Last modified: February 6, 2018 --- # Table empty after editting * Resolved [jvdb88](https://wordpress.org/support/users/jvdb88/) * (@jvdb88) * [8 years, 4 months ago](https://wordpress.org/support/topic/table-empty-after-editting/) * Hi, * After updating my table and update my page the table is suddenly empty. Same story on every page that contains a table. * Kind regards, * Jeroen * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ftable-empty-after-editting%2F%3Foutput_format%3Dmd&locale=en_US) to see the link]_ Viewing 5 replies - 1 through 5 (of 5 total) * Thread Starter [jvdb88](https://wordpress.org/support/users/jvdb88/) * (@jvdb88) * [8 years, 3 months ago](https://wordpress.org/support/topic/table-empty-after-editting/#post-9988553) * Hi Johann, * Nice! The plugin works for me. * Thanks a lot! * Greetings Jeroen * Thread Starter [jvdb88](https://wordpress.org/support/users/jvdb88/) * (@jvdb88) * [8 years, 3 months ago](https://wordpress.org/support/topic/table-empty-after-editting/#post-9988868) * Hi Johan, * Found a problem. When i want to add a field to AFC I get this: * Warning: strpos() expects parameter 1 to be string, array given in C:\xampp\htdocs\ Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\acf-table-v4.php on line 47 * Warning: json_decode() expects parameter 1 to be string, array given in C:\xampp\ htdocs\Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\acf-table- v4.php on line 50 * Warning: strpos() expects parameter 1 to be string, array given in C:\xampp\htdocs\ Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\acf-table-v4.php on line 47 * Warning: json_decode() expects parameter 1 to be string, array given in C:\xampp\ htdocs\Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\acf-table- v4.php on line 50 * Warning: strpos() expects parameter 1 to be string, array given in C:\xampp\htdocs\ Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\acf-table-v4.php on line 47 * Warning: json_decode() expects parameter 1 to be string, array given in C:\xampp\ htdocs\Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\acf-table- v4.php on line 50 * Warning: strpos() expects parameter 1 to be string, array given in C:\xampp\htdocs\ Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\acf-table-v4.php on line 47 * Warning: json_decode() expects parameter 1 to be string, array given in C:\xampp\ htdocs\Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\acf-table- v4.php on line 50 * Warning: strpos() expects parameter 1 to be string, array given in C:\xampp\htdocs\ Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\acf-table-v4.php on line 47 * Warning: json_decode() expects parameter 1 to be string, array given in C:\xampp\ htdocs\Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\acf-table- v4.php on line 50 * Warning: strpos() expects parameter 1 to be string, array given in C:\xampp\htdocs\ Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\acf-table-v4.php on line 47 * Warning: json_decode() expects parameter 1 to be string, array given in C:\xampp\ htdocs\Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\acf-table- v4.php on line 50 * Warning: strpos() expects parameter 1 to be string, array given in C:\xampp\htdocs\ Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\acf-table-v4.php on line 47 * Warning: json_decode() expects parameter 1 to be string, array given in C:\xampp\ htdocs\Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\acf-table- v4.php on line 50 * Warning: strpos() expects parameter 1 to be string, array given in C:\xampp\htdocs\ Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\acf-table-v4.php on line 47 * Warning: json_decode() expects parameter 1 to be string, array given in C:\xampp\ htdocs\Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\acf-table- v4.php on line 50 * Warning: strpos() expects parameter 1 to be string, array given in C:\xampp\htdocs\ Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\acf-table-v4.php on line 47 * Warning: json_decode() expects parameter 1 to be string, array given in C:\xampp\ htdocs\Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\acf-table- v4.php on line 50 * Warning: strpos() expects parameter 1 to be string, array given in C:\xampp\htdocs\ Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\acf-table-v4.php on line 47 * Warning: json_decode() expects parameter 1 to be string, array given in C:\xampp\ htdocs\Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\acf-table- v4.php on line 50 * Warning: strpos() expects parameter 1 to be string, array given in C:\xampp\htdocs\ Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\acf-table-v4.php on line 47 * Warning: json_decode() expects parameter 1 to be string, array given in C:\xampp\ htdocs\Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\acf-table- v4.php on line 50 * Warning: Cannot modify header information – headers already sent by (output started at C:\xampp\htdocs\Tyfoon\wp-content\plugins\advanced-custom-fields-table-field\ acf-table-v4.php:50) in C:\xampp\htdocs\Tyfoon\wp-includes\pluggable.php on line 1216 * Moderator [Jan Dembowski](https://wordpress.org/support/users/jdembowski/) * (@jdembowski) * Forum Moderator and Brute Squad * [8 years, 3 months ago](https://wordpress.org/support/topic/table-empty-after-editting/#post-9989439) * NUTS. Now I need to review and redact all of [@jonua](https://wordpress.org/support/users/jonua/) replies. * [@jvdb88](https://wordpress.org/support/users/jvdb88/) Please excuse me while I chat with the author. * [@jonua](https://wordpress.org/support/users/jonua/) I’ve deleted your offer to login to your user’s site. I’m am 100% sure you mean well but please _never ask for credentials on these forums._ * [https://wordpress.org/support/guidelines/#the-bad-stuff](https://wordpress.org/support/guidelines/#the-bad-stuff) * Now for the why: The internet is a wonderful place full of very nice people and a few very bad ones. I’m sure everyone here is very nice however, by giving some ones keys to your house you are trusting they wont steal anything. Likewise the person who takes the keys is now responsible for the house FOREVER. * If something was to go wrong, then you the author may well legally become liable for damages, which they would not normally have been as their software is provided without warranty. * **Please be aware that repeatedly asking for credentials will result in us asking you to repeatedly stop before escalating up to the plugins team.** * There are many ways to get information you need and accessing the user’s site is not one of them. That’s going too far. - Ask for a link to the [http://pastebin.com/](http://pastebin.com/) log of the user’s web server error log. - Ask the user to create and post a link to their `phpinfo();` output. - Ask the user to install the [Health Check plugin](https://wordpress.org/support/plugin/health-check/) and get the data that way. - Walk the user through [enabling WP_DEBUG and how to log that output to a file and how to share that file.](https://codex.wordpress.org/WP_DEBUG#WP_DEBUG_LOG_and_WP_DEBUG_DISPLAY) - Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again. - Ask the user for the step-by-step on how they can reproduce the problem. * You get the idea. * Volunteer support is not easy. But these forums need to a safe place for all users, experienced or new. Accessing their system that way is a short cut that will get you into real trouble in these forums. * Please reply to this topic [@jonua](https://wordpress.org/support/users/jonua/) to confirm that you understand this prohibition against asking for login access. - This reply was modified 8 years, 3 months ago by [Jan Dembowski](https://wordpress.org/support/users/jdembowski/). * Plugin Author [Johann Heyne](https://wordpress.org/support/users/jonua/) * (@jonua) * [8 years, 3 months ago](https://wordpress.org/support/topic/table-empty-after-editting/#post-9989535) * I´m sorry Jan, * yes, now I understand this prohibition against asking for login access now. * Thanks for the important note! Johann * Plugin Author [Johann Heyne](https://wordpress.org/support/users/jonua/) * (@jonua) * [8 years, 3 months ago](https://wordpress.org/support/topic/table-empty-after-editting/#post-9989655) * Hi Jeroen, * I found the issue in the new plugin´s version code and put it right. Unfortunately I´m not sure now, if I´m allowed to post that temporarily plugin download link again. May I ask Jan? * Thanks! Johann Viewing 5 replies - 1 through 5 (of 5 total) The topic ‘Table empty after editting’ is closed to new replies. * ![](https://ps.w.org/advanced-custom-fields-table-field/assets/icon-256x256.png? rev=1962986) * [Table Field Add-on for ACF and SCF](https://wordpress.org/plugins/advanced-custom-fields-table-field/) * [Frequently Asked Questions](https://wordpress.org/plugins/advanced-custom-fields-table-field/#faq) * [Support Threads](https://wordpress.org/support/plugin/advanced-custom-fields-table-field/) * [Active Topics](https://wordpress.org/support/plugin/advanced-custom-fields-table-field/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/advanced-custom-fields-table-field/unresolved/) * [Reviews](https://wordpress.org/support/plugin/advanced-custom-fields-table-field/reviews/) * 5 replies * 3 participants * Last reply from: [Johann Heyne](https://wordpress.org/support/users/jonua/) * Last activity: [8 years, 3 months ago](https://wordpress.org/support/topic/table-empty-after-editting/#post-9989655) * Status: resolved