• Resolved tobiasburri

    (@tobiasburri)


    Hi,

    when adding a new blog post and performing a Single Export, additional files will be created. According to thedocumentation these are:

    • assigned category and tag pages
    • the blog page
    • the homepage
    • extract and export all images from that page
    • the XML sitemap

    Question:

    Does only the /blog page get updated ? What about results on blog/page/2/, blog/page/3/ and so on ? With new blog posts results will be moved to the next page. Will these also be updated ?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author patrickposner

    (@patrickposner)

    Hey @tobiasburri,

    thanks for reaching out!

    This is indeed not yet automated by the single export integration.

    We have it as part of our internal roadmap already (alongside some other things like auto-including non-image files, improving the delete page/post mechanism, and the ability to combine single exports with builds).

    Still, as of now, this would require either a build or full export.

    Thread Starter tobiasburri

    (@tobiasburri)

    Thank you for the reply.

    As a follow question: A full export might take very long, so I have tried out a Build. I have provided the url of every existing pagination page /blog/page/2/; /blog/page/3/; /blog/page/4/; etc.

    Will this only export the paginated pages, or it will also export all linked pages ? When running this Build it looks like it is trying to do a full export, which was not intended. Is there a way to make sure only the paginated pages get exported ?

    Plugin Author patrickposner

    (@patrickposner)

    Hey @tobiasburri,

    thanks for the follow-up!

    Could you reach out to our pro support?

    I built a pagination handler now into the current beta version of Simply Static Pro which will take care of that automatically for you, but I obviously can’t include a download to it here in the forum! ??

    Thanks,
    Patrick

    Thread Starter tobiasburri

    (@tobiasburri)

    Thanks, I’ll do that.

    However, I do have one concern—there are still several unresolved issues with the official release that need further investigation. When testing the beta version earlier, we were informed that support wouldn’t be available for it.

    As a result this would require me to maintaine two separate environments—one for testing new functionality and another for addressing existing issues with the official release. It feels like a bit of a catch-22. I’d appreciate any guidance on the best way to manage this.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.