Merge branch 'release/3.5.7' into v3

CHANGELOG.md

@@ -1,5 +1,9 @@
 # SEOmatic Changelog
 
+## 3.5.7 - 2024.11.14
+### Fixed
+* Fixed a parse error if running PHP < `8.0`
+
 ## 3.5.6 - 2024.11.12
 ### 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](https://github.com/nystudio107/craft-seomatic/issues/1482))
@@ -8,8 +12,8 @@
 ### Changed
 * No longer do a potentially expensive query on page load for sections that have a massive number of entries ([#1526](https://github.com/nystudio107/craft-seomatic/issues/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](https://github.com/nystudio107/craft-seomatic/issues/1482))
-* The SEO preview display in Content SEO will pull an entry from the specific Entry Type rather than just the first entry ([#1535](https://github.com/nystudio107/craft-seomatic/issues/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](https://github.com/nystudio107/craft-seomatic/issues/1535))
+* The SEO preview display in Content SEO will pull an entry from the specific Entry Type rather than just the first entry. Note: If you have a custom `SeoElement` PHP class, it will require a very minor method signature change to continue working ([#1535](https://github.com/nystudio107/craft-seomatic/issues/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. Note: If you have a custom `SeoElement` PHP class, it will require a very minor method signature change to continue working ([#1535](https://github.com/nystudio107/craft-seomatic/issues/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](https://github.com/nystudio107/craft-seomatic/issues/1530))

composer.json

@@ -2,7 +2,7 @@
   "name": "nystudio107/craft-seomatic",
   "description": "SEOmatic facilitates modern SEO best practices & implementation for Craft CMS 3. It is a turnkey SEO system that is comprehensive, powerful, and flexible.",
   "type": "craft-plugin",
-  "version": "3.5.6",
+  "version": "3.5.7",
   "keywords": [
     "craft",
     "cms",

src/services/MetaBundles.php

@@ -350,7 +350,7 @@ public function createMetaBundleFromSeoElement(
         $sourceModel,
         int $sourceSiteId,
         $baseConfig = null,
-        $syncConfig = false,
+        $syncConfig = false
     ) {
         $metaBundle = null;
         // Get the site settings and turn them into arrays

src/web/assets/dist/manifest.json

@@ -37,12 +37,12 @@
     ]
   },
   "src/js/seomatic.js": {
-    "file": "assets/seomatic-pGx7eHQv.js",
+    "file": "assets/seomatic-C8AB7bSt.js",
     "name": "seomatic",
     "src": "src/js/seomatic.js",
     "isEntry": true,
     "css": [
-      "assets/seomatic-CR7hXxYp.css"
+      "assets/seomatic-9d2V52Sp.css"
     ]
   }
 }