Skip to content

Releases: nystudio107/craft-seomatic

3.5.6

13 Nov 03:53
Compare
Choose a tag to compare

Added

  • Added the Site Alternate Name property to Site Settings, used in the JSON-LD for the homepage, if the MainEntityOfPage is WebPage or WebSite (#1482)
  • Added Letterbox crop mode for SEO image transforms (#1337)

Changed

  • No longer do a potentially expensive query on page load for sections that have a massive number of entries (#1526)
  • If the current route is the homepage, set the name and alternateName JSON-LD for the mainEntityOfPage to seomatic.site.siteName and seomatic.site.identity.genericAlternateName respectively, rather than the seomatic.meta.seoTitle (#1482)
  • The SEO preview display in Content SEO will pull an entry from the specific Entry Type rather than just the first entry (#1535)
  • Text and Asset pull sources in Content SEO will now display only fields from the specific Entry Type rather than all fields for that Section (#1535)

Fixed

  • Fixed an issue where an exception would be thrown if the Campaign plugin was installed first, and then you newly installed SEOmatic (#1530)

5.1.5

21 Oct 23:19
Compare
Choose a tag to compare

Fixed

  • Fixed togImageField field typo in the FeedMe integration (#1520)
  • Fixed a field mapping issue for fields in the FeedMe integration (#1520)

4.1.5

21 Oct 23:14
Compare
Choose a tag to compare

Fixed

  • Fixed togImageField field typo in the FeedMe integration (#1520)
  • Fixed a field mapping issue for fields in the FeedMe integration (#1520)

3.5.5

21 Oct 23:11
Compare
Choose a tag to compare

Fixed

  • Fixed togImageField field typo in the FeedMe integration (#1520)
  • Fixed a field mapping issue for fields in the FeedMe integration (#1520)

5.1.4

29 Sep 23:31
Compare
Choose a tag to compare

Fixed

  • Normalize the incoming url and path so that mergUrlWithPath() handles edge-cases properly (#1512)
  • Fixed an issue where the ads.txt wasn't renamed properly when requested via GraphQL (#1513)
  • Fixed an issue where the homepage metacontainer cache did not get properly cleared (#1514)
  • Fixed an exception caused by the wrong argument passed to Asset::getAssetById() in edge cases (#1515)
  • Removed vestigial sitemap rendering code in SitemapTemplate that had a code path that had a code path that could return a 503 (#1437)

4.1.4

29 Sep 23:30
Compare
Choose a tag to compare

Fixed

  • Normalize the incoming url and path so that mergUrlWithPath() handles edge-cases properly (#1512)
  • Fixed an issue where the ads.txt wasn't renamed properly when requested via GraphQL (#1513)
  • Fixed an exception caused by the wrong argument passed to Asset::getAssetById() in edge cases (#1515)
  • Removed vestigial sitemap rendering code in SitemapTemplate that had a code path that had a code path that could return a 503 (#1437)

3.5.4

29 Sep 23:29
Compare
Choose a tag to compare

Fixed

  • Normalize the incoming url and path so that mergUrlWithPath() handles edge-cases properly (#1512)
  • Fixed an issue where the ads.txt wasn't renamed properly when requested via GraphQL (#1513)
  • Fixed an exception caused by the wrong argument passed to Asset::getAssetById() in edge cases (#1515)
  • Removed vestigial sitemap rendering code in SitemapTemplate that had a code path that had a code path that could return a 503 (#1437)

5.1.3

11 Sep 03:42
Compare
Choose a tag to compare

Changed

  • Make the Content SEO listings better at eliminating duplicates by pruning sections that no longer exist (#1499)
  • Fixed an issue where a section with a typeId of 0 wouldn't validate, and thus the changes to the Content SEO settings would not validate & save (#1510)

Fixed

  • Fixed the visual appearance of the Entry Type dropdown menu in Content SEO settings

4.1.3

11 Sep 03:41
Compare
Choose a tag to compare

Changed

  • Make the Content SEO listings better at eliminating duplicates by pruning sections that no longer exist (#1499)
  • Fixed an issue where a section with a typeId of 0 wouldn't validate, and thus the changes to the Content SEO settings would not validate & save (#1510)

3.5.3

11 Sep 03:41
Compare
Choose a tag to compare

Changed

  • Make the Content SEO listings better at eliminating duplicates by pruning sections that no longer exist (#1499)
  • Fixed an issue where a section with a typeId of 0 wouldn't validate, and thus the changes to the Content SEO settings would not validate & save (#1510)