collective / collective.venue

Dexterity venue type for use with events.

collective.venue

This package provides an Dexterity Venue type with geolocation support for use with events or any other location specific content.

Geolocation

If you want to use collective.venue with geolocation behavior, you should add the following line to your eggs buildout section:

eggs =
    collective.venue [geolocation]

collective.venue's Issues

geopy dependency

since geopy is only in extra_require:geolocation but imported unconditionally here https://github.com/collective/collective.venue/blob/master/collective/venue/browser/locationsearch.py#L5 my instance doesn't start up without providing [geolocation] to the dependecies ... either move the import into the try/except block of get_location_info or move the geopy dependency to install_requires

map with multiple venues

I'm trying to use collective.venue to show multiple venues on a map.
My idea was to create a collection with venues and select a template which places a viewlet above (or below ... configurable?) the contentbody with a map showing all marks of the venues. This would be even nicer in combination with collective.collectionfilter which would enable filtering the venue marks on the map ...

This is quite similar to collective.geo.locationmap (which I used here long time ago: http://www.wohin-heute.at/freizeitbetriebe ) but this doesn't work in Plone 5 anymore and I don't want to mess around with the heavyweight collective.geo.* addons ...

@thet maybe you can give me a pointer, how to achive this in leafletjs with pat-leaflet?

Error in Event Venue Settings

Traceback (innermost last):
Module ZPublisher.WSGIPublisher, line 162, in transaction_pubevents
Module ZPublisher.WSGIPublisher, line 359, in publish_module
Module ZPublisher.WSGIPublisher, line 262, in publish
Module ZPublisher.mapply, line 85, in mapply
Module ZPublisher.WSGIPublisher, line 63, in call_object
Module plone.z3cform.layout, line 63, in call
Module plone.z3cform.layout, line 47, in update
Module plone.z3cform.fieldsets.extensible, line 65, in update
Module plone.z3cform.patch, line 30, in GroupForm_update
Module z3c.form.group, line 145, in update
Module plone.app.z3cform.csrf, line 22, in execute
Module z3c.form.action, line 98, in execute
Module z3c.form.button, line 315, in call
Module z3c.form.button, line 170, in call
Module plone.app.registry.browser.controlpanel, line 63, in handleSave
Module z3c.form.group, line 114, in applyChanges
Module z3c.form.form, line 51, in applyChanges
Module z3c.form.datamanager, line 91, in set
Module plone.registry.recordsproxy, line 60, in setattr
Module plone.registry.registry, line 51, in setitem
Module plone.registry.record, line 82, in _set_value
Module zope.schema._bootstrapfields, line 292, in validate
Module zope.schema._field, line 483, in _validate
zope.schema._bootstrapinterfaces.ConstraintNotSatisfied: ('08f36b607c914d8581e4fbe11cdb352d', 'value')

What about setting z3c.unconfigure <= 1.1 as a requirement?

Hi @thet,
What do you think on changing the requirement of collective.venue from
z3c.unconfigure < 1.1
to
z3c.unconfigure <= 1.1 ?

I ask this because from the version 5.1 and greater of Plone (in http://dist.plone.org) there's z3c.unconfigure pinned to version 1.1.

See here:
http://dist.plone.org/release/5.1/versions.cfg
http://dist.plone.org/release/5.1.1/versions.cfg
http://dist.plone.org/release/5.1rc2/versions.cfg

Whith <= it could be used with both buildout.coredev and the release of Plone >= 5.1.

Traceback if I call /@@venue-controlpanel

I encountered a traceback after I installed Venue [geolocation] and tried to call /@@venue-controlpanel.

Versions:
Plone = 5.0.6rc1
Plone Patternslib = 1.0
collective.geolocationbehavior = 1.5.1
collective.venue base profile = 3.1.1

Traceback:
`
Es ist leider ein Fehler aufgetreten…

Dies ist die vollständige Fehlermeldung:

Zeige Fehlerbericht als Text

Traceback (innermost last):

Module ZPublisher.Publish, line 138, in publish
Module ZPublisher.mapply, line 77, in mapply
Module ZPublisher.Publish, line 48, in call_object
Module plone.z3cform.layout, line 66, in __call__
Module plone.z3cform.layout, line 60, in update
Module z3c.form.form, line 162, in render
Module zope.browserpage.viewpagetemplatefile, line 51, in __call__
Module zope.pagetemplate.pagetemplate, line 132, in pt_render
Module five.pt.engine, line 98, in __call__
Module z3c.pt.pagetemplate, line 163, in render
Module chameleon.zpt.template, line 261, in render
Module chameleon.template, line 171, in render
Module 2e226ec8d5a364c7bb94a9af6df7cf43.py, line 91, in render
Module 52f963cda721cddd1087a721b7303fc4.py, line 1806, in render_titlelessform
Module 52f963cda721cddd1087a721b7303fc4.py, line 451, in render_fields
Module 52f963cda721cddd1087a721b7303fc4.py, line 126, in render_widget_rendering
Module 52f963cda721cddd1087a721b7303fc4.py, line 1069, in render_field
Module five.pt.expressions, line 161, in __call__
Module Products.Five.browser.metaconfigure, line 485, in __call__
Module zope.browserpage.viewpagetemplatefile, line 83, in __call__
Module zope.browserpage.viewpagetemplatefile, line 51, in __call__
Module zope.pagetemplate.pagetemplate, line 132, in pt_render
Module five.pt.engine, line 98, in __call__
Module z3c.pt.pagetemplate, line 163, in render
Module chameleon.zpt.template, line 261, in render
Module chameleon.template, line 191, in render
Module chameleon.template, line 171, in render
Module b29bad6a2df27580e36641c2d93515e6.py, line 591, in render
Module b29bad6a2df27580e36641c2d93515e6.py, line 466, in render_widget_wrapper
Module five.pt.expressions, line 161, in __call__
Module plone.app.z3cform.widget, line 90, in render
Module plone.app.widgets.base, line 111, in render
Module plone.app.widgets.base, line 102, in update
Module json, line 244, in dumps
Module json.encoder, line 207, in encode
Module json.encoder, line 270, in iterencode
Module json.encoder, line 184, in default

TypeError: <function get_site at 0x7f1b8113c050> is not JSON serializable

• Expression: "widget/@@ploneform-render-widget"
• Filename: ... rm-1.2.1-py2.7.egg/plone/app/z3cform/templates/macros.pt
• Location: (line 98: col 81)
• Source: ... place="structure widget/@@ploneform-render-widget"/>
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
• Expression: "widget/render"
• Filename: ... rm-1.2.1-py2.7.egg/plone/app/z3cform/templates/widget.pt
• Location: (line 38: col 46)
• Source: ... xt" tal:replace="structure widget/render"
  ^^^^^^^^^^^^^
• Arguments: repeat: {...} (0)
  context: <RelatedItemsWidget search_base at 0x7f1b7ad57210>
  views: <ViewMapper - at 0x7f1b7b27d810>
  modules: <TraversableModuleImporter - at 0x7f1b8da4e6d0>
  args: <tuple - at 0x7f1b98153050>
  nothing: <NoneType - at 0x7883f0>
  target_language: <NoneType - at 0x7883f0>
  default: <object - at 0x7f1b98129c20>
  request: <instance - at 0x7f1b812673f8>
  wrapped_repeat: {...} (0)
  loop: {...} (0)
  template: <ViewPageTemplateFile - at 0x7f1b7af41710>
  translate: <function translate at 0x7f1b7b46a398>
  options: {...} (0)
  view: <RenderWidget ploneform-render-widget at 0x7f1b7b27d390>
  `

Bundle. Structure, Compilation

Hi
I'm preparing a bundle for an add-on. I took this add-on as an orientation how to do this.
May I ask how you got the compiled files. Is a gruntfile used for this? What is the prefered way to generate the compiled files?
Thank you for any hint, Katja

Override of standard event accessor also when product is not installed

I added this product in a buildout with several websites.
I need to install this product only on one website.

The problem is that in the other websites, standard events use collective.venue eventaccessor adapter instead the default one, because there is an unconfigure directive.
This cause some problems in some views (for example event_summary) where they try to access the location accessor, and it returns None also when the field is correctly set.

Is there a different way to override the accessor? Maybe only when the product is installed or better when the event has the behavior enabled? Maybe registering the accessor for behavior's interface?