Simplify your stack and build anything. Or everything.
Build tomorrow’s web with a modern solution you truly own.
Code-based nature means you can build on top of it to power anything.
It’s time to take back your content infrastructure.

PAYLOAD 3.0 - SEO plugin screwed up my setup and i can't get it to work since

default discord avatar
asaps666last year
11

Installed SEO plugin, everything screwed up, tried to uninstall it, nothing changed. Tried million of payload related libraries versions variations and cant get it to work.



For now it shows me

"Error: ServerFunctionsProvider requires a serverFunction prop"

My package.json is like this:



"dependencies": {


"@faceless-ui/css-grid": "^1.2.1",


"@heroicons/react": "^2.1.5",


"@payloadcms/plugin-nested-docs": "beta",


"autoprefixer": "^10.4.20",


"classnames": "^2.5.1",


"postcss": "^8.4.47",


"qs": "^6.13.0",


"tailwindcss": "^3.4.14",


"@payloadcms/db-postgres": "beta",


"@payloadcms/richtext-slate": "beta",


"@payloadcms/ui": "beta",


"babel-plugin-react-compiler": "0.0.0-experimental-48eb8f4-20240822",


"@payloadcms/db-mongodb": "beta",


"@payloadcms/next": "beta",


"@payloadcms/payload-cloud": "beta",


"@payloadcms/richtext-lexical": "beta",


"cross-env": "^7.0.3",


"graphql": "^16.8.1",


"next": "15.0.0",


"payload": "beta",


"react": "19.0.0-rc-65a56d0e-20241020",


"react-dom": "19.0.0-rc-65a56d0e-20241020",


"sharp": "0.32.6"


},


"devDependencies": {


"@types/node": "^22.5.4",


"@types/react": "npm:types-react@19.0.0-rc.1",


"@types/react-dom": "npm:types-react-dom@19.0.0-rc.1",


"eslint": "^8",


"eslint-config-next": "15.0.0",


"typescript": "5.6.3"


},




Can anyone tell me whats wrong?



Praying for stable to come out asap. 🙏🏽

  • default discord avatar
    zed0547last year

    Your issue doesn't sound like something the SEO plugin caused, but the result of missing the breaking changes while upgrading your packages.



    See here:

    https://github.com/payloadcms/payload/compare/v3.0.0-beta.127...v3.0.0-beta.128

    The reason why uninstalling didn't work is because in your package.json your payload versions are labeled as beta instead of fixed versions, so you likely tried reinstalling node modules and got updated to the latest betas instead.

  • default discord avatar
    asaps666last year

    Thank You for interacting.



    So U'r suggesting me to label all the payload dependencies to '3.0.0-beta.128', am i right?

  • default discord avatar
    zed0547last year

    Before you do this



    Can you run npm or pnpm list payload

  • default discord avatar
    asaps666last year

    yea, sure


    1 sec

  • default discord avatar
    zed0547last year

    Sorry the link above wnt all goofy and into compare mode, what I meant to send was this:



    https://github.com/payloadcms/payload/releases/tag/v3.0.0-beta.128

    Have a look at the breaking changes

  • default discord avatar
    asaps666last year

    npm list payload gives me "invalid: "beta" from the root project" for all the payload related packages



    aight, going to check it out.



    I'm pullimg my hair out of my head 😮‍💨



    Error: Objects are not valid as a React child (found: object with keys {root}). If you meant to render a collection of children, use an array instead.




    I've checked something around 20-30 recent releases and looks like my project has everything stated in those breaking changes.



    ay maan



    i got it working



    God exists



    Closing this issue.


    Thanks a lot for pointing me in the right direction. Btw.. I bumped the NextJS version to 15.0.3 and everything suddenly works.

  • default discord avatar
    zed0547last year

    This is unusual



    Oh nice



    You figured it out

  • default discord avatar
    asaps666last year

    that was actually because me being dumb and not going to /admin but /

  • default discord avatar
    zed0547last year

    Thanks for coming back with the solution

  • default discord avatar
    asaps666last year

    but at one point the error occoured about the react :key={} missing, then i realized that its not even related to payload.



    Yeah, thanks for interacting man 🤙🏽

  • default discord avatar
    thgh.last year

    I'm having this same error after upgrading from beta-123 to ^3 🤔



    Solved by

    https://discord.com/channels/967097582721572934/1215659716538273832/1306950772973371433
Star on GitHub

Star

Chat on Discord

Discord

online

Can't find what you're looking for?

Get dedicated engineering support directly from the Payload team.