Headline
CVE-2020-9757: craft-seomatic/CHANGELOG.md at v3 · nystudio107/craft-seomatic
The SEOmatic component before 3.3.0 for Craft CMS allows Server-Side Template Injection that leads to RCE via malformed data to the metacontainers controller.
SEOmatic Changelog****3.4.30 - 2022.04.18****Changed
- Ensure that the
currentSite
is set to the requested one when processing headless requests via API endpoint or GraphQL, to ensure things likesiteUrl()
etc. resolve correctly (#1111) - Use the native
str_contains()
overStringHelper::contains()
(which is slower, and allocated objects, etc.)
Fixed
- Fixed an issue where the
Autocomplete
helper could throw an exception if it encountered aReflectionUnionType
- Fixed an issue with the default
Humans.txt
implementation ofparseEnv()
(#1109)
3.4.29 - 2022.04.08****Changed
- Only regenerate sitemaps via queue jobs if they are a result of an invalidation of the sitemap cache (#1098) (#1097)
Fixed
- Fixed an issue where disabled entries could appear in breadcrumbs JSON-LD (#1088)
3.4.28 - 2022.03.22****Fixed
- Fixed an issue that could cause an exception to be thrown during a console request (#1080)
- Fixed an issue in the
TwigExpressionValidator
class that prevented you from accessing theseomatic.
variable in some circumstances (#1076)
3.4.27 - 2022.03.13****Changed
- Added validation rules for
metaCacheDuration
property on theSettings
model - Change the default email address in
security.txt
to the placeholder[email protected]
- The
ads.txt
andsecurity.txt
templates are no longer enabled by default, because they require configuration before use (#1077)
Fixed
- Ensure that the
metaCacheDuration
is normalized to0
if set tonull
or'null'
3.4.26 - 2022.02.21****Changed
- Add
parseEnv()
to thehumans.txt
template to parse environment variables/aliases (#1069)
Fixed
- Fixed an issue where “Same as Site Name Position” did not appear on the Global -> Facebook settings for the Facebook OpenGraph Site Name Position Source setting (#1066)
- If paginated URLs are not using a query string, strip the query string from the canonical URL
- Handle an edge-case where a migration didn’t work properly to add
SECURITY_TXT_HANDLE
(#1065) - Explicitly typecast
limit
to(int)
for Solspace Calendar queries (#1064) - Fixed an issue where hitting Command-S wouldn’t save any changes to edited template code (but clicking on the Save button would) (#1068)
3.4.25 - 2022.02.11****Fixed
- Fixed a typo in the
EVENT_AFTER_SAVE_PRODUCTTYPE
event name - Fixed an issue with empty
tagAttrs
throwing an exception
3.4.24 - 2022.02.10****Added
- Build only the Monaco editor components needed, drastically reducing the assetbundles size
- Added the ability to set
<script>
tag attributes for tracking scripts
Fixed
- Fixed an issue that could cause an exception if a MetaBundle was malformed (#1058)
- Fix a bug where modifying sites or element containers would not update the corresponding meta bundle settings. (#979)
3.4.23 - 2022.01.31****Fixed
- Delay registering SEO Elements to give other plugins a chance to load first (#654)
- Fixed an issue where textarea fields aren’t disabled, and ensure previously hidden fields work as expected (#1049)
- Fixed an issue where the SEO Settings field would display the Twitter Image and Facebook Image even if they were disabled in the field settings (#1047)
- Register GraphQL types after all plugins are loaded, so that we can work with plugins that register their own types (#1037)
- Fix Bing’s sitemap submission URL (#1043)
3.4.22 - 2022.01.12****Fixed
- Fixed an issue that would cause an exception to be thrown if an SEO Settings field was added to an unknown/custom Element’s field layout (#1031)
- Fixed an issue where you couldn’t query for frontend containers from sites other than the current site request via GraphQL (#1039)
- Fixed an issue where Solspace Calendar events would not have the
seomatic
field on them when using the GraphQL API (#1037)
3.4.21 - 2021.12.13****Added
- Added in the Monaco editor, with autocomplete & hovers for the Craft APIs as well as variables available in the various SEOmatic templates, such as the tracking scripts
Fixed
- No longer attempt to run the Craft queue manually (#10189)
- Generate sitemaps immediately via console command, bypassing the queue job (#10189)
- Use HtmlPurifier to remove HTML instead of
strip_tags
to prevent errant stripping of content likeI <3 Craft
(#1024)
Changed
- Check to see if a site is Enabled in Craft CMS > 3.5 to determine whether to generate sitemap URLs &
rel="alternate"
links (#1023) - Check to see if a site is Enabled in Craft CMS > 3.5 to determine whether to generate breadcrumbs (#1023)
- Check to see if a site is Enabled in Craft CMS > 3.5 to determine whether a metabundle should be generated/pruned or not (#1023)
- Updated the buildchain to use Node 16
- Updated to Tailwind CSS
^3.0.0
3.4.20 - 2021.11.23****Changed
- Deprecated the
frontendTemplateContainer
GraphQL field
Fixed
- Eliminated multiple queries to the same asset via a memoization cache in ImageTransformHelper (#1016)
3.4.19 - 2021.11.13****Changed
- Changed the
frontendTemplateContainers
GraphQL query tofrontendTemplates
, and made the query inline with thesitemaps
queries, returning afilename
andcontents
3.4.18 - 2021.11.11****Added
- Added the ability to query for
sitemaps
,sitemapIndexes
, andsitemapStyles
via GraphQL (#517) - Added the Always include
canonical
links regardless of environment setting to Plugin Settings -> Advanced (#1006)
Fixed
- Don’t try to run the sitemap queue job immediately if it’s the result of an invalidation, only when the actual sitemap is requested via frontend request
- Fix Matomo script URL value by removing the // and / that are in the Matomo docs (#1004)
- Fixed an issue where meta value parsing could fail with unquoted object keys passed in (#1007)
- Fixed the date in the
security.txt
template
3.4.17 - 2021.10.19****Added
- Added the ability to specify the SEOmatic environment to use with the GraphQL API (local, staging, production)
Fixed
- Ensure URLs with no
path
work indecomposeUrl()
(#1001) - Make sure the *Sources variables at least exist, for things like the QuickPost widget (#1002)
3.4.16 - 2021.10.13****Changed
- Add an empty value to possible selections for the Robots setting, to allow it to fall back on global settings (#996)
Fixed
- Ensure the FrontendTemplatesContainer exists before accessing it via GraphQL (#1000)
- Render Canonical URL overrides from the SEO Settings field properly via GraphQL requests (#1001)
- Don’t show the “SEO Image Transform Mode” text (sans controls) if it’s not enabled in the Field Settings (#995)
3.4.15 - 2021.09.28****Fixed
- Disable strict variables during meta value rendering, to mirror the functionality of
renderObjectTemplate()
. Resolves (#990)
3.4.14 - 2021.09.27****Changed
- Substantial performance increase on element save, because we ensure the sitemap queue job doesn’t attach itself to web-based queue runners (#989)
- Changed the core MetaValue parsing method to be faster, also resolves (for real) (#653)
- Remove all references to the now-deprecated
object.
syntax (though it still functions as usual)
Fixed
- Fixed an issue where the query string would be erroneously stripped from image URLs (#987)
3.4.13 - 2021.09.26****Fixed
- Fixed a regression that could cause sitemap generation via console command to throw an error (#985)
- Fixed an exception that could be thrown on paginated pages that were not the first page
3.4.12 - 2021.09.26****Fixed
- Fixed an issue where the preview in Content SEO would not display the correct information if “Summary from Field” was chosen (#653)
Security
- Sanitize all rendered URLs in an effort to mitigate a potential attack vector on an improperly configured site
3.4.11 - 2021.09.24****Added
- Added support for security.txt in SEOmatic → Global settings
- Added an option to SEOmatic → Plugin Setting → Sitemaps to have items that have a different Canonical URL than the item URL excluded from the sitemap (#983)
- Moved all the sitemap Plugin Settings to their own tab in SEOmatic → Plugin Setting → Sitemaps
Changed
- Ensure that paginated self-referencing
hreflang
urls match the paginated canonical URL (#984)
Fixed
- Fixed an issue where a tracking script that had no templateString or templatePath could not be saved, showing " Couldn’t save tracking settings due to a Twig error." (#981)
- Fixed the default values for Entry meta bundles that were errantly changed to be empty
- Fixed an issue with the SEO Settings field throwing an exception is no
$element
context was passed in
Security
- Ensure that only files with the extensions listed in
allowedFileExtensions
General Config setting can be used with the SEO File Link controller - Sanitize the canonical URL after the absolute URL has been returned, to mitigate poisoned
X-Forwarded-Host
headers
3.4.10 - 2021.09.15****Fixed
- Fixed a regression that would throw an exception if Commerce was not installed
3.4.9 - 2021.09.15****Added
- Added the ability to automatically include Commerce’s
variant=XXX
URL parameter in the metadata cache key, allowing for unique values per variant (#971) - Added a
allowedUrlParams
config setting that allows URL parameters to be manually whitelisted for inclusion in the metadata cache key (#971) - Added the ability to query for frontend template containers (
robots.txt
, etc.) via GraphQL or Meta Container API Endpoint
3.4.8 - 2021.09.09****Added
- Added a nicer looking theme for the Twig & JavaScript code editors, and a more pleasant font selection
Fixed
- Fixed an issue where an empty Category (or other element type) could throw an exception when creating the first category item (#973)
- Fixed profiling on certain methods by using
endProfile()
in theMetaContainers
service
3.4.7 - 2021.09.08****Fixed
- Fixed an issue where dynamic meta information wasn’t injected during Craft Previews of pages (#954)
- Fixed an issue where the SEO column would all display the same entry due to a caching issue (#970)
3.4.6 - 2021.08.30****Fixed
- Fix a bug where the same ID would be re-used for multiple element select fields. (#965)
3.4.5 - 2021.08.29****Changed
- Further optimized the CP requests by eliminating redundant calls to
loadMetaContainers()
and also only callingaddDynamicMetaToContainers()
on headless requests - Added more fine-grained profiling to the
DynamicHelper
class
Fixed
- Fix a bug where SEO image settings could be inherited incorrectly (#962)
- Fixed an issue where elements with newly added SEO Settings field wouldn’t appear in the sitemap (#964)
3.4.4 - 2021.08.26****Fixed
- Ensure metacontainers are loaded for new elements that have an SEO Settings field in their layout (#960)
- Typecast the setting collection to an array to handle the case of an empty string being returned (#961)
- Instantiate at least the global metacontainers for CP requests, to sidestep regression issues for code that depends on the metacontainers being present (#954) (#960)
3.4.3 - 2021.08.25****Added
- Added a Include Homepage in Breadcrumbs general plugin setting to control whether the generated JSON-LD for Breadcrumbs includes the homepage or not (#957) & (#747)
Changed
- Switch to
rawurldecode()
to avoid changing+
signs into spaces in pull fields (#785)
Fixed
- Don’t call
loadMetaContainers()
explicitly for CP requests (#954) - Fixed an issue where if you had an SEO Settings field with the Sitemap tab enabled, but did not have Override on, the
<link rel="alternate">
would not render (#958) - Fixed a validation error that wouldn’t allow you to save Tracking Scripts that didn’t have a body script (#959)
- Fixed a cosmetic issue with the human-readable display of custom sitemaps (#955)
3.4.2 - 2021.08.20****Fixed
- Fixed an issue that could cause an exception to be thrown or CSS to be broken for the Social Media Preview (#953)
3.4.1 - 2021.08.19****Fixed
- Fixed an exception that could be thrown on a frontend form submission (#951)
- Fixed an issue where entry index pages wouldn’t auto-refresh after deleting multiple entries (#952)
3.4.0 - 2021.08.18****Added
- Improved the way overrides are handled & displayed in SEO Settings fields by having an explicit Override switch for each setting (#535)
- Scripts are now rendered and checked for Twig errors before they can be saved (#944)
- Robots, Humans, and Ads templates are now rendered and checked for Twig errors before they can be saved (#944)
- Added Pinterest Tag tracking script (#936)
Changed
- Switch from the shorthand format to object format for the search target JSON-LD (#945)
Fixed
- Only default to not generating image transforms immediately if the image is remote and the environment is local dev (#949)
- Fixed an issue where the Robots setting was ignored in SEO Settings fields for sitemap generation if the Sitemap tab was not enabled (#947)
- Don’t have
useFieldset()
return true, as it causes a visual error when resizing the window in Craft CMS 3.7.x
3.3.48 - 2021.08.11****Fixed
- Fixed a regression that caused sitemap generation via console command to fail (#943)
3.3.47 - 2021.08.10****Fixed
- Fixed an issue where
Sitemaps::invalidateSitemapCache()
wasn’t going through the same bottleneck as the sitemap render, and thus wasn’t properly hitting the caching layer - Don’t access
Craft::$app->getResponse()->statusCode
during console requests (#940)
3.3.46 - 2021.07.27****Added
- Added support for pulling from Preparse fields for SEO fields (#927)
Fixed
- Fix an issue where
Undefined class constant ‘EVENT_REGISTER_GQL_SCHEMA_COMPONENTS
would be thrown if you were running Craft CMS <^3.5.0
(#933) - Empty out the entity image settings to ensure the image gets removed if it no longer exists (#760)
3.3.45 - 2021.07.20****Fixed
- Fixed an issue where
MedicalBusiness
JSON-LD type didn’t inherit all of the properties fromMedicalOrganization
that it should - Handle per-entry type settings for the sitemap generation (#929)
3.3.44 - 2021.07.09****Added
- Added
truncateTitleTags
&truncateDescriptionTags
settings to control whether the max title / description lengths should be enforced or not (on by default) (#922)
Changed
- Changed the Google & Bing sitemap submission URLs to
https
(#903)
Fixed
- Handle the case where
additionalSitemaps
isn’t a zero-based index, due to items being deleted from it (#921)
3.3.43 - 2021.06.08****Added
- Add GraphQL schema components for SEOmatic.
Changed
- Switched documentation system to VitePress
Fixed
- Additional Sitemap URLs will now appear only in the Site’s sitemap index where they are defined (#897)
3.3.42 - 2021.05.18****Changed
- Strip the query params from next/prev pagination meta tags if we’re not using query-string based pagination (#896)
- Ensure that frontend templates are checked first, so things like
humans.twig
androbots.twig
can be overridden (#891)
Fixed
- If sitemaps aren’t enabled globally, return nothing for the sitemap index (#895)
- Fixed an issue where an empty transform mode could cause errors generating social image transforms (#892)
3.3.41 - 2021.05.06****Added
- Only add a sitemap to the sitemap index if there’s at least 1 element in the resulting sitemap (#873)
Changed
- Have all of the Site Map settings in the SEO Settings field default to empty, so they fall back on the Content SEO value by default (#871)
- Have the image transform modes all default to empty, so they will fall back on the Content SEO value by default (#868)
Fixed
- For paginated pages, re-apply the adjustment to the canonical URL tag as well (#875)
- Handle the case of empty asset ids being passed in from a missing asset source (#882)
- Fixed the verbiage in the Matomo script URL setting (#880)
- Don’t call any AssetManager methods in the component
init()
method during console requests (#885)
3.3.40 - 2021.04.15****Added
- Added support for Matomo Analytics in the Tracking Scripts section
Changed
- Wrap tracking scripts in IFFYs
Fixed
- Ensure assets imported via FeedMe don’t end up in a
null
volume ID (#840)
3.3.39 - 2021.04.09****Added
- Added support for Facebook domain verification via the
facebook-domain-verification
tag (#856) - Add proper support for importing assets via Feed Me (#840)
- Google gtag.js is now the first and default option in Tracking Scripts, and a footnote to use it for Google Analytics 4 is included (#788)
- Added support for Fathom Analytics in the Tracking Scripts section (#823)
- Added support for Plausible Analytics in the Tracking Scripts section (#817)
Changed
- Changed how we determine whether environment mappings should be applied to meta items so GraphQL requests will have them applied
Fixed
- For pagination, adjust the canonical URL tag as well as the variable
- Don’t strip the query string from paginated canonical URLs
3.3.38 - 2021.04.06****Added
- Added
make update
to update NPM packages - Added
make update-clean
to completely removenode_modules/
, then update NPM packages
Changed
- SEOmatic will now register frontend templates even if they request matches no Craft site, but the request is for a document in the root domain that has a file extension, e.g.
robots.txt
- Use Tailwind CSS
^2.1.0
with JIT
3.3.37 - 2021.03.31****Added
- Added the
.tagAttrs
property to all meta items, so you can dynamically add attributes likedata-
to any of the meta item tags
Changed
- Move the manifest service registration to the constructor
- Guard against a Site that has a
null
Base URL inloadFrontendTemplateContainers()
(#861)
Fixed
- Fixed an issue where the default settings for Content SEO for sections with multiple entry types was set incorrectly (#814) & (#794)
- Fixed the GTag script to use the
???
empty coalescing operator, to prevent empty strings from being used ingtagProperty
(#860)
3.3.36 - 2021.03.25****Changed
- More consistent
makefile
build commands - Use Tailwind 2.x &
@tailwindcss/jit
- Move settings from the
composer.json
“extra” to the plugin main class - Don’t register any frontend templates if this site has a sub-directory as part of the URL (#859)
- List all sites sitemaps in the
robots.txt
(#859)
Fixed
- Ensure really long titles are cropped in the sidebar preview
- Fixed the documentation for the
EVENT_ADD_DYNAMIC_META
event - If Manually Set SEOmatic Environment is on, ignore
devMode
in determining the environment - Fixed issue with global meta bundles not being updated when their version is changed
3.3.35 - 2021.03.03****Fixed
- Fixed a regression with SEO Settings fields using the old
ManifestHelper
3.3.34 - 2021.03.03****Added
- Added
seomatic.containers
to allow access to theMetaContainers
service via Twig - Added
seomatic.bundles
to allow access to theMetaBundles
service via Twig
Changed
- Only include localized versions of elements that are enabled for hreflang tags
- Dockerized the buildchain, using
craft-plugin-manifest
for the webpack HMR bridge
3.3.33 - 2021.02.23****Added
- Added a Manually Set SEOmatic Environment setting (defaults to off) for people who want to manually set the SEOmatic environment via environment variable
Changed
- Updated build system infra
- Parse the SEOmatic Environment as a variable before displaying it on the dashboard
Fixed
- No longer include any
<body>
script tags (as in Google Tag Manager) if the entire script meta container is excluded - The
og:locale
tag no longer shows the wrong language for headless requests - Don’t link to the settings page if
allowAdminChanges
isfalse
- No longer URL decode text that is pulled from another field in SEOmatic
3.3.32 - 2021.02.12****Fixed
- Fixed a typo in the global JsonLDContainer that caused errors to be generated
3.3.31 - 2021.02.08****Changed
- Implemented
useFieldset
for Craft 3.6
Fixed
- Explicitly parse the
seomatic.site.identity.genericUrl
so that aliases & environment variables are parsed - Fixed an issue with PHP 8 and
array_walk_recursive()
wanting the second parameter to not be passed by reference ( opposite of what the error message states) - Fix Feed Me mapping and asset-creation
3.3.30 - 2021.01.26****Changed
- Make the canonical URL point to the current page for paginated links ref
- Run the queue via CLI command via
QueueHelper::runConsole()
to handle queues that don’t conform to Craft’ sQueueInterface
- Updated Axios to
^0.21.1
- Removed unneeded duplicate
og:locale:alternate
if it matches the currentog:locale
- Don’t strip query strings from
link rel="canonical"
for paginated pages
3.3.29 - 2020.12.31****Changed
- Renamed
common.js
->commons.js
, which is the correct name, and also will suppress it from appearing in the error logs - Switch from using
->each()
to usingcraft\db\Paginator
to paginate asset query results, to address out of memory issues on massive queries - SEOmatic now requires Craft CMS 3.1.19 or later
3.3.28 - 2020.12.22****Fixed
- Fixed a regression that caused Script variables to not be parsed as environment variables
- Fixed a bug that could cause Content SEO image settings to not override the global settings properly
- Set the the canonical URL to be the first page of the paginated pages
- Ensure that paginated pages are cached individually, regardless of the
addPaginatedHreflang
setting
3.3.27 - 2020.12.18****Changed
- Split out vendors & commons chunks
Fixed
- Changed
unlimitedStock
tohasUnlimitedStock
for the Product JSON-LD defaults - Ensure that the
runtime.js
is included in the Field Settings and Field
3.3.26 - 2020.12.08****Changed
- Moved the CSS/JS buildchain over to webpack 5
- Updated to latest npm deps
3.3.25 - 2020.12.04****Added
- Added the ability to query the
MetaSiteVarsContainer
via GraphQL or Meta Container endpoint, to allow accessing things such as the social media sites/urls, and other site-wide information
Changed
- Normalize the script variables by parsing them as environment variables, and trimming whitespace
3.3.24 - 2020.11.23****Changed
- Moved the environment swapping functionality back to
MetaItem::init()
- Removed
type="text/javascript"
from the<script>
tags that SEOmatic injects for tracking scripts
Fixed
- Ensured environment settings for
robots
are not saved to the db
3.3.23 - 2020.11.18****Changed
- Revert "Social image transforms for remote volumes no longer default to not generating the image transforms immediately (they fall back on whatever your system setting is)" because it caused slowdown when working with remote volumes
- Ensure the URLs in the breadcrumbs JSON-LD adheres to the
addTrailingSlashesToURls
general config setting - Added better checks for
InStock
for Product JSON-LD schema
Fixed
- Fixed an issue where SEOmatic could permanently change “robots” to “none” inadvertently in edge-case circumstances
- Fixed an issue where the Main Entity of Page could reset to undesired values
- Use unicode safe string functions to truncate meta values > 4096 characters before parsing them
3.3.22 - 2020.10.20****Added
- Added a
--queue
flag that can be passed to theseomatic/sitemap/generate
flag to cause the sitemap generation jobs to be queued, but not run
Fixed
- Fixed an issue in sitemap generation if an alternate site element had
null
for a URL - Fixed awkward spacing on Tracking Scripts environment warning
- Handle clearing caches properly when the homepage is in a structure via
__home__
in the slug
Changed
- Ensure that
canonicalUrl
is always a string
3.3.21 - 2020.09.30****Fixed
- Fixed a regression that would cause a Garnish error on some SEOmatic pages, causing the JavaScript to not operate property
3.3.20 - 2020.09.29****Changed
- Don’t trigger
EVENT_INVALIDATE_CONTAINER_CACHES
in a console command - Replace
$this::
(??) withself::
globally in the codebase
3.3.19 - 2020.09.28****Changed
- Improved the user-visible sitemap .xsl stylesheet
- Removed SEOmatic name & link from the user-visible Sitemap footer
Fixed
- Fixed an error that could occur if your primary site has no BaseUrl
- Fixed an issue that could result in multiple
X-Robots-Tag
headers if Craft is setting the header itself (as it does in 3.5.10 or later) - Fixed an issue where changing Entry Types would cause the SEO Settings field to not display properly
3.3.18 - 2020.08.31****Added
- Added styling to create human-readable sitemaps via
.xsl
files - Added
hreflang="x-default"
to sitemaps if the Includex-default
hreflang
Tag setting is enabled
Changed
- Ensure that sitemap
alternate
URLs also do not include trailing slashes on root website URLs ifaddTrailingSlashesToUrls
is false - Requests for
sitemap.xml
are now 302 redirected to the actual sitemap rather than serving the same content from both
Fixed
- Fixed an issue where sitemap index alternate tags had unnecessary whitespace in them
3.3.17 - 2020.08.24****Added
- Added
seomatic.helper.sanitizeUserInput()
in cases where you want to manually sanitize user input
Changed
- Ensure that sitemap URLs also do not include trailing slashes on root website URLs if
addTrailingSlashesToUrls
is false
Fixed
- Fixed a formatting issue for fields in the SEOmatic Settings pages that showed the number of characters left
- Fixed an issue where the token field wouldn’t be created if keywords had no value
- Fixed an issue where the previews in an SEO Settings field wouldn’t match what they should be previewing
- Live Preview and Preview requests now never have their metadata cached
3.3.16 - 2020.08.17****Added
- Added additional unit tests for URL/entity decoding
- Added a new SEO File Link Endpoint Access setting (off by default) to make the feature opt-in
Changed
- Adjusted the logic in the
seomatic.helper.isPreview()
function to make it more correct
Fixed
- Fixed a formatting issue introduced in Craft CMS 3.5.4 that caused the layout in some of SEOmatic’s settings to be incorrect
- Fixed an issue where the “Leave Site?” dialog would come up on the General Settings page, regardless of whether the page changed or not
Security
- Refactored the GraphQL SSTI code to normalize the string via URL/entity decoding it before stripping tags or Twig
3.3.15 - 2020.08.14 [CRITICAL]****Added
- Add unit tests for the Meta Title tag
- Added a unit test for newline insertion in the GraphQL query payload
Changed
- Social image transforms for remote volumes no longer default to not generating the image transforms immediately (they fall back on whatever your system setting is)
- If no title is provided, just use the site name
Security
- Fixed a potential SSTI if the GraphQL API is enabled in Craft, is open to the public, and a specially crafted request is sent to it
3.3.14 - 2020.08.10****Changed
- Handle empty titles and empty site names by not including the separator character
- Trim trailing slashes from absolute URLs unless
addTrailingSlashesToUrls
is true
Fixed
- Fixed an issue that caused sitemap generation to fail if you’re using a non-native queue runner
- Handle invalid sites that have no site group without throwing an exception
- Fixed an issue where you were unable to set the Canonical URL to an environment variable
3.3.13 - 2020.07.30****Fixed
- Added
craftcms/cms
back in as a dependency so Craft sees updates to the plugin again - Fixed deprecation errors with Craft CMS 3.5RC1
- Fixed an issue where a regression caused the Include
x-default hreflang
Tag setting was not respected
3.3.12 - 2020.07.21****Fixed
- Fixed an issue where
null
could be passed intogroupId
for the sitemap generation job, causing it to fail - If a request is a preview request of any kind, set the
robots
tag tonone
- Don’t send any headers for preview requests
Changed
- Check for
null
to ensure that the SEO Settings field exists when trying to prune properties from it inpruneFieldMetaBundleSettings()
3.3.11 - 2020.07.14****Added
- Added support for automatically adding Content Security Policy ( CSP) nonces to <script> tags (including JSON-LD)
- Added Fixed Content Security Policy ( CSP) script-src policies that should be added before the nonces
- Added a
sanitizeFieldData()
that’s called when pulling from other Craft fields, to ensure no executable Twig code exists - Added a unit test for
sanitizeFieldData()
3.3.10 - 2020.07.07****Fixed
- Handle trailing slashes properly for generated URLs such as the
canonicalUrl
- Fixed an issue where URLs that depended on the
canonicalUrl
(such asog:url
) would be wrong in the Craft CP or via MetaContainer endpoint or GraphQL - Fixed an issue where an error could be thrown editing Content SEO settings
3.3.9 - 2020.07.03****Added
- Added the Codeception testing framework to SEOmatic
- Added a SSTI Unit Test to SEOmatic that executes on every push to GitHub to verify there are no regressions for CVE-2020-12790
Changed
- Make entity’s a
VarsModel
so they have access to.parsedValue()
Fixed
- Fixed an issue where additional sitemap entries with empty location settings would throw an error
3.3.8 - 2020.06.04****Changed
- Strip the query string from breadcrumb URLs
- Marked the 3.3.0 update as
critical
- Ensure that
typeId
is explicitly typecast, to avoid it being treated as a string
3.3.7 - 2020.06.04****Fixed
- Fixed an issue where the Dashboard wasn’t showing the Content SEO Checklist properly
- Fixed an issue where a sitemap might not show up if there were overlapping Section/other ids
3.3.6 - 2020.06.03****Added
- Added support for querying for SEOmatic metadata via GraphQL inside of Entry, Category, and Product queries
- Added environment variable & alias auto-complete for Canonical URL and Entity URL settings
- Added a Referrer setting under Site Settings → Miscellaneous
Fixed
- Fixed an issue where some Sections might not appear in Content SEO if they had overlapping ids
- Display “Select…” instead of “(unknown)” when no Main Entity of Page has been selected
3.3.5 - 2020.05.26****Fixed
- Fixed an issue with Digital Products throwing an error on saving SEOmatic Content SEO settings
- Fixed an issue that could cause an SQL error when saving Content SEO settings on Postgres
3.3.4 - 2020.05.18****Added
- Added support for Digital Products
- Added a Meta Cache Duration setting under Plugin Settings → Advanced
- Added the ability to control anonymous access to the Meta Container & JSON-LD endpoints (with both off by default)
Fixed
- Fixed a namespacing issue for UrlHelper on certain versions of PHP
- Don’t call
metaBundles->getMetaBundleBySourceId()
unless there are no pending plugin migrations - Fixed an issue where element caches were not broken on element save for elements with
__home__
for the URI
3.3.3 - 2020.05.12****Changed
- Wrap the JSON-LD encoding in try/catch to handle malformed characters
- Added exception logging to
MetaValue::parseMetaString()
to make debugging the error source easier
Fixed
- Fix Content SEO settings display for MySQL with
sql_mode=only_full_group_by
- Fixed an issue where the sitemap index could show duplicate section sitemaps
3.3.2 - 2020.05.09****Fixed
- Fixed an issue where the Main Entity of Page could retain stale values in the SEO Settings field
- Fixed an issue with duplicate entries appearing in the Content SEO listing
3.3.1 - 2020.04.28****Fixed
- Fixed an issue with the Content SEO listing not appearing if you are using Postgres
- Ensure that the Content SEO listing paginates property if you have multiple entry types
3.3.0 - 2020.04.28 [CRITICAL]****Added
- Added a new searchable Schema UI selector for finding Main Entity of Page types quickly
- Added support for importing SEO meta info into SEOmatic via FeedMe
- Added support for multiple Entry Types, each of which can have its own SEOmatic settings in Content SEO
- Added a validator for the
Duration
schema.org type - Added a “Include Paginated
hreflang
Tags” setting - Added a Submit Sitemap Changes plugin setting
- Added emoji support for Sections
Changed
- The MetaLink error
...did not render because it is missing attributes
is no longer render as an error, but rather via theinfo
log level, withWARNING -
proceeding it - You can now pass in
@type
ortype
for the schema type
Fixed
- Fixed an issue where the Robots setting could be “sticky” when generating sitemaps with SEO Settings fields involved
- If a page has a
robots
tag that marks it asnoindex
ornone
, don’t include a canonical URL - No longer delete caches in response to
TemplateCaches::EVENT_AFTER_DELETE_CACHES
- Fixed an issue where SEO previews could have the wrong URLs for multi-site setups
Security
- Fixed a regression where malformed data passed to the metacontainers controller could result in SSTI which leads to information disclosure
3.2.51 - 2020.04.06****Added
- Updated to Schema.org 7.0.3 including SpecialAnnouncement and other types/changes to handle the COVID-19 crisis
- Added several optional properties to the Event schema.org type:
eventStatus
,eventAttendanceMode
, andpreviousStartDate
- Included the
extension
schema.org types as well ascore
schema.org types - Added
eventAttendanceMode
andeventStatus
with defaults to the Event JSON-LD
3.2.50 - 2020.04.02****Fixed
- Fixed an issue that appears to be a regression in Yii2, which would cause the Opening Hours to be unable to be saved
- Fixed an issue with the Site URL Override feature that could result in a malformed URL
Changed
- Updated to latest npm dependencies via
npm audit fix
for both the primary app and the docs - Have the SEO Preview displayed URL reflect the Site URL Override
3.2.49 - 2020.03.24****Added
- Aliases will now auto-suggest in the Site URL Override settings field
- SEOmatic now will replace any stripped HTML tags with a space, so that the text is more readable
Fixed
- The Site URL Override is now parsed for both aliases and environment variables
Security
- Ensure that URLs are
urldecode
d before attempting to use a RegEx to strip tags from them
3.2.48 - 2020.03.18****Added
- Added batching to sitemap generation so that the memory used is fixed, and no longer dependent on how many sitemap entries are being processed
- Added a
Cache-Control
header ofno-cache, no-store
to the503
w/Retry-After
that SEOmatic returns for sitemaps that are still being generated
Fixed
- Fixed regex in
sanitizeUrl()
3.2.47 - 2020.03.06****Fixed
- Fixed an issue where hreflang URLs were incorrect if you had different localized URIs per entry
- Take keys into account when comparing defaults with values in SEO Settings fields
- Fixed a regression with the canonical URL when fetched via GraphQL/XHR
- Fixed an issue in which if Globals were used as source to pull from in a multi-site setup, they’d always preview as the default site value
3.2.46 - 2020.03.03****Changed
- Fixed some dates to dateCreated as categories doesn’t have postDate
Security
- Fixed an issue where malformed data passed to the metacontainers controller could result in SSTI which leads to information disclosure
3.2.45 - 2020.02.28****Added
- Added the ability to query by site handle via GraphQL (in addition to
siteId
)
Changed
- Ensure that the
x-default
hreflang
is set to the primary site, not just the first site
Fixed
- Ensure that the GraphQL service has the
invalidateCaches()
method before attempting to call it (it wasn’t added until 3.3.12)
3.2.44 - 2020.02.24****Added
- Added the ability to copy any of the SEOmatic settings from one site to another, to make setup easier
- If
robots
is set tonone
in an SEO Settings field, the entry won’t appear in the sitemap
Fixed
- Fixed an issue where if you changed the Sitemap Limit to something other than None, then switched it back, you’d get an empty but non-null value for the limit, which didn’t play nice with element queries from third party elements
- Preserve numeric
0
values in JSON-LD properties
Security
- Don’t include headers for any response code >= 400
- Remove any Twig tags that somehow are present in the incoming URL
3.2.43 - 2020.02.13****Changed
- Make sure that the
BreadCrumbsList
JSON-LD andlink rel="home"
tags respect thesiteUrlOverride
setting
Fixed
- Fixed some minor UX spacing issues on Craft CMS 3.4
3.2.42 - 2020.02.06****Added
- Added
seomatic.helper.isPreview
and updated the tracking scripts to utilize it, to handle Craft 3.2 deprecation ofcraft.app.request.isLivePreview
- Added an
account
column to the Same As URLs so you can store the social media account (if any) along with the URL - Added
seomatic.helper.sameAsByHandle(HANDLE)
to retrieve information about one of the Same As URLs by handle
Fixed
seomatic:dashboard
permission is now required for the displaying of the Dashboard
3.2.41 - 2020.01.29****Added
- Added the ability for sitemaps to extract images & video from SuperTable fields
- Added the ability for text to be pulled from SuperTable fields for SEO Descriptions, etc.
Fixed
- Fixed a regression that caused you to no longer be able to put an array of values in the
content
field of anog:image
tag for multiple OpenGraph images - Fixed a regression that could cause SEO Settings fields to not propagate images properly
3.2.40 - 2020.01.23****Added
- Added rules to
MetaJsonLd
to allow for mass-setting via.setAttributes()
ofid
,type
, andcontext
Changed
- Eliminated harmless JavaScript errors if a keywords element doesn’t exist
Fixed
- Social Media preview targets are now only added if the element has a
uri
that is notnull
3.2.39 - 2020.01.17****Added
- SEOmatic will now send back an array of data in the
metaScriptContainer
for GraphQL, etc. so that you can get at both thescript
andbodyScript
even ifisArray
is false - When an entry is saved, if the value in an SEO Settings field matches the value in Content SEO for that section, the field is set to an empty value to allow for overriding
Fixed
- Fixed an issue where you couldn’t change the Facebook OpenGraph Type in Content SEO if you had an SEO Settings field added to that section
- SEO Settings fields no longer defaults to whatever the parent element’s Content SEO settings, which fixes the override cascade
3.2.38 - 2020.01.07****Changed
- Saving changes to the SEOmatic settings will now also clear the GraphQL caches on Craft 3.3 or later
- SEOmatic now tracks if sitemap jobs are pushed into the queue, and will release old sitemap queue jobs so that they don’t stack up
Fixed
- Fixed an issue where the JavaScript console could have an error logged if there were no keywords
- Make sure
twitter:creator
andtwitter:site
are not resolve as aliases
3.2.37 - 2019.12.11****Security
- Throw an exception if an invalid sort field is passed into the
actionMetaBundles()
controller method, to eliminate a low-impact SQL injection vulnerability
3.2.36 - 2019.12.10****Security
- Fixed a low-impact SQL injection vulnerability
3.2.35 - 2019.11.26****Added
- Added a
siteUrlOverride
config setting for when you need to override thesiteUrl
, for instance in a headless GraphQL or ElementAPI setup
Changed
- If a
config/seomatic.php
file is present, use that as the source of truth for the'environment'
setting - Refactored the plugin settings into separate tabs to make them easier to use
Fixed
- Removed thousands separator from Product schema
3.2.34 - 2019.11.19****Changed
- Made the
robots
default to an empty value for SEO Settings fields - Updated the URL for sitemap submissions to the Bing search engine
- URL encode the query part of the sitemap submissions to search engines
3.2.33 - 2019.11.11****Added
- Added
MAX_TEMPLATE_LENGTH
to prevent rendering super large object templates
Changed
- Renamed several JSON-LD core types that were using reserved PHP 7 class names
- No longer match disabled elements unless we’re previewing
3.2.32 - 2019.11.05****Changed
- Rolled back a change that could cause the CP and site to slow down on uncached requests
3.2.31 - 2019.11.04****Changed
- Fixed the base image transform to be
'position' => null
3.2.30 - 2019.10.31****Changed
- SEOmatic will now invalidate container caches if they contain pending image transforms
- Enforce the
og:locale
andog:locale:alternaate
formats ofxx_XX
even for two-character language codes - Set
'position' => 'null'
for the base image transforms
3.2.29 - 2019.10.24****Changed
- If an section has its robots set to
none
ornoindex
in Content SEO, don’t add it to the sitemap index - Add a Lowercase Canonical URL setting to Plugin Settings
- Fixed an issue with the
DataType
JSON-LD type - Cleaned up the GraphQL type generator
3.2.28 - 2019.10.08****Changed
- The sitemaps and sitemap indexes that SEOmatic generates are now automatically minified
- Added native GraphQL support
3.2.27 - 2019.09.30****Changed
- Fixed an issue with breadcrumbs beyond the first one
3.2.26 - 2019.09.26****Changed
- Fixed an issue where SEOmatic would put multiple sitemap entries for recurring Solspace Calendar events
- Removed errant logging in the Content SEO controller
- Fixed an issue where the script tag caches could be outputting something other than a string
- Updated the Breadcrumbs format to match Google’s new format requirements
- More specifically list what happens in
local
dev &staging
environments
3.2.25 - 2019.09.18****Changed
- Fixed an issue where
mainEntityOfPage
overrides via an SEO Settings field could be the wrong model type
3.2.24 - 2019.09.09****Changed
- Fixed a potential XSS issue if you used
{% do seomatic.helper.paginate() %}
and there was a malformed query string - Replaced frontend api route with an actionUrl()
3.2.23 - 2019.09.06****Changed
- Fixed a typo in the environment info popup
- If the SEO image is not on a local volume, avoid a potentially long round-trip by being paranoid, and defaulting to not generating the image transform immediately
3.2.22 - 2019.09.03****Changed
- Cleaned up the
title
parsing to allow forsiteName
only titles more cleanly - If the source asset file is missing, set
generateNow
tofalse
rather thannull
, overridinggenerateTransformsBeforePageLoad
- Maintain the currently selected site between global nav items in the CP sidebar
3.2.21 - 2019.08.26****Changed
- Fixed an issue where SEOmatic would errantly say the environment was disabled
- Parse the SEOmatic environment variable in the environment check
- Preflight to ensure that the source asset actually exists to avoid Craft hanging
- Fix incorrect event type for
RegisterSitemapUrlsEvent
3.2.20 - 2019.08.16****Changed
- Added a Environment label on the Dashboard, with explanations for why the environment setting is overridden (if it is)
3.2.19 - 2019.08.06****Changed
- Strip the query string at render time for the
canonical
link, to ensure any Craft 3.2token
params are stripped
3.2.18 - 2019.07.31****Added
- Added searching, sorting, and pagination to the Content SEO pages
Changed
- Typecast the
sourceName
andsourceTemplate
to a string before validation - Moved over to a more modern tokenfield library for SEO Keywords
3.2.17 - 2019.07.25****Changed
- Typecast the
sourceName
andsourceTemplate
to a string everywhere, to handle numeric section/template names - No longer use
error
andwarning
log levels for MetaItem debug messages - No longer use
error
log levels for MetaTag debug messages
3.2.16 - 2019.07.18****Added
- Added Social Media Preview Target plugin setting
- Added
X-Robots-Tag: noindex
header to the sitemaps to prevent the sitemaps themselves from appearing in the SERP
Changed
- Fixed an issue with the sitemap generation not respecting an already running queue
3.2.15 - 2019.07.15****Changed
- Fixed an issue where assigning a Rich Text field to a JSON-LD property didn’t work
- Added typecast behavior to the
MetaBundle
model - Typecast the
MetaBundle
sourceName
to a string
3.2.14 - 2019.07.12****Added
- Added to the cache tag dependencies for the Field’s preview data
- Added
sourceType
to theInvalidateContainerCachesEvent
event - Added
siteId
andsourceType
to the source cache tag dependencies
Changed
- Prevented public accessing of the Social Media Preview
- Added a 📣 in front of the Social Media Preview
3.2.13 - 2019.07.11****Added
- Added Social Media Preview as a Live Preview target on Craft 3.2 or later
3.2.12 - 2019.07.10****Changed
- Do not invalidate meta bundle for drafts and revisions in Craft 3.2 or later
3.2.11 - 2019.07.09****Changed
- If an entry has its robots set to
none
ornoindex
, don’t add it to the sitemap - Only append
mtime
to an SEO image if there are no query params already
3.2.10 - 2019.06.27****Added
- The generated JSON-LD now uses a single root JSON-LD object with the JSON-LD types included in the
@graph
array
Changed
- Fixed an issue where headers were sent when the corresponding tags were not present
- Fixed an issue that caused SEOmatic to throw an error after you deleted a Solspace Calender calendar
- If we’re not in local dev, tell it to generate the transform immediately so that urls like
actions/assets/generate-transform
don’t get cached - Add an
mtime
cache busting URL param to all social media images - The Facebook and Twitter Transform and Transform Mode settings are now visible even if “Same As SEO Image” is selected
3.2.9 - 2019.06.13****Changed
- Fixed an issue where the built JS bundles would error inside of webpack
3.2.8 - 2019.06.13****Changed
- Switched over to
startDateLocalized
&endDateLocalized
for Solspace Calendar defaults - Fixed an issue with the Breadcrumbs JSON-LD not being generated properly for sites that has a path as part of their URL (e.g.
example.com/us/
) - Handle an edge-case where a migration didn’t work properly to add
ADS_TXT_HANDLE
- Fixed an issue where an error would be thrown if a new Section was created, and you had a site group that had no sites in it
- Fixed an issue where the SEOmatic CSS was affecting the CP CSS
- Fixed the Look up Latitude/Longitude button; it now opens www.latlong.net because Google requires an API key now
3.2.7 - 2019.06.03****Changed
- Added the ability to pass in
asArray
as a parameter for CraftQL queries to a JSON-encoded array of data back - Updated build system
3.2.6 - 2019.05.29****Changed
- Updated to schema.org 3.6 with over 900 JSON-LD Structured Data schemas!
3.2.5 - 2019.05.29****Changed
- Added
FAQPage
schema type from schema.org - Ensure that URLs with spaces or other non-RFC1738 compliant characters are encoded
- Replace “steps” by “step” in HowTo JSON-LD
- Changed
copyrightYear
to output just the year - Fixed an issue with the JavaScript bundle not instantiating for SEO Settings fields
- Updated to latest npm deps
3.2.4 - 2019.05.24****Changed
- Fixed a typecasting issue that caused
link rel="alternate"
to render for entries that were disabled for a particular site - Remove pagination via query string for
link rel="alternate"
- Remove the pointless
Twig_Node_Expression_EmptyCoalesce
class
3.2.3 - 2019.05.22****Changed
- Fixed an issue where the new SEO Settings Field implementation could cause images to be duplicated
- Fixed an issue where JSON-LD schema could not be properly overridden via an SEO Settings field
- Fixed an issue where the dynamically populated schema menu would have improper padding in the
value
s
3.2.2 - 2019.05.21****Changed
- Fixed an issue where a Section with no elements in it could cause the Sitemaps queue job to stall
- Fixed Slack & Discord “summary card” CSS
3.2.1 - 2019.05.21****Changed
- Fixed an issue where the Site Setup checklist wasn’t accurately reflecting the site settings
- Fixed an issue where trying to create a new section would throw a Type Error, preventing you from doing so
3.2.0 - 2019.05.20****Added
- Added SEO Previews for LinkedIn, Pinterest, Slack, and Discord
- Added the ability to control what SEO Previews appear in the sidebar
- Added CraftQL support for fetching SEOmatic container meta data
- Added support for Solspace Calendar events for custom metadata, JSON-LD, etc.
- SEO Settings fields now default to whatever the parent element’s Content SEO settings are when instantiating it
- The Dashboard setup checklists now display checkboxes for items have have been set up properly
- Added a
SeoElementInterface
to abstract out the support for custom elements
Changed
- Changed paginated
rel="alternate"
URLs to always point to the first page in other languages, not the paginated page (that may or may not exist) - Fixed an issue in
getLocalizedUrls()
so that it handlesgetElementUriForSite()
returning bothnull
andfalse
- If a meta value with the key of
target
(used for schema.orgSearchAction
s) doesn’t have a{
as the first character, it is not parsed as Twig - Fixed an issue where environment variables in tracking scripts were not parsed
3.1.50 - 2019.04.30****Added
- Added the
???
Empty Coalesce operator to allow for the easy cascading of default text/image SEO values
Changed
- Fix the
addXDefaultHrefLang
so it doesn’t throw an error if enabled
3.1.49 - 2019.04.22****Changed
- Don’t create
rel=alternate
links for sections that aren’t enabled for a site - Added a new
addXDefaultHrefLang
setting (which defaults totrue
) to control whether thex-default
hreflang
tag is included - Updated Twig namespacing to be compliant with deprecated class aliases in 2.7.x
- Changed the default Google Tag Manager data layer variable back to the default
dataLayer
(which it should have been all along) - Fixed
SoftwareApplication
JSON-LD object model
3.1.48 - 2019.04.16****Changed
- Added
/cache/
to the default paths excluded inrobots.txt
to auto-exclude the default Blitz/cache/blitz/
path - SEOmatic now throws a
AddDynamicMetaEvent
event to give modules/plugins a chance to add any dynamic meta items to SEOmatic’s containers - SEOmatic now throws a
InvalidateContainerCachesEvent
event whenever it clears its meta container caches, so other plugins/modules can listen in for it - No longer regenerate sitemaps when a Section is edited and
'regenerateSitemapsAutomatically' => false
- Update the display name of sections, category groups, and products in Content SEO when they are edited
3.1.47 - 2019.04.02****Changed
- Added
Environment::determineEnvironment()
so SEOmatic is can be smarter about automatically mapping environments - Allow the SEOmatic Environment plugin setting to be an Environment Variable in Craft 3.1 or higher
- Allow for Section handles that are longer than 64 characters
- Fixed an issue where the
mainEntityOfPage
could reset to the defaultWebPage
if you saved the settings on panes other than General - Fixed an issue with paginated
rel="alternate"
links on a multi-site setup where the slugs differed from site to site
3.1.46 - 2019.03.15****Changed
- Use dash instead of underscore for sitemap urls
- Don’t allow editing of the plugin settings if
allowAdminChanges
is false - Sort Content SEO listings by name to make things easier to find
- Add missing properties to the
Question
JSON-LD schema
3.1.45 - 2019.03.04****Changed
- Fixed an issue where
container.clearCache
wasn’t using the correct cache key to invalidate the cache - Fixed an issue where Google Tag Manager would render in Live Preview
- Added try/catch around alias/parseEnv to try to catch errors that shouldn’t happen
3.1.44 - 2019.02.18****Changed
- Fixed an issue with the URL in the sitemap index to the custom sitemap was invalid
- Fixed an issue when using the meta containers controller with tracking scripts
and asArray=true
3.1.43 - 2019.02.15****Changed
- Fixed an issue in Content SEO if no field layouts are yet defined
- Fixed a regression where pagination info is stripped from hreflang
- Add
JSON_HEX_TAG
flag for encoding JSON-LD to ensure that<
&>
are escaped - Addressed an issue where you couldn’t set the Main Entity of Page to nothing in Content SEO settings
3.1.42 - 2019.02.07****Changed
- Fixed an issue where
.env
vars were not actually parsed for the Tracking settings
3.1.41 - 2019.02.07****Changed
- If you’re using Craft 3.1, SEOmatic variables/fields are parsed for environment variables as well as aliases
- All tracking fields auto-complete
.env
environment variables
3.1.40 - 2019.01.30****Changed
- Fixed an issue with sitemap generation if your Section had a Neo field in it
- Fixed an issue if you passed in no parameters to
seomatic.helper.getLocalizedUrls()
could cause the incorrect localized URLs to be returned - Removed errant error logging
3.1.39 - 2019.01.24****Added
- Added a SEO Setup checklist to the Dashboard
- Added support for pulling content from Neo fields
Changed
- Fixed an issue where the generated
hreflang
URLs were wrong if you had localized slugs - Sitemaps now return a 503 Service Unavailable an a
Retry-After
so bots will try back later if for some reason they can’t be rendered for the current request (Async Queue generation, etc.) - Fixed a namespacing issue with
UrlHelper
- Handle the case where no sections have been set up yet more gracefully
3.1.38 - 2019.01.03****Changed
- Register cache options for every type of request
- Refactored the sitemaps and sitemap indexes to always be in the server root, as per the sitemaps spec
3.1.37 - 2018.12.19****Changed
- Ensure that title truncation handles edge cases gracefully
- Breadcrumbs in the CP now maintain the selected site
- Parse sitemaps and sitemap URLs for aliases and as Twig templates
- Don’t try to add assets with null URLs to sitemaps
3.1.36 - 2018.12.10****Added
- Added the ability to add additional sitemaps that exist out of the CMS into the
sitemap.xml
via Site Settings -> Sitemap as well as via plugin
Changed
- Fixed an issue where
LocalBusiness
JSON-LD type didn’t inherit all of the properties fromPlace
that it should - Fixed an issue with
seomatic.helper.getLocalizedUrls
not working as expected for routes other than the current request - Fixed an issue where plugin-generated custom sitemap URLs didn’t have their
lastmod
respected for the sitemap index - Fixed an issue accessing
metaBundleSettings
in the Field when it doesn’t exist
3.1.35 - 2018.12.03****Changed
- Fixed an issue where the
potentialAction
JSON-LD for the Site Links Search was rendered even if it was left empty - Fixed an issue where the SEO Settings field did not properly override the
mainEntityOfPage
3.1.34 - 2018.11.28****Added
- Added a level 2 cache on the controller-based API requests for meta containers to improve “headless” performance
- Added support for LinkedIn Insight analytics in Tracking Scripts
- Added support for HubSpot analytics in Tracking Scripts
- Display the status of tracking scripts in the listing section
- Allow editing of the tracking scripts body scripts
Changed
- Added the Open Graph tag
og:site_name
- Removed
craftcms/vue-asset
composer dependency - Call
App::maxPowerCaptain()
whenever a queue is manually run (both via web and console request)
3.1.33 - 2018.11.22****Changed
- Fixed an issue with socialTransform() throwing a Twig exception
3.1.32 - 2018.11.19****Added
- Added
<title>
prefixes for the Control Panel anddevMode
Control Panel - Allow social media images to be either
.jpg
or.png
formats
3.1.31 - 2018.11.18****Added
- Added a console command
./craft seomatic/sitemap/generate
to generate sitemaps via the CLI - Added the SEOmatic->Plugin setting Regenerate Sitemaps Automatically to control the automatic regenerate of sitemaps
Changed
- Fix division by zero error if no sections exist
- Dynamically base the Twitter transform type from the current evaluated type, rather than hardcoding it
3.1.30 - 2018.11.13****Added
- Added support for the ads.txt Authorized Digital Sellers standard
Changed
- Clear FastCGI Caches upon sitemap generation
- If
runQueueAutomatically
istrue
return the generated sitemap immediately via http request - Adjusted Control Panel dashboard charts
- Fixed an issue where the Content SEO settings would display sections that are not enabled for a given site
3.1.29 - 2018.11.11****Changed
- Added the ability to show SEO Settings fields in the Element Index’s Table Columns
- Redid the Dashboard graphs to be more useful and modern looking
- Modernized package.json and webpack build
- Confetti on install (yay!)
3.1.28 - 2018.11.07****Changed
- Remove
__home__
from preview URIs - Fixed a regression that caused the SEO Settings field to not override things like Facebook/Twitter images properly
- Fixed an issue that caused the SEO Settings field to not display tabs properly if the General tab was hidden
3.1.27 - 2018.11.07****Changed
- Fixed an issue where sitemaps generated in the Control Panel did not have the proper cache duration set, so they were always invalidated
- Disabled tracking scripts from sending Page View data during Live Preview
- Ensure background image values are quoted for the SEO previews
- If
runQueueAutomatically
is set, start running the queue job to generate the sitemap immediately
3.1.26 - 2018.11.05****Changed
- Don’t regenerate the sitemaps when elements are being re-saved enmasse via Section resaving
- Fixed JavaScript console error due to outdated assets build
3.1.25 - 2018.11.05****Added
- Moved sitemap generation to a queue job, to allow for very large sitemaps to be generated without timing out
Changed
- Normalize the incoming URI to account for
__home__
3.1.24 - 2018.11.02****Added
- Added the ability to control the depth that sitemaps should be generated for Categories (just like already existed for Structures)
- Added
EVENT_INCLUDE_CONTAINER
event to manipulate containers - Always create sitemap URLs from the given site, since they have to have the same origin
- Added labels to the Google, Twitter, and Facebook previews
Changed
- Fix rendering for MetaLink and MetaTag with multiple tags when requesting them via Controller
- Fixed an issue where SEO Settings fields would override the Sitemap settings even if that was disabled
- Fixed an issue with the SEO Settings field when switching between Entry Types
- Pass down the
$uri
and$siteId
toaddDynamicMetaToContainers()
toaddMetaLinkHrefLang()
- Fix rendering of canonical and home links from Controllers
- Fixed an issue with there Dashboard charts could be out of sync if sections were deleted/renamed
- Use the default transform mechanism for SEO images
- Only include the fields the user is allowed to edit in the SEO Settings overrides
- Fixed an issue where Twitter images could be resized improperly based on the card type
3.1.23 - 2018.10.15****Changed
- Returns the correct
sitemap.xml
for multi-site “sister site” groups - Cache frontend templates on a per-site basis
- Make sure that
humans.txt
links are full URLs - Handle the case where all Same As URLs are deleted
- Fixed an issue where
hreflang
tags were still added even with the setting was disabled, but only for paginated entries - Changed the default
title
length to70
and the defaultdescription
length to155
- Fixed an issue where nested JSON-LD objects would contain erroneous
key
andinclude
properties
3.1.22 - 2018.09.25****Changed
- Fixed an issue where choosing All for sitemap Structure Depth resulted in it displaying nothing
- Fixed an issue with the SiteLinks Search Box not having the correct format in
query-input
- Fixed an issue where Craft could sometimes hang if we asked for an image transform with
generateNow
=true
3.1.21 - 2018.09.18****Added
- Added the
.clearCache
property to all meta containers, allowing them to be manually cleared via Twig - Don’t include any dynamic metadata for response codes
>= 400
Changed
- SEOmatic will now automatically take the
dataLayer
property into account for the script container’s cache key - Better document titles for SEOmatic Control Panel pages
- Remove vestigial Redirects classes
- Don’t check the response
statusCode
for console requests
3.1.20 - 2018.09.12****Added
- Added memoization cache to the FieldHelper class to help improve inner loop performance
- Add the ability to control structure depth for sitemaps
Changed
- For requests with a status code of >= 400, use one cache key
3.1.19 - 2018.09.04****Changed
- Changed the Composer dependency for
davechild/textstatistics
to lock it down to1.0.2
Semver?
3.1.18.1 - 2018.08.30****Changed
- Fixed an
undefined index
error
3.1.18 - 2018.08.30****Added
- Added the Site Groups define logically separate sites Plugin Setting to allow for different Site Group use-cases
Changed
- Removed potential duplicates from
og:locale:alternate
- Don’t include
alternate
orog:locale:alternate
tags for Content SEO sections that have Sitemaps disabled - Handle disabled sections for sites in Content SEO better
3.1.17 - 2018.08.29****Changed
- Fixed an error trying to access a property of a non-object in MetaContainers.php
- Prevent classname conflict with older versions of PHP
- Fix an issue where transform modes didn’t work with Custom Image sources
- Scale the
logo
to fit to 600x60 as per Google specs
3.1.16 - 2018.08.23****Changed
- Handle elements that don’t exist on other sites better
- Don’t include hreflang in sitemaps for sites where it has been disabled, whether through Content SEO or SEO Settings field settings
- Hide Transform Image and Transform Type in the SEO Settings field if they aren’t enabled
- Fixed a conflicting use \craft\helpers\Json import
3.1.15 - 2018.08.16****Changed
- Fixed an issue where sitemap caches were not getting properly cleared
- Fixed an issue where elements disabled in a site were showing up in the
hreflang
- Fixed namespaces and custom sitemap event triggering
3.1.14 - 2018.08.14****Added
- Added in the ability to override sitemap settings on a per-Entry/Category Group/Product basis
- Implement
Json::decode()
to avoid large integers being converted to floats - If the SEO Settings field for an entry has Robots set to
none
or has sitemaps disabled, it isn’t included in thehreflang
- Added a setting to control whether
hreflang
tags are automatically added
Changed
- Ensure that the sitemap index cache gets invalidated when entries are modified
- Specify
rel="noopener"
for external links. - Fix the order that the field migration happens to let the mapping magic happen
- SEOmatic now requires Craft CMS 3.0.20 or later
- Fixed an issue with paginated pages that have no results on them
3.1.13.1 - 2018.08.07****Changed
- Fixed a potential
undefined index
error with pull fields, resulting from the new cropping modes
3.1.13 - 2018.08.07****Added
- Added the ability to choose between Crop (the default), Fit, or Stretch for the SEO, Twitter, and Facebook image transforms
Changed
- Brought back the missing ** Transform Facebook OpenGraph Image** field
- Don’t do anything with pagination on console requests
3.1.12 - 2018.08.06****Changed
- Make the base
Container
class extendFluentModel
so that containers can be accessed via templates just like MetaTags are - Ensure that we check to see if a container’s
include
property is set before rendering it - Use a unique cache key for everything for the request, including the pagination and URI
- Prep script containers for inclusion in
includeScriptBodyHtml()
3.1.11 - 2018.08.05****Changed
- Fixed a regression that caused an error loading entries
3.1.10 - 2018.08.05****Changed
- Cleaned up how the pagination cache key works
- Add the current request path into the mix for the meta container cache key
- Force social media values to be displayed as strings
3.1.9 - 2018.08.04****Changed
- Fixed an issue where SEOmatic wouldn’t find Entry metadata if the entry was first saved as a Draft, then published
- Include the pagination page in the cache key to ensure paginated pages are uniquely cached
3.1.8 - 2018.08.03****Changed
- Fixed a regression that caused you to be unable to save Custom URL for an image source in the Control Panel
3.1.7 - 2018.08.02****Changed
- Fixed an issue where Content SEO permissions were not respected properly in the Control Panel
- Display the Tracking Scripts status in the Control Panel regardless of
devMode
setting
Added
- Don’t render a canonical url for http status codes >= 400
- Set meta robots tag to
none
for http status codes >= 400
Security
- Decode HTML entities, then strip tags in
safeCanonicalUrl()
3.1.6 - 2018.07.25****Changed
- Really ensure that paginated pages are cached separately in the second-level cache
3.1.5 - 2018.07.24****Changed
- No longer include any matched element in the Content SEO previews (which can be confusing if there are SEO Settings field overrides)
- Ensure that paginated pages are cached separately in the second-level cache
- Fixed an issue where changes to the SEO Image would not propagate to the Facebook/Twitter image when changed if “Same as SEO Image” was set
3.1.4 - 2018.07.23 [CRITICAL]****Security
- Changed the way requests that don’t match any elements generate the
canonicalUrl
, to avoid potentially executing injected Twig code
3.1.3 - 2018.07.20****Added
- Added Additional Sitemap URLs to Site Settings -> Miscellaneous for custom sitemap URLs
- Added
EVENT_REGISTER_SITEMAP_URLS
event so plugins can register custom sitemap URLs - Added the
Referrer-Policy
header based on the value of thereferrer
tag - Added the ability to control whether any http response headers are added by SEOmatic
- Added the Facebook OpenGraph tags
og:image:width
&og:image:height
- Added the Twitter card tags
twitter:image:width
&twitter:image:height
Changed
- Clear SEOmatic caches after saving the plugin settings
- Fixed an issue where boolean settings in meta containers that were set to false would not override as expected
3.1.2 - 2018.07.17****Changed
- Fixed an issue with the language being set to
en_US
instead ofen-US
ingetLocalizedUrls()
3.1.1 - 2018.07.14****Changed
- Fix parsing logic error in
MetaValue
- Fixed an issue where the SiteLinks Search Box wouldn’t work because it errantly parsed the setting as Twig
- Better title for pull field dropdown menus
- Fix potential preview issues in Content SEO for certain multi-site setups
3.1.0 - 2018.07.11****Added
- Added full support for Craft Commerce 2
- Added a caching layer to
includeMetaContainers()
for improved performance - Added more fine-grained profiling data
- Re-organized how event handlers are loaded to allow for compatibility with Fallback Site plugin
Changed
- Canonical URLs are now always lower-cased, and made absolute
- Fixed an issue where the SiteLinks Search Box wouldn’t work because it errantly parsed the setting as Twig
- Allow for default empty settings for the SEO Settings field for things like the Twitter Card type, etc.
- Added a warning to let people know tracking scripts are disabled when
devMode
is on - Fixed an issue with JSON-LD dropping certain properties if non-default types were selected
3.0.25 - 2018.07.03****Changed
- Strip tags from the incoming
craft.app.request.pathInfo
for thecanonicalUrl
- Fixed the breadcrumbs link on the Plugin Settings page
- Fixed an issue where users without admin privileges could not save the SEOmatic Plugin Settings
- Fixed an issue where category groups would be lumped together in the sitemap
- Fixed an issue with og:locale and og:locale:alternate being improperly formatted
3.0.24 - 2018.06.25****Added
- Allow the use of Emoji in the plugin settings, such as for the
devMode
title prefix
Changed
- Set the default devMode title prefix to 🚧
- Sync section / category group handles that are renamed
- Don’t log meta item error messages unless
devMode
is on - Don’t encode preview URLs
- Fixed an issue where disabling a section’s URLs was not sync properly with the Content SEO settings
3.0.23 - 2018.06.18****Added
- Added support for emojis in any of the SEOmatic fields
Changed
- Fixed an issue introduced in Craft CMS 3.0.10 that would cause JSON-LD to be not fully rendered
- Allow nothing (
--
) to be selected as a Source Field in the Image/Video Sitemap fields - Added cache busting to the SEO preview images so that they will always display the latest image
- Fixed an issue where removing an SEO Image from an SEO Settings field would cause it to persist
3.0.22 - 2018.06.12****Changed
- Remove default value for devMode Prefix that prevented it from saving an empty value
- Fix default values for Title position, Twitter Title position, and OG Title position
- Allow for the setting of the
dataLayer
via Twig for Google Tag Manager - Added pagination support via
seomatic.helper.paginate()
to properly set the paginatedcanonicalUrl
as well as the<link rel='prev'>
and<link rel='next'>
tags - Preserve the pagination trigger query string for the
<link rel='hreflang'>
tags
3.0.21 - 2018.06.01****Changed
- Fixed
ContactPoint
rendering - Fixed an issue where an array of one JSON-LD would not render
- Make JSON-LD URLs fully qualified
3.0.20 - 2018.05.31****Changed
- Make sure
twitter:creator
andtwitter:site
are not resolve as aliases - Fixed an issue where
syncBundleWithConfig
could returnnull
- Preserve the FrontendTemplate settings during meta bundle updates
3.0.19 - 2018.05.21****Changed
- Ensure that the previews are not double-encoded
- Remove vestigial meta bundles from the sitemap index
3.0.18 - 2018.05.20****Changed
- Fixed an issue where the JSON-LD types weren’t correct
- Sync bundle when Global SEO, Content SEO, and Site Settings are changed
- Ensure that the first character of each meta item key is lower-cased
- Render JSON-LD properties that have an
@id
set
3.0.17 - 2018.05.19****Changed
- Make the various
seomatic.helper
functions more tolerant about havingnull
passed in as a parameter
3.0.16 - 2018.05.18****Changed
- Fixed a regression that the
rel="alternate"
link tags to not render properly - Fixed a regression where the Site Settings would throw an exception
3.0.15 - 2018.05.17****Changed
- Fixed a regression that caused per-environment settings to be applied in the Control Panel
- Fixed an issue that caused
seomatic.xxx.get()
to not returnnull
if no matching item was found
3.0.14 - 2018.05.17****Changed
- Ensure that any image or video URLs in the sitemap are full absolute URLs
- Fixed multiple issues with the
gtag.js
script that prevented it from working properly - HTML-encode all URLs and user-enterable data in the sitemaps and sitemap indexes
- Fixed an issue where the meta items are not indexed properly, causing you to be unable to get them from the Twig API
- Fixed an issue where meta items that should have been excluded by environment were not
3.0.13 - 2018.05.15****Changed
- Fixed an issue where the
gtag
body script did not properly render - Fixed an issue where empty results for pull fields would not fall back on the parent (usually global) settings
- Fixed an issue where
seomatic.helper.loadMetadataForUri()
might not replace the container metadata properly
3.0.12 - 2018.05.10****Changed
- Switch from
.one()
syntax to[0]
to account for eager loading of transformed social media images - Fixed an issue where SEOmatic incorrectly showed how many categories were in a category group on the Content SEO page
- Fixed an issue where Content SEO social images wouldn’t fall back on the global images if they were set to “Same as SEO Image” and the SEO Image was empty
- Fixed a typo in the SEO Settings field settings
- SEOmatic no longer renders the
rel="author"
tag if you havehumans.txt
disabled
Added
- Added translations for the SEO Settings Field options
3.0.11 - 2018.05.03****Changed
- Removed
'interlace' => 'line'
from the social media transforms, which inexplicably caused Focal Points to not be used - Fixed an issue where the JSON-LD would not fully render due to a regression
3.0.10 - 2018.05.02****Changed
- Fixed incorrect social media permissions that prevented access to that settings page
- Fixed an issue where
section
meta bundles would be improperly marked asfield
due to a regression in the migration importing code - Fixed an issue where
categoryGroup
meta bundles would be improperly marked asfield
due to a regression in the migration importing code - Removed OpenGraph tag dependency on
facebookProfileId
orfacebookAppId
being present - Fixed Pinterest verification tag dependency
- Bumped the schemaVersion
Added
- Added a migration to remove any errant
seomatic_metabundles
rows that havesourceBundleType
set tofield
3.0.9 - 2018.05.01****Changed
- Fixed an issue when migrating data from Craft 2.x
Seomatic_Meta
fields and an Asset was set to “Custom”
3.0.8 - 2018.04.30****Changed
- Removed excessive validation that was causing SEOmatic Fields to not save properly
3.0.7 - 2018.04.30****Changed
- Fixed a regression that caused SEOmatic to not import data from old Craft 2.x
Seomatic_Meta
fields properly
3.0.6 - 2018.04.30****Changed
- Fixed a regression that caused the Section meta bundles to be the wrong type
3.0.5 - 2018.04.27****Changed
- Better instructions for the Canonical URL
- Updated translations
- Use correct
sourceBundleType
for Field meta bundles - Fixed a regression that caused Content SEO sections to not save properly
3.0.4 - 2018.04.26****Changed
- Don’t display Sections / Category Groups in Content SEO that no longer have public URLs
- Fixed an issue with console requests
- Fixed an issue where Sections and Category groups with the same
handle
didn’t work right in Content SEO - More validation on the data passed into the SEO Settings field as a config array
3.0.3 - 2018.04.25****Changed
- Fixed an issue where re-using the same Field handle from other Field types would cause an exception to be thrown in the Control Panel
- Improved the way SEOmatic matches the current element
- Bypass the data cache entirely in the Control Panel, to avoid refresh issues
- Fixed an issue where sometimes the correct data is not what is previewed in the Control Panel
- Fixed an issue where the
canonicalUrl
seemed immutable on the Global SEO pages
3.0.2 - 2018.04.24****Added
og:image
tags are now validated to ensure they are fully qualified URLsog:image
tags now are converted to absolute URLs (to handle protocol-less URLs)twitter:image
tags are now validated to ensure they are fully qualified URLstwitter:image
tags now are converted to absolute URLs (to handle protocol-less URLs)- Added missing translations
Changed
- Fixed an issue where Tracking Scripts permissions weren’t all propertly presented
3.0.1 - 2018.04.20****Changed
- Fixed an issue with sitemap indexes for elements that have null URLs
- Fixed an issue with permissions and the Tracking Scripts page
3.0.0 - 2018.04.17****Added
- Official GA release
3.0.0-beta.24 - 2018.04.17****Changed
- Fixed a regression that caused the Site switcher to no longer work in the SEOmatic settings
- Fixed a regression that could cause the sitemap index to include the appropriate sections
3.0.0-beta.23 - 2018.04.16****Changed
- Fixed an issue where the social transforms sometimes might not render properly
- SEOmatic now requires Craft CMS 3.0.2 or later (so we can listen to
TemplateCaches::EVENT_AFTER_DELETE_CACHES
) - Handle Section or Category Groups that may have had their handles renamed
Added
- SEOmatic now clears its caches any time
TemplateCaches::EVENT_AFTER_DELETE_CACHES
is triggered - If the FastcgiCacheBust plugins is installed, clear its caches when SEOmatic clears its own caches
3.0.0-beta.22 - 2018.04.12****Added
- Added performance profiling to major bottlenecks
- Lots of code cleanup courtesy of the PHP Inspections plugin
Changed
- Fixed an issue with the Field improperly saving values as objects
- Removed caching from Control Panel requests, which fixes improperly displayed social media previews
- Fixed a deprecation error with
.iso8601()
Changed****3.0.0-beta.21 - 2018.04.06****Added
- Don’t display the Facebook/Twitter not set in the sidebar preview, only on the Settings pages
- Added an
Seomatic_Meta
Field to more gracefully handle sites upgraded from Craft 2.x that used the old FieldType - If you add an SEO Settings field to a Section that has an old Craft 2.x Seomatic Meta field in it, it will automatically migrate the data and settings to the new field for you
- SEOmatic will automatically map your old Craft 2.x Field settings to corresponding Content SEO settings
Changed
- Better Dashboard display of SEO setup graphs
- Fixed an issue with an improperly named Site / Social Media permission
- Fixed an issue with the helper functions not gracefully handling
null
being passed in - Fixed validation errors that could cause you to be unable to save changes to various SEOmatic settings
3.0.0-beta.20 - 2018.04.02****Changed
- Added additional fields for the
mainEntityOfPage
JSON-LD - Clicking on Settings on from the Control Panel now redirects to the appropriate SEOmatic sub-nav
Added
- Added an SEO Settings Field that allows you to override SEO settings on a per-entry basis
- Added a schema.org link for the Main Entity of Page type you have specified
- Added
seomatic.helper.truncate
andseomatic.helper.truncateOnWord
helper functions for truncating text
3.0.0-beta.19 - 2018.03.28****Changed
- Fixed an issue where you could not disable
humans.txt
orrobots.txt
- Fixed an issue where the
computedType
wasn’t saved properly for Global and Content SEO - Fixed an issue with JSON-LD generated for content containers not cascading as intended
Added
- Added the ability to globally disable sitemap rendering
3.0.0-beta.18 - 2018.03.26****Changed
- Preserve Site Identity and Site Creator settings across bundle updates
3.0.0-beta.17 - 2018.03.26****Changed
- Check against
siteType
,siteSubType
andsiteSpecificType
beingnull
on the Site Settings pages - Updated
humans.txt
template to display information from the Creator settings - Separate Identity and Creator Entity Brand fields
- Remove JSON-LD schema.org properties that have just one entry in them (just the
@type
) - Fixed an issue where
hreflang
s could be incorrect
Added
- Documented the Identity and Creator Site Settings variables
- Added
menu
andacceptsReservations
to the FoodEstablishment JSON-LD - Added link
rel=“home”
to the default tag container - Added
seomatic.helper.getLocalizedUrls()
function that will return a list of localized URLs - Added
sameAs
social media URLs to the Identity JSON-LD - Added
og:locale:alternate
Facebook OpenGraph tags
3.0.0-beta.16 - 2018.03.25****Changed
- Fixed an issue where fresh installations were not taken to the Welcome screen
- Replaced old SEOmatic icon in the Asset Bundle
- Fixed an issue where Identity and Creator settings were not properly defaulted from the config files on fresh installations
- Better parsing of the JSON-LD config files
Added
- Added Miscellaneous settings with Google Site Links search settings
- Preserve user settings in the Tracking Scripts when bundles are updated
- Fleshed out the JSON-LD for
mainEntityOfPage
,identity
, andcreator
3.0.0-beta.15 - 2018.03.24****Changed
- Separated the mainEntityOfPage templates off into a partial
- Cleaned up the Identity Settings & Creator Settings pages
Added
- Added a description of JSON-LD Structured Data to the Identity & Creator pages
- Added Main Entity of Page settings on the Global SEO and Content SEO General pages
3.0.0-beta.14 - 2018.03.23****Changed
- Fixed an issue with console requests raising an exception in
addDynamicMetaToContainers()
- Add
errors
display to all settings templates
Added
- Implemented dynamic Identity Settings & Creator Settings pages
3.0.0-beta.13 - 2018.03.22****Changed
- Don’t look for
getPathInfo()
during a console request - Fixed an issue switching between sites on the Tracking scripts settings
- Revise how
seoFileLink()
works - Handle eager loaded elements in
TextHelper
3.0.0-beta.12 - 2018.03.20****Added
- Added colored status indicators on the Content SEO index page that match the colors in the donut chart on the Dashboard
- Added
seomatic.helper.seoFileLink()
to allow setting theX-Robots-Tag
andLink
headers on static files as per Advanced rel="canonical" HTTP Headers - Added a
Link
header for the canonical URL
Changed
- Don’t display SEO previews if the Section has no URLs
3.0.0-beta.11 - 2018.03.19****Changed
- Refactored the meta bundle update process to preserve user configured meta bundle settings
- Throw a 404 if a sitemap is hit but sitemaps have been disabled for that section
- Exclude section sitemaps from the sitemap index if sitemaps have been disabled for that section
3.0.0-beta.10 - 2018.03.18****Changed
- Reverted incorrect bundle merging
3.0.0-beta.9 - 2018.03.18****Added
- Added
Schema
helper class & controller in preparation for dynamic schema types displayed in the Control Panel
Changed
- Fixed incorrect
moz-transform
vendor prefix that caused the sidebar SEO preview to look weird in FireFox - Fixed a nasty bug that could cause improper merging of config arrays, resulting in an ever-growing column size in the db
3.0.0-beta.8 - 2018.03.16****Changed
- Fixed per-environment rendering of attributes
- Made meta bundle updating non-destructive to existing data
3.0.0-beta.7 - 2018.03.16****Added
- Added a “Same as Global Site Name Position” setting as the default for the Site Name Position Content SEO settings
Changed
- Fixed an issue where the last breadcrumb on the Content SEO
edit-content
page was a 404 - Fixed a caching issue that could result in stale data if you used
seomatic.helper.loadMetadataForUri()
- Don’t automatically generate thumbnails for videos in the sitemap
- Changed the Dashboard charts over to gauge charts
3.0.0-beta.6 - 2018.03.15****Added
- Check whether the
seomatic_metabundles
table exists before installing any even listeners
3.0.0-beta.5 - 2018.03.15****Changed
- Fixed an issue where the caching didn’t work properly for multi-sites
3.0.0-beta.4 - 2018.03.14****Added
- Added a validation rule for
genericAddressCountry
so it saves - Added a validation rules for
renderEnabled
,separatorChar
,displayAnalysisSidebar
anddisplayPreviewSidebar
so you can save the plugin settings. - Added initial Dashboard
Changed
- Don’t install event listeners until after all plugins have loaded, to ensure db migrations have been run
3.0.0-beta.3 - 2018.03.14****Added
- Added a migration for older Craft 2.x sites that had SEOmatic installed already, so that SEOmatic for Craft 3 can install its base tables
Changed
- Fixed an issue with an incorrect redirect destination after saving a Tracking Scripts setting in the Control Panel
- Optimized the images used in the documentation
3.0.0-beta.2 - 2018.03.13****Changed
- Fixed issues with
: void
on PHP 7.0.x
3.0.0-beta.1 - 2018.03.13****Added
- Initial beta release