I have a problem that I can see but not really understand why this happens.
I have a toolset post type created. This post type has 2 repeatable field groups.
For both field groups, I created a view and those views work pretty fine.
For one of these repeatable field group views, there is something strange. In the query filter section of this view, I can chose between:
Select posts in a lm_helme_boosts-2 relationship, that are a related to the current post in the loop.
Select posts in a lm_helme_boosts relationship, that are a related to the current post in the loop.
But there is not a second relationship.
This results in a strange behaviour cause sometimes, when I edit a post and select data for thiese lm_helme_boosts repeatable field group, I save the post and it is not shown in the view.
For other posts of this post type, I enter data for this repeatable field group and i see those in the view.
I can remember that I set up this field group twice but I deleted one of those.
So, maybe there seems to be a memory or caching problem for this deleted field group.
Another strange thing is, that I can move views to trash but there is not trash. But this only seems to be a little bug.
Just want to let you know that I found a little workaround.
In a view, there is the possibility to build the view not from cache but everytime it is quieried.
deactivating the cache makes my values appear.
So, this works for me (actually), even I know that the page loading speed is raised a little by this.
Anyway... it would be pretty cool to have an option to (1) clear the Toolset cache and additional really delete values when views, field groups, layouts and others are trashed (maybe by really showing the trash and allow to delete permanently. many pages of toolset just allow to move to trash (what makes the items still available I hink)
Hi,
Yes, there is built-in cache feature within Views, and you can display it by adding cached="off" in Views shortcode [wpv-view]. for example:
[wpv-view name="My view name" cached="off"]
Please let me know if you still need assistance for it. thanks
More help:
https://toolset.com/documentation/user-guides/views-shortcodes/#wpv-views
cached (opt): off
Turns off the caching system for the View.
still strange behaviour....
I think I need to add some screenshots
In the screen, you see created post type, repeatable group, along with view for repeatable group and view for post loop plus frontend output.
As you see, fields are not constantly saving.
When I add a new post and fill the fields and publish the post, than open the post again in the backend, the fields are (1) sometimes gone or (2) filled but not shown in frontend.
It seems to have a some big bugs
Oh.. by the way.
I also tried to completely remove the post nozerosmask (permanent delete) and add it again.
No changes on frontend
I found the problem (and it´s definetly caused by toolset).
As said above, I created the lm_helden_boosts repeatable field group twice, deleted one and worked with the second.
I also said that when creating a view for this group, two choiced where selectable: lm_helden_boosts and lm_helden_boosts-2.
I now visited PHPmyAdmin and searched the wordpress database.
In table _toolset_relationships I found the above mentioned entries:
lm_helden_boosts & lm_helden_boosts-2
i deleted the second and now the view works perfectly.
Please urgently message your developers that created and later delected views and relationships are NOT correctly and permanently delected when moved to trash. They are still in the database and cause problems when creating a view for repeatable field groups
The problem you mentioned above is abnormal:
fields are not constantly saving.
When I add a new post and fill the fields and publish the post, than open the post again in the backend, the fields are (1) sometimes gone or (2) filled but not shown in frontend.
Please provide a database dump file (ZIP file) with same problem, and fill it in below private detail box, I need to test and debug it in my localhost, thanks
Also point out the problem page URL, and where and how can I see the problem as you mentioned above:
the fields are (1) sometimes gone or (2) filled but not shown in frontend
Hi,
I would really love to send you your debug file, but it collects so much data that I decided not to do.
Anyway.. I even told you that the mysql database was not cleared after types elements are cleared . I found and solved this on my own and also asks you to send this to your developers to solve it for other users.
Just try
add post type
and field group to it with repeatable
save
delete
save
add field group again.
No there isn't same problem in my localhost with the steps you mentioned above:
add post type
and field group to it with repeatable
save
delete
save
add field group again.
And when you create the post field group again, you can add the custom field back to field group again, by this:
Dashboard-> Toolset-> Post Fields
click button "Post Field Control", find the custom field and add it back to the new field group.
I am not sure how I can help you cause I have already deleted that not correct saved custom field from the mysql database and the problem does not appear again (cause this ghost custom field was the problem).
As I mentioned above, I need to duplicate same problem, and I tried the steps you mentioned above, there isn't same problem in my localhost, so please update this thread when your database dump file is ready, thanks
