-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Way for shortcake interface to remember user shortcode parameters #742
Comments
I'm confused as to what behavior would make sense here. Text input fields do what you're describing out of the box through browser autocomplete functionality. For other field types, there isn't an autocomplete UI built in to the field itself, so we'd have to style something custom. If you want to do this yourself for a specific shortcode (ie, when creating a new instance of a shortcode, pull certain values from the last edited instance of that shortcode, you could use the |
Sorry for not being clearer. I think the issue I am experiencing is directly related to #738 |
For a short term fix until the next release I just grabbed the code from the issue #738 with one minor tweak. The fix didn't address multi selects so instead of an empty split, i used a comma as the separator and I don't use commas in any select values. Not ideal but was simplest way for me until this gets worked out with a release and I can move on to other things.
|
Thanks @cowanr - that certainly resolves my issue for the meantime! |
Is there a way for the Shortcake plugin to remember user parameters that have previously been entered?
The plugin works perfectly in the first instance creating a shortcode on the page/post. However, when user wants to edit the shortcode, the modal window does not seem to remember the user specified settings/parameters.
Any 'text' field does this perfectly and that does not appear to be the issue. However, when I introduce select fields or checkboxes/radio buttons, the user data is not displayed when editing the shortcode using the Visual Editor. Is there a hook or function I can use to get the editor to remember this information?
The text was updated successfully, but these errors were encountered: