You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This changes our approach from one where `srcset` and `sizes` are written to the
image markup in post content to one where the responsive attributes are added on the
front end when the page is being rendered. There is a small performance hit but the
benefit is worth the tradeoff for what is gained. What exactly do we gain? Glad you
asked:
* Automatically extend support to images in posts published before we responsive image
support was available.
* Removes the need to update the markup in TinyMCE when the image size is changed.
* Keeps `sizes` attributes, which should probably be adjusted based on the needs of the
theme, from being stored in the database.
* Is non-destructive if a site needs to change available image sizes and regenerate
thumbnails.
Changes:
* Removes the old JS code for handling markup changes in TinyMCE
* Adds `tevkori_filter_content_images()` as a display filter.
* Adds `_tevkori_filter_content_images_callback()` to process filtered images.
* Adds tests
$content = '<p>Welcome to WordPress! This post contains important information. After you read it, you can make it private to hide it from visitors but still have the information handy for future reference.</p>
396
+
<p>First things first:</p>
397
+
398
+
%1$s
399
+
400
+
<ul>
401
+
<li><a href="http://wordpress.org" title="Subscribe to the WordPress mailing list for Release Notifications">Subscribe to the WordPress mailing list for release notifications</a></li>
402
+
</ul>
403
+
404
+
%2$s
405
+
406
+
<p>As a subscriber, you will receive an email every time an update is available (and only then). This will make it easier to keep your site up to date, and secure from evildoers.<br />
407
+
When a new version is released, <a href="http://wordpress.org" title="If you are already logged in, this will take you directly to the Dashboard">log in to the Dashboard</a> and follow the instructions.<br />
408
+
Upgrading is a couple of clicks!</p>
409
+
410
+
%3$s
411
+
412
+
<p>Then you can start enjoying the WordPress experience:</p>
413
+
<ul>
414
+
<li>Edit your personal information at <a href="http://wordpress.org" title="Edit settings like your password, your display name and your contact information">Users › Your Profile</a></li>
415
+
<li>Start publishing at <a href="http://wordpress.org" title="Create a new post">Posts › Add New</a> and at <a href="http://wordpress.org" title="Create a new page">Pages › Add New</a></li>
416
+
<li>Browse and install plugins at <a href="http://wordpress.org" title="Browse and install plugins at the official WordPress repository directly from your Dashboard">Plugins › Add New</a></li>
417
+
<li>Browse and install themes at <a href="http://wordpress.org" title="Browse and install themes at the official WordPress repository directly from your Dashboard">Appearance › Add New Themes</a></li>
418
+
<li>Modify and prettify your website’s links at <a href="http://wordpress.org" title="For example, select a link structure like: http://example.com/1999/12/post-name">Settings › Permalinks</a></li>
419
+
<li>Import content from another system or WordPress site at <a href="http://wordpress.org" title="WordPress comes with importers for the most common publishing systems">Tools › Import</a></li>
420
+
<li>Find answers to your questions at the <a href="http://wordpress.orgs" title="The official WordPress documentation, maintained by the WordPress community">WordPress Codex</a></li>
0 commit comments