[Sven Lehnert]

Hi @imath and @danbp,

thanks for the fast replay. You are right. I have tested again on a fresh install and it works.

I will dig into it and check why it dosen’t work on my other dev install.

Many thanks 😉

[Sven Lehnert]

I have also created a plugin for this purpose if you need more complex forms check out BuddyForms. https://wordpress.org/plugins/buddyforms-members/

There is also a demo available http://buddyforms.com/

Feedback is welcome 😉

Cheers,
Sven

[Sven Lehnert]

I have just created a short video to show BuddyForms in action:

http://youtu.be/n0yv0n_e91o

[Sven Lehnert]

Hi,

thanks @mercime for letting me know.

@ahri2012 thanks a lot for your feedback, I have just created a ticket in github with your issue, one of our developers will look into this soon and come back to you.

Here is the link: https://github.com/Themekraft/Custom-Community/issues/18

If you already have a bugfix, you are welcome to contrebute. Github is the right place.

If you have further technical questions, please use our support system and write us a ticket here: http://support.themekraft.com/anonymous_requests/new

[Sven Lehnert]

I already asked the user for access

[Sven Lehnert]

@miguelcortereal, Thanks for the feedback, SeoPress update is in work.

@djpaul Some user report this issue:

Fatal error: Cannot access empty property in …/wp-content/plugins/buddypress/bp-core/bp-core-template.php on line 787

and after update to 1.6.1 the error moved to line 823:

Fatal error: Cannot access empty property in …/wp-content/plugins/buddypress/bp-core/bp-core-template.php on line 823

I’m not sure if this is a theme bug or BuddyPress related.

[Sven Lehnert]

Hi @all, we testet the issues and could not reproduce them. The theme works just fine with a child theme as well. We can’t guarantee it works with modified child themes, as we don’t know what are the changes.

Do you use a child theme? If so, please check if the issue still exists if you switch to the parent theme.

Also, please make sure you have all other plugins disabled (except BuddyPress), to make sure this error does not arise from a plugin conflict.

[Sven Lehnert]

Hello everyone,

Sorry for your discomfort.
We missed it to test the theme properly enough against BP 1.6 and feel sorry for it.

We are now working with 2 devs on a new version to support 1.6 and fix some overdated issues.

New version will be available around next week.

I will post it here in the forum when the new version is released.

Thanks to Paul Gibbs for pointing us on this.

[Sven Lehnert]

add it in your function.php

function remove_group_home_nav() {
bp_core_remove_nav_item( bp_get_current_group_slug(), ‘home’ );
}
add_action( ‘bp_setup_nav’, ‘remove_group_home_nav’ );

[Sven Lehnert]

@linick, check out seopress: https://buddypress.org/community/groups/seopress/

[Sven Lehnert]

add it into a function in your functions.php and hook this function into bp_setup_nav

read more here http://bpdevel.wordpress.com/tag/bp_core_remove_subnav_item/

hope that helps you

[Sven Lehnert]

Hi @phyz, this is fixed now. check out the new version: https://github.com/Themekraft/Custom-Community

[Sven Lehnert]

try this:
bp_core_remove_subnav_item( bp_get_current_group_slug(), ‘home’ );

[Sven Lehnert]

you can do it with SeoPress: https://buddypress.org/community/groups/seopress/

[Sven Lehnert]

wow, could this topic become sticky for a while, so everyone can find this easily?

[Sven Lehnert]

+1 mobilized style sheet for BuddyPress by default

[Sven Lehnert]

one more:

by reading the code, I can see the locate_template() function comes with 3 parameters

locate_template($template_names, $load = false, $require_once = true )

the third parameter “$require_once” is ignored in buddypress and default is true

locate_template( array( ‘sidebar.php’ ), true )

that means the conflict could just happen by using something like this

locate_template( array( ‘sidebar.php’ ), true, false ); where $require_once is false.

[Sven Lehnert]

Hi,

thanks @djpaul for the instructions. We will write a patch hopefully until Friday.

I guess some things were misunderstood… to switch from right to left is easy done by css, but has nothing to do with the double sidebar conflict we need to avoid, if a plugin comes with a sidebar and we add one in the footer too.

I guess best is just to write the patch and check if it fits the needs.

To have an option page is a great idea, but more a feature for me than a bugfix. I’d like to concentrate on the basics first. Actually, to move the sidebar in the footer is one step to have options built in much more easy.

For the future, I believe the bbpress way of handling templates files is a good example and like I understood, the idea behind is that we will have no need of header, footer, sidebars and so on, we just deliver the content part and make themedesign much easier this way.

looking forward

[Sven Lehnert]

Hi @johnjamesjacoby

we are kind of new to all this… How to start? I will check out the latest version via svn. That’s fine. But how to check in? Commit? Push?
Should I add the complete theme as .zip file on a ticket? I guess the size will be too big.
I would like to write this patch, I’d like to start with some easy job to slowly go into all this. So the sidebar bug is an easy startup.

@dennissmolek, i guess we can keep it update save (backwards compatible) by asking if the sidebar is already active
https://codex.wordpress.org/Function_Reference/is_active_sidebar

Some more newbee questions:
Where do I add my other subjects? The sidebar was just one example of a long list we would like to discuss and write patches for.

Should we open a ticket for every idea we’d like to change?

Sorry, if some of the questions are already answered in other forum threads.
Maybe it would be a good idea, to write a guide to become an active part on the project.
Thanks for all, we are excited to start

[Sven Lehnert]

Hi @All,

I’m writing for themekraft.com, we are a young startup, making our lives with WordPress and 80% BuddyPress related development.
Buddypress has changed our lives and we want to count us in.
We have read the thread from bowe at bp-tricks.com and this thread here, and we want to help, too. It’s like bowe and this thread is bringing our thoughts to the public, and we feel it’s time to come together.

We are 3 people, and we can give 2 hour every week to help out. That makes 6 hours – let’s say one day a week.
We are two developers and 1 theme designer.
There are many small and bigger problems we found in our daily work, we like to have changed. And we would immediately start helping.

For example: bp-default:

We have developed a theme for BuddyPress. And in the theme you can change sidebars, also for BuddyPress components .
But it’s very difficult for us to provide a left sidebar only, because buddypress comes with a right sidebar in the default theme and the sidebar is included in the pages instead of in the header and the footer.

Every component that extends BuddyPress, comes up with the right sidebar in the template files.

That means for us (and all theme devs with theme options like sidebars), we have to rework every template file from every plugin to support having just a left sidebar.

This is just one theme example, we would like to share all experiences to improve theme development with BuddyPress.
We know, there must be at least some templates files for buddypress to work. But they should integrate in different way as now.
We have read this thread, and there are quite a lot of people willing to get their hands on the bp-default.

Wouldn’t it be a great thing to have the bp-default in github, so we can create a team to work together the git way?
There is also an issue tracker in github, and I feel it’s much easier as the trac…

This way integration in a new bp-default team would be very easy.

Patches and all the BuddyPress stuff.

We have done some funny things with custom post types and groups, because it is so difficult to filter groups in a certain way.
Also if we use the custom post type api, we get a lot of benefits like revision backups and so on.

To be honest, we believe that BuddyPress could handle groups more powerful, and we would like to work on this, too.

I have seen the conversation from the BuddyPress ninjas in the early days of 1.2 where JJJ started to think of groups in a API way.
Everything is a group. Like a group of people and so on. I really liked the idea and we would like to see groups become something more powerful.

I will stop writing now, hoping we will just start working, as I guess everything has been discussed before.

Thanks for all, we love BuddyPress and see it us a powerful tool to build great websites, often without the need of a direct social network, using it to realize our customers needs.

We look forward to start helping. We always had the feeling before, that it’s not so easy to become a working part.
So just let us know where we can start, or what you need to be done

Thanks,
svenl77, konradS and mahype

[Sven Lehnert]

I needed to change the path in the settings, there has been a missing “/” after the domain.

Complete URL of upload directory

hope this helps you

[Sven Lehnert]

It looks for me like a server or permalink issue. Have you tried to save your permalink structure again?

[Sven Lehnert]

Hi @folkertattema, please check out the forum for support, http://themekraft.com/forums/.

It’s my every second answer in this thread. @hnla or @mercime, could you close this topic please? I would really appreciate it.
Thanks Sven

[Sven Lehnert]

Thanks, we most enjoy such a feedback!

[Sven Lehnert]

Hi chrono1012, Thanks for your interest.
Please use the support forum: http://themekraft.com/forums/ to find your answers. Thanks Sven