Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Supposedly empty fields shows values in pods manage page. #1854

Open
bakaburg1 opened this issue Nov 12, 2013 · 3 comments · May be fixed by #5776
Open

Supposedly empty fields shows values in pods manage page. #1854

bakaburg1 opened this issue Nov 12, 2013 · 3 comments · May be fixed by #5776
Labels
Keyword: Puntable Status: Help Wanted We have not prioritized this yet, but you can help make it happen to speed it up Type: Bug
Milestone

Comments

@bakaburg1
Copy link

Hello Scott & folks,

I'm having a strange bug here.

On the pods list manage table all simple list field that should be empty are showing the first option!

I can't track whether the bug was introducing during a change in the code or after a pods upgrade!

@bakaburg1
Copy link
Author

Any news here? I can give access to site if needed!

@bakaburg1
Copy link
Author

Any news on this? it happens also in my local site.

Here is a pod item saved via php and not edited manually:
schermata 2014-02-19 a 14 51 41
The field from "Context" and so on should be empty, and indeed they are, both if you open the item to edit in wordpress and also if you check the item in the MySQL database via phpmyadmin.
But in the pods item manage page it shows values.

To be noticed: these fiields are all simple relationships defined with a index|value notation and the fake values that is showing is always the first one identified by 0.

schermata 2014-02-19 a 14 56 41
schermata 2014-02-19 a 14 56 16
schermata 2014-02-19 a 14 56 25
schermata 2014-02-19 a 14 56 07
schermata 2014-02-19 a 14 57 23

The only field that doesn't give any problems is social network, I suppose because is not indexed.

So, my guess is that there is a wrong identity catched between NULL and the 0 index used for the first element of these relationships.

@bakaburg1
Copy link
Author

Ok I patched the bug by saving the pod item with false as value for the mentioned fields.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Keyword: Puntable Status: Help Wanted We have not prioritized this yet, but you can help make it happen to speed it up Type: Bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants