Installation procedure / modules page

I just add my second comment in this same issue:

1. I think the configuration page is an unnecessary step in the installation process: your module is fairly simple; it has only 1 thing to do, so why bother going to a config page to activate after installation? A configuration page might be a good idea if you plan to have more options in the future, so you might consider setting the default value already to YES directly with installing. Site Admin then can Deactivate upon request without going to the modules page, which may be Developers's domain.

2. When you add the following line in the info file, the config page gets listed on the modules page:
configure = admin/config/content/form_save

3. When you add a README.txt file in your module, this also gets listed on the modules automatically when Advanced help is installed. If you do not want to maintain your info on 2 places (because it is already in the project page), it can contain a link to the drupal.org project page.

With points 2 and 3 in place, the modules page is my 'cockpit' for this module!

And yes, the module works perfactly fine on IE8 and Chrome. Thanks!

Nice! I tried to download the package, but get the following result: "The requested URL /files/projects/form_save-7.x-1.0-alpha1.tar.gz was not found on this server."

Should I wait a night?

When I use http://ftp.drupal.org/files/projects , I land on a USA Oregon university mirror site. Perhaps we need to give it some time to spread the file over all CDN sites (if there are any..)

First findings:
- your module is still called 'From Save' on the modules page;
- since you have removed the Configure page, you can remove the permissions, too.
- Do I need to flush caches to get is working? I will try to disable/enable to find this out.

OK, Everything seems to work fine! But before setting a RTBC, some more nitpicking:

info-file:
+name = Form save
-name = Form Save // core modules do not use capitals either; if you change, then on project page, too
description = Allows users to save their forms using Ctrl+S or Cmd+S.
-package = Other // other si the default package, so you don't need to mention it here

module-file:
- function form_save_help() : seems like a copy&paste residue. Can be removed (?); the path 'admin/config/front' does not exist.
- function form_save_find_default_button(): I don't think this is supposed to be a public function? I believe common practice is to add prefix '_' and change the name then to _form_save_find_default_button($form, $buttons)
- some typo's below (but I don't know css, don't know if they are, and don't know if/when software is broken);

-      if (!isset($button['#deafult_button'])) {
+      if (!isset($button['#default_button'])) {  // typo?
         $button['#attributes']['class'][] = 'form-save-default-button';
...
-      $element['#attributes']['class'] .= ' form-save-default-button';  // You used this class before without space.
+      $element['#attributes']['class'] .= 'form-save-default-button';
       return TRUE;
     }

Hi Tim, didn't the typo's break things? I suppose you have testcases with and without default buttons, and tested yourself, too. I only test some forms, not knowing if a default button is enabled or not. I can test again next friday.
Groeten, John

Well, looks goods, works fine! ready for the world!

version 1 is released.
Timothy, thanx for the credits on the project page.