[@chouf1 Participant 14 years, 1 month ago]

@mercime, ok thanks! But “honor” is too much i opened a ticket witch probably would be considered as “not important” yet…. There are other more important tasks to do first

https://buddypress.trac.wordpress.org/ticket/4506

[@chouf1 Participant 14 years, 1 month ago]

bump…
Also do this be related in a ticket ?

[@chouf1 Participant 14 years, 1 month ago]

hello,

you can read here at the bottom:
https://codex.buddypress.org/extending-buddypress/changing-internal-configuration-settings/

and also here:
http://www.otreva.com/buddypress-how-to-change-avatar-size-larger-or-smaller/

[@chouf1 Participant 14 years, 1 month ago]

hi,

add his to your “/plugins/bp-custom.php”
add_filter( 'bp_use_wp_admin_bar', '__return_false' );

[@chouf1 Participant 14 years, 1 month ago]

You have to create a child theme first.
Than you can modify the members-loop by adding a contitionnal tag for loged-in users into
your_theme/members/members-loop.php

Line 20
`

`

[@chouf1 Participant 14 years, 1 month ago]

All CSS changes (and others) must be done from within your child theme. That’s the reason of the child theme 😉
If you do that in bp-default, they gone at the buddypress next update

https://codex.buddypress.org/theme-development/building-a-buddypress-child-theme/

[@chouf1 Participant 14 years, 1 month ago]

@mercime
doesn’t work for me. The javascript tag is closed immediatly after
I insert and save [ javascript ] the code[ /javascript ]
When i edit the post i have
[ javascript ] [ /javascript ] here the code[ /javascript ]

[@chouf1 Participant 14 years, 1 month ago]

@mercime, it seems that the word «php» is censored somehow

Tag [ code language= ” php ” ] bla bla [ / code ]
Word php is stripped. In the DB i see this [ code language=” ” ” ” ]

[@chouf1 Participant 14 years, 1 month ago]

Some progress in debuging…
When i insert
[ sourcecode language=” php ” ][ /sourcecode ]
and open the post for editing, i get [ sourcecode language=”””” ][ /sourcecode ]
The word php disappeared and the place is double quoted !

Then i save these changes and the code cames up, but without colored synthax.
This is a first step on the right way. Colors are missing but code is showing correctly at 90%
Single quotes became curly for ex.

Probably backpress kses filtering.

I tried to deactivate BP’s filters bp_get_the_topic_post_content wptexturize and bp_get_the_topic_post_content bp_forums_filter_kses, but this changed nothing.

I posted on the support forum, but it seems still for a long time ago.
https://wordpress.org/support/topic/plugin-syntaxhighlighter-evolved-conflict-with-buddypressbbpress?replies=1#post-3112451

[@chouf1 Participant 14 years, 1 month ago]

@mercime Thank you for the screenshots. But I still use the same settings and shorcodes.
I observe that your example is on a bbPress page. My forums are on BP integrated bbPress skills (default install).
In the past mounth with other html outputs on forum posts, i still observed that bbPress filters and BP filters conflict sometimes.
I tested also the plugin on another BP 1.6.1 site and got the same wrong output of HTML
Surprisingly, after inserting mixed code (html+php) with the plugin activated, all html is filterd and gives &gt, &lt and so on. After deactivating the plugin, the whole code shows correctly, without the plugin styles effect, but all is appearing and correctly.
As soon as i edit the post and register it again, all html is stripped and only the php parts remain.

So i guess that bbPress (as standalone plugin) filters HTML correctly before and after DB insertion, but not BP.

[@chouf1 Participant 14 years, 1 month ago]

The reason is that i want to understand why mysite.com/comments/feed/ contains only comments used in a private group. Despite this the feed is public.
While searching around this, i found what i mentionned above. Just curiosity in fact, to learn from.
Thank’s

[@chouf1 Participant 14 years, 1 month ago]

I use it on my homepage as a widget with some CSS adjustment, so i presume it’s not template dependant. But i haven’t tested it in the sidebar position. Would say YES.

[@chouf1 Participant 14 years, 1 month ago]

Thank you @mercime, but i already tested your advice with only BP and SH activated. I also deactivated my functions.php and i have the same problem.
Can you give me a link to an example on your site, to see how it looks on your config.
Perhaps it has to do with some server config.

[@chouf1 Participant 14 years, 1 month ago]

i’m using this plugin on wp 3.4.1/bp 1.6.1
https://wordpress.org/extend/plugins/bbpress-latest-discussion/

[@chouf1 Participant 14 years, 1 month ago]

I don’t cheat. I only asking questions for trying to help you. J’me casse. Tchao.

[@chouf1 Participant 14 years, 1 month ago]

Oups ! Also missed ” I’m asking for another alternative instead of plugin as use the function.php.”

Try with this in theme’s functions.php
`function my_member_username() {
global $members_template;
return $members_template->member->user_login;
}
add_filter(‘bp_member_name’,’my_member_username’);`

[@chouf1 Participant 14 years, 1 month ago]

Hi,
try this in bp-custom.php
remove_filter( 'wpmu_signup_blog_notification', 'bp_core_activation_signup_blog_notification', 1, 7 );

source infos buddypress /bp-core/bp-core-filters.php

The concerned filter do this
/***
* bp_core_filter_blog_welcome_email()
*
* Replace the generated password in the welcome email.
* This will not filter when the site admin registers a user.
*
* @uses locate_template To see if custom registration files exist
* @param string $welcome_email Complete email passed through WordPress
* @param integer $blog_id ID of the blog user is joining
* @param integer $user_id ID of the user joining
* @param string $password Password of user
* @return string Filtered $welcome_email with $password replaced by [User Set]
*/

[@chouf1 Participant 14 years, 1 month ago]

Hi,
did you read the warning at the top of the official plugin page ?
https://wordpress.org/extend/plugins/buddypress-usernames-only/

The problem is perhaps the plugin ?

[@chouf1 Participant 14 years, 1 month ago]

I’m on a BP install and i want to use syntax highlighting in the forum post.
I already know and use Notepad++
And as explained previous i use syntaxhighlighter evolved witch output you can see if you go to link above.

[@chouf1 Participant 14 years, 1 month ago]

Sorry, i haven’t noticed that you’re on a BP single blog install.
I’m not familiar with single install, but i guess you have to create a page called blog.
In the bp settings, click on the tab “component” and check the “site tracking” box
On the tab “pages”, assign this page to blog in the directory
save

But unsure if this works for single WP.

[@chouf1 Participant 14 years, 1 month ago]

i’m not a programmer at all, but better try this:
`function add_sumtips_admin_bar_link() {
global $wp_admin_bar;
if ( !is_super_admin() || !is_admin_bar_showing() || is_user_logged_in() )
$wp_admin_bar->add_menu( array(
‘id’ => ‘sumtips_link’,
‘title’ => __( ‘SumTips Menu’),
‘href’ => __(‘http://sumtips.com’),
) );
endif
}
add_action(‘admin_bar_menu’, ‘add_sumtips_admin_bar_link’,25);”`

[@chouf1 Participant 14 years, 1 month ago]

Ok, you’re diabolique.
Try this
http://buddydev.com/buddypress/changing-default-avatar-size-croppedused-by-buddypress/

and tailor the sizes in the group_loop with https://codex.buddypress.org/developer-docs/custom-buddypress-loops/the-groups-loop/
` `
And same thing in the member loop with
“

[@chouf1 Participant 14 years, 1 month ago]

You can use a template conditionnal tag.
if ( is_user_logged_in() ) :
your custom menu stuff
else
something for non logged user
endif

[@chouf1 Participant 14 years, 1 month ago]

Hello,
what is your mother language ?

If you use define(‘DOMAIN_CURRENT_SITE’, ‘buddypress.seyte.com’); it means that “buddypres”s is a subdomain of seyte.com !
This suppose also that wordpress is installed at the root of seyte.com.
But you declare define(‘SUBDOMAIN_INSTALL’, false);
Pass this to true instead of false and see what you get.

Subdomain install needs also the usage of a wildcard declaration on your host settings.

https://codex.wordpress.org/Create_A_Network
https://codex.wordpress.org/Before_You_Create_A_Network

If this is too complicated for you, i suggest that you deactivate all your plugins and custom theme.
Erase the wp-config file and restart your WP install. Be sure that wp is at the root of seyte.com
After this install, go to wp-admin and activate the network install.
When done, activate the buddypress plugin.
Make the setting of BP specially “blogs” creation.
Activate bp-default theme and test your install.
If everithing is working, create a new blog and test again.
Now if you want you can change the themes of the main site and/or the newly created blog.
And finally reactivate your other plugins (if you use some)

[@chouf1 Participant 14 years, 1 month ago]

Yo, i understand your frustration, but debuging by the “common way” is the first thing to do.
If your install worked before upgrading and no more after, it’s logical to think that there is somewhere a conflict or a missing piece of code.
Custom themes and plugins are mostly the culprit. JS sliders, plugs with text editors are also common sources of problems.

There is no universal answer. Each site is different, each problem too.
I recently get a blank page because of a missing > in one of my template loop !
I updated to 1.6.1 and all my pages disapeared and i had to recreate them one by one.
After 4 years of BP usage, it’s just an incident. But i understand, especially it it’s the first time you run such a trouble, how this can be annoying, for sure !

On this topic, you claim all “it’s no more working.” but no one said what he did, what theme he use and what type of install he manage. All these details are missing in this topic. And so far i know, nobody here is a soothsayer. I’m not.

Other common forum user behavior: no or less feedback when a solution is found. So coming here and saying “it’s not the problem” after an answer, is not fair. If it’s not the problem, why do you ask for help ? And if it’s the problem, why don’t you explain it ?
Pages are gone is not the probleme description, it’s the problem RESULT description.

A clearly explained problem brings to a clearly solution.
I don’t know what happens for you. I only try to help you with common questions intented to guide your debug search.

Let me suggest you that if you want to know what 1.6.1 did, go to the trac and compare the version changes. It’s very easy to find this information on the Trac. But you have to read the code.

If “it’s not the problem” with common guidance as read above, may i suggest you to activate the debug mode in wp-config file. Perhaps some warnings or server information will help you further.

Sorry it’s also a common help answer. And as i’m french, sorry for my poor english.