Options will not save

I am working on building a new Joomla 2.5 web site for my church to replace our current Joomla 1.5 web site (with SermonSpeaker v3.3). I am working from scratch (no upgrading) on the new site using a private server before moving the new site to our public web host.

After I installed SermonSpeaker 4.5 on the site, I received an error message stating "Your settings are not yet saved, please click on 'Options' on the upper right corner and save them." Every time that I go to 'Options' and click on Save, nothing is saved so I get the error message again. I have also noted strange behavior when I click on Save from the Options in the light-box. The Joomla Global Configurations page is displayed in the light box and the light box does not close as I would expect. (See attached screen shot.)

I suspect that there may be a permissions or similar problem some where, but I have not been able to where. Any ideas?

Setup is:
Joomla 2.5.9
PHP 5.2.6
Apache 2.2.9
SermonSpeaker 4.5.3 (same problem happened with 4.5.1)
Template = JSN_Boot_Pro

Thanks,
George

This sounds a lot like something is wrong with eitheryour Joomla installation or the SermonSpeaker installation.
Did you check if the options work for other extensions like the articles or weblinks?

The reason I ask is that basically the options are done by a Joomla core function. SermonSpeaker only provides the config.xml file and the rest is all done by Joomla itself.

Thanks for the quick reply. To update you, I did find some minor problems with saving options, etc. for some other extensions, so I started looking at my server configuration. I tried a few changes to both PHP and the database, but with no success.

So, I decided to move the entire site up to the live site with a temporary sub-domain URL. As expected, no problems there. Once I get the new site on-line, I will take some time to rebuild and update our off-line development server to match our live site. Probably should have done that first.

George

Interesting.
By the way: Joomla stores the component settings as an json_encoded array into the params field of the #__extensions table. Maybe that helps to track down the problem. The extension responsible for this is the core component com_config.
Maybe this helps track down the problem of your development server.