Write a good README.txt

Yeah, it's confusing, but read the readme.txt file in the module's directory.

There are no configuration screens. You have to update your settings.php file.

Also, you might want to use the Dev version, since there's a lot more code...

Nothing in the readme about settings.php...

Seems to be working though. Nevermind.

Feel free to provide a better README.txt

Yes. confusing.

after enable modules. I don't know what i should do.
It looks working and saving some watchdog message but no session or other entries.

I've written a new README with many additional examples and some additional pointers targeted at people who may like to experiment with the module but aren't MongoDB experts.

@ddiakopoulos: Thanks for you documentation, it's really clean and helpful.

@ddiakopoulos +1 Thanks!

One mistake.

mongodb_items should be mongodb_watchdog_items

Made a patch from the above README with some formatting and the correction from #11.

I would also add a missing variable watchdog_limit. This variable define the maximum level of severity to save into mongodb

In the following example, only errors more critical than WATCHDOG_CRITICAL status will be saved into mongodb (WATCHDOG_EMERGENCY, WATCHDOG_ALERT, WATCHDOG_CRITICAL)

Example :
$conf['watchdog_limit'] = WATCHDOG_CRITICAL;

I did a new patch based on the latest version of the README.txt and the patch done on comment #12. I've also added the comment #14 and followed conventions of README.txt found here.

It seems that the bot failed because of a problem on tests. I renamed my patch as "patch.txt" to mark it as "need review".

I was unable to install Drupal without adding include_once('./path/to/mongodb/mongodb_cache/mongodb_cache.inc');

Without this I received an error that the class DrupalMongoDBCache was not found in includes/cache.inc

If I add $conf['field_storage_default'] = 'mongodb_field_storage'; to my settings.php then during a drush install I get the following error

WD php: FieldException: Attempt to create a field with unknown storage type mongodb_field_storage. in field_create_field() (line 122 of [error]
.../public_html/modules/field/field.crud.inc).
Cannot modify header information - headers already sent by (output started at /usr/local/Cellar/drush/4.5/includes/drush.inc:917) bootstrap.inc:1221 [warning]
FieldException: Attempt to create a field with unknown storage type mongodb_field_storage. in field_create_field() (line 122 of .../public_html/modules/field/field.crud.inc).
Drush command terminated abnormally due to an unrecoverable error.

langworthy, what have your two questions to do with writing a better README.txt?

MiSc, following the instructions in the README patch produced the the problems listed above

That has nothing to do with this issue. Please create a new issue about that.

MiSc, I'm confused. If this issue is about updating the README and the additions to the README are incomplete and cause problem, how is reporting those problems not part of this issue? For example to fix the problem in #18 the README just needs another line including mongodb_cache.inc.

As I see it, this issue is about fixing the README,txt, nothing else.

MiSc. I agree completely.

I can see that my comment in #19 is probably a separate issue.

Regarding #18, when following the instructions of the patched README I could not install Drupal. I had to add an extra line to settings.php.

Here is an updated patch with the extra required line include_once('./sites/all/modules/mongodb/mongodb_cache/mongodb_cache.inc');

langworthy, I looked into it and you totally right about that include_once('./sites/all/modules/mongodb/mongodb_cache/mongodb_cache.inc')(or where ever you have your mongodb_cache.inc) like that in the settings.php, and that should really be in the README.txt.

But this is not how it should work - mongodb_chache should use the settings in $conf['cache_backends'] but does not. That conf seems not to be doing nothing right now. I create an new issue on that, I suggest we remove $conf['cache_backends'] from the README.txt right now - because it is confusing to write the same stuff in two places.

Patch applied to latest dev of 7.x-1.x.