There are a lot fixes that have been added to the module since the latest release, should we do a new release in the near future? From my point of view the dev is more stable then the beta release.

Comments

misc’s picture

misc commented

I prepared to a new new beta release of the module, and pushed the tag. So, someone of the maintainers, could you take a look?

Here are are the commit messages since the latest release:

  • Issue #1470884, reported by jcfiala: Setting node_types causes pages to be ignored
  • Issue #1188156: Improve index on mongodb_queue, reported by litwol
  • Issue #1488092: Update mongodb_block_ui to current Drupal coding standards
  • Issue #1225788 reported by moshe weitzman: Rename block_test module
  • Issue #1488028: Update mongodb_queue to current Drupal coding standards
  • Issue #1488044: Update mongodb_block to current Drupal coding standards
  • Issue #1305580 reported by Paul Kim Consulting: MongoDB Field Storage does not work with various revisioning modules
  • Issue #1454078 reported by nagba
  • Issue #1465938, reported by drupik
  • Formatting in the session module
  • Issue #1378468, reported by ckng: Notice: Undefined index: status in _drupal_session_read()
  • Issue #1381410 reported by makara: Use drupal_load() when it's possible
  • Issue #1454078 reported by nagba: Missing timezone handling
  • Formatting in field storage module
  • minor formatting in mongodb_field_storage
  • Issue #1448130 reported by chx: Coding style is broken
  • Issue #839264 reported by Pasqualle
  • Issue #1269954 reported by ericduran: mongoDebugCollection doesnt instantiate mongoDebugCursor
  • Issue #1269954 reported by ninerian: Adding Rules not possible. A temporary workaround that should been fixed for real.
  • Issue #1335326 reported by psynaptic: Call to undefined method MongoCollection::delete()
  • Issue #910726 reported by gordon: Drupal Crashes when writting to page cache in mongodb
  • Issue #994984 reported by jspapas: Write a good README.txt
  • Issue 1361912, reported by MiSc: Fatal error: Class TaxonomyTermController not found
  • Issue 1328956, reported by univate: <> operator not implemented
  • Issue 1400220, reported by MiSc: mongodb_field_storage_query doesnt handle IN operator in entity conditions
  • Issue 1565730, reported by Iivonen: mongodb_field_storage_query doesnt handle IN operator in entity conditions
  • Issue 1355890, reported by univate: Field query Contains should be case-intensive?.
  • Issue 1144398, reported by StryKaizer: Attempt to create a field with unkonown storage type.
  • Issue #660426 by fgm: Skip tests when setUp() cannot connect, to save testing resources.
  • Issue #1190606 by fgm: Fixed Watchdog event view links to non existent user pages
  • Issue #1187946 by fgm: Provide dblog-equivalent 403 and 404 reports, straight port from the D6 version, include workaround for core issue #904994
  • Issue #1355808 by fgm: Implement watchdog filter-on-insert in mongodb_watchdog. implement feature in module, request a different message on each pass of test, minor commenting/naming changes to minimize differences with the D6 version, add note about the relevant watchdog_limit variable in README
  • changes to be used together with mongodb_dbtng commented out.
  • changes to be used together with mongodb_dbtng commented out.
  • Issue #1173058: inconsistent variable use in mongodb_watchdog.
  • Fixed #816026: PHP Notice: Undefined variable: roles by dereine.
  • Fixed #814846: Update for DRUPAL-SA-CORE-2010-001 by dereine
  • Fixed #878000: We should not try to clear the entity cache if not enabled by Damien Tournoud
fgm’s picture

fgm
Primary language French
Location Paris, France
commented

Sounds like a good idea. The commit message summaries could use some work, though.

chx’s picture

chx commented
Assigned: Unassigned » chx
chx’s picture

chx commented

This is awesome work, thanks! The only thing caught my eye is minor: why did we rename to admin/reports/mongodb/%mongodb_watchdog_event ?

misc’s picture

misc commented

@fgm, do you now why we renamed in watchdog?

fgm’s picture

fgm
Primary language French
Location Paris, France
commented

I'm afraid I do not really understand the question asking why a path was renamed (from what ?). Did you find the issue for which this commit was done ?

misc’s picture

misc commented

@fgm - It was commited by you: http://drupalcode.org/project/mongodb.git/blobdiff/9c3fc740f7f14c4234f2f...

Before it were admin/reports/mongodb-event/%mongodb_watchdog_event

See: #1187946: Provide dblog-equivalent 403 and 404 reports

fgm’s picture

fgm
Primary language French
Location Paris, France
commented

I seem to remember that this was for better path consistency: with the previous path, "hacking" the paths by removing the last component led to a 404, because admin/reports/mongodb-event had no menu entry: with this new path, all mongodb watchdog reports are under admin/reports/mongodb, including the top 403 and top 404 at local tasks, which would not work if the path was not admin/reports/mongodb.

Alternatively, it would also have been possible to create them all under admin/reports/mongodb-event, but that would have made a bit less sense, I think.

chx’s picture

chx commented
Status: Active » Reviewed & tested by the community

I thought that pattern was established by core but then again the argument here is a hash isn't so there is no collision. Go for it.

univate’s picture

univate commented

I see the tag for beta3 in git, but it appears someone forgot to create the release on d.o, wondering if there is known reason for not publishing the release?

Rok Žlender’s picture

Rok Žlender commented

Before creating new release I think this #1571890: Mongodb session's user update hook breaks profile's custom fields needs to get in.

chx’s picture

chx commented
Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.