• Hi,
    I have an issue with my homepage page. I’m trying wp2static on my new project. I created homepage add jobs to queue manually and trigger jobs from wp-cli – no files in export folder. So i tried add new page and repeat steps – i have only the second page no homepage. I’m not sure what i’m doing bad.
    Maybe it’s problem that i’m using roots.io/bedrock and it look that the wp2static identify site on bad URL? But home URL si correct.

    View post on imgur.com

    Please any ideas for what to try?

    • This topic was modified 4 years, 10 months ago by filiptvarek.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Leon Stafford

    (@leonstafford)

    Hi @filiptvarek,

    V7 should be OK with Roots, but I haven’t done any proper testing with it yet (on my near todo list, along with a few other platform tests).

    Does the Diagnostics screen show any warnings? Anything in your WP2Static > Logs? No notices/errors in the output when you run from WP-CLI?

    Rather than enqueue jobs via UI / you may try deleting those and then running the following WP-CLI command: wp wp2static full_workflow or else, each step individually:

    detect
    crawl
    post_process
    deploy

    And check for expected output after each step.

    Beware when running a mix of UI and WP-CLI, that the system user that runs wp commands plays nicely with the www/www-data/other webserver user. If one creates a dir/file the other doesn’t have permissions to access, it can be a pain.

    Ideally, I try to run my WP-CLI commands as the webserver user or give ownership/permissions to the webroot to allow my system user to create/access things correctly. Running WP-CLI as the webserver user tends to cause less headaches.

    Cheers,

    Leon

    Thread Starter filiptvarek

    (@filiptvarek)

    Thanks for response.
    I tried all steps.

    It looks like a problem with page for HP. It isn’t detected. I doesn’t have any error or warning in diagnostic page. Same when i run full_workflow.
    When i list crawl queue it show / in URLs, but the HTML for homepage isn’t created. But second page is crawled and post processed.

    Next thing witch i found. Processed site folder contain only raw HTML no CSS and JS files is this correct? What export structure should look like?

    Thanks,

    Filip

    Thread Starter filiptvarek

    (@filiptvarek)

    I tried version from your master branch
    this is from log

    
    ...
    2020-05-13 12:09:09: Removed /app/plugins/elementor-custom-widget/dist/js/main.js from Crawl Cache
    2020-05-13 12:09:09: 404 for URL /app/plugins/elementor-custom-widget/dist/js/main.js
    2020-05-13 12:09:08: Removed /app/plugins/elementor-custom-widget/dist/css/main.css from Crawl Cache
    2020-05-13 12:09:08: 404 for URL /app/plugins/elementor-custom-widget/dist/css/main.css
    2020-05-13 12:09:08: Removed / from Crawl Cache
    2020-05-13 12:09:08: 404 for URL /
    2020-05-13 12:09:08: Not using CrawlCache.
    2020-05-13 12:09:08: Starting to crawl detected URLs.
    2020-05-13 12:09:08: Starting crawling
    ...
    

    looks like everything is 404 and i don’t know why. Have you any suggestions?

    Thanks,

    Filip

    Thread Starter filiptvarek

    (@filiptvarek)

    It’s cause moved root to /wp in roots so crawler have this input

    $response = $this->request->getURL( $url->get(), $handle );

    where

    $url->get returns for example https://test.loc/wp/favicon.ico

    and it should return https://test.loc/favicon.ico

    Is it possible to change root somewhere?

    Thanks,

    Filip

    Thread Starter filiptvarek

    (@filiptvarek)

    Looks like Root.io need to use get_home_url() instead of site_url()
    related to this discussion https://discourse.roots.io/t/how-do-i-completely-remove-wp-from-url/5572

    Should i open issue in repo?

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Homepage doesn’t created’ is closed to new replies.