Schema Installation Fails

If schema installation fails, check:

Invalid Token Error

• Verify you're using an admin token, not a regular user token
• Token must have full admin permissions
• Check that the token hasn't expired (if using non-static tokens)
• Generate a new token and try again

Connection Errors

• Verify your Directus URL is correct (include https://)
• Check that your Directus instance is accessible
• Ensure there are no firewall rules blocking the connection
• Test the URL in a browser to confirm it loads

Schema Already Exists

• If you see "collection already exists" errors, the schema may be partially installed
• Check your Directus collections to see what was created
• You may need to manually clean up or reinstall completely
• Contact support if you're unsure

Theme Won't Start Locally

If your theme doesn't start:

Dependencies Not Installed

• Run pnpm install or npm install in your theme folder
• Ensure Node.js 18+ is installed
• Delete node_modules and reinstall if issues persist

Environment Variables Missing

• Check that .env.local file exists
• Verify DIRECTUS_URL is set correctly
• Ensure no syntax errors in the .env.local file

Port Already in Use

• Change the port: pnpm dev -- -p 3001
• Or stop other applications using port 3000

Content Not Appearing

If content doesn't show on your site:

Check Content Status

• Ensure content items are set to "Published" status in Directus
• Draft items won't appear on the live site

Verify Directus Connection

• Test that your Directus URL is accessible
• Check that your access token has read permissions
• Verify the API endpoint is returning data

Clear Cache

• Next.js caches content - try hard refresh (Ctrl+F5)
• Restart your development server
• Clear .next folder and rebuild