BuddyPress.org

1. Capabilities are also added to the existing roles like author, etc. Subscribers aren’t given event creation capabilities as that seemed to be against the definition of ‘subscriber’ — in case you wanted to open event creation to any user then you could make Event Creator the default role which will only allow event creation and not…[Read more]

Not at the moment. I guess I’ll make map iteration a part of 0.1.4 — right now focusing on calendar based functionality in 0.1.3.

Hi — replied to the issue on the google code site — but are the “other errors” EP related? What exactly is happening?

there should be a /lang folder in EventPress.

Added that to the list of open issues. I’ll have to check out the plugin — off hand I’d say that the loop created for the widget is not reset and causes the page loop to display that text too.

Strange — cause the issue is definitely with js. WIll have to investigate further.

So I was mimicking the wp-admin behaviour on this, reverting to the simple html tags version when the rich text editor is disabled. I’m directly using the_editor tag provided in wp-admin to render that text field.

@ekine Hmm … I haven’t actually faced this issue — will have to check this out. Does the firefox console show any javascript errors with this? And the rte settings are inherited based on user capabilities; so if you do disable the rte in wp-admin for users, it should get disabled on the front end too.

hmm … event widgets definitely need an upgrade. The calendar/time based widgets will be upgraded by 0.1.3, will check out how much work it takes me to modify this and accordingly fix the rest of the widgets.

0.1.3 should be around by 20th October or so.

@Troy EventPress at a minimum requires WordPress 3.0 — the whole functionality and UI is built around Custom Post Types introduced in WP 3.

Hey — I had moved the file to buddypress-custom-posts.php; so WP won’t be able to reactivate automatically; you just need to activate the plugin once from the plugins page and that should solve any issues.

@Pisanojm Not exactly sure what you mean — but in 0.1.3 I’m planning to add “Add event” buttons to a rather improved calendar view page to be able to quickly create events — can you give me an example site to see what you mean?

hmm, are you logged in with the right capabilities? Worst case, try deactivating and reactivating the plugin.

Great!

hey …. hadn’t seen your posts. Can you give me some more details? Updating the permalink structure/deactivating and activating the plugin should be good enough.

@gus-f2c Hi — can you give me a few details about what is happening? As such it shouldn’t be messing with widget areas at all; only adding a few more widgets which you can enable/disable.

– Uploading an event avatar should have the same workflow like uploading a profile avatar. It just breaks the frontend consistency and users hate to learn more ways doing similar stuff.
I’ve received a lot of requests (ie 3) for this — so I’ll try to see what I can do for the next version after 0.1.3… it will take some time though (specially…[Read more]

A quick fix should be to copy ep_details.php from eventpress/themes/bp/ to your theme folder and changing the arguments in the call to ep_map to the dimensions you’d prefer. This will effectively over-ride the default event_details.php.

Replying separately so that I don’t feel so boxed in ;). So uninstalling/reinstalling the plugin will (*should*) not touch your events or registration in any way. I would still recommend a backup to avoid any untoward incidents happening; but there’s no code in there to delete events.

Essentially, what should be happening is that you get a “set as thumbnail link” — the uploader is the same as that in the backend. Could you try re-installing the plugins?

Also, it might be something to do with roles — what user role are you logging in from?

Strange. I can’t actually replicate this on my test BP install with the 0.1.2.1 versions installed. This was a bug in 0.1, but I had assumed that this was resolved.

Is anyone else facing the same problem?