pengx17 / logseq-publish

Archived. Please check https://github.com/logseq/publish-spa instead

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Problem deploying

javierfuentesm opened this issue · comments

Hey Guys,

A the beginning the site was being deployed in blank , then I make all the pages public, but now the page doesn't load anything
Here is my repo: https://github.com/javierfuentesm/logseq
the page
https://javierfuentesm.github.io/logseq/

And I see these errors on the console
image
image

when I exported it locally everything works fine
image

I'm comparing the 2 index.html and they are the same
image

Any ideas about what could be happening?

when I download it locally what is being generated on gh-pages, it doesn't work until I replace the folders of assets and statics

i think the issue is that I'm using plugins and the version of logseq doesn't have so it doesn't generate the necessary files, si there a way to fix this? i pushed the necessary files to that branch but it replaces all the files including the scripts

I have checked your site at javierfuentesm.github.io/logseq, but it seems it was working fine. I am not exactly sure why the 404 errors - maybe base URL is misconfigured, or the deployment is failed, or GitHhub pages server did not pick the assets from your gh-pages yet. 🤔

i think the issue is that I'm using plugins and the version of logseq doesn't have so it doesn't generate the necessary files, si there a way to fix this?

Please try removing/disabling all plugins, rebuild index and try again.

I have checked your site at javierfuentesm.github.io/logseq, but it seems it was working fine. I am not exactly sure why the 404 errors - maybe base URL is misconfigured, or the deployment is failed, or GitHhub pages server did not pick the assets from your gh-pages yet. 🤔

Hi, i fixed it by committing directly to the branch the right assets and then changing the yml changing the clean property in order to exclude the static folder in that way my site started working , the bad thing is that if i add a new plugin I'm gonna have to do that process manually again