FireWire Posted 2 hours ago Share Posted 2 hours ago This may be an issue when using the ProFields Custom Field. I have a block that contains a Custom Field. That custom field contains a Page Reference field (single), Page Reference field (multiple), and a number input. When I create several blocks containing this field the values become unmanageable. They all appear in all blocks and can't be ordered in any of them. I have several of these blocks and each should have only 3 or 4, but they are all rendered with all of them. I did do some digging and found that the custom fields are not prefixed as a repeater field in the request data when saving the page, so each of these Page Reference field with multiple pages selected are all returned as a single variable array. I've attached a txt file with the POST request parameters and it shows the following variable repeated without a repeater suffix: event_activities_select_activities[] Which may need to be handled as something like: event_activities_select_activities_repeater5783[] This is just a guess... I could be off on that, but the only constant that I could see in the issues when rendering is that every block has the same event_activities_select_activities variable without a way for it to be processed individually by block. That's what I could pull together while experimenting. Something that's fixable? I have to determine if I need to rewrite the blocks to use different fields 😵💫 rpb_blocks_custom_fields_request.txt Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now