Unable to change Form Options

Also, Settings cannot be changed, although I see that I did update the Notification email, but cannot add a PayPal Email.

The log shows attempts to save the form:
PREPARING DONATION FORM
Seamless Donations Version: 4.0.6
User browser: Chrome 44.0.2403.157
Assigning hidden field session ID to [########]
Form action: https://commongroundmeditation.org/wpsite/wp-content/plugins/seamless-donations/seamless-donations-payment.php

However, no logging of attempts to change Settings.

The log doesn’t record any settings changes, just the transaction process. Although that’s a good idea.

I have encountered an odd “can’t save settings” issue once before. What are the big save button names for your Form Options panel page?

–David

Sure, Four buttons at the bottom of each section of Form Options:
Save Changes

<input type=”submit” value=”Save Changes” id=”seamless_donations_admin_forms_section_levels_submit__0″ name=”SeamlessDonationsAdmin[seamless_donations_admin_forms_section_levels][submit]” data-id_model=”seamless_donations_admin_forms_section_levels_submit__-fi-” data-name_model=”SeamlessDonationsAdmin[seamless_donations_admin_forms_section_levels][submit]” class=”button button-primary” title=”Save Changes” alt=””>

I am setting up a Sandbox to Clone the site for testing, as they need a new Donation process, and this look very nice.

FYI, set up Sandbox with clean install of WP 4.3, and Seamless Donations works perfect on same WiredTree VPS server. So, will clone in the production site and test for other config/plugin issues.

The button on the bottom of Form Options should be “Save Fields.” I don’t have a Save Changes anywhere in the entire code. I saw this once before, and some plugin had written an option into the database that somehow caused button names to change.

The user never figured out which plugin or which option, but went to a fresh install. I’m leaving this post unresolved until I hear you’ve got it working.

–David

P.S. on the Form Options panel, you want button names of Save Giving Levels, Save Defaults, Save Fields, and Save Tweaks.

Got It. Will test and Sandbox and report the source. Thanks!

Awesome. Thanks!

Yes works with a fresh install but not with a clone of the production website with all plugins and custom themes deactivated and directories renamed. You are correct, as I did find a single row in wp_options with the setting that causes the problem with option_name: Submit set to option_value: Save Changes.

I can see in the table stack that this is a legacy Headway setting from an earlier developer, who actually never completed his design, and this proves my opinion that Headway sucks, like most page design frameworks that hijack WordPress to their own benefit.

Thanks for the tip David!!!

I’m sorry about the delay. As you probably know from my support forum post, I’ve been away on a family emergency.

You’re welcome. That one is crazy-making.

–David

Hey David,

I have the exact same problem. My button read “Save changes”. Can’t find the plugin that’s messing with it. Do you know from other people what were those?

My issue was not a plugin. It was an options setting in the database made by the Headway framework theme. The theme was not in use, but it was legacy code from a previous developer. There was no indication in the table row what had set it, but I could tell from neighboring rows that it was the old theme. You may disrupt a theme or plugin that is still in use, so do this at your own discretion.

You need to search the database table wp_options to delete a row that has:
option_name: Submit
option_value: Save Changes

You’ll need to access the database on your server using something like phpMyAdmin.

And I have no idea why that’s happening. I use an admin builder framework to construct the settings pages, and I checked with the framework’s developer. He’s never touching anything with either option_name or option_value that has a Submit and Save Changes. It could be deeper in WordPress.

I’m thinking of adding a little tweak hack to remove this row, but I have no idea what kind of ripple effect it might have. It’s baffling, especially since it’s clearly impacting our options, but doesn’t appear to be anything in our code.

Just odd.