Title: Legacy Plugins?
Last modified: January 9, 2022

---

# Legacy Plugins?

 *  Resolved [loyukfai](https://wordpress.org/support/users/loyukfai/)
 * (@loyukfai)
 * [4 years, 4 months ago](https://wordpress.org/support/topic/legacy-plugins/)
 * Currently, some Jetpack plugins are classified as “legacy” by the latest WordPress,
   such as Popular Posts and Pages, and I’m seeing this warning in the theme customizer“
   Warning: Attemp to read property “ID” on null in /home/public…./extras.php on
   line xx ….”
 * Is that normal?
 * Cheers.

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

 *  Plugin Contributor [Dan (a11n)](https://wordpress.org/support/users/drawmyface/)
 * (@drawmyface)
 * [4 years, 4 months ago](https://wordpress.org/support/topic/legacy-plugins/#post-15235350)
 * Hi there
 * > Currently, some Jetpack plugins are classified as “legacy” by the latest WordPress,
   > such as Popular Posts and Pages
 * Where exactly are you seeing that? Could you share a screenshot so we can see
   what you’re describing?
 * You can create screenshots using something like [Snipboard](https://snipboard.io/)
   or [Imgur](https://imgur.com/) and post the link here.
 * > I’m seeing this warning in the theme customizer “Warning: Attemp to read property“
   > ID” on null in /home/public…./extras.php on line xx ….”
 * Can you share the full error message, including the line number?
 * Thanks
 *  Thread Starter [loyukfai](https://wordpress.org/support/users/loyukfai/)
 * (@loyukfai)
 * [4 years, 4 months ago](https://wordpress.org/support/topic/legacy-plugins/#post-15235545)
 * Legacy:
    [https://ibb.co/bXHrFkj](https://ibb.co/bXHrFkj) [https://ibb.co/gMmj2FD](https://ibb.co/gMmj2FD)
 * One of the issues with “legacy” widgets is that, their titles’ styles are hardcoded.
   New widgets don’t have titles built-in and you need to insert one and use the
   group function of Gutenberg. So when legacy and new widgets are used together,
   there is a slight difference of the titles…
 * [https://ibb.co/4ND5LKW](https://ibb.co/4ND5LKW)
 * Error: [https://ibb.co/PYFRFDt](https://ibb.co/PYFRFDt)
 *  [Bruce (a11n)](https://wordpress.org/support/users/bruceallen/)
 * (@bruceallen)
 * Happiness Engineer
 * [4 years, 4 months ago](https://wordpress.org/support/topic/legacy-plugins/#post-15237309)
 * Hi [@loyukfai](https://wordpress.org/support/users/loyukfai/)
 * Since Block widgets were introduced, we’ve had a project to migrate the legacy
   widgets to be able to work with the block editor. You can see the progress of
   this here:
 * [https://github.com/Automattic/jetpack/issues/21069](https://github.com/Automattic/jetpack/issues/21069)
 * We also have legacy widget documentation here:
 * [https://developer.wordpress.org/block-editor/how-to-guides/widgets/legacy-widget-block/](https://developer.wordpress.org/block-editor/how-to-guides/widgets/legacy-widget-block/)
 *  Anonymous User 18700194
 * (@anonymized-18700194)
 * [4 years, 4 months ago](https://wordpress.org/support/topic/legacy-plugins/#post-15265062)
 * Hi there,
 * It has been more than one week since we have heard from you, so I’m marking this
   topic as resolved.
 * But if you have any further questions or need some more help, you’re welcome 
   to reply here or open another thread.

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

The topic ‘Legacy Plugins?’ is closed to new replies.

 * ![](https://ps.w.org/jetpack/assets/icon.svg?rev=2819237)
 * [Jetpack - WP Security, Backup, Speed, & Growth](https://wordpress.org/plugins/jetpack/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/jetpack/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/jetpack/)
 * [Active Topics](https://wordpress.org/support/plugin/jetpack/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/jetpack/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/jetpack/reviews/)

 * 4 replies
 * 4 participants
 * Last reply from: Anonymous User 18700194
 * Last activity: [4 years, 4 months ago](https://wordpress.org/support/topic/legacy-plugins/#post-15265062)
 * Status: resolved