solved. figured it out on my own.
Here is an example of the query
http://screencast.com/t/RBHLJZQO
sweet! is there anything wrong with doing it this way?
if (current_user_can('administrator')) {
if(function_exists('acf_add_options_page')) {
acf_add_options_page();
acf_add_options_sub_page('Global');
acf_add_options_sub_page('Home');
acf_add_options_sub_page('Ads');
acf_add_options_sub_page('Social Media Widget');
acf_add_options_sub_page('Calendar Options');
}
}
I think it has something to do with the field name length. is there a limit to the length of the custom field names?
I found a work around for this.
Save the URL’s as “www.google.com” instead of “http://www.google.com” then in your theme change it to
Looks like others have already filed this problem as a bug report.
I came to this conclusion/problem as well after banging my head against the desk for hours.
http://support.advancedcustomfields.com/forums/topic/options-page-not-working-with-godaddy/
After more testing I’ve found the cause of the issue. It’s not the renaming of the field.
The problem is when I try to save a field that has a URL in it. Renaming the repeater field simply made it so there wasn’t any URL to be saved in the fields.
So in my sponsors repeater field I had a text field where I entered a URL into it.
I tried switching the field to a URL field instead of a text field and it’s the same issue.
So the issue is trying to save an options page with a url as one of the fields that’s causing the 404.
Any idea why this could be happening?
EDIT: after more debugging I found the real issue in the post below this one.
So I thought that changing the “sponsors” repeater field to “ky_sponsors” was the solution but it doesn’t look like it.
Here’s what I’ve done and what I’ve found about this issue.
I deployed the site from my local install with duplicator to godaddy. Tried to save options but 404 error on one of my option pages. However no problems on my local install.
Narrowed the problem down to a repeater field called “sponsors”. Changed the name of the field to “ky_sponsors” on godaddy, save options and it works.
Make the same change to my local server of changing the field to “ky_sponsors” then sync the godaddy installation with my local installation with migrate db pro. Try and save the problematic option page on godaddy server and 404 error again.
So I change the field back to “sponsors” on the godaddy server, save options and it works.
Based on all of this I think the problem has to be due to something with godaddy + duplicator/migrate db pro + ACF. The problem seems to happen when databases are being synced.
Maybe the “sponsors” field isn’t being written properly during the database syncs? I don’t know enough mysql to answer that though.
Any ideas?
Ok I went through each field and appended some text to them.
It looks like you’re right. It looks like a repeater field with the name “sponsors” is triggering the 404 error.
This is strange because I don’t have a problem with it on my local wamp install or my liquid web servers.
Any idea why this is happening??
I’m not having the issue with my non go daddy server though.
I’ll try though just to make sure!
I’m having this issue as well.
@Ben Pearson
I simply had my host look at the logs and white list the things that were triggered. the support is A+ 🙂
sorry I couldn’t be of anymore help!
ahh. I see. thanks for the answer!!
do you know of a possible alternative solution to use for now?
hey @Elliot Condon , I already marked the issue as solved. It was a modsec issue with the server 🙂
thanks!
my sql skills are non existent 😛 . I’ll try it out though! thanks!
It looks to be an issue with my wordpress version.
Updated from 3.8.1 to 3.9.1 and it seemed to fix the issue.
there was a conflicting error with other custom field data being in the post. not sure why but deleting it fixed the issue.
narrowed it down. it’s not the date picker but the date and time picker plugin that’s not working with the latest update.
http://wordpress.org/plugins/acf-field-date-time-picker/
Also no js errors in the console.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Privacy Policy. If you continue to use this site, you consent to our use of cookies.