Form Designer

Dazed
Dazed
@dazed
12 years ago
1,022 posts
So I have created a bunch of forms with the designer and this new one is being troublesome. I am adding another field on the audio page for the admin only. I added it to Create and Update. As an admin, I can create and audio or edit audio and the field is visible. However, if I go to an artist page they do not exist. I have run integrity checks and cache resets.

I do however see one field still listed with the asterisks like *Field Name*. Those should disappear when the field is initialized correct?

What am I missing?

Oh I did see it appear once on an artist page and when I clicked the checkbox and I submitted, I get the below.

NOT FOUND
The Page You Requested Was Not Found!

updated by @dazed: 12/14/13 12:56:09PM
michael
@michael
12 years ago
7,772 posts
not sure here. somethimes 404 will show if the user does not have permissions to see the page, so check the same URL with the admin to see if it is 404 or not.

*Field Name* might need changing to something if you created that field, like *use whatever name you like here* type thing.

Try that first, so we can narrow it down as much as possible. I dont know the answer here, but will try to help if I can.
brian
@brian
12 years ago
10,148 posts
The asterisks around the field don't mean it has not been initialized - it means that string has been setup as a language string, but it is showing the DEFAULT string and does not have an entry in your current loaded language string set. This should go away with a cache reset (or log out and log back in) since the lang strings are cached.

I use custom fields quite a bit and have never seen a "not found" so something is not right.

Let me know if you still see a problem.

Thanks!


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
Dazed
Dazed
@dazed
12 years ago
1,022 posts
Thanks guys. I sent Brian screen shots of the create and update fields. These are just a checkbox visible to admin only. Just kind of odd since I have added several of these in the past. Probably user error hehe
brian
@brian
12 years ago
10,148 posts
This should be fixed for you now - for some reason the form table entries for that field were not correct in the DB, and it looks like there might have been another field named the same that was previously created then deleted, so I am guessing that is related, and I will check it out.

Thanks!


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
Dazed
Dazed
@dazed
12 years ago
1,022 posts
appreciate it Brian