Many people have complained that users cannot access event finder options when viewing event nodes directly. To solve this event finder module should create a block and have it support viewing event finder info when viewing event nodes normally and through the event finder search interface.
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | ef_t.diff | 761 bytes | Zack Rosen |
| #11 | ef_t.diff.dif | 761 bytes | Zack Rosen |
| #10 | ef.diff.5 | 11.1 KB | Zack Rosen |
| #5 | ef.diff.4 | 8.94 KB | Zack Rosen |
| #4 | EventFinderOptionBlock.png | 51.57 KB | Zack Rosen |
Comments
Comment #1
Zack Rosen commentedHere is my first cut as a patch.
* moved event finder information out of the node body and into a block.
* made the block accessible when viewing event nodes normally and through event finder's interface
I also fixed a couple interface bugs
* made it 'volunteer module aware' - links to volunteer for the event show in the event finder info block when applicable
* added a link in event finder block to "Login to register for this event" when event finder registration is set to "one click" and the node is being viewed by an anonomous user.
Comment #2
Zack Rosen commentedOops. Forgot to remove the now deprecated ef_display_opts setting from event finder settings. Try this patch instead.
Comment #3
Zack Rosen commentedFixed bug that caused wrong registration link to show for users who were logged in and wanted to register.
Comment #4
Zack Rosen commentedFor those without patch-foo here is a screenshot
Comment #5
Zack Rosen commentedNow with correct .diff format and better link text standardization
Comment #6
Zack Rosen commentedoh yah...
Comment #7
leoklein commentedThis is a great addition. I always thought that the reformatting of Event Details in EventFinder -- reformatting from the normal Detail view -- is a usability issue.
My only thought, is that it's nice to have these options in a Block but is that how other modules achieve the same end? Consistency is this area just makes things a whole lot easier to manage.
Comment #8
Anonymous (not verified) commentedHey - How about patches that do not break current functionality?
I have eventfinder deployed on a ton of sites and have no plan on including eventfinder options in a block. In some cases, we are not even using blocks on the event pages.
M
Comment #9
Zack Rosen commentedpatachon: wrt consistancy - putting options in a block is how organic groups and CiviCRM handle this problem. It let's site designers have control over where the controls are positioned and what they look like.
techsoldaten: ok, i'll reroll the patch to make it a configuration option:
Show Event Finder Options
(*) In a block
( ) Above event content
( ) Below event content
Comment #10
Zack Rosen commentedHere is an updated version of the pack that makes the event finder options configurable to display above the node body, below the node body, or in a block.
Comment #11
Zack Rosen commentedComment #12
Zack Rosen commentedNeeded to create a new themable function for my patch. Here it is.
Comment #13
Zack Rosen commentedComment #14
Anonymous (not verified) commentedPatches applied.
Comment #15
(not verified) commented