Conflict between Element Connection and SEOmatic sitemap settings #546
Replies: 2 comments 3 replies
-
|
Sorry for the delay @strandofgenius... I will see if there's anything we can do to prevent Freeform from triggering this queue job. 🙂 |
Beta Was this translation helpful? Give feedback.
-
|
That would be great! Keep me posted. Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
We've replied to the issue in SEOmatic as we believe it might be an issue on their end. 🙂 |
Beta Was this translation helpful? Give feedback.
-
|
It looks as though a reply came back and it might be something on your end again. Any update on this? |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for the delay @strandofgenius. This slipped through the cracks, but I've now created an internal issue item to have it revisited shortly. 🙂 |
Beta Was this translation helpful? Give feedback.
-
Queue jobs are running to generate a sitemap when an entry type has public URLs but the sitemap setting is set to disabled in the SEOmatic content SEO settings.
This only happens when someone fills out the form from the front end of the site and the Element Connection is made between Freeform and creating an entry.
The sitemap does not get added to sitemap.xml but it is going through a process to generate it. This is unnecessary and it seems to get stuck from time to time and bogs things down. This especially becomes problematic since the client has thousands of leads in the system and each time a lead fills out the form it creates a new job to generate the sitemap again.
Here is the initial discussion about this issue: nystudio107/craft-seomatic#1212
Steps to reproduce
Expected behavior
It is expected that because the entry type sitemap setting is disabled it would not create a queue job to generate a sitemap.
Craft & Plugin Info (please complete the following information):
Beta Was this translation helpful? Give feedback.
All reactions