Skip Navigation
Buy Now
Home » Errata » Autocomplete does not work when adding a link to create child post or to delete a post

Autocomplete does not work when adding a link to create child post or to delete a post

Resolved

Reported for: Toolset Forms 1.9.5

Resolved in: Toolset Forms 2.0

Symptoms

When adding a CRED link to add a child post, or to delete an existing post, there are some elements that let you search for posts and offer results based on the title as you type in. Those elements let you select the page where the form to add a new child post is, and the parent that will be used. This is also used when selecting the page to redirect to after deleting a post.

The current stable release for CRED, when combined with the current stable release for Types, will not return any results when you type in those elements.

Workaround

This issue will be solved in the next version for CRED. In the meantime, this patch can be used by unzipping it and uploading the file it contains to replace the one with the same name, located in /application/controllers/shortcode_generator.php in your CRED installation.

4 thought on Autocomplete does not work when adding a link to create child post or to delete a post

  • Hi,
    After applying this patch, the parent field in cred form has uncontrolled behaviour. For example I have three hierarchies for cars, Make (Toyota, Honda etc.) –is parent of–>Type (4×4, SUV etc.) –is parent of –> Model (Toyota Land Cruiser, Honda Accord, Honda Civic). I have wpml installed as well where above parent names are translated in two more languages.

    Using CRED add or edit form, I noticed that when I add or edit child post of type Model in any language and try to search for parent the result shows all types of posts in all languages.

    Same edit I try from wordpress admin for my post type ‘Make’ and it is working fine.

    • Hi there

      Thanks for the feedback.

      Yes, currently the search mechanism in those selectors is not separating results per language. We are aware of this issue and we are working on a solution that will get released with our 2.0 version for the plugin, which should happen at some point in the coming weeks.

      Hope it helps.

  • Is there a temporary fix for this? My client have only front-end access to the site, and this is creating a shame for us.

Comments are closed