marrow / contentment Goto Github PK

Field(s) under details that allow a user to include an optional ticket price for a given event.

Even more useful would be optional multiple tiers, with a customized descriptor; ie, 'Member' and 'Non-member', or 'Adult', 'Senior' and 'Youth'.

When I click 'modify' on an event, it removes all previously input information in the 'Contact' tab.

This prevents indexing of content after initial page creation.

A field under 'details', perhaps just under the event date/time fields that lets a user include an 'RSVP by:'

Like some of the contact fields, it could be optional.

This isn't exclusively tied to Contentment, but Contentment is probably the most extensive use of MongoEngine by Marrow projects.

The following issues directly impact our use of the library, and since 0.10 there have been an absolutely astounding number of regressions and new bugs added which have had far-reaching effects. Here are the short lists.

• MongoEngine/mongoengine#897 — Overall code health.
• MongoEngine/mongoengine#2103 — Removal of contributed positional instantiation functionality.

Enhancements

• MongoEngine/mongoengine#167 (rejected) — A nearly four year old ticket directly relating to promotion and demotion of Contentment Asset classes to allow for post-creation specialization and migration between specializations.
• MongoEngine/mongoengine#298 — 2013. Allow access to referenced document ID without full dereferencing; similarly aged ticket.
• MongoEngine/mongoengine#450 — Can't query on the generated class name field.
• MongoEngine/mongoengine#529 — Projection positional operator. 2013. I mean, really.
• MongoEngine/mongoengine#1319 — Using model class name for unique identification is sub-optimal.
• MongoEngine/mongoengine#1321 — Field order not preserved during redefinition.
• MongoEngine/mongoengine#1293 — Can't define a primary key attribute name.
• MongoEngine/mongoengine#1099 — Support MongoDB collection compression options in meta.

Performance

• MongoEngine/mongoengine#1137 (and MongoEngine/mongoengine#1230) — MongoEngine recursively converts documents on load, suffering performance issues on large documents due to this eager conversion.
• MongoEngine/mongoengine#1116 — List field in checks are quite slow.
• MongoEngine/mongoengine#1073 — Unaddressed drop from 0.8.7 to 0.9.0.
• MongoEngine/mongoengine#937 — Queryset cache really kills things, especially len() performance.

Regressions

• MongoEngine/mongoengine#1178 — Fields with overridden db_field (about 95% of ours) don't get marked as dirty and are not saved correctly.
• MongoEngine/mongoengine#1245 — Disabling dereferencing doesn't disable dereferencing.
• MongoEngine/mongoengine#1136 — An internally infamous bug, if you count the result of a query, limit is no longer applied.
• MongoEngine/mongoengine#1135 — Cascade reverse delete rule issues.
• MongoEngine/mongoengine#904 — A PR exists, but not accepted yet, to fix db_field usage in hierarchical embedded documents.
• MongoEngine/mongoengine#564 — Saving uses an upsert by default. This has certainly caused some of our harder to track down "where the hell did this mangled data come from?!" problems.

Bugs

• MongoEngine/mongoengine#475 — Can't query/filter fields that are present on embedded document subclasses.
• MongoEngine/mongoengine#1246 — Use of primary_key is pretty broken.
• MongoEngine/mongoengine#1276 — Reload attempts to write attributes based on data, not current field lists.
• MongoEngine/mongoengine#1284 — Beyond not disabling dereferencing, the context manager also eats all exceptions. (As does the no_sub_classes manager.)
• MongoEngine/mongoengine#1288 — Dereferencing in the context of multiple database connections fails.
• MongoEngine/mongoengine#1126 — MongoEngine/mongoengine#620 incorrectly references fields by attribute name, not db_field.
• MongoEngine/mongoengine#1102 — Field not present, but defined with db_field, fails validation.
• MongoEngine/mongoengine#1086 — Calling len() on a query set mid-iteration breaks iteration.
• MongoEngine/mongoengine#1085 — Critical data loss can occur if using projection.
• MongoEngine/mongoengine#1034 — not__match__nin fails.
• MongoEngine/mongoengine#997 — Can't safely reference abstract document base class.
• MongoEngine/mongoengine#909 — URI overrides username/password on connect, even if it does not define a username or password.
• MongoEngine/mongoengine#808 — Can't handle diamond inheritance. (This is huge for Contentment.)

Field Bugs

• MongoEngine/mongoengine#1228 — Poor regular expression-based e-mail validation.
• MongoEngine/mongoengine#1320 — Atomic operations on decimal fields.
• MongoEngine/mongoengine#1316 — Disabling of document cache breaks iteration protocol.
• MongoEngine/mongoengine#1318 — List fields fail to correctly track changes.
• MongoEngine/mongoengine#1301 — GridFS file storage stores against default DB in multi-DB context.
• MongoEngine/mongoengine#637 — More decimal field issues.
• MongoEngine/mongoengine#618 — ObjectId fields behave badly on Python 3.
• MongoEngine/mongoengine#632 — List field data loss.
• MongoEngine/mongoengine#1119 — Can't utilize negative indices on list fields for assignment/update.
• MongoEngine/mongoengine#1059 — More decimal field setter issues; transform to float.
• MongoEngine/mongoengine#847 — Image field nukes itself after retrieval and save.

Don't get me started on the potential and the failure of CachedReferenceField.

• MongoEngine/mongoengine#1075 — Missing _get_db.
• MongoEngine/mongoengine#1047 — Creates DBRef, can't save.

I can't even find back the ticket where I requested access to cached data without triggering dereferencing. (Was closed as "wont fix" long ago.) The vast majority of the above are directly impactful and/or have actually been encountered at Illico, forcing us to pin to < 0.10. Given that our database servers will be updated to 3.2 in the near future, with new getMore semantics, we can't stay pinned forever.

So yeah, marrow.schema and marrow.mongo are somewhat more important things moving forward.

AttributeError: 'NoneType' object has no attribute 'timetuple'

The above exception is raised in getChildren on line 67 of web.extras.contentment.components.asset.core.