The Interface for creating events is too complex

RESOLVED INVALID

Status

P1
normal
RESOLVED INVALID
10 years ago
8 years ago

People

(Reporter: Usul, Assigned: paul)

Tracking

Details

(Whiteboard: [plzfixme1.2])

Attachments

(1 attachment)

(Reporter)

Description

10 years ago
There are too many fields to fill in.

What I want from such a service is :
 * a field where I can describe the event.
 * A link to contact me. 
 * A good way to export the calendar to my local applications (ical/sundbird). 

The rest should be optionall as I can enter urls in the Events description.

The current Event creation would be usable if I could clone events and change a few fields while cloning.
Marcia, tony, clint: what do you think (see comment #0). We should change some field to optional instead of requirement ?
Priority: -- → P3
Everything in Drupal is too complex! :D
I vote yes for Tomcat's proposal.
I dunno, we should expand a bit on this more as there's a couple of functions needed:


- Title, Date and Time
- Summary 
- Forum thread location should always be defaulted to the Events forum instead of being a required selectable drop down list 


Also, we don't need event details sections, more tips section(s), tool box and do more fields as that should be done in the summary. On top of that, does anyone use the log field field at the bottom?
Okay, cool, so make a list of stuff you'd like removed and I'll go ahead and do that once it's decided.
Assignee: nobody → paul.craciunoiu
Target Milestone: --- → 1.1
(Reporter)

Comment 5

9 years ago
(In reply to comment #3)
> anyone use the log field field at the bottom?
 I would use it if I would edit events - which I usually don't do. IT can safely go away.
So in summary, what stays and what goes?
*bump*
The simplest solution is to require less fields to be filled in.
Ok, here's my list of what should/should not be in the events form. Tomcat, I need your approval on this, so we can push it for the 1.1 milestone.

Fields required for events:

- Title, Date, Summary, Forums, Event details, 

Fields that should stay, but are not required:
- How to Get Started, Getting Started E-mail, 

Fields need to be removed:

- Stay Connected and Do More (redundant since How to Get Started can do the same), More Tips & More Tips Items (haven't seen anyone ever use it), Tool Box and Tool Box Items (haven't seen anyone ever use it), Do More and Do More Links (haven't seen anyone ever use it).
Let me know when this is finalized.
(In reply to comment #8)
> Ok, here's my list of what should/should not be in the events form. Tomcat, I
> need your approval on this, so we can push it for the 1.1 milestone.
> 
yeah thats fine for me !
Think you can take this on Aakash? You can decide it by going to Manage Fields for the Events content type. Try it on stage?
I made the changes on staging and got the following errors:


    * warning: Invalid argument supplied for foreach() in /data/www/quality.mozilla.org/sites/all/themes/qmo/template.php on line 441.
    * warning: Invalid argument supplied for foreach() in /data/www/quality.mozilla.org/sites/all/themes/qmo/template.php on line 441.
    * warning: Invalid argument supplied for foreach() in /data/www/quality.mozilla.org/sites/all/themes/qmo/node-event.tpl.php on line 160.


It's hardcoded into the template apparently.
Status: NEW → ASSIGNED
Do you think you can get this done, Paul? It seems like all that needs to be done is some code removal
Target Milestone: 1.1 → 1.2
Priority: P3 → P1
(Assignee)

Updated

9 years ago
Assignee: paulc → mozilla
(Assignee)

Comment 14

9 years ago
Created attachment 406692 [details] [diff] [review]
Code fix.
Attachment #406692 - Flags: review?
(Assignee)

Comment 15

9 years ago
With the following patch the required changes to the cck event fields can be made without no errors being reported on form submission

Best, 
Paul Booker
Could someone please link to an example of this form?  I don't know what to look at
Attachment #406692 - Flags: review? → review?(buchanae)
Alex, here's a link to the event creation form: http://quality.mozilla.org/node/add/event
Comment on attachment 406692 [details] [diff] [review]
Code fix.

The patch didn't apply correctly.

patching file sites/all/themes/qmo/template.php
patching file sites/all/themes/qmo/node-event.tpl.php
Hunk #1 FAILED at 157.
1 out of 1 hunk FAILED -- saving rejects to file sites/all/themes/qmo/node-event.tpl.php.rej

Other than that, the fix seems OK.
Attachment #406692 - Flags: review?(buchanae) → review-
(Reporter)

Comment 19

9 years ago
(In reply to comment #16)
> Could someone please link to an example of this form?  I don't know what to
> look at

And if you want to see a simple one have a look at upcoming.yahoo.com - event creation there is quite simple.
Whiteboard: [plzfixme1.2]
This bug is being moved to a resolved state of invalid due to one of the following reasons:

- we're moving to wordpress and so all drupal cruft is not going to be fixed
- the feature is not supported on the new qmo, at least for this release.
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INVALID
This bug is being moved to a resolved state of invalid due to one of the following reasons:

- we're moving to wordpress and so all drupal cruft is not going to be fixed
- the feature is not supported on the new qmo, at least for this release.
Target Milestone: 2.2 → ---
You need to log in before you can comment on or make changes to this bug.