Because Fever is written in PHP and the un-obfuscated source is made available to you upon purchase, I cannot offer free trials or refunds. #
There are no plans to offer a hosted version of Fever. For the foreseeable future Fever will remain a prosumer product that requires some technical proficiency and a server of your own to run it on. #
First try clicking the "attempt to fix" button. If that doesn't work you should be given the option to "proceed regardless" along with the following note:
This issue is not a deal-breaker. Progress indicators may appear to stall but the processes they represent will continue to work in the background.
I'm still working on the definitive solution but some hosts allow you to change the way PHP is served on your domain (from PHP-as-CGI or FastCGI to the PHP Apache mod). Under the CGI options, gzip-encoding (which prevents push because the entire request needs to be generated and gzipped before sending) cannot be disabled on a per-directory basis. #
Adding the following to an
.htaccess file in your
/fever/ directory should disable the includes:
php_value auto_prepend_file none php_value auto_append_file none
If that does not work you will need to contact your host for assistance. #
Your CMS or blogging software might be interfering with the request. Try adding an
.htaccess file to the
/fever/ directory containing the following:
<IfModule mod_rewrite.c> RewriteEngine off </IfModule>
That might fix it. If not you should refer to your CMS, blogging software or host’s documentation. #
safety-unlace.php in your
/fever/ directory to
unlace.php and load it in a web browser,
boot.php to automatically pull down an updated Compatibility Suite which may resolve the problem.
Be sure to change
unlace.php back to
safety-unlace.php once you’re done.
If it does not, you can also try this. Open up
/fever/.htaccess and change:
Then run the suite again but this time don’t choose “Attempt to fix.”
If you do not see an "attempt to fix" or "proceed regardless" button you might be using Safari 3. Try upgrading to Safari 4 or Firefox, both of which are free. #
The best way to move Fever is to migrate the database as you normally would (using the
mysqldump CLI or a similar migration tool) then install a fresh copy of Fever.
As long as you provide the correct connection details for your new database Fever will find and offer to use/update the existing database tables.
While you can just copy your Fever files from one server to another, this will cause permission and file ownership conflicts that will prevent Fever from updating in the future due to PHP security limitations. #
This is usually the result of an overzealous
mod_security rule. You ca try disabling
mod_security in your
/fever/ directory by adding the following to its .htaccess file:
<IfModule mod_security.c> SecFilterEngine Off SecFilterScanPOST Off </IfModule>
It has come to my attention that a recent update to either Apache or the
mod_security module seems to prevent per directory
.htaccess-based overrides so you may need to ask your host about disabling it for that directory.
Hosts running SuExec (also referred to as
mod_suphp) do not allow scripts to run with world-writable permissions. Try changing the
/fever/ folder's permissions to
755 and each file inside it to
PHP security demands precise ownership and permissions. Manually modifying (or moving) any of Fever’s files or folders will most likely prevent Fever from being able to update.
Once modified the easiest way to restore update functionality is to delete your Fever directory and upload a fresh copy. As long as you provide the same database connection details Fever will find and offer to use/update the existing database tables. #
I don't know if it's the best way but here's some screenshots of my Fever Fluid.app relevant preferences that work for me.
The iPhone-optimized version of Fever you see in the demo is a webclip. Visit your Fever installation in Safari and hit the + button in the bottom Safari bar then click "Add to Home Screen." #
The short answer: you don't.
Fever will automatically begin refreshing any stale feeds any time you hit the default screen. Returning from any sub-screen will automatically resync with the server. You can also manually resync by tapping the Fever logo. Regardless of which interface you use to access Fever, consider setting up a cron job to handle refreshing feeds (as described on the Extras page in your Fever installation). #
No, Fever is a single-user application. #
No, Fever cannot be licensed or installed on a local machine. #