BuddyPress.org

Wrong code: On the BP Post Button issue.

This is the media code, whats wrong why does it show the link of the inserted image. Anyone??

function bp_post_buttons_inserts($form, $element, $snippetstag) {
//uncomment and use insert_body instead of insert_body_disabled to hide by default
// echo(‘<span class=”insert_head”><b>[Insert Media..] </b></span>’);
echo(‘<div class=”insert_body_disabled bppb_headroom”>’);
echo(“‘);\”>link“);
echo(“<a href=\"javascript:insert_tag_url('$form','$element','‘);\” />image“);

BP Post Buttons Problem

The line that generates the popup and adds an image includes the img url in the post. Where in this code does it says that the must me added:

echo(“<a href=\"javascript:insert_tag_url('$form','$element','‘);\” />afbeelding vanuit album“);

Hello Cam,
Thanks for your reply, but unfortunately, didn’t worked.
From wp-login.php I can log in from the first try.
The scenario is like this: http://s11.postimg.org/t8t4umamb/cookie.png
I have the login form with the exact code from bp-default’s theme sidebar on my index page, I type the user and PW there, press Login, redirects me to wp-login.php, press again it will log me in. Same scenario on a fresh WP + BP install with BP-Default Theme.

If I try to log in using directly wp-login.php, I can log in with no problem. But when I try using a login form like the bp-default’s theme:

<form name="login-form" id="" class="standard-form" action="<?php echo site_url( 'wp-login.php', 'login_post' ) ?>" method="post">
		<input type="text" name="log" id="" class="input" placeholder="Email sau nume utilizator" value="<?php if ( isset( $user_login) ) echo esc_attr(stripslashes($user_login)); ?>" tabindex="97" />
	<br />
		<input type="password" name="pwd" id="" placeholder="Parola" class="input" value="" tabindex="98" />
	<br />

		<label class="parola"><?php do_action( 'bp_sidebar_login_form' ) ?>
		<input type="submit" name="wp-submit" id="" value="<?php _e( 'Simply, be awesome!', 'buddypress' ); ?>" tabindex="100" />
		</label>
		<label class="parola">Ai uitat parola?</label>
		<input type="hidden" name="testcookie" value="1" />
	</form>

I get cookie error.

@crazycoolcam IT WORKS! Thank you Sir! It Works..hehehe, I guess the code wanted the real single quote instead of the ascii code. Changed to them and it works dandy! Thanks again! The original issue in my eyes is resolved thanks to @crazycoolcam but will leave open until everyone else confers–let me know please!

Awesome Thanks again!

William

Hi Seth!

Interesting, I didn’t know that you had a BP integration in place for EE. With which BP version was it compatible?

I know that the BP core developers have their hands full of work, so I won’t blame them for not taking on a complete events module in the core.

For me the question now is, which plugin takes the least effort to extend on our own. And yes, I know about your crowdfunding like offer to fund extensions to EE. But I need to meet certain deadlines and I don’t think you can guarentee a certain development until then.

BTW, isn’t the “I’ll attend’ and ‘Maybe’ a pretty simple code addition? A user presses a button which captures that users user id and writes it into a custom field of the event page. The plugin then fetches those ids and shows avatars of those people who attend.

I found an interesting tutorial (http://wp.smashingmagazine.com/2012/01/27/limiting-visibility-posts-username/) which might lead the way for my other request, specific event visibility/privacy:

1. Only friends of events creator (again, write all the user ids of the event creator into a custom field thats not visible/accessible to users and then restrict visibility of event page to those users)

2. Only invited (would require more work. First have a way to notify other users of the event by private message or BP notification. Write the user ids of those into yet another custom field, rest see above)

I am pretty much a PHP noob. But are these things really so hard to do? More than a week of work for an experienced BP developer?

@crazycoolcam Thanks. I did exactly what you said and I still am receiving this error:

Parse error: syntax error, unexpected T_IF in /server_info/wp-content/plugins/bp-custom.php on line 5

This is what the file consists of:

1 <?php
2 //fix for cookie error while login.
3 function set_wp_test_cookie() {
4	setcookie(TEST_COOKIE, 'WP Cookie check', 0, COOKIEPATH, COOKIE_DOMAIN);
5	if ( SITECOOKIEPATH != COOKIEPATH ) {
6		setcookie(TEST_COOKIE, 'WP Cookie check', 0, SITECOOKIEPATH, COOKIE_DOMAIN);
7	}
8 }
9 add_action( 'after_setup_theme', 'set_wp_test_cookie', 101 );
10 
11 ?>

Thank you soooo much for assisting. I think I speak for everyone here — THANKYOU!

@crazycoolcam I was so excited to see this fix here this morning. I hurried to put this into effect because it matches what you say-if you try the sidebar firsttime it fails and then it works after this until cookies are deleted or cache. I have been always able to login without fail using the wp-login – just not the sidebar login the first time. Anyway, I could only find the functions.php file and I added it to the end before the ?> at the end of the file. For some reason I got a blank screen and this error.

Parse error: syntax error, unexpected T_IF in /server_info/wp-content/plugins/buddypress/bp-themes/bp-default/functions.php on line 796

I guess I just don’t know where to put the code or something. I look forward to hearing back from you for your direction to help my simple ignorance of not knowing what to do.

Thanks William

@modemlooper:
The plugin I use is called “BP Group Hierarchy”:
https://wordpress.org/plugins/bp-group-hierarchy/

And here’s how to use it for listing a subset of groups:
http://www.generalthreat.com/2012/01/extending-buddypress-group-hierarchy-list-member-groups/

*Solved Problem*

It had to do with a rule in the .htaccess
ExpiresByType text/html A3600
Tells the browser to cache the page for 1 hour, well it caches the non logged in page so after log in when you go back to it the browser gives the cached version.

The reason it was so hard to figure out has to do with my hosting setup. I have my main site hosted then my buddypress site is an addon domain so lives in a folder /addondomain

Well the .htaccess files are recursive so the rule ExpiresByType text/html A3600 was set by W3 Total Cache, a plugin I use on my main website living in Public_html caused the rule to be applied to the add on domain pages.