[Resolved] Post created from parent post page in back-end doesn't validate correctly

[Author]

Posts

[matthiasI]

I am trying to:
Create a post from its parent page in back-office.
This post has a numeric field so it should not allow letter.
But if I create this post with a letter inside the numeric field, there is no error showing and the post is created with the numeric field empty.
If I modify it then it will show the error.

Link to a page where the issue can be seen:

I expected to see:
an error message and no post creation

Instead, I got:
a post created with an empty field.

[Minesh]

Hello. Thank you for contacting the Toolset support.

Can you please check if you have any js error on the browser's console - if yes, can you please share it.

Can you please share problem URL and admin access details.

*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin) 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.

[Minesh]

I tried to add a new post within the post-relationship box and when I try to publish it either with non-numeric characters to the numeric field it does works as expected and it shows the error message.

Please check the following video:
- hidden link

[matthiasI]

Please do the following to see the bug :
1. Select a date in the field Date début
2. Select a date in the field Date fin
3. Enter a non numeric value in the field Numéro période, for example "n3"
4. Click on the button "Appliquer"

[Minesh]

I found that you are using the legacy post relationship and you did not migrated to the new post relationship:
=> hidden link

Please check the following article:
- https://toolset.com/2018/05/when-if-to-migrate-relationships-in-old-toolset-sites/

*** Please make a FULL BACKUP of your database and website.***
If you decide to migrate to new post relationship, please make sure to take FULL backup of your database and website so in any worst case you will have backup with you to restore it.

Would you mind to migrate to new post relationship?

[matthiasI]

Did you see the problem I was referring to ?
I would prefer not to migrate to new post relationship.
Is it possible to solve the bug ?

[Minesh]

No, there is no way to solve the existing issue as its using the legacy post relationship.

We always recommend to use latest feature as the new post relationship have better URL and storage structure that will help you to boost performance.

[matthiasI]

The website is quite complex with a lot of data manipulation.
Migrating to new post relationship would take a lot of time. I'm okay with the actual performance so no need to boost it.

I just want to fix this bug and I don't have the budget for doing the whole migration. It's sad you can't fix it on your side.

[matthiasI]

Maybe you can tell me which file is responsible for the bug ?

[Minesh]

Unfortunately, I do not have any solution for this issue. It could not be a bug but you can say usability issue when you are using the legacy post relationship.

It seems the issue only happens when you have added the posts with either empty(blank) number field value.

[matthiasI]

Hi Minesh,
I finally added some javascript to fix the bug.
Thanks for your help and have a nice day

[matthiasI]

My issue is resolved now. Thank you!