Skip to content

Latest commit

 

History

History
67 lines (41 loc) · 6.17 KB

to-test.md

File metadata and controls

67 lines (41 loc) · 6.17 KB

4.1

SSO

  • We've completely redesigned and refactored Jetpack's SSO Module. It would be great if you could use the module as much as possible, with different users, in different browsers, and different roles on your site. The additional options mentioned at the bottom of this page should still work.

Comments

  • We've improved the way comment avatars were stored and displayed. To test, try leaving comments while logged in, logged out, from Twitter, Facebook, Google+, or WordPress.com, and make sure all avatars are always displayed properly.

Contact Form

  • We've changed the way that contact forms are titled- please use the forms and make sure that responses show up correctly in your wp-admin
  • We've added an unread count to the feedback menu item in your wp-admin/ -- keep in mind that this resets to 0 when you view the page. Test it out, make sure it works!

Custom CSS

  • It is now possible to use multiple display properties in Custom CSS. You can follow the instructions here to test.
  • We fixed a memory issue with Custom CSS on sites with a very large amount of CSS revisions. To test this, try saving new CSS changes a few times on your site, and make sure you can still access those changes thanks to the Revisions links below the Save button in the Custom CSS editor.

General

  • We cleaned up and restyled jetpack related banner notices to match Core notification styles.
  • We've improved our connection process. Previously, you sometimes had to specify a port number for your site when using HTTPS, otherwise Jetpack wasn't properly connected to WordPress.com. From now on, Jetpack will take care of that for you. To test, you can try removing _SERVER['SERVER_PORT'] = 443; from a site that uses HTTPS with CloudFlare, for example. When removing this, you should still be able to use features relying on the WordPress.com connection, like the Post Editor on WordPress.com.
  • We fixed Fatal Errors occuring when Jetpack was activated alongside other plugins using an old Bitly class, such as old versions of the official Bitly plugin. To test this, try using Jetpack alongside an old version of that plugin.
  • We improved the connection process when HTTPS isn't properly configured on a site before it's connected to WordPress.com. To test, you can follow the instructions here.

JSON API

  • We updated several API endpoints to match WordPress.com endpoints, with a focus on SAL (Site Abstraction Layer). To test, you can try using several features from the WordPress.com desktop apps or from WordPress.com to manage your Jetpack site, and make sure everything works properly. You should be able to change site settings, publish and update posts and pages, update plugins, customize your theme...
  • We added support for custom taxonomies, to prepare for the upcoming custom post types features in Calypso. You can follow the instructions here to test things.

Publicize

  • We've added a new filter, jetpack_publicize_capability, allowing you to give Publicize capabilities to more users. You can read more about it here.

Sharing

  • Make sure your sharing buttons display as expected
  • Add Telegram and WhatsApp buttons and make sure they operate properly

Shortcodes

  • New Untappd shortcode. To test: Shortcodes enabled, test [untappd-menu location="65" menu="3355a50d-600d-4956-9491-dd0ac2582053"]
  • Recipes: new shortcodes and options to create more detailed recipes. To test, you can follow the instructions in this support document.
  • VideoPress: use HTML5 videos when using the freedom shortcode parameter. To test, try using the force_flash and freedom parameters when inserting VideoPress shortcodes, and check that the video is displayed according to your settings.
  • VideoPress: we've made some changes to the shortcode modal, available when inserting and editing a VideoPress video in the Visual Editor. To test, you can play with shortcode options for a video you've inserted by clicking on the little Pencil icon appearing above the video.
  • Audio: we have completely removed the Audio shortcode, as audio players have been part of WordPress Core for some time, and we didn't include our shortcode for all versions of WordPress above 3.6. To test, try inserting Audio shortcodes into your posts, and make sure no error appears.

Sitemaps

  • We made some changes to avoid PHP notices when one of your posts included a slideshow. To test, you can follow the instructions here.
  • Sitemaps also support permalinks using index.php now. You can follow the instructions here for your tests.

Support

  • We've improved the self-help tools available in the Jetpack Debug menu. To test, you can go to the Jetpack Menu in your dashboard, scroll down, click on "Debug", and make sure there are no errors on the page or in your logs. You should also be able to use the Contact Form to send debug information to the Jetpack Support team.

Tiled Galleries

  • In some cases, like when specific concatenating plugin were used to minify and reorder JavaScript resources, Tiled Galleries would give JavaScript errors, as explained here. You should now be able to display Tiled Galleries without any issues.

Widgets

  • We've refactored the Contact Info Widget to improve performance. To test, try adding and editing options of a Contact Info Widget.
  • We now use Photon to resize images in the Gallery Widget, thus improving performance of that widget. To test it, add a Gallery widget to your sidebar, set it to use Tiles, and make sure the images are displayed properly and use Photon (i.e. use the i*.wpcom domain).
  • You can now set the top posts widget to look at traffic for more than the last 10 days. Try cranking up that setting and make sure nothing breaks.