Taxonomies not saving and post order

Anonymous

#1568

Hi there
Great plugin.
I’m currently having a couple of issues
The custom taxonomies are not saving when I update the search form.
Only one saves and the remaining say Format after the page has finished loading.
Also I would like to order the posts automatically by a combination of 2 postmeta mata_key values.
I have seen a post you have added earlier this last week however I have implemented this and it has no effect.
Can you offer any advice regarding this.
Thanks
MArk

Ross Moderator

#1570

Hey Mark

You can’t currently order by more than 1 sort field at a time – this is something I will look to improve in the future.

RE the saving issues, can you send me your login details and I’ll take a look?

Thanks

Anonymous

#1572

This reply has been marked as private.

Ross Moderator

#1573

Hey Mark

My reply in the other post was a work around, what are you trying to achieve, a default sort order?

That code was written without testing, but I’ll look in to it and see if I can get it working.

Re the save problem in the backend, do you have “hide empty” ticked for those fields?

Also, check in your JS console to see if there are any JS errors, this may be preventing the form from saving properly.

When you edit a form, are the fields still shown incorrectly?

Just to note, for AJAX loading, your search form must not be inside the “ajax content selector”.

Thanks

Anonymous

#1574

This reply has been marked as private.

Anonymous

#1575

Hi Ross
You are right I am trying to set up a default post order. I have successfully achieved the pre_get_posts with an archive based upon the meta_key values.
The challenge is now to set the default order in the ajax results.
Regarding the taxonomies not saving, I have tried all ways of saving. Each type of Input Type and also checking and unchecking the other options. But no joy.
Quite baffling.

The fields are still shown as “Format” when editing a saved form.

Below is what appears in the Console log of Chrome

Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi) post.php?post=14316&action=edit&message=1:1
Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: only screen and (-webkit-min-device-pixel-ratio: 1.5), only screen and (min-resolution: 144dpi) post.php?post=14316&action=edit&message=1:1
Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi) post.php?post=14316&action=edit&message=1:1

Any thoughts?

Ross Moderator

#1577

Hi Mark

Looks like your JS is fine,

I’m a bit confused myself, no idea why the forms are not getting saved properly.

If I am not able to access the admin I would recommend the standard course of action for troubleshooting:

• Disable all other plugins to see if there is a conflict
• Test with another theme
• Try on a fresh install (can be locally)

I’ll have a look into setting a default sort order – for now please try the above and let me know the results.

Thanks

Ross Moderator

#1578

I have just noticed you are using salesforce, which uses the same prefix as search & Filter (sf) for class names, so it is possible that there may be another conflict somewhere else – where both plugins are using “sf” – I would try disabling this plugin first.

Thanks

Anonymous

#1580

Hi Ross
The reason they were not saving is because there were capital letters used in the custom taxonomy function name.
All I need to do now is sort the default order and I am good to go.

Many thanks for the support

Ross Moderator

#1581

Ah cool no worries 🙂

[Author]

Posts