The fields look like this on my Payload installation, any clues on what could be wrong? The second screenshot is how I would want it to look like
Hey
@138382559913574400
What payload version are you using and what lang did you load?
Latest Payload version, and didn't load any language, it's probably that! How do I load a language? I used the blank starter on Cloud
Hmm, this is strange
You shouldn't need to load any language for the default to show I think
Try doing this
In your buildConfig
i18n: {
fallbackLanguage: 'en',
supportedLanguages: { en } // en is imported from @payloadcms/translations
}Didn't seem to do anything
This is very strange
Can you share your config with me, as well as package.json
payload.config.ts
// storage-adapter-import-placeholder
import { mongooseAdapter } from '@payloadcms/db-mongodb' // database-adapter-import
import { payloadCloudPlugin } from '@payloadcms/payload-cloud'
import { lexicalEditor } from '@payloadcms/richtext-lexical'
import path from 'path'
import { buildConfig } from 'payload'
import { fileURLToPath } from 'url'
import sharp from 'sharp'
import { en } from '@payloadcms/translations/languages/en'
import { Users } from './collections/Users'
import { Media } from './collections/Media'
import { Pages } from './collections/Pages'
const filename = fileURLToPath(import.meta.url)
const dirname = path.dirname(filename)
export default buildConfig({
admin: {
user: Users.slug,
importMap: {
baseDir: path.resolve(dirname),
},
},
collections: [Users, Media, Pages],
editor: lexicalEditor(),
secret: process.env.PAYLOAD_SECRET || '',
typescript: {
outputFile: path.resolve(dirname, 'payload-types.ts'),
},
i18n: {
fallbackLanguage: 'en',
supportedLanguages: { en } // en is imported from @payloadcms/translations
},
// database-adapter-config-start
db: mongooseAdapter({
url: process.env.DATABASE_URI || '',
}),
// database-adapter-config-end
sharp,
plugins: [
payloadCloudPlugin(),
// storage-adapter-placeholder
],
})package.json
{
"name": "template-blank-3.0",
"version": "1.0.0",
"description": "A blank template to get started with Payload 3.0",
"license": "MIT",
"type": "module",
"scripts": {
"build": "cross-env NODE_OPTIONS=--no-deprecation next build",
"dev": "cross-env NODE_OPTIONS=--no-deprecation next dev",
"devsafe": "rm -rf .next && cross-env NODE_OPTIONS=--no-deprecation next dev",
"generate:importmap": "cross-env NODE_OPTIONS=--no-deprecation payload generate:importmap",
"generate:types": "cross-env NODE_OPTIONS=--no-deprecation payload generate:types",
"lint": "cross-env NODE_OPTIONS=--no-deprecation next lint",
"payload": "cross-env NODE_OPTIONS=--no-deprecation payload",
"start": "cross-env NODE_OPTIONS=--no-deprecation next start"
},
"dependencies": {
"@payloadcms/db-mongodb": "latest",
"@payloadcms/next": "latest",
"@payloadcms/payload-cloud": "latest",
"@payloadcms/plugin-seo": "latest",
"@payloadcms/richtext-lexical": "latest",
"@payloadcms/translations": "^3.30.0",
"cross-env": "^7.0.3",
"graphql": "^16.8.1",
"next": "15.1.5",
"payload": "latest",
"react": "19.0.0",
"react-dom": "19.0.0",
"sharp": "0.32.6"
},
"devDependencies": {
"@eslint/eslintrc": "^3.2.0",
"@types/node": "^22.5.4",
"@types/react": "19.0.7",
"@types/react-dom": "19.0.3",
"eslint": "^9.16.0",
"eslint-config-next": "15.1.5",
"prettier": "^3.4.2",
"typescript": "5.7.3"
},
"engines": {
"node": "^18.20.2 || >=20.9.0"
},
"pnpm": {
"onlyBuiltDependencies": [
"sharp"
]
}
}A few things here with the package.json - you should pin your versions to latest ie 3.30.0
So instead of
"payload": "latest",do
"payload": "3.30.0",or vice versa?
Exactly
Then reinstall deps
But your issue seems to be that plugin-seo isn't actually activated
You need to pass it into config via plugins
Like this:
https://github.com/payloadcms/payload/blob/main/templates/website/src/plugins/index.ts#L54Oops that was silly from me! Thank you!
Hahaha no worries, it's my pleasure - so it's working for you now?
You can also remove the
i18nif you don't need it
A few things here with the package.json - you should pin your versions to latest ie 3.30.0
By the way the "latest" way is how Cloud automatically generated my GitHub repo, so it's the default there
Yep works, and will delete that
Yeah, the devs recently reverted that to show pinned versions instead, going forward it won't use latest as that can cause confusion and issues
Glad we figured it out here though!
Star
Discord
online
Get dedicated engineering support directly from the Payload team.