• Still quite raw, I had to do manually few fixes in the code and a lot of additional setup, but it works and works quite fine after all.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Leon Stafford

    (@leonstafford)

    Thanks @maksimkuzmin!

    Aiming to reduce a lot of the common issues in the upcoming version 7.

    You can try out the new core plugin from our homepage and/or grab all new add-ons from source code if you haven’t already.

    Thanks for your patience and persevering!

    Cheers,

    Leon

    Thread Starter maksimkuzmin

    (@maksimkuzmin)

    I’ve actually tried v7, but honestly it differs from v6 that much that I couldn’t even understand how it works, so I quit it and installed v6 back. Maybe you should publish at least some kind of Getting Started/Quick start for v7, or maybe Magration from v6 to v7, because it makes not much sense to users who already got used with version 6.

    I hopefully propose you to remain version 6 for long-term support including fixing bugs that annoy users like me so much. You say that bug X and bug Y is fixed in V7, but it’d be really awesome, as well as extremely needful, if you fixed these bugs for current version.

    P. S.

    As long as I have strong demand in your plugin for my own and my clients’ websites, I can offer myself for maintaining v6. I’ve already implemented bug fix for “no protocol” URLS like “//example.com” on my own, and I’m planning to fix “placeholder.wpsho” issue, so I can pull request my fixes to your repo. Of course, if you have such a need.

    P. P. S.

    I also have an idea to implement crawler via Chrome Driver (headless), because some advanced WP themes like Avada have a lots of content loaded dynamically, so if you think it’d be a good feature for your project, I can start working on that too.

    Plugin Author Leon Stafford

    (@leonstafford)

    Hi @maksimkuzmin,

    Damn, it excites me when people are into the project, hard to say no to anything ??

    First, lemme address issues transitioning to V7. Definitely different and even for new users, it’s way less intuitive, no “Start now” button, like in 6. In this last week, though, I’ve spent quite a bit of time updating the docs – if you start at the homepage, you can follow links to the 5 core concepts, how they work and how to configure:

    – URL Detection
    – Crawling
    – Post-processing
    – Deploying
    – Jobs

    In hindsight, “Jobs” may have been better as “Tasks”, anyway… I’d love if you took another look, maybe after official release.

    Re maintaining a fork of V6 – let me think about it some more… I’ve also been wanting to maintain a fork of Simply Static, so along the same lines.

    Of course, there’s nothing to stop you sharing/rebranding your own fork as you like – it’s under The Unlicense, so no copyright issues and I would be more supportive than blocking to have more solutions out there. Bi-directional code-sharing could help both projects.

    I just don’t want to promise anything right now, as I want to focus on V7 and still have a lot to do.

    Code maintenance is one aspect, but user support can be a large time consumption, too.

    Because there is such a difference in functionality/behaviour between 6 and 7, I’d like to avoid supporting 2x the products once V7 is out.

    Anyway, will keep thinking on things and thanks so much for your interest in it all, it really gives me a boost!

    Re a headless-browser solution, I’d love to see that, too! Biggest blocker until now in my mind, was not having control over the user’s environment to install anything. So a few options come to mind: 1) offer optimized dev server hosting 2) do it as a SaaS 3) optional add-on that requires headless browser available in environment. How do you see it working in an ideal situation?

    Cheers,

    Leon

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Best of its kin’ is closed to new replies.