Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter trajche

    (@trajche)

    Sorry for the late response.

    The use case for using the plugin is the following: when all of the Media Library is stored on S3 then it makes our WordPress set-up much lighter, as well as storage is cheaper (not to mention backups). This is especially useful when we are talking about 100,000+ images each with different sizes.

    But I believe that WP Media Offload does hook into the ‘full delete’ of an image library item, so if your plugin does delete the Media Library items, it will also get rid of the S3 image. So at least partly compatible perhaps.

    Another thought: WP Offload Media has an option where it completely removes the image from the local filesystem and only keeps it on S3. Thinking about it, the Pro addon Filesystem Analyzer probably transverses the uploads directory and looks for references of unused/old media. I think the equivalent would be here done by listing all of the S3 which I understand is out of scope.

    We will probably end up writing our own CLI script for the latter, if interested to have a look/collab shoot me an email at trajche@kralev.eu

    Thanks,
    TJ

    Thanks Sybre. I am helping Kristina with this and had a few questions.

    If we disable TSF’s sitemap and use WordPress’ default, what are the drawbacks (other than having everything indexed)? Are there certain features in TSF that won’t work? For example, will it respect noindex rules etc.

    Second question is whether it’s possible that we can create a separate sitemap for products (WooCommerce)? For ex. products.xml and have that indexed? The website has *a lot* of products indexed on daily basis and it almost suffocates the Post/Page content. If there are functions/hooks that make this possible, I was thinking about creating a “sitemap-index.xml” which would point to the TSF sitemap and then the custom one products.xml?

Viewing 2 replies - 1 through 2 (of 2 total)