Just installed the 3.0.0-beta update into my MODX 3.0.0-beta1 installation. Installation completed, but ended with this error:

Could not load class: modTransportPackage from mysql.modtransportpackage
Could not get table name for class:
Error 42000 executing statement: Array ( [0] => 42000 [1] => 1064 [2] => You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AS latestPackage WHERE latestPackage.package_name = `modTransp' at line 3 )

This line generates a warning PHP warning: Undefined array key "debug"

Maybe you can give this property a default value in constructor to prevent the warning?

When I add the property &type to SeoSuiteSitemap with either images or index no pages are returned. It works without it.

The description text below the upload field recommends a 1200x630 format as the "best format", but if I upload a landscape image, it is displayed as a square image.

P.S. From what I can see, metatag output sticks to the original image

I don't know what is going wrong, but I did the following and nothing is returned in my code on the website:

1. Install SEOsuite
2. choose upgrade SEOTab and SEOpro
3. remove SEOTab and SEOpro
4. seosuite.placeholder_plugin_enabled is enabled
5. cleared cache

Nothing happens. Only the sitemap works. Did I overlook something? Do I need to put something in the head?

disabling seosuite.placeholder_plugin_enabled and put [[!+ss.meta]] or [[!+ss_meta]] also returns nothing.

Not clear to me what goes wrong.

Modx 2.8.1. PHP 7.4

When the default media source is set to another directory in the system settings, f.e. assets/userfiles/, then the link to the image is wrong.

It must be:

<meta property="og:image" content="https://www.website.com/assets/userfiles/galleries/23/14_8.jpg" />

instead I get (when selecting the correct image in the backend):

<meta property="og:image" content="https://www.website.com/galleries/23/14_8.jpg" />

The assets/userfiles/ path is missing.

Modx 2.8.3. PHP 7.4.

I am having a routing problem migrating from apache to nginx using SEO Suite and Articles extension:

• example.com/blog/test-article.html is set in 301 redirects
• correctly redirects to example.com/blog/category/2021/10/29/test-article/ (set via freeze URL)

After migrating to nignx this redirect is not working anymore. I’m getting a 404. When I change the 301 redirect to something like this

• example.com/path/does/not/exist/article.html

it is working again.

How to reproduce this issue:

1. Install MODX with SEO Suite and Articles on LEMP Stack (using MODX docs nginx configuration file)

2. Create an ArticlesContainer called blog

3. Inside blog create an article set to unpublished => URL will be /blog/test-article.html

4. Publish article => URL will change to /blog/2021/10/29/test-article.html

5. Redirect 301 will be automatically added for /blog/test-article.html

6. Open this url
   => MODX returns 404 instead of 301

7. Modify the path of the 301 redirect to something that doesn’t exist for example /does/not/exist/test-article.html

8. Open this url
   => MODX returns 301 and redirects to the article

So it looks like nginx can’t resolve the path correctly when it matches an existing path. I am using the example nginx configuration from modx docs. Any ideas? (https://docs.modx.com/current/en/getting-started/friendly-urls/nginx)

Is this something that should be fixed in SEO Suite, in Articles extension or is the nginx configuration not setup correctly?

The SEO panel is really large, pushing the Content area way down the screen. It would be great to be able to move this under the Content area, or into a tab by itself.

As it seems, seoSuite has taken over the *longtitle field as the META title field. I can live with that, but we used to apply <strong>words</strong> or <br/> (can be <br> without slash, so no problem) in the longtitle. That worked fine but after installing seoSuite we can't do that no more as an error occurs:

VM621:1 Uncaught SyntaxError: Invalid regular expression: missing /
    at doDecode (ext-all.js:21)
    at Object.decode (ext-all.js:21)
    at Ext.form.Action.Submit.handleResponse (utilities.js:340)
    at Ext.form.Action.Submit.processResponse (ext-all.js:21)
    at Ext.form.Action.Submit.success (ext-all.js:21)
    at o (ext-all.js:21)
    at Ext.data.Connection.s (ext-all.js:21)
    at HTMLIFrameElement.I (ext-all.js:21)

We are using PHP 7.4, MySQL 8

Could not create table `seosuite_url` SQL: CREATE TABLE `seosuite_url` (`id` INTEGER unsigned NOT NULL AUTO_INCREMENT, `context_key` VARCHAR(100) NOT NULL DEFAULT '', `url` VARCHAR(2000) NOT NULL DEFAULT '', `suggestions` TEXT NULL, `visits` INTEGER(11) NOT NULL DEFAULT '0', `last_visit` TIMESTAMP NULL DEFAULT '0000-00-00 00:00:00', `createdon` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP, PRIMARY KEY (`id`), INDEX `context_key` (`context_key`), INDEX `url` (`url`)) ENGINE=InnoDB ERROR: Array ( [0] => 42000 [1] => 1071 [2] => Specified key was too long; max key length is 3072 bytes )
xPDOVehicle resolver failed: type php

Could not create table `seosuite_redirect` SQL: CREATE TABLE `seosuite_redirect` (`id` INTEGER unsigned NOT NULL AUTO_INCREMENT, `context_key` VARCHAR(100) NOT NULL DEFAULT '', `resource_id` INTEGER(10) NOT NULL DEFAULT '0', `old_url` VARCHAR(255) NOT NULL DEFAULT '', `new_url` VARCHAR(255) NOT NULL DEFAULT '', `redirect_type` VARCHAR(75) NOT NULL DEFAULT '', `active` TINYINT(1) unsigned NOT NULL DEFAULT '1', `visits` INTEGER(11) NOT NULL DEFAULT '0', `last_visit` TIMESTAMP NULL DEFAULT '0000-00-00 00:00:00', `editedon` TIMESTAMP NULL ON UPDATE CURRENT_TIMESTAMP, PRIMARY KEY (`id`), INDEX `context_key` (`context_key`), INDEX `resource_id` (`resource_id`), INDEX `old_url` (`old_url`), INDEX `active` (`active`)) ENGINE=InnoDB ERROR: Array ( [0] => 42000 [1] => 1067 [2] => Invalid default value for 'last_visit' )

Summary
Permanent error in logs:
[2021-03-26 11:53:45] (ERROR @ ../components/seosuite/model/seosuite/seosuite.class.php : 778) PHP warning: trim() expects parameter 1 to be string, array given

Environment
MODX 2.8.1-pl
SEO Suite 2.0.2-pl

Looking for a way to hide the panel that SEO Suite uses to add meta data. We often use resources that are just the content field for CSS or JS, since the SEO Suite panel is large (and isn't needed for these resources) it would be nice to be able to hide it.

This may be related to #7 or #10.

I'm not incredibly well versed in MODX development, outside of snippets and small plugins, but I could try to get a PR together if I'm pushed in the right direction 🙂

I get this warning form Facebook scraper:

The following meta tags are specified using 'name' instead of 'property' and will be ignored unless specified using the 'property' key: og:description, og:image, og:title, og:type

Hello how to fix error!

1. /xpdo/om/xpdoquery.class.php : 764) Encountered empty IN condition with key id

I have installed this on two sites and both times it caused issues with Redactor 3.0.

All formatting within Redactor is removed or set to "p" tags.

When switching to code view CodeMirror is not available and switching back removes formatting.

Thanks for all the work on this. I was paying for this extra through modmore but I see that it's no longer available there.

Modx 3.0.0-beta1
MAMP PRO 6.6
PHP 7.3.29
BD : mysql
Version : 5.7.34
SEO Suite : 2.0.5

First of all thank you for offering this great plugin to the community.

I am testing SEO Suite with Modx 3 and I am having this problem :

I got a blank page when I put an image path in the “Facebook Image” and/or “Twitter Image” field.

If I keep the “Facebook Image” and “Twitter Image” field empty, my page is displayed correctly with all the meta tags.

As soon as I enter a path in the “Facebook Image” and / or “Twitter Image” field, then I have a completely blank page, without any code.

Here is the error log:
With the image for Facebook only
[2021-11-23 23:11:05] (ERROR @ /Volumes/HDT5/webdev/modx3/core/vendor/xpdo/xpdo/src/xPDO/Om/xPDOObject.php : 227) Error 42S02 executing statement:
Array
(
[0] => 42S02
[1] => 1146
[2] => Table 'modx3beta.modx_seosuite_redirect' doesn't exist
)

[2021-11-23 23:11:24] (ERROR @ /Volumes/HDT5/webdev/modx3/core/vendor/xpdo/xpdo/src/xPDO/xPDO.php : 786) modMediaSource::load() is not a valid static method.

With image for Twitter only
[2021-11-23 23:12:27] (ERROR @ /Volumes/HDT5/webdev/modx3/core/vendor/xpdo/xpdo/src/xPDO/Om/xPDOObject.php : 227) Error 42S02 executing statement:
Array
(
[0] => 42S02
[1] => 1146
[2] => Table 'modx3beta.modx_seosuite_redirect' doesn't exist
)

[2021-11-23 23:12:42] (ERROR @ /Volumes/HDT5/webdev/modx3/core/vendor/xpdo/xpdo/src/xPDO/xPDO.php : 786) modMediaSource::load() is not a valid static method.

Thanks for your help

Be good to be able to set the media source to use for the images that are uploaded to avoid users uploading to the root of the default media source.

I haev found that SEO Suite doesn't work with Articles pages?
Which is tricky because the blog pages are the most relevant for SEO!

MODX 3.0.1, 3.0.2-dev; SEOSuite 3.0.4-beta

disabled_templates aren't working correctly:

• left empty: shows on all templates (correct)
• template(s) entered don't show but others do.

Frankly I prefer this behaviour as I'd rather opt-in than out, but it doesn't do what it's supposed to.

Summary
https://prnt.sc/14uovku/

Environment
MODX 2.8.1-pl
SEO Suite 2.0.3-pl

Add system setting for disabling/hiding the Yandex button in the search preview,.

Summary

Fatal error: Uncaught TypeError: trim(): Argument #1 ($string) must be of type string, array given in /core/components/seosuite/model/seosuite/seosuite.class.php:779
Stack trace: #0 [internal function]: trim(Array)
#1 /core/components/seosuite/model/seosuite/seosuite.class.php(779): array_map('trim', Array)
#2 /core/components/seosuite/model/seosuite/snippets/seosuitesnippets.class.php(151): SeoSuite->renderMetaValue('[[+description]...', Array)
#3 /home/smproject/330om.smartconstractor.ru/docs/core/cache/includes/elements/modsnippet/32.include.cache.php(14): SeoSuiteSnippets->seosuiteMeta(Array)
#4 /home/smproject/330om.smartconstractor.ru/docs/core/model/modx/modscript.class.php(76): include('/home/smproject...')
#5 /home/smproject/330om.smartconstractor.ru/docs/core/model/modx/modx.class.php(1861): modScript->process(NULL)
#6 /home/smproject/330om.smartconstractor.ru/docs/core/components/seosuite/model/seosuite/plugins/seosuiteresourceplugin.class.php(238): modX->runSnippet('seosuiteMeta', Array)
#7 /home/smproject/330om.smartconstractor.ru/docs/core/components/seosuite/model/seosuite/seosuite.class.php(338): SeoSuiteResourcePlugin->onLoadWebDocument(Object(modSystemEvent), Array)
#8 /home/smproject/330om.smartconstractor.ru/docs/core/cache/includes/elements/modplugin/8.include.cache.php(11): SeoSuite->firePlugins(Object(modSystemEvent), Array)
#9 /home/smproject/330om.smartconstractor.ru/docs/core/model/modx/modscript.class.php(76): include('/home/smproject...')
#10 /home/smproject/330om.smartconstractor.ru/docs/core/model/modx/modx.class.php(1670): modScript->process(NULL)
#11 /home/smproject/330om.smartconstractor.ru/docs/core/model/modx/modrequest.class.php(133): modX->invokeEvent('OnLoadWebDocume...')
#12 /home/smproject/330om.smartconstractor.ru/docs/core/model/modx/modrequest.class.php(122): modRequest->prepareResponse()
#13 /home/smproject/330om.smartconstractor.ru/docs/core/model/modx/modx.class.php(1457): modRequest->handleRequest()
#14 /home/smproject/330om.smartconstractor.ru/docs/index.php(54): modX->handleRequest()
#15 {main} thrown in /home/smproject/330om.smartconstractor.ru/docs/core/components/seosuite/model/seosuite/seosuite.class.php on line 779

Environment
MODX 2.8.2-pl
SEO Suite 2.0.2-pl

Just tried the amazing Seosuite. It’s been a bliss to see those extras work together. Thanks so much for putting it out.

So the problem I have is to display the sitemap correctly.

What i did:

1. Create a resource tpl empty
2. Uncheck cache and richtext
3. Put the snippet [[!SeoSuiteSitemap]] in content
4. Set the type to XML

But the result is: This XML file does not appear to have any style information associated with it. The document tree is shown below.

Generally, if [[*id]]==[[++error_page]], the canonical link should not get set. You would therefore be able to create a never-ending stream of self-referencing 404-pages if you post all of those into a forum post and misguide the search engine.

Easy fix for myself, for someone with little SEO knowledge however this might be something they would not want to do.

One thing I noticed is that it formats canonical links incorrectly. It outputs them as meta tags:

But they shouldn’t be meta tags - they should be output like this:

Canonical tags need their own tpl.

When there is no SeoSuiteResource object for a resource, the ss_meta placeholder does not return anything due to the return false in the seosuiteMeta method in the SeoSuiteSnippets class. I feel this return false could be removed.

So I’ve used SEO Sutie a handful of times, all great.
I prefer using the placeholders:

[[!+ss_meta.meta_title]]
[[!+ss_meta.meta_description]]
[[!+ss_meta.robots]]
[[!+ss_meta.canonical]]
[[!+ss_meta.alternates]]
[[!+ss_meta.og_title]]
[[!+ss_meta.og_description]]
[[!+ss_meta.og_image]]
[[!+ss_meta.og_image_alt]]
[[!+ss_meta.og_type]]
[[!+ss_meta.twitter_site]]
[[!+ss_meta.twitter_title]]
[[!+ss_meta.twitter_description]]
[[!+ss_meta.twitter_image]]
[[!+ss_meta.twitter_image_alt]]
[[!+ss_meta.twitter_card]]

so i can have full control over the output, rather than using this snippet:

[[!SeoSuiteMeta]]

On this occasion, I ‘migrated’ from SEO Pro to SEO Suite in the installer.

I’m not sure if this has done something different, but the placeholders don’t work - I can only bring in the meta tag using the snippet.

I’ve tried everything I can think of - turned on/off the system setting:
seosuite.placeholder_plugin_enabled

Cleared the core/cache
Logged out and in again.

I can only assume it’s related to the migration, as opposed to a standard install - although I have also reinstalled the extra.

We don't want Google to know where our MODX installation is. Is there a way to block this?

It appears that the "Include this page in the sitemap?" is on by default, but pages do not show up in the sitemap unless you open and save that resource after the SEOSuite has been installed. This would be a grand pain for sites with more than 20/4/050++ pages.

ALSO

Once a page has been added to the sitemaps - if you disable the SEOSuite on the template that generates that page - there is no way to remove it from the sitemap, unless you enable the suite, edit the page then disable the suite again. (or delete it from the seosuite_resource table)

Managing sitemap preferences, frequencies & priorities on a page by page basis is extremely cumbersome - A sitemap management tool is really needed under the Extras->Seo Suite section.

It would be really nice if users would be able to filter the SEO Suite CMP (404's) based on Context.

Redundantly managing content and images isn't something that clients like to do. This would be a lot more powerful if SEO Suite could just be installed and fall back to certain fields and values if null or empty.

Example:

• Facebook description defaults to [[*description]] if empty
• og:image defaults to a certain TV if empty, if that TV is empty, fall back to dedicated system setting
• same for title etc.

This is a great tool and could be a drop-in extension that is super powerful. Right now we need to manage each and every page individually. The process above would solve this and make it useful immediately after installation.

SEO Suite 2.0.1 seems to break the display of the rich text Content field? MODX is 2.8.1 and editor is TinyMCE 4.3.4-pl.
Removing SEO Suite restores the correct rich text display.

If you put in a value under the system setting seosuite.disabled_templates it disables SEO suite for all resources that aren't using that template rather than disabling for the specified template ID.

There is a problem when switching to php version 8.0.1.

Fatal error: Uncaught TypeError: implode(): Argument #2 ($array) must be of type ?array, string given in /home/smproject/dasha.pro/docs/core/components/seosuite/model/seosuite/snippets/seosuitesnippets.class.php:141
Stack trace:
#0 /home/smproject/dasha.pro/docs/core/components/seosuite/model/seosuite/snippets/seosuitesnippets.class.php(141): implode(Array, '\n')
#1 /home/smproject/dasha.pro/docs/core/cache/includes/elements/modsnippet/44.include.cache.php(14): SeoSuiteSnippets->seosuiteMeta(Array)
#2 /home/smproject/dasha.pro/docs/core/model/modx/modscript.class.php(76): include('/home/smproject...')
#3 /home/smproject/dasha.pro/docs/core/model/modx/modx.class.php(1865): modScript->process(NULL)
#4 /home/smproject/dasha.pro/docs/core/components/seosuite/model/seosuite/plugins/seosuiteresourceplugin.class.php(238): modX->runSnippet('seosuiteMeta', Array)
#5 /home/smproject/dasha.pro/docs/core/components/seosuite/model/seosuite/seosuite.class.php(338): SeoSuiteResourcePlugin->onLoadWebDocument(Object(modSystemEvent), Array)
#6 /home/smproject/dasha.pro/docs/core/cache/includes/elements/modplugin/21.include.cache.php(9): SeoSuite->firePlugins(Object(modSystemEvent), Array)
#7 /home/smproject/dasha.pro/docs/core/model/modx/modscript.class.php(76): include('/home/smproject...')
#8 /home/smproject/dasha.pro/docs/core/model/modx/modx.class.php(1674): modScript->process(NULL)
#9 /home/smproject/dasha.pro/docs/core/model/modx/modrequest.class.php(133): modX->invokeEvent('OnLoadWebDocume...')
#10 /home/smproject/dasha.pro/docs/core/model/modx/modrequest.class.php(122): modRequest->prepareResponse()
#11 /home/smproject/dasha.pro/docs/core/model/modx/modx.class.php(1461): modRequest->handleRequest()
#12 /home/smproject/dasha.pro/docs/index.php(54): modX->handleRequest()
#13 {main} thrown in /home/smproject/dasha.pro/docs/core/components/seosuite/model/seosuite/snippets/seosuitesnippets.class.php on line 141

After I upload image , select it, save page and refresh it - I get broken image.
Image is from Custom media Souce. On frontend I also get broken image

Loving this extra.
Typo in the docs as they mention the use of [[!+ss.meta]] when it should be [[!+ss_meta]]

When running the snippet with toPlaceholders switched on, all fields that have been set will be rendered when triggered individually, however, the placeholder allegedly holding all placeholders is empty.

Add support for media manager extra input types for the social image fields

In your CSS, this line:

.x-btn-text .icon, .x-tab-strip-text .icon {
    margin-right: 8px;
}

puts spacing to the right of the social icons in the Social tab, but it also puts a margin to the right of the trash icon in the main MODX editing button bar:

I suggest changing your CSS to make it specific to the tab area instead of globally — something like this:

.x-tab-panel-header .x-btn-text .icon, .x-tab-panel-header .x-tab-strip-text .icon {
    margin-right: 8px;
}

Adding ".x-tab-panel-header" in front of the classes fixes the problem, although with ".x-tab-strip-text .icon" this still makes the style applied to any other extras that may use icons in the side tabs. It also applies to the trash can in the modx-leftbar-tabpanel, but fortunately it gets overridden by one of the MODX manager CSS declarations.

Hi Sterc, thanks for this shiny new piece of an extra!
In source I'm getting htmlentities in the title and in all the metas.
ä gets ä

It would be useful to hide (disallow, disable etc.) all the settings (inc. the blue "Search engine" and "Social" links/tabs) based on the user-group to prevent certain users from poking around where they don't need to be.

I've seen some Extras use a System Setting that allows the user to type a comma-separated list of user-groups that are not allowed access to settings. Perhaps something along those lines?

I was hoping I could simply hide all of it using ACLs but that doesn't seem possible.

I keep getting an error during installation:

The max limit for the index is 3072 bytes, but the table has a varhar field (2000)
It turns out that when encoding utf8mb4_unicode_ci, the limit is exceeded.
If the MySQL server is configured correctly, then the index should be truncated to 768, but this is not the case for most hosting companies.

A changefreq value of hourly returns 0.5 in the changefreq placeholder. The changefreq value of always returns 1 in the changefreq placeholder. I have not checked this further, but at least the two values are definitely wrong.

These values can be selected in the dropdown in the Search engine -> Sitemap tab of a resource.

Installing it without setting or installing SEO Pro or SEO Tab before, a new 2.8.1, I get this one in error-log:
core/components/seosuite/model/seosuite/seosuite.class.php : 779) PHP warning: trim() expects parameter 1 to be string, array given

Hi to Sterc,

thanks for your great job guys with SEOSuite. I have found one bug in generated (using default chunks) sitemap.xml:

• <priority>normal</priority> - string value "normal" is not valid, it should be decimal (https://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd)
• string value is saved in DB modx_seosuite_resource

Please, take a look at it.
Thanks a lot
Regards
Michal

Hello Sterc-Team,

would it be possible to provide an option in the system settings to disable the Yandex search engine?
Likewise for the social area in relation to Twitter and Facebook?

Best regards,
Stefan

When activating this plugin, it will display above the content in a very dominant way. MODX is about customizing the user-experience as close to the clients needs as possible. I'd like to move the SEO settings per resource either below the content or have the SEO-Section collapsed. Otherwise the most important part (the content) will always display belog the SEO section.
Would be glad if we could just choose to move it some place else, much like Tagger does it.

I'm using dedicated media sourcs for each resource

basePath: [[ppb_migxResourceMediaPath? &pathTpl=assets/uploads/resources/{id}/ &createFolder=1 ]]
baseUrl: [[ppb_migxResourceMediaPath? &pathTpl=assets/uploads/resources/{id}/ &createFolder=1 ]]

This technique goes back to a post writen by BobRay about 10 years ago (time flies) and with a few exceptions that need special attention (for example: pdoTool), it usually works very well.

The idea is that each resources has a unique directory that collects all files needed.

If I set the default media source to a media source with a snippet, this setting is picked up by Seo Suite and I can upload images into the right directory.

The image is also correctly dispayed on the manager tabs for facebook and twitter.

The plugin creating the placeholders on the frontend side doesn't process this setting, but returns it as a normal string.

<meta property="og:image" content="https://example.com/index.php?id=1/[[ppb_migxResourceMediaPath? &pathTpl=`assets/uploads/resources/{id}/` &createFolder=`1` ]]/cardi.jpg">

If we use custom plugin we get
<meta name="og:image" content="LINK_TO_IMAGE" /> 
but correct should be
<meta property="og:image" content="LINK_TO_IMAGE" /> 

So all social meta tags should use PROPERTY instead of name.
Will be good If U add this as custom feature

In MODX 3 pre release adding a facebook image in the tab or in the system setting crashes the page.

Error Log says the following

[2021-11-18 14:43:43] (ERROR @ /www/core/vendor/xpdo/xpdo/src/xPDO/xPDO.php : 786) modMediaSource::load() is not a valid static method.