Check if there is an editor present before trying to add buttons to it about tablepress

[TobiasBg]

Thanks for your bug report, and sorry for the trouble.
I can imagine that removing the editor can cause trouble with the buttons then being added, but I have no real clue how this should result in the error/notice that you posted. At best, it should result in a JavaScript error...
Therefore (and because I can't check the WP-Views source code), I'd like to take a direct look at this on your site. Could you therefore please create a temporary admin account for me and send me the details via email (the address is in the main plugin file "tablepress.php")? That way, I can investigate this directly. Thanks!

[Willem-Siebe]

I will do!

[TobiasBg]

So far, I have not received an email for you, unfortunately. Can you maybe send it again?

[Willem-Siebe]

Hi, you have received email, I gave you super admin rights to the network and added you on the specific site (klepbankonline dot nl). I also can create a staging area for you since this is my livesite. So if you are going to do more then just 'look', please let me know. Staging area is already available, only somebody else is debugging there right now for other problem.

[TobiasBg]

Thanks for the account! I was able to log in and checked a few things, but can't really see any errors that are related to TablePress in particular. Can you maybe give me directions on how I can see those errors that are presumably caused by TablePress?

[Willem-Siebe]

Hi Tobias,

In the menu from WP backend you find 'CRED'. If you go there and click on 'Forms' > then choose one of the Forms there and then on top you get the warning.

I actually mistaked about the website, so sorry! On klepbankonline{dot}nl I don't have any CRED forms yet! The problem is visible on caesarsbeauty{dot}nl > I will send you new login details. If you need to do more then just look, please let me know so I create a staging area for you since this is a livesite.

[TobiasBg]

Ah, thanks! :-) Now I can see the error (on the new site). Unfortunately though, I have no clue how TablePress could be causing this, or how to fix it. I'm not saying that TablePress is "innocent" here, but I just don't see a way right now to prevent this in TablePress. TablePress is already making sure to only load its editor buttons on pages that have an editor (by using the WordPress action hooks for that).

Instead, the WP Views plugin should fix this notice by adding a check whether the $post->post_type property that they are trying to access in the mentioned line of code in the notice really exists.

Of course, if someone knows a fix for this in TablePress, I'm more than willing to add it!

[Willem-Siebe]

I will post your reply to them. I know that normally they are willing to communicate with other developers as well. Thanks so far, I will send you an update with their reply.

[TobiasBg]

Yes, that would be great! Maybe they can spot a solution.
If not, and as you seem to be experiencing this on a production site right now, I recommend to turn off WP_DEBUG there, to not be bothered by the notice.