Title: eduwebdev's Replies | WordPress.org

---

# eduwebdev

  [  ](https://wordpress.org/support/users/eduwebdev/)

 *   [Profile](https://wordpress.org/support/users/eduwebdev/)
 *   [Topics Started](https://wordpress.org/support/users/eduwebdev/topics/)
 *   [Replies Created](https://wordpress.org/support/users/eduwebdev/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/eduwebdev/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/eduwebdev/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/eduwebdev/engagements/)
 *   [Favorites](https://wordpress.org/support/users/eduwebdev/favorites/)

 Search replies:

## Forum Replies Created

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

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[The Events Calendar] tribe_get_events returns empty array on multisite switch_to_blog after upgrade](https://wordpress.org/support/topic/tribe_get_events-returns-empty-array-on-multisite-switch_to_blog-after-upgrade/)
 *  Thread Starter [eduwebdev](https://wordpress.org/support/users/eduwebdev/)
 * (@eduwebdev)
 * [2 years ago](https://wordpress.org/support/topic/tribe_get_events-returns-empty-array-on-multisite-switch_to_blog-after-upgrade/#post-17741598)
 * Hi Darian,
 * Thanks for the feedback. I had run the events upgrade multiple times on local
   test/staging servers, but it always stops in the preview scan with no errors 
   and about 24 events left to scan. Assuming this might be the issue based on your
   comments and other threads, I deleted hundreds of old drafted events (we had 
   nearly 3,000 events), emptied the trash, and finally got the preview to complete.
   This identified 50+ events that failed to migrate, so I deleted those and emptied
   the trash. This time the preview completed, and then I was able to complete the
   migration. I will test this on our public staging server environment that matches
   the live site environment more closely and see if it works on there.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Font Awesome] Multisite Support Available in Pre-release 4.3.0-1](https://wordpress.org/support/topic/multisite-support-available-in-pre-release-4-3-0-1/)
 *  [eduwebdev](https://wordpress.org/support/users/eduwebdev/)
 * (@eduwebdev)
 * [3 years, 9 months ago](https://wordpress.org/support/topic/multisite-support-available-in-pre-release-4-3-0-1/#post-15912043)
 * Yes, the plugin version 4.3.0-1 works as expected after cleanup.
 * The fatal error occurred in the admin dashboard immediately after clicking Network
   Activate, after installing the plugin via the zip file upload, on the multisite
   installation that had 4.2.0 installed but deactivated at the time.
 * I also just tested the plugin on a public staging environment running WordPress
   6.0.1 and PHP 7.4 that did not previously have any version installed. This fresh
   install is also working as expected.
 * You are correct about the rest_enabled filter: something else changed in my environment
   that I did not catch.
 * Thanks for the explanation about the multisite features.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Font Awesome] Multisite Support Available in Pre-release 4.3.0-1](https://wordpress.org/support/topic/multisite-support-available-in-pre-release-4-3-0-1/)
 *  [eduwebdev](https://wordpress.org/support/users/eduwebdev/)
 * (@eduwebdev)
 * [3 years, 10 months ago](https://wordpress.org/support/topic/multisite-support-available-in-pre-release-4-3-0-1/#post-15909556)
 * I previously installed the Font Awesome 4.2.0 plugin on a multisite (subdirectory)
   installation with compatibility mode enabled and it actually worked properly.
   There were no errors reported, it successfully found the conflict with “Advanced
   Custom Fields: Font Awesome” plugin, and FA version 4 shims were loaded. Since
   I simply needed the default settings, I did not need to update any settings on
   each site. My icons continued to work correctly on the front-end and backend 
   ACF fields.
 * When I installed the Font Awesome 4.3.0-1 plugin, I received the fatal error 
   message. After I installed and ran the font-awesome-cleanup.zip, I was able to
   install and run 4.3.0-1 without any errors. Again, the plugin conflicts and icons
   are all working properly. It did seem to find two additional conflicts (a link
   and a script). However, I do not see any differences in the functionality of 
   4.3.0-1: there is no Network Admin Dashboard management page, so the settings
   must still be configured on each site.
 * I see one PHP error:
    PHP Deprecated: rest_enabled is **deprecated** since version
   4.7.0! Use rest_authentication_errors instead. The REST API can no longer be 
   completely disabled, the rest_authentication_errors filter can be used to restrict
   access to the API, instead. in C:\laragon\www\hbu\wp-includes\functions.php on
   line 5586
 * WP 5.8.4
    PHP 7.4.29
 * Let me know if I can provide additional information.

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