Title: Update Errors 2.2.19
Last modified: November 7, 2017

---

# Update Errors 2.2.19

 *  [yourbudweiser](https://wordpress.org/support/users/yourbudweiser/)
 * (@yourbudweiser)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/update-errors-2-2-19/)
 * After updating to 2.2.19 from an older version, I am getting multiple errors 
   on the Plugin page.
 * Warning: Invalid argument supplied for foreach() in /home/xxxxx/public_html/wp-
   content/plugins/types/vendor/otgs/installer/includes/class-wp-installer.php on
   line 308
 * and
 * Warning: Invalid argument supplied for foreach() in /home/xxxxx/public_html/wp-
   content/plugins/types/vendor/otgs/installer/includes/class-wp-installer.php on
   line 2255
 * WordPress: 4.8.3
    PHP Version: 5.6.32 Types Version: 2.2.19
 * Error log only shows the errors listed above.

Viewing 6 replies - 1 through 6 (of 6 total)

 *  Anonymous User 14808221
 * (@anonymized-14808221)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/update-errors-2-2-19/#post-9661816)
 * I know about this and even if I cannot replicate, I know from the code-logic 
   point of view why it happens.
 * I am pushing our developers for an immediate fix. Please await my new here.
 *  Thread Starter [yourbudweiser](https://wordpress.org/support/users/yourbudweiser/)
 * (@yourbudweiser)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/update-errors-2-2-19/#post-9662855)
 * Thanks Beda.
 * While I am waiting, I have other WordPress sites to update and many of them use
   older versions of Types.
 * For example, on one site, the installed version of Types is Version 1.6.4. Should
   I hold off on updating Types to the latest version? Will I be able to update 
   it once you provide the fix?
 *  [polazhenko](https://wordpress.org/support/users/polazhenko/)
 * (@polazhenko)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/update-errors-2-2-19/#post-9664609)
 * I have also problems with this update, but in my case site shows white death 
   page with text:
 * Warning: require_once(/var/www/brugge/wp-content/plugins/types/vendor/toolset/
   toolset-common/toolset-forms/classes/class.cred.php): failed to open stream: 
   No such file or directory in /var/www/brugge/wp-content/plugins/wp-views/embedded/
   inc/wpv-conditional.php on line 768
 * Fatal error: require_once(): Failed opening required ‘/var/www/brugge/wp-content/
   plugins/types/vendor/toolset/toolset-common/toolset-forms/classes/class.cred.
   php’ (include_path=’.:/usr/share/php:/usr/share/pear’) in /var/www/brugge/wp-
   content/plugins/wp-views/embedded/inc/wpv-conditional.php on line 768
 * For a long time plugins were not able to be updated, but few days ago i was succeded
   with it’s update i whish i don’t.
 *  Anonymous User 14808221
 * (@anonymized-14808221)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/update-errors-2-2-19/#post-9665535)
 * [@polazhenko](https://wordpress.org/support/users/polazhenko/) the issue you 
   report is not related to Toolset Types free Plugin.
    Please use the [Paid Support Forum](https://wp-types.com/forums/forum/professional-support/)
   for issues surging together with the paid Toolset (in your case, Types, _CRED
   and Views_).
 * [@yourbudweiser](https://wordpress.org/support/users/yourbudweiser/) You an updated
   even now.
    Just disable the WP Debug constant or ignore that error on the plugin’s
   page. This error should not break any functionality.
 * It is only a warning. And you do not need that code necessarily to use Toolset.
   
   What can be is that automatic updates might present issues. In that case please
   update manually using the FTP.
 * As for the functionality of the plugin this should not affect any thing.
 * I will update you here as soon we have a fix.
 *  Thread Starter [yourbudweiser](https://wordpress.org/support/users/yourbudweiser/)
 * (@yourbudweiser)
 * [7 years, 11 months ago](https://wordpress.org/support/topic/update-errors-2-2-19/#post-10217488)
 * Hello, I was hoping that this error would have been fixed by now.
 * I am getting the following errors (over 800 of them) on the plugin page. I am
   unable to hide them, even with debug false:
 * Warning: Invalid argument supplied for foreach() in
    /plugins/types/vendor/otgs/
   installer/includes/class-wp-installer.php on lines 303 and line 305
 * and
 * Warning: Invalid argument supplied for foreach() in /plugins/types/vendor/otgs/
   installer/includes/class-wp-installer.php on lines 2289 and 2291
 * The site is currently using an older version of WordPress and Toolset Types Version
   2.2.23.
 *  Anonymous User 14808221
 * (@anonymized-14808221)
 * [7 years, 11 months ago](https://wordpress.org/support/topic/update-errors-2-2-19/#post-10217539)
 * [@yourbudweiser](https://wordpress.org/support/users/yourbudweiser/), there is
   a fix to be released soon for this:
    [https://wordpress.org/support/topic/class-wp-installer-php-issue/](https://wordpress.org/support/topic/class-wp-installer-php-issue/)

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Update Errors 2.2.19’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/types_ced1d3.svg)
 * [Toolset Types - Custom Post Types, Custom Fields and Taxonomies](https://wordpress.org/plugins/types/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/types/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/types/)
 * [Active Topics](https://wordpress.org/support/plugin/types/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/types/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/types/reviews/)

## Tags

 * [errors](https://wordpress.org/support/topic-tag/errors/)
 * [toolset](https://wordpress.org/support/topic-tag/toolset/)
 * [update](https://wordpress.org/support/topic-tag/update/)
 * [update errors](https://wordpress.org/support/topic-tag/update-errors/)

 * 6 replies
 * 3 participants
 * Last reply from: Anonymous User 14808221
 * Last activity: [7 years, 11 months ago](https://wordpress.org/support/topic/update-errors-2-2-19/#post-10217539)
 * Status: not resolved