Submit Venue allows authorised frontend users to create a new JEM venue or edit an existing venue when they have the required permissions. A venue is more than a name: it can include address data, country, coordinates, map visibility, image, description, custom fields, type classification, attachments and publishing information.
This documentation applies to JEM 4.5.x for Joomla 4/5 and JEM 5.0.x for Joomla 6. The feature set is intended to remain equivalent across both branches, adapted to the Joomla version used by the site.
When To Use This View
| Use case | Recommended setup | Expected result |
|---|
| Community venue submission |
Allow registered users to submit venues, but restrict publish permission. |
Users can propose venues while administrators keep editorial control. |
| Frontend venue management |
Allow trusted editors to add and edit venues from the frontend. |
Venue maintenance can be delegated without backend access. |
| Map-based event directory |
Require address, country, latitude and longitude where possible. |
Venues can be used reliably in maps, venue lists and event detail pages. |
| Venue catalogue |
Add images, description, website, type and attachments. |
The venue becomes a reusable content object, not only an event location. |
Access And Permissions
The Submit Venue form is permission-driven. It should only be visible to users who are allowed to create or edit venues.
| User condition | Behaviour |
|---|
| Guest user |
The form is not available. JEM returns an authorisation message. |
| User can add venues |
The user can create a new venue from the frontend. |
| User can edit own venues |
The user can edit venues they created, depending on access level and ownership. |
| User cannot publish venues |
The publication field is restricted and the venue may require administrator review. |
| User can publish venues |
The user can set the venue as published or unpublished, according to permissions. |
Menu Options
The Submit Venue menu item supports page intro and footer text. These texts are useful for explaining what data the user should provide before submitting a venue.
| Option | Default | Purpose |
|---|
| Show Introtext |
No |
Displays instructions above the venue form. |
| Introtext |
Empty |
Can explain required venue details, address quality, map usage or approval workflow. |
| Show Footer Text |
No |
Displays a note below the venue form. |
| Footer Text |
Empty |
Can include contact information, editorial policy or location submission guidance. |
Main Form Areas
| Area | Main fields | What it controls |
|---|
| Venue |
Venue name, alias, colour, website, street, postal code, city, county/state, country, description. |
The main identity and address information of the venue. |
| Geodata |
Latitude, longitude, map enabled, geolocation helper when map service is configured. |
Controls whether the venue can be shown accurately on maps. |
| Publishing |
Status, access level, created by, created date, modified date and version. |
Controls publication and visibility. |
| Image |
Venue image selection or upload. |
Adds a visual identity to the venue for lists, detail pages and timeline/card layouts. |
| Custom fields |
Venue custom fields 1 to 10. |
Allows site-specific venue metadata. |
| Attachments |
Venue-related downloadable files. |
Can be used for floor plans, accessibility information, brochures or technical sheets. |
| Metadata |
Meta description and meta keywords. |
Supports SEO metadata where the venue detail page is used publicly. |
Address And Coordinates
A venue can work with a normal postal address, GPS coordinates, or both. For map-based views, coordinates are the most reliable data. Address fields are still important because they help users understand the location and can be used by geocoding tools.
| Field | Recommended content | Why it matters |
|---|
| Venue |
The official or recognisable place name. |
Used in event details, venue lists, search results and map labels. |
| Street |
Street name and number where possible. |
Improves address precision and geocoding quality. |
| Post code |
The local postal code. |
Helps distinguish similar street names or cities. |
| City |
The city or locality. |
Used in venue lists, filters and visitor-facing address blocks. |
| County / State |
Administrative region, state, province or county. |
Useful where cities or postal codes are ambiguous. |
| Country |
The country selected from the JEM country list. |
Used by country filters, flags and map/location displays. |
| Latitude and Longitude |
Decimal GPS coordinates. |
Required for precise map markers. |
Map Behaviour
The map section depends on the global JEM map service configuration. When a supported map service is enabled, the frontend venue form can help users find or confirm address data and coordinates.
| Configuration | Behaviour | Recommendation |
|---|
| Map disabled globally |
The venue can still store address data, but map tools may not be shown. |
Use this for sites that do not display maps. |
| Map enabled and coordinates provided |
The venue can show an accurate marker. |
Best option for venue maps and event maps. |
| Address provided without coordinates |
The venue address is readable, but map precision may depend on geocoding. |
Add coordinates whenever the venue should appear on a map. |
| Coordinates provided without address |
The marker can be accurate, but the visitor-facing address may be incomplete. |
Use only when the venue is a natural location, temporary point or non-postal location. |
Venue Type
Venue types can classify venues independently from event categories. This is useful when the same venue may host events from many categories but still belongs to a venue class such as museum, theatre, club, classroom, outdoor location or online venue.
| Example type | Use case |
|---|
| Museum |
Used for galleries, museums and cultural institutions. |
| Club |
Used for nightlife, music venues or community clubs. |
| Conference room |
Used for talks, workshops and internal meetings. |
| Outdoor |
Used for parks, squares, routes or open-air places. |
| Online |
Used when the venue represents a virtual meeting space. |
Images And Attachments
A venue image helps users recognise the location in lists, detail pages and visual layouts. Attachments can provide additional practical information.
| Feature | Use it for | Notes |
|---|
| Venue image |
Exterior photo, logo, illustration or recognisable venue image. |
Image upload depends on global JEM image settings and file size limits. |
| Attachments |
PDF brochure, accessibility guide, seating plan, technical rider or directions. |
Frontend attachment uploads depend on global attachment settings and permissions. |
| Attachment layout |
Row or column display, icon size and frame behaviour. |
Can be inherited from global settings or adjusted per venue. |
Publication And Review Workflow
| Workflow | Permissions | Result |
|---|
| Moderated venue submissions |
User can add venues but cannot publish. |
The venue is submitted for administrator review. |
| Trusted frontend editors |
User can add, edit and publish venues. |
The venue can become public immediately. |
| Private/internal venue |
Access level restricted to selected Joomla groups. |
Only authorised users can view or use the venue. |
Recommended Configurations
| Scenario | Recommended venue data | Why |
|---|
| Museum venue |
Name, website, full address, country, GPS coordinates, image, type “Museum”. |
Works well for venue lists, maps, event timelines and cultural event demos. |
| Music club |
Name, city, country, image, venue type, map coordinates and website. |
Useful for event listings where the venue identity is part of the event appeal. |
| Temporary outdoor venue |
Clear name, coordinates, city, country and practical description. |
Coordinates are more important than street address for open-air or temporary locations. |
| Online venue |
Venue name, type “Online”, description and website if relevant. |
Useful when events are grouped by virtual meeting space or platform. |
| Frontend community submissions |
Intro text explaining required address data and publication review. |
Reduces incomplete venues and moderation time. |
Common Data Quality Rules
- Use the official venue name whenever possible.
- Include street number when the venue should be found on a map.
- Use consistent city and country names across venues.
- Add coordinates when venue maps or event maps are enabled.
- Do not use the venue name as a substitute for the address unless the place is uniquely identifiable.
- Use venue type for classification and categories for event organisation.
- Use images that identify the venue clearly, not generic decoration.
Related Project Notes
- #2131 relates to generating a complete JEM frontend menu, including venue submission entries.
- #2154 standardises intro and footer text options across JEM views.
- #2041 covers online events and online venue support in the JEM 4.5 development line.
- #2151 discusses country selector management and reducing long country lists in filters and forms.
- #1660 improves frontend attachment removal wording and behaviour.
Practical Example
| Field | Example value |
|---|
| Venue |
Museo del Prado |
| Type |
Museum |
| Street |
Calle de Ruiz de Alarcón 23 |
| Post code |
28014 |
| City |
Madrid |
| Country |
Spain |
| Latitude / Longitude |
40.4138, -3.6921 |
| Map |
Enabled |
| Description |
Historic museum venue used for talks, guided tours and cultural events. |
