[Resolved] Custom fields bugs since latest update

[Author]

Posts

[Nigel]

Yes, it has been escalated, some preliminary debugging has been done by second tier support, and the issue has been forwarded to the developers for detailed analysis.

I'll let you know when I have more info to share.

[matthewL-7]

Hi Nigel,

Is there any update on this being fixed?

Cheers
Matt

[Nigel]

Hi Matt

From the internal tickets I can see that the developer proposed a fix and it is undergoing testing, so hopefully it won't be too long before I can get the fix to you.

I'm monitoring the ticket and I'll update you as soon as I can.

[matthewL-7]

Hey Nigel

What is the latest on this please? This bug is causing a lot of frustration.

Cheers.

[Nigel]

Let me see if I can get a patch from the developer.

[Nigel]

Hi Matt

We are waiting on a tester to confirm the patch is safe to apply, it looks like it will be Monday when I can give the patch to you.

Sorry to keep you waiting.

[Nigel]

Hi Matt

I have the patch for you now: hidden link

That is an updated version of Types. You need to manually delete your existing Types from the main plugins page and then upload this zip on the Add new plugins page.

Make sure you have a backup first.

(And, more generally, it seems you work exclusively on the live site, I would strongly encourage you to set up a staging site where you can test plugin updates etc. before pushing them live.)

Let me know if the update fixes the issue or whether you see any other problems arise.

[matthewL-7]

Hey Nigel,

Thanks, this patch seems to be working fine form initial tests :). How will this patch work now for updates? When an update comes out will it just over-write the patch? Will the next version be patched?

Hmm I hear what you are saying with the staging site, did try this but ended up having too many differences, are there any decent plugins/services you can recommend to manage a staging site? A way to sync the data across easily?

Cheers.

[matthewL-7]

Just to follow up on my last message this has fixed this on our CPT but having the same issue on pages still where the date picker does not work.

[Nigel]

Sorry Matt, can you clarify that last message.

The reported issue was about JavaScript errors on post edit screens arising from a problem with custom field group permissions.

The patch has fixed this issue on the custom post type edit screens, but you have JS errors when editing pages which is stopping the datepicker of a date field from working, is that right?

Can you share a screenshot of the JS errors from the browser console?

[matthewL-7]

Hey Nigel,

Good news. Been testing this and it looks like it was maybe a caching issue as it seems to be working fine now with repeatable field groups which I thought were not working with the date picker still.

So this patch fixes the date picker issue. Do you know when this patch will be going into the main plugin?

Cheers.
Matt

[Nigel]

Just released!

Please go ahead and update Forms (and Views) and let me know if you still see any issues.

[matthewL-7]

Hey Nigel,

I thought this bug was related to Types not Forms and Views?

[Nigel]

Sorry Matt, you are of course correct, I had been expecting Types to be included with the updates but in the end it was not because it needs to go through QA testing and our testing team is loaded at the moment, so it is likely to be another couple of weeks before we see a Types update.

If you have the patch applied there should be nothing for you to do, when the update is published it will overwrite your patched version with the version that includes the fix anyway.

[Nigel]

Hi Matt

Just to let you know, Types 3.3 is finally out and updating you should find the issue resolved (your current patched version will be overwritten).