WordPress / WordPress/secure-custom-fields

(Frontend forms) SCF could not validate this form because its security information is invalid or has expired.

Open
#541 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
131
Forks
64
Avg merge
10m
Merged PRs (30d)
1

Description

Hello,

We are using Advanced Forms for ACF to create frontend forms.

  • It is working using the latest version of ACF Pro, nut in SCF
  • It might be related to validate_save_post_authority in form_front.php -> this is something new in SCF
    • from the code, I'm not sure what this is good for :)

(I'm not sure, if this is within the scope of SCF, at least it's something where SCF is not a drop-in replacement anymore)

Problem

  • Submitting a form results in an error: "Validation failed. SCF could not validate this form because its security information is invalid or has expired."
  • Advanced Forms is not using acf_form to render the form.

Workaround

Use ACF in the meantime.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the submission failure with a frontend form built using Advanced Forms, then inspect validate_save_post_authority in form_front.php, which the report identifies as a possible source. Done means the form submits successfully in SCF without the invalid-or-expired security information error, while preserving validation behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
frontend, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.