Errors in 2.2.16

I don’t see that error on my or other installs.

It is eventually due to the list of Plugins returned by the Installer.
But this code makes no problems in my Local tests.

Could you try one thing?
Delete the FTP file of the Types plugin and replace it with a manually downloaded copy from the repository:
https://www.ads-software.com/plugins/types/

Does that solve the issue?
If not, I am afraid I have once more to redirect you to our own Forum, where I can ask for a Site’s Snapshot.
It’s free.

Thanks!

Hi, thanks for your response.

Unfortunately I receive the same error when I upload from a manually downloaded version vs. upgrading from within wordpress.

Rolling back to an earlier install did solve the issue for now. I will have a look at your company’s forums and follow up.

Thanks!

Yes, please, this is really important to be looked at.

In my local tests this does not happen, but I suspect it can be due to for example a modified Plugins location folder, or other, uncommon, WordPress paths.

If the code finds no plugin, it returns no array, and hence, the error.
And we should probably check that better in the code, I will immediately inform the DEV in regard, even if I cannot yet replicate it.

It would be very nice to have a Duplicator of the site to look at it

• This reply was modified 7 years, 3 months ago by Anonymous User 14808221.

I have got the same errors like @insaneyjaney since version 2.2.14, last version without them is 2.2.13

FYI @keramzyt Since my last post, the issue has resolved, although I wasn’t on-point enough to determine exactly when.

I am now running Toolset Types V 2.2.16 with WordPress 4.8.2 and the issue has cleared. I am also (and always have been) running my wordpress install in a subdirectory, rather than on the site root. Based on @bedas previous response, I’m thinking perhaps that had initially caused the issue with the plugin which may now have been resolved by support.

I am unfortunately not able to confirm that we consciously shipped a fix for this.

In fact, my internal tracking ticket is not yet replicated, hence not solved either.

I am happy that this is solved for you, still in case you have any issue regarding this coming back, or can share specific replication steps, I would be passing those details immediately to the Developers for further looks at it.

Right now, we are in the process of adding some checks in the code to make it safer – means, the theoretical possibility of this error will be avoided.

I cannot state an ETA yet.

Please let me know any issue you might have regarding this topic.

Hi @bedas.

I’m recently having the same problem. Is there anything I can do while this is being fixed?

Can I, for example, install an older version of this plugin? Where Can I find it?