Skip Navigation
Buy Now
Home » Errata » Required Image Fields in a CRED form will appear as not set until you re-upload a new image

Required Image Fields in a CRED form will appear as not set until you re-upload a new image

Resolved

Reported for: Toolset Forms 1.9.5

Resolved in: 1.9.6

Topic Tags: Content-submission forms, Toolset Forms

Symptoms

If you have a CRED Edit Form where a required Image field is inserted, and then show that CRED Edit Form on a Post that already has such an image set, on the front-end the form appears to require a new Image to be uploaded, even if there is already an image set.

You can only submit the CRED form after after uploading a new image.

Workaround

his issue will be fixed in the upcoming version of CRED.

As a workaround, you can download this patch and replace the class.abstract_credfile.php file found in the ../wp-content/plugins/cred-frontend-editor/application/models/field/wptoolset folder.

5 thought on Required Image Fields in a CRED form will appear as not set until you re-upload a new image

  • Thanks Beda, that works perfectly.

    Can you tell me if file uploads will have a size limit and also if multiple upload files will be able to be capped at a certain number? So, I might have a field called pictures-of-cats and i want to have a max upload size of 2MB and only three of these files? Also what is the ETA for the new version?

    Thanks mate.

    • Beda is away, so he can’t reply. Can you please re-post this in Toolset technical support forum?

    • Hi

      I suggest as Amir pointed out to reach out in the Support Forum.
      The question you have is not something we can clarify in this erratum post.

      Here we solely handle the issue described in the opening comment 🙂

      Thank you for understanding.

  • Hi,

    Workaround works perfect 🙂

    When will this bug be fixed officially?

    I’m afraid a plugin upgrade will erase the workaround 🙁

    Thanks

    • It’s planned for the coming release of CRED. Whenever you see this errata marked as solved, you won’t have to re-apply the patch. If the errata stays open, you should re-apply it.

Comments are closed