We have setup repeatable fields for one of the post type and when we edit the post it was showing empty fields for some of the posts. After digging it further by comparing that same post's data with previous database backups, we found that IDs of all the repeatable fields are different meaning they have been replaced with new fields. We have checked the server error logs but did not find anything related. We also checked the logs of the repeatable fields post type in Stream and we noticed that as soon as we edit the post, it created new posts for those repeatable fields. Is there anything in the plugin code which would remove the repeatable fields and replace with empty ones?
Please let us know if you need any more details regarding the issue we are facing.
Hello. Thank you for contacting the Toolset support.
As I understand you created repeating field group that is attached to display with XX post type.
Repeating field group treated as one-to-many post-relationship between post type where you attached it where parent will be the post type where you attached the repeating field group and child post type will be repeating field group it self.
So, obviously when you add a new item (row) to your repeating field group it will be added as a new post and all custom fields will be saved to postmeta table with associated post ID.
I'm not sure yet what exactly the issue is but if you have orphans content with post-relationship, you could see such issue. You are welcome to share problem URL and admin access details and let me know what steps I should follow to see the issue.
*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.
I have set the next reply to private which means only you and I have access to it.
We didn't add any new item, it was still the same set of fields which were replaced with the empty fields the next day. I am attaching the screenshots of one of the affected post (with same ID) from the DB backups.
I'm not sure yet what exactly the issue is but if you have orphans content with post-relationship, you could see such issue.
Can you elaborate more on this please? How the repeatable fields can be converted into orphans content?
Thing is this issue affected a lot of posts in our site, for the time being we have restored the data but trying to understand under what circumstances this can happen and how to avoid it.
I'm not sure yet what exactly the issue is but if you have orphans content with post-relationship, you could see such issue.
Can you elaborate more on this please? How the repeatable fields can be converted into orphans content?
==>
When I said orphans, I mean to say that if you have ever tried to import the repeating field and due to that you see the empty contents.
You will have to keep eye and check on what action you able to reproduce the issue. As we can not monitor your site. If you find a clue or action that causes this issue we are happy to help you.
Apologies if issue wasn't clear but as you can see the screenshots attached in my previous reply, we had content in repeatable fields and the next day suddenly they all were empty. This happened to a lot of posts in our site.
I can confirm we haven't imported any of the repeating fields. We use this plugin along with WPML, you think it could have cause any issue? We took a look at the plugin's codebase and looks like if it can't find the translated post for a field, it creates a new one for current language which results into empty fields.
Also wanted to ask if it has any issues with WordPress 5.9.3.
Do you mean that you have number of posts available with content added with repeating field group and then later you added the WPML plugin and then you see that the content for repeating field group is not showing after installing and activating the WPML plugin?
The thing is that we will require to know at what course of action this happen as we do not have any tool to backtrack the thing.
Did someone changed any WPML settings? Do you have any idea after what action this started to happen as without all this information we could not able to know from where to start to see the issue. I hope you understand what I mean.
The topic ‘[Closed] Repeatable fields removed from the database’ is closed to new replies.
