We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug Upgraded from ^2.1.15 to ^2.4.1 and now the following happens on next build:
^2.1.15
^2.4.1
next build
sitemap.xml
sitemap-0.xml
<?xml version="1.0" encoding="UTF-8"?> <sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> </sitemapindex>
Hence, not referencing the sitemap-0.xml. The configuration file has not been modified.
To Reproduce Steps to reproduce the behaviour:
Expected behavior Expected output of sitemap.xml would've been:
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> <sitemap> <loc>https://johnschmidt.de/sitemap-0.xml</loc> </sitemap> </sitemapindex>
Additional context Contents of the configuration file:
/** @type {import('next-sitemap').IConfig} */ module.exports = { siteUrl: "https://johnschmidt.de", generateRobotsTxt: true, }
The text was updated successfully, but these errors were encountered:
[Fix] Index sitemap does not reference the generated sitemaps
4e09807
Fix: #301
@jopesh Thanks for reporting this. Fixed #302
Sorry, something went wrong.
iamvishnusankar
Successfully merging a pull request may close this issue.
Describe the bug
Upgraded from
^2.1.15
to^2.4.1
and now the following happens onnext build
:sitemap.xml
andsitemap-0.xml
are produced as expected.sitemap-0.xml
does have the expected contentsitemap.xml
however yields:Hence, not referencing the
sitemap-0.xml
. The configuration file has not been modified.To Reproduce
Steps to reproduce the behaviour:
^2.1.15
to^2.4.1
next build
Expected behavior
Expected output of
sitemap.xml
would've been:Additional context
Contents of the configuration file:
The text was updated successfully, but these errors were encountered: