#Pagefind not working the deployed

15 messages · Page 1 of 1 (latest)

tough solar
#

Whan i run npx astro preview it works. But on server not. Could that be related to base path in config?

base: import.meta.env.DEV
        ? '/'
        : '/mw/design/spectro/',
woeful terraceBOT
#

Hi @tough solar. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

The issue you're experiencing might be related to the base path configuration in Astro. The base option in the Astro configuration is used to set the base path for your project. This is especially useful when deploying your site to a subdirectory.

In your case, you're setting the base path to be '/' during development and '/mw/design/spectro/' in production. This could potentially cause issues if the server is not properly configured to serve files from this subdirectory.

However, without more information, it's hard to say definitively if this is the cause of your issue. It's also worth noting that the pagefind option in the Astro configuration is used to enable or disable the default site search provider, Pagefind. If set to false, it will disable indexing your site with Pagefind and hide the default search UI if in use. Make sure this is set to true if you want to use Pagefind.

If you're still having issues, I would recommend checking the server configuration and ensuring that it's properly set up to serve files from the subdirectory specified in your base path. You might also want to check the Astro GitHub issues to see if anyone else has experienced a similar problem.

Sources:

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@tough solar kapa.ai is still learning and improving, please let us know how it did by reacting below

tough solar
#

In https://teaf.tescosw.cz/mw/design/spectro/system/functional-colors/ i have error when searching

Uncaught (in promise) Error: Failed to load the Pagefind WASM:
Error: invalid gzip data
    at PagefindInstance.loadWasm (pagefind.js:4:26)
    at async Promise.all (functional-colors/index 1)
    at async PagefindInstance.init (pagefind.js:1:18108)
    at async Pagefind.init (pagefind.js:9:1379)

@woeful terrace

woeful terraceBOT
#

Let me check the knowledge base for you. One moment! :books:

#

The error message you're seeing suggests that there's an issue with loading the Pagefind WebAssembly (WASM) module. This could be due to a variety of reasons, such as network issues, server configuration problems, or issues with the WASM file itself.

Unfortunately, the provided knowledge sources do not contain specific information on how to resolve this error. However, here are a few general suggestions:

  1. Check your network: Ensure that your server has a stable network connection and is able to access the internet. Network issues could prevent the WASM module from being downloaded correctly.

  2. Verify server configuration: Make sure your server is properly configured to serve WASM files. Some servers may require specific configuration to serve these types of files.

  3. Inspect the WASM file: If possible, check the WASM file to ensure it's not corrupted or malformed. The error message suggests that there might be an issue with the gzip data in the file.

If you're still having issues, I would recommend reaching out to the Astro community or the maintainers of the Pagefind library for more specific guidance.

Sources:

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@tough solar kapa.ai is still learning and improving, please let us know how it did by reacting below

tough solar
#

Ok, in settings of Pagefind i need to set baseUrl exactly like this

"baseUrl": import.meta.env.DEV
? '/'
: '/mw/design/spectro/',

Is it possible in astro.config.mjs ? @woeful terrace

woeful terraceBOT
#

Let me check the knowledge base for you. One moment! :books:

#

Yes, you can use environment variables in your astro.config.mjs file. However, the import.meta.env object is typically used to access environment variables in Astro components, not in the Astro configuration file.

In the astro.config.mjs file, you can use process.env to access environment variables. Here's how you can set the baseUrl in your Astro configuration:

export default {
  // ...
  pagefind: {
    baseUrl: process.env.NODE_ENV === 'development'
      ? '/'
      : '/mw/design/spectro/',
  },
  // ...
}

In this example, process.env.NODE_ENV is used to check if the current environment is development or production. If it's development, the baseUrl is set to '/'. If it's production, the baseUrl is set to '/mw/design/spectro/'.

Please note that the pagefind option is not a standard Astro configuration option and is not documented in the Astro Configuration Reference. If you're using a custom plugin or library that requires this option, please refer to the documentation for that plugin or library.

Sources:

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@tough solar kapa.ai is still learning and improving, please let us know how it did by reacting below

tough solar
#

Now I have more errors. I get 404 but tha file exists

GET https://teaf.tescosw.cz/mw/design/spectro/pagefind/pagefind.cs-cs_2495042161c66.pf_meta 404 (Not Found)

pagefind.js:2 Failed to load the meta index:
Error: invalid gzip data

pagefind.js:3

   GET https://teaf.tescosw.cz/mw/design/spectro/pagefind/wasm.unknown.pagefind 404 (Not Found)

Failed to load the Pagefind WASM:
Error: invalid gzip data

Uncaught (in promise) Error: Failed to load the Pagefind WASM:
Error: invalid gzip data
at PagefindInstance.loadWasm (pagefind.js:4:26)
at async Promise.all (functional-colors/index 1)
at async PagefindInstance.init (pagefind.js:1:18108)
at async Pagefind.init (pagefind.js:9:1379)

@woeful terrace

woeful terraceBOT
#

Let me check the knowledge base for you. One moment! :books:

#

The errors you're seeing suggest that the Pagefind library is unable to load certain resources. Specifically, it's failing to load a metadata index file (pagefind.cs-cs_2495042161c66.pf_meta) and a WebAssembly (WASM) file (wasm.unknown.pagefind). Both of these files are returning a 404 error, which means the server can't find them.

Here are a few things you could check:

  1. File paths: Ensure that the paths to these files are correct. The paths are relative to the baseUrl you've set in your Astro configuration. If the baseUrl is incorrect, or if the files are not in the expected location, you'll get a 404 error.

  2. Server configuration: Make sure your server is configured to serve the types of files that Pagefind is trying to load. Some servers require specific configuration to serve WASM files or other types of static assets.

  3. Gzip compression: The error messages also mention "invalid gzip data". This could mean that there's an issue with how the files are being compressed or decompressed. Check your server's gzip settings, and ensure that the files are being correctly compressed.

Unfortunately, the provided knowledge sources do not contain specific information on how to resolve these errors. If you're still having issues, I would recommend reaching out to the Astro community or the Pagefind library maintainers for more specific guidance.

Sources:

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: