The variables you can set in the settings.php should be variables editable via an admin page. Maybe even separate for each importer.
This is fully on purpose.
Hidden variables are setup level changes that should not need any configuration in most set ups.
Most importantly, they should not be changed by anybody who is not familiar with the code. Hence it does not make sense to expose them in the UI.
Is there a specific variable where the above does not apply?
According to our talk in IRC and due to the lot of "feeds not working" issues that pop up and can be solved via defining the correct values in the settings.php i would like to bump this up again.
Like i said in irc, the values should be set to "infinite" except they are customized via an setting. That is the expected behavior. Period. And due to the d7 accessibility "movement" that should be done via an admin setting page.
This is definitely not major.
I don't completely understand this issue, but I am certain that needing to edit values in a php file is not an accessibility issue.
Late to the game here, but it is a few extra steps to find out there are hidden settings, to then needing to FTP in, switch out permissions to edit them.
I think it would be less accessible to people not familiar with PHP or Drupal, who rely on the UI to build their sites.
I'm getting to the bottom of the job_schedule_num setting which has taken a bit of searching and still not at the solution yet.
An instruction or easy field in the UI would have meant I'd never hit the forums.
Liking the module btw... I just haven't got it under control yet but looks really powerful.
Drupal is a registered trademark of Dries Buytaert.