BuddyPress.org

Not sure about how EventPress works with MU as I’ve never tested—but anyone author and above should be able to create events. There’s also a special role called ‘event_creator’ who just has event creation capabilities and nothing else.

Hi I’ve actually never used—or run into anyone using—Custom Press and EventPress. As for xProfiles, EP as such doesn’t interfere with any of those. I can only comment based on past bug reports and yours is the first one of this kind—and the only way that I can think of for EP to cause a […]

Ok—EventPress creates events under a post type ep_event and registrations under post type ep_reg; just in case that proves useful.

Hey—not expected behavior at all. Could another plugin/theme be causing this somehow? Anything you’ve changed recently?

@Imjscn Using CSS to hide content is not exactly a safe thing—all someone needs to do to see the hidden content is just do a view-source on the page, or use firebug to modify the css for that page and show all hidden content. You can also permanently save stylesheets for specific sites that over-ride the […]

You could try using BuddyPress Custom Posts and modify it to what you need. That’s what EP uses, and it basically attempts to minimally replicate the dashboard for custom post types. (http://code.google.com/p/buddypress-custom-posts/)

Have a look at how capabilities are granted in models/events.php—you can grant the required caps to subscribers too. Or, there’s an event_creator role that’s just meant for this—in the wordpress admin area, you could make the default user role Event Creator, and also bulk modify the existing user capabilities to event_creator.

The .dev.css is there because I’d started automating minimizing the .css and .js files using Phing/YUICompressor. While my code (switching between .dev.css and .css and .dev.js and .js was working by the time I pushed the current version of EP, I wasn’t completely sure that I had missed a file or two—hence the current version […]

The over-ride works only for the php files, not the CSS files, actually. To remove the css file in an upgrade-proof way, dequeue events.dev.css: http://justintadlock.com/archives/2009/08/06/how-to-disable-scripts-and-styles. Or you might just want to add the css with an !important added to child theme’s style css, for example .ep-event-details {…[Read more]

@4ella http://localhost/eventpress/members/kunalb/events/ and http://localhost/eventpress/members/kunalb/events/my-events/ will reach the same page; as in the default child page of /events/ in profiles is /my-events/ — so it shouldn’t be a problem as far as I know. Event Category (essentially, taxonomy) support is planned for the next release of B…[Read more]

Change the file buddypress-custom-posts/themes/type/index.php—just remove the call to the bpcp_search_box.

Hi—unfortunately search isn’t implemented yet¸ and when I was working on the plugin I forgot to disable/remove the search box.

@KendrickSnyder Hi—I can’t replicate the featured image issue. Are you clicking “Set as featured image” after uploading the image? The CSS for the create new event page is mainly in the Buddypress Custom Posts plugin—you can have a look at BPCP/themes/type/assets/css/edit.dev.css — I’d suggest dequeueing this file and enqueueing your own CSS file…[Read more]