Troubleshooting

Veltro Theme Documentation

Config Changes Do Not Appear

Veltro imports .astro/config.generated.json, not the TOML file directly.

Start development with npm run dev.
Confirm .astro/config.generated.json changed.
Restart the dev process after changing multilingual URL settings or trailingSlash.
Never edit the generated JSON by hand.

A Page Or Section Is Missing

Check draft on the page, item, and collection -index.md.
Check the section’s enable value.
Check the relevant menu item’s enable value only if the page exists but is absent from navigation.
Open the route file and confirm the section component is rendered.

Localized Links Are Wrong

Check src/config/language.json, settings.multilingual in config.toml, and the matching content/menu files for the locale. Use getLocaleUrlCTM() for links created in components.

An Interaction Does Not Initialize

Check whether the relevant markup exists before debugging the script. Preline features load dynamically, some hover features wait for the first pointer interaction, and reduced-motion or coarse-pointer conditions intentionally disable some effects.

Relevant files include:

src/layouts/components/widgets/GlobalScripts.astro
src/layouts/components/global/header/Header.astro
the specific widget or section component

Build Cache Rename Error

Do not run astro check and astro build simultaneously in the same working tree. Both can write Astro’s generated content cache. Run them sequentially:

npm run astro-check
npm run build

Vercel Build Script Is Missing

The included vercel.json currently points to sh vercel.sh, but the source does not include vercel.sh. Use npm run build with output directory dist/ in the Vercel project settings, or add the missing script before relying on that config.