Forum Replies Created
-
AuthorPosts
-
Content Pilot
ParticipantI second this. If
multipleis set tofalsethen it could work in tandem with another flag likepost_metaset totrueso that the block can save to the db as the block's ID for themeta_keyNot totally sure if it is possible but saving to the db as post_meta and rendering on the frontend at the same time would be a game changer. I need blocks for page creating but still use pieces of data on archive pages or search result like phone numbers, emails, etc.
Content Pilot
ParticipantHi Ahn, I made another comment on a merged PR for this topic. Your feedback is appreciated.
https://github.com/wpmetabox/mb-relationships/pull/22#issuecomment-566784736
Content Pilot
ParticipantI understand Anh, I'll return if I have any idea how to improve it further.
At the moment we will try to reduce with the client the amount of relationships for the posts that still load very slow (some load more than 100 MB)
I also noticed that yesterday you integrated it into the new versions of meta-box and mb-relationships.
Thanks for all the help.Content Pilot
ParticipantMy thought is to remove the queries that are made when the page loads, only for the relationship fields that are closed
closed => trueSo we use the ajax query to fetch the items when the user open the field.
If the field is set open, those queries cannot be omitted in the page load since the selected items must be displayed from the start.Although when the page load the queries are done only once, having several relationship fields and many elements selected in each one, all queries are made even if the user does not need to edit the fields.
This is just my guess, you can tell me if it's feasible. Thanks again.
Content Pilot
ParticipantThanks so much for the solution Anh, we have noticed that the time to editing the relationship fields is greatly improved. The customization of parameters also worked well. However, we still find two more moments where the load becomes really heavy in post with many relationships.
One of those moments happens when the user open a closed relationship field. We understand that there is not much to do, since all relationships are loaded only once.
The other moment is in the initial charge. We are not sure that this happens there, but it's possible not to query any relationships for the relationship fields closed? In this way, a lazy load could be added that loads only the relationship field requested by the user.Please correct me if I am wrong or if you find something else that can improve the initial load of the editor that is still very heavy.
Content Pilot
ParticipantThat would be great Anh, thanks
Content Pilot
ParticipantHi Anh, just to know if you think you'll get it soon or if it can get complicated. I appreciate your time on this. Thanks
Content Pilot
ParticipantHi Anh,
We found that recently Advanced Custom Fields is using Ajax to populate the posts on the relationship field as the field comes into the browser.
https://www.advancedcustomfields.com/blog/acf-5-8-4-release/
I share this in case it helps. Thanks
Content Pilot
ParticipantAnh, do you have any ETA when you can have this? We really appreciate your help.
Content Pilot
ParticipantThank you for your reply Anh and for working on this.
You're right about the number of relationships, now I've seen it.
I will stay expectantContent Pilot
ParticipantThanks Anh, the problem was that I was not getting one of the latest versions of metabox that is necessary since you have made important JavaScript changes for MB Blocks.
For me it's fine if we close the ticket.
Thanks for your helpContent Pilot
ParticipantThanks for your reply Anh,
I was trying with the API. Now I tried it with plugin v1.0.3 and the same thing happens, the fields are not shown and the values are not saved. Note: if I add the fields within a clonable group, from the second they are displayed.
Content Pilot
ParticipantUpdate: If the fields are within a clonable group, the first item is not displayed correctly, as of the second, yes. Still, the values are not saved.
May 22, 2019 at 7:20 PM in reply to: ✅rwmb_normalize_meta_box Filter not present in code but is present in docs #14678Content Pilot
ParticipantThanks Ahn!
Content Pilot
ParticipantFor sure. I was expecting to be a big part of it. I greatly appreciate you guiding the way. Let's come up with a strategy and start a branch.
-
AuthorPosts