[@mariusooms Participant 17 years, 2 months ago]

Hi everybody, we are now up to version 1.1.6. I know we went through a lot of little updates in the last week, but I think finally it should settle now as all the features we wanted are incorporated and everything seems to run smooth. If you find some bugs we forgot to squash, let me know.

Also, feature request or good ideas are always welcome, but don’t expect it to make popcorn.

PS. Browny points for those who can find the hidden easter egg that references a popular (best ever made) tv-series!

[@mariusooms Participant 17 years, 2 months ago]

Yes, everything behaves like it normally would.

[@mariusooms Participant 17 years, 2 months ago]

Okay, things should be better now. Pending what jjj will add, I fixed the issue with tagline and location as well as cleaned up references in regards to avatar_thumb and avatar_full.

Please test and report back. Thank you for you patience and sorry for the inconvenience.

http://svn.ywamnetworks.com/bp-events/trunk/

If you have a svn client you can track changes easier.

[@mariusooms Participant 17 years, 2 months ago]

Hang on epixalex, it looks like the fault is at my end as I’ve juggled a few things around since my last copy and created a few misbehaves. Let me sort those out first as we continue.

[@mariusooms Participant 17 years, 2 months ago]

Sorry, that field is a remnant. avatar_thumb is deprecated in core so also for bp-events. Just remove the references as they don’t do anything. I must have forgotten some as I updated from core code. That’s working with trunk, it changes daily.

[@mariusooms Participant 17 years, 2 months ago]

epicalex at line 15:

define ( 'BP_EVENTS_DB_VERSION', '1700' );

So, disable the plugin, up the number and re-enable the plugin. Create an event and you should have tables.

[@mariusooms Participant 17 years, 2 months ago]

so I dropped all the event tables and deleted all the plugin files

This will not work because every plugin sets a table version number, so you would have to up the number in the plugin. It is in the first few lines of bp-events.php. Also, possibly tables will get created when you actually create an event, not on install.

So has the original developer abandoned bp-events?

No, but he is still very busy getting a stable version out for the bp1.0.3 branch. With BP1.1 around the corner there is a huge need for many site owners to have an events plugin that supports bp1.1. I can’t afford to wait, so I’m picking up the torch for now and John James Jacoby has offered to help.

This is the beauty of open source, nobody has to sit on side lines and watch the development. Jump in and get your hands dirty.

[@mariusooms Participant 17 years, 2 months ago]

Thanks conceptfusion and major props to John James Jacoby for helping out.

[@mariusooms Participant 17 years, 2 months ago]

No problem

[@mariusooms Participant 17 years, 2 months ago]

At that point, they are just members of blogs, so yes, they have access to the dashboard with options according to their blog role. Asfaik, P2 is not meant to be the only post option as it meant for quick posting and only text. So it would greatly limit things by having that as the only post option.

For your situation I would not use the groupblog plugin, but stay with either wire or discussion forum. Also, to answer your other question, bp-groupblog does not work wihtout buddypress.

[@mariusooms Participant 17 years, 2 months ago]

– is it possible with BP to disable the “Wire” ?

Yes…this can be disabled per group at the group creators discretion.

– is it possible to use P2-theme in your “Group-blog” ?

I don’t know, I have not use the P2 theme yet, but I imagine it should be no problem.

– are there any language-related wording in your plugin (at the user-interface) which need to be translated when I would like to run your plugin for a german-language-website ?

Yes, a language file is included which you may translate using the wordpress guidelines.

[@mariusooms Participant 17 years, 2 months ago]

Also…when you find issues, please open a new new forum topic, so it stays manageable for everybody

[@mariusooms Participant 17 years, 2 months ago]

– I would like to disable User-Blogs for each single user, but instead have a Group-Blog using P2-theme. Does this work with your plugin ?

Yes, this one of the nice features. You can have blog creation disabled for users, but groups can still create blogs.

– Is your plugin compatible with BP-version 1.1 ?

Yes, it was build on bp1.1 architecture.

– what is the difference from your Group-Blog-plugin compared with the one from Burt ?

I admit, I am not super familiar with Burts plugin, but I believe Burts plugin is focussed on a single blog with defined (by the site admin) groups to able to post in to.

The groupblog plugin has a single blog for each single group. So the blog is unique to the group. Also, I don’t know if Burt will adopt his plugin to bp1.1, you could ask him.

[@mariusooms Participant 17 years, 2 months ago]

Each group can have only one blog attached to it, much like each group has a forum and a wire. Since it is an extension of the group, each member is added to the blog automatically with a predefined role cap. Just like each member can participate in forums.

Each component has a different role and it is up to you which you would like to have enable or disabled. Per definition:

– The wire acts like quick comments for the group, text only.

– Forums allow deeper discussions related to the group and are not as linear as the wire.

– Blogs have even greater functionality as you can have categories and tags, also, you have more post options such as photos and videos. Blogs have all WP plugins available to them, so your options for the group are endless.

Since you can build wp post loops in the group page there is a lot you could do with it. It is up to your imagination. If something would be obsolete, it would be the wire, as forum discussions supersede those.

The group creator has option to enable all, disable all, or any possible configuration. Each component will not show up when disabled as not to create confusion.

I hope that helps and thanks for your interest.

[@mariusooms Participant 17 years, 2 months ago]

No trac, but you can just send patches or code through my profile or irc. The svn at the moment is temporary until Erwin takes over again. I should note, that while testing is really appreciated and that you for sure can use the plugin as is, there is no guarantee that Erwin will actually use this code base and he could take a different direction all together. Just to disclaim on my part So, also new features will not be implemented as the base code first needs to be accepted.

That being said. On what url or you missing icons? I might have completely overlooked it. I have gone through a LOT of code, so it easy to miss something. I’ll fix the translation as well. Thanks…

I just set up a new event, and the issue with the location still exists

This could be because you have upgraded? On a clean install I am pretty sure this is not the case, but I will verify later today.

[@mariusooms Participant 17 years, 2 months ago]

OK, well I had a few problems to start with, mainly due to remnants from the previous plugin version’s structure.

The main purpose was actually moving forward as I had no way of testing backwards compatibility. Therefore please don’t expect to much out of old events, rather focus on creating new ones.

Another thing to note is that I tried putting the events directory in the framework directory rather than the default theme directory, and that caused things not to work. I think it would be better, and in line with groups and member directories, if events could be added to the framework, not just the theme.

Actually when dealing with parent and child themes, it is best to leave the framework alone imo. Since than you don’t lose any information when updating the frame work. I think this is common with parent/child themes. Evens so, it should just work in the framework folder as well. What exact errors were you having in regards to this.

When I look at an event that was already created prior to installing this version, I see the location as it should be, however, when going to the front end admin screens, the location is set to the tagline. Updating the location instead adds the new location to the recent news, and leaves the location unchanged IN THE FRONT END ADMIN SCREENS.

Again, this is probably due to incompatibility with the previous version. Namely the website field has been left out, which is likely to shift everything around. I’m not sure.

There are no icons for the event menu list.

Hmmm, they work fine on my install. Please check where the path is pointing to for the image that is missing.

Event invite isn’t working, but I don’t think it is for groups either.

Yeah…did not get around testing this, but should behave the same way as groups as the architecture is identical.

The ajax loading icon has gone from the widget; although the ajax change in newest etc still works, without the loading icon it isn’t necessarily clear that anything is happening.

Ajax functionality is lacking yes.

Also for the widget, can we have event details back in?

I actually did not change the widgets. I would have to check this out.

Going to domain.com/events doesn’t bring anything up; I’m assuming that this will be where the calendars will be put back in?

The directory still needs to be ported. You could theme your own.

This is definitely a step in the right direction. Things seem cleaner. But some of those features really need building back in once this base is established.

It is essential that the base is solid imo. Before the plugin was so much and much of it did not work. I think it could also be versioned better, but that is really up to the author. At this point my aim was to help jump start this plugin. Code and patches are welcome if you would like to help.

[@mariusooms Participant 17 years, 2 months ago]

The new feature to select an existing blog is now available. We also fixed some other bugs.

There is only one (known) bug left, which we will squash on Monday. Namely member roles are not set upon creation, but they are set when saving the 2nd time around form the admin as explained in the readme.

https://wordpress.org/extend/plugins/bp-groupblog/

[@mariusooms Participant 17 years, 2 months ago]

You can get the trunk version here:

http://svn.ywamnetworks.com/bp-events/trunk/

[@mariusooms Participant 17 years, 2 months ago]

We are actually trying to make the commit this feature now, but are having svn issues.

On a note though…this feature to select an existing blog can only be done once. When a group has a blog associated with it can not be changed.

This decision was due to the fact that many weird things can happen when a blog gets dissociated. In the near future we are adding a site admin option to dissociate group blogs upon request by the group admin. In turn the group admin can choose a new existing blog.

[@mariusooms Participant 17 years, 2 months ago]

Uhmm…while I do agree there should be an option to do so, your argument did made me chuckle as I don’t think a terror cell would need your network. Especially considering that you can download wordpress and buddypress free of charge.

[@mariusooms Participant 17 years, 2 months ago]

Yes…it was developed since the group api came into existence after bp 1.0.3. Currently it is still undergoing changes as trunk is changing rapidly. We are also adjusting theme structure to match the current parent/child structure.

However it should already work, along some minor bugs, with the current trunk.

An official 1.1 release of the plugin will come out at bp 1.1’s release.

[@mariusooms Participant 17 years, 2 months ago]

This plugin is not compatible with BP 1.0.3 and will not be. Please wait for BP 1.1 or use trunk at your own risk.

[@mariusooms Participant 17 years, 2 months ago]

* Deactivate plugin

* Rename ‘buddypress-group-blog’ to ‘bp-groupblog’

* Make sure the ‘groupblog’ folder is moved to your active member theme as explained in the readme.

P.s. The plugin accidentally was added to the wp repository under the wrong name. It is currently being rectified so that the path will actually be correct in regards to the plugin name, namely bp-groupblog.

[@mariusooms Participant 17 years, 2 months ago]

BP1.1 will be released in September pending development speed. I’m inclined to agree with Mike Pratt. Especially if you have a deadline that close, your solution seems very elaborate even trying to use the fullname function from BP. There is no guarantee the first and last name are existing in the username, so you can’t back on that info to be in usermeta. The only way to guarantee accurate first and last name info is to have those in user registration as a mandatory field.

Bypassing the username and using email as a login option further removes you from even having remotely any user information other than the email address.

Sorry to sound a little discouraging, but I’m scratching my head as to how you are trying to achieve this? Perhaps a combination with the email plugin and two required fields for first and last name is your best option, imho.

That way you do need another plugin that needs development after you release your project and stays inline with bp updates and what not.

[@mariusooms Participant 17 years, 2 months ago]

Hi Peterverkooijen, sorry you are struggling with this for a long time now. I’m not sure if you absolutely need this for bp1.0.3, but if you study the registration process of the upcoming bp, you’ll see it is much easier to manipulate registration data at a theme level.

It might be best worth your time to study the new code and wait a bit longer. Or work with trunk if you are developing.