fix (cleanup): simplifies “Create Event” page and remove unstable options

[taanvi2205]

Remove unstable component selection and ensure initial event data setup (closes #1154)

Summary

This PR removes the unstable component selection UI (Tickets, Talk, Video) from the “Create Event” page and ensures all three components are initialized automatically when a new event is created.

Changes

• Commented out “Create this event for” section in
  eventyay/eventyay_common/templates/eventyay_common/events/create_foundation.html
• Ensured backend event initialization logic (talk/src/pretalx/event/models/event.py) builds all default components on event creation.

Expected Behavior

• “Create this event for” section and related toggles are no longer visible.
• Event creation automatically sets up Tickets, Talk, and Video.
• No component-related warnings or errors occur.

Screenshots

Before:

After:

TODO (Future)

• Reintroduce component selection once unified component setup is stable.
• Re-enable event series after unified scheduling logic testing.

(closes #1154)

Summary by Sourcery

Remove the component-selection toggles from the event creation template and ensure all event components (Tickets, Talk, Video) are initialized by default during event setup.

Bug Fixes:

• Automatically initialize the Tickets component on event creation to prevent missing component errors.

Enhancements:

• Remove the unstable component-selection UI section from the Create Event page.
• Update build_initial_data to auto-create default ticket items alongside Talk and Video components.

[sourcery-ai]

Reviewer's Guide

Removes unstable component-selection UI from the “Create Event” page and enhances the build_initial_data method to automatically initialize the Tickets component alongside existing CfP, schedules, mail templates, review phases, and score categories.

Class diagram for updated Event initialization logic

classDiagram
    class Event {
        +build_initial_data()
        cfp
        schedules
        items
        score_categories
    }
    class CfP {
        event
        default_type
    }
    class Schedule {
        event
    }
    class ItemCategory {
        event
        name
    }
    class Item {
        event
        name
        default_price
        category
    }
    class ReviewScoreCategory {
        event
        name
    }
    class ReviewScore {
        category
        value
        label
    }
    Event --> CfP
    Event --> Schedule
    Event --> ItemCategory
    ItemCategory --> Item
    Event --> ReviewScoreCategory
    ReviewScoreCategory --> ReviewScore

Loading

File-Level Changes

Change	Details	Files
Removed unstable component-selection UI from the “Create Event” page	Commented out the “Create this event for” section and related toggles Retained only essential form fields (organizer, event type, locales) Inserted TODO comments for future reintroduction of selection logic	app/eventyay/eventyay_common/templates/eventyay_common/events/create_foundation.html
Enhanced backend event initialization to auto-setup Tickets component	Imported pretix.presale models for Item and ItemCategory Added logic to create a default Tickets category and Item when none exist Streamlined ReviewScore creation calls for score categories	talk/src/pretalx/event/models/event.py

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#1154	Remove the component selection options (Tickets, Talk, Video) from the 'Create Event' page UI and logic, and ensure all three components are created automatically when a new event is created.	✅
#1154	Comment out or hide the 'Event series or time slot booking' option in the UI and skip all related form inputs and backend calls, with a TODO for future reactivation.	✅
#1154	Ensure backend logic supports initializing all components (Tickets, Talk, Video) by default when an event is created.	✅

Possibly linked issues

• Cleanup: Simplify “Create Event” Page and Remove Unstable Options #1154: The PR removes the 'Create this event for' and 'Event series' UI sections and updates backend logic to automatically initialize Tickets, Talk, and Video components, as requested.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey there - I've reviewed your changes - here's some feedback:

• The create_foundation.html template is cluttered with large commented-out sections; consider removing dead code or wrapping it behind a feature flag for better maintainability.
• In build_initial_data, use get_or_create for ItemCategory and Item instead of always create to make initialization idempotent and avoid IntegrityErrors on reruns.
• Ensure the automatic ticket setup covers any additional Pretix requirements (like quotas or tax rules) so no essential configurations are missing post-creation.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The create_foundation.html template is cluttered with large commented-out sections; consider removing dead code or wrapping it behind a feature flag for better maintainability.
- In build_initial_data, use get_or_create for ItemCategory and Item instead of always create to make initialization idempotent and avoid IntegrityErrors on reruns.
- Ensure the automatic ticket setup covers any additional Pretix requirements (like quotas or tax rules) so no essential configurations are missing post-creation.

## Individual Comments

### Comment 1
<location> `talk/src/pretalx/event/models/event.py:647-657` </location>
<code_context>

+        # --- New Section: Initialize Tickets system automatically ---
+        from pretix.presale.models import Item, ItemCategory  # adjust import if needed
+        if not self.items.exists():
+            category = ItemCategory.objects.create(event=self, name=_("Tickets"))
+            Item.objects.create(
</code_context>

<issue_to_address>
**suggestion (bug_risk):** Check for existing ticket categories/items with more granularity.

Currently, the check does not differentiate between ticket and non-ticket items, which may result in duplicate ticket categories. Please update the logic to specifically check for an existing 'Tickets' category or 'General Admission' item.

```suggestion
        # --- New Section: Initialize Tickets system automatically ---
        from pretix.presale.models import Item, ItemCategory  # adjust import if needed

        # Check for existing 'Tickets' category
        tickets_category = ItemCategory.objects.filter(event=self, name=_("Tickets")).first()
        if not tickets_category:
            tickets_category = ItemCategory.objects.create(event=self, name=_("Tickets"))

        # Check for existing 'General Admission' item in the 'Tickets' category
        general_admission_item = Item.objects.filter(
            event=self,
            name=_("General Admission"),
            category=tickets_category
        ).first()

        if not general_admission_item:
            Item.objects.create(
                event=self,
                name=_("General Admission"),
                default_price=0,
                category=tickets_category,
            )
        # ------------------------------------------------------------
```
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

suggestion (bug_risk): Check for existing ticket categories/items with more granularity.

Currently, the check does not differentiate between ticket and non-ticket items, which may result in duplicate ticket categories. Please update the logic to specifically check for an existing 'Tickets' category or 'General Admission' item.

Suggested change

	# --- New Section: Initialize Tickets system automatically ---
	from pretix.presale.models import Item, ItemCategory # adjust import if needed
	if not self.items.exists():
	category = ItemCategory.objects.create(event=self, name=_("Tickets"))
	Item.objects.create(
	event=self,
	name=_("General Admission"),
	default_price=0,
	category=category,
	)
	# ------------------------------------------------------------
	# --- New Section: Initialize Tickets system automatically ---
	from pretix.presale.models import Item, ItemCategory # adjust import if needed
	# Check for existing 'Tickets' category
	tickets_category = ItemCategory.objects.filter(event=self, name=_("Tickets")).first()
	if not tickets_category:
	tickets_category = ItemCategory.objects.create(event=self, name=_("Tickets"))
	# Check for existing 'General Admission' item in the 'Tickets' category
	general_admission_item = Item.objects.filter(
	event=self,
	name=_("General Admission"),
	category=tickets_category
	).first()
	if not general_admission_item:
	Item.objects.create(
	event=self,
	name=_("General Admission"),
	default_price=0,
	category=tickets_category,
	)
	# ------------------------------------------------------------

[hongquan]

Please use a descriptive title for the PR.
Reading "fix:closes #1154", people don't understand what this PR does.

[mariobehling]

Please address AI reviews. Thank you