“Attempt to read property” errors cause my dev site to break

Hi @nico23

Is it possible that you have custom code, or another plugin that is hooking in the edd_das_get_terms filter and passing data as an array?

According to the message that’s the most likely cause here as the line refers to term objects being in an array format instead of an Object.

I would recommend that you try to deactivate plugins except for EDD and even change the theme to a default one from WordPress to rule out this probable cause.

Just marking as “resolved” without any idea. Shady.

I was about to actually share some valuable info, but I guess not anymore.

Hey @nico23

We mark topics as resolved as soon as someone from our team posts a reply. It’s our way to know that a topic here on the forum has received a response.

Please provide any info you have and please check if you might have any custom code or another plugin that could be triggering this.

Your way hm. Yeah, shady AF as I said! Funny that you even admit this as opposed to a claim “no clue how that happened” I recently got from the SupportCandy folks, who also just marked my topic as resolved.

It says “resolved” and your shady practice is because this is how you FAKE your “resolved” topics display that is shown on your plugins page. This should be against wp.org rules.

Here is how I do it. I tell people to not use this forum and use the ticketing system on my site. People love to not read or straight up ignore it. So sometimes I mark questions as “not a support question”. Because I feel it unfair how they raise the “unsolved” number that way. This way, topics get removed from the counter completely. But if you do give support here, then do not do this shady shit!