Download the PHP package humanmade/msm-sitemap without Composer
On this page you can find all versions of the php package humanmade/msm-sitemap. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download humanmade/msm-sitemap
More information about humanmade/msm-sitemap
Files in humanmade/msm-sitemap
Package msm-sitemap
Short Description Comprehensive sitemaps for your WordPress.com VIP site.
License GPL-2.0+
Homepage https://vip.wordpress.com/plugins/msm-sitemap/
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package msm-sitemap
Comprehensive Sitemaps
Comprehensive sitemaps for your WordPress.com VIP site. Joint collaboration between Metro.co.uk, WordPress.com VIP, Alley Interactive, Maker Media, 10up, and others.
How It Works
Sitemap Data Storage
- One post type entry for each date.
- Sitemap XML is generated and stored in meta. This has several benefits:
- Avoid memory and timeout problems when rendering heavy sitemap pages with lots of posts.
- Older archives that are unlikely to change can be served up faster since we're not building them on-demand.
- Archive pages are rendered on-demand.
Sitemap Generation
We want to generate the entire sitemap catalogue async to avoid running into timeout and memory issues.
Here's how the defualt WP-Cron approach works:
- Get year range for content.
- Store these years in options table.
- Kick off a cron event for the first year.
- Calculate the months to process for that year and store in an option.
- Kick off a cron event for the first month in the year we're processing.
- Calculate the days to process for that year and store in an option.
- Kick off a cron event for the first day in the month we're processing.
- Generate the sitemap for that day.
- Find the next day to process and repeat until we run out of days.
- Move on to the next month and repeat.
- Move on to next year when we run out of months.
CLI Commands
The plugin ships with a bunch of wp-cli commands to simplify sitemap creation:
Filtering Sitemap URLs
If you need to filter the URLs displayed in a sitemap created via the Comprehensive Sitemap plugin, there are two considerations. First, if you are filtering the individual sitemaps, which display the URLs to the articles published on a specific date, you can use the msm_sitemap_entry hook to filter the URLs. An example for a reverse-proxy situation is below:
Second, if you are filtering the root sitemap, which displays the URLs to the individual sitemaps by date, you will need to filter the home_url directly. There is no plugin-specific hook to filter the URLs on the root sitemap.
Filter Sitemap Index
Use the msm_sitemap_index filter to exclude daily sitemaps from the index based on date.
