BuddyPress.org

Rename the buddypress folder in wp-plugins via FTP or cPanel to deactivate BuddyPress.

The correct translation in WP lingo is “You do not have sufficient permissions to access this page.” And while this was triggered by activating BuddyPress, it starts with your WordPress installation.

There are plenty of threads in WP.org forums and Google search with different solutions to get back your Admin/Super Admin privilege in the installation. Good luck.

I’m using a standard BP theme as child theme , and only for translation purpose.
As you can compare with what is on pastebin, some code is wrong, also here on bp.org

the return contains $text between backstick, but they are converted to < code >

i give a try here, using backticks
`
function bporg_decodeit( $matches ) {
$text = $matches[2];
$trans_table = array_flip(get_html_translation_table(HTML_ENTITIES));
$text = strtr($text, $trans_table);
$text = str_replace(‘
‘, ”, $text);
$text = str_replace(‘

‘, ”, $text);
$text = str_replace(‘

‘, ”, $text);
$text = str_replace(array(‘&’,’&’), ‘&’, $text);
$text = str_replace(”’, “‘”, $text);
if ( ‘

' == $matches[1] )

$text = "n$textn";

return "`$text`";

}

`

on my forum it is showing this

http://bp-fr.net/groups/groupe-de-tests/forum/topic/another-test/

It’s best to ask someone more used to the translations format; I’ve not heard about this issue before. What about trying the wp-polyglots mailing list?

Here’s the code that does it on buddypress.org. It’s basically repurposed from bbPress.

I had to replace the actual backtick with the phrase `[backtick]` so that it would render properly on this forum. Make sure to correct that in your version.

`// Borrowed from bbPress
function bporg_encodeit( $matches ) {
$text = trim($matches[2]);
$text = htmlspecialchars($text, ENT_QUOTES);
$text = str_replace(array(“rn”, “r”), “n”, $text);
$text = preg_replace(“|nnn+|”, “nn”, $text);
$text = str_replace(‘&’, ‘&’, $text);
$text = str_replace(‘<', '<', $text);
$text = str_replace(‘>’, ‘>’, $text);
$text = “$text“;
if ( “[backtick]” != $matches[1] )
$text = “

$text

“;
return $text;
}

// Borrowed from bbPress
function bporg_decodeit( $matches ) {
$text = $matches[2];
$trans_table = array_flip(get_html_translation_table(HTML_ENTITIES));
$text = strtr($text, $trans_table);
$text = str_replace(‘
‘, ”, $text);
$text = str_replace(‘

‘, ”, $text);
$text = str_replace(‘

‘, ”, $text);
$text = str_replace(array(‘&’,’&’), ‘&’, $text);
$text = str_replace(”’, “‘”, $text);
if ( ‘

' == $matches[1] )

$text = "n$textn";

return "`$text`";

}



// Borrowed from bbPress. Makes code in backticks work, both in forum posts and in activity updates.

function bporg_code_trick( $text ) {

$text = str_replace(array("rn", "r"), "n", $text);

$text = preg_replace_callback("|(`)(.*?)`|", 'bporg_encodeit', $text);

$text = preg_replace_callback("!(^|n)`(.*?)`!s", 'bporg_encodeit', $text);

return $text;

}

add_filter( 'bp_get_the_topic_post_content', 'bporg_code_trick', 1 );

add_filter( 'bp_get_activity_content_body', 'bporg_code_trick', 1 );`

The pomo files you used were corrupted – po was not unicode compliant so the compiled mo file gives a wrong output.

The solution was to replace these files.
I found them here:
https://i18n.trac.buddypress.org/browser/pl_PL/tags/1.2.6

This buggy message is annoying (a synchronizing delay between WP update service and your site), but not important.
At the place where this message appears, you have option button who says “hide this option ?”.
You can use it, or if the button does not appear, wait a few hours or can add this at the end of the file wp-includes/version.php
$wp_local_package = ‘pl_PL’; (will be lost at the next WP update)

I have had the same text “WordPress 3.0.1 is available! Please update now.” appearing on the admin page. Should be a bug, but don’t be affraid of it, your site is updated. View the version number of WP at the bottom right of your admin interface.

pl-PL.po is a translation for the WP part – PAth: wp-content/languages
buddypress-pl_PL.po is the BP translation. – Path: wp-content/plugins/buddypress/bp-languages

if you put pl_PL.po in the bp-languages folder, neither WP or BP are translated.

Dear Mark!

I have just installed BuddyPress 1.2.6 along with WordPress 3.0.1, installed translations for both and put `define (‘WPLANG’, ‘pl_PL’);` inside wp-config.php. Everything seems to work fine, even if only the BuddyPress translation is in place.

If you can’t find who it is @markhahnel, ask on http://lists.automattic.com/mailman/listinfo/wp-polyglots

I think the best solution is to have two separate .mo files with the interface translation and set the translation on wp-content/plugins/bp-custom.php (If you havent the file, create one) with the following code
$lang = substr($_SERVER, 0, 2);
switch ($lang){
case ‘en’:
define( ‘BPLANG’, ‘en’ );
if ( file_exists( BP_PLUGIN_DIR . ‘/bp-languages/buddypress-en.mo’ ) ) {
load_textdomain( ‘buddypress’, BP_PLUGIN_DIR . ‘/bp-languages/buddypress-en.mo’ );
}
break;
case ‘es’:
define( ‘BPLANG’, ‘es’ );
if ( file_exists( BP_PLUGIN_DIR . ‘/bp-languages/buddypress-es.mo’ ) ) {
load_textdomain( ‘buddypress’, BP_PLUGIN_DIR . ‘/bp-languages/buddypress-es.mo’ );
}
break;
}
Check that the filenames are the same

This code detects automatically the browser language and defines the language.

Follow this article to find more about this
https://codex.buddypress.org/buddypress-site-administration/customizing-labels-messages-and-urls/

Hi Paul, yes my fr_FR translation is working correctly on 1.2.6. You’re probably right with the mo expectation. Something is certainly going wrong somewhere. And polish use some accentuated caracters, i guess.

Maybe a stupid question: has the .mo file added after upgrade the right permission set to 644 on your server ?

Mark, I’ve just tested the translation on a test site. Some of the BuddyPress localisation seems to work, most of it doesn’t. I think the .mo file is incomplete.

Have you contacted the maintainer to ask if it is up-to-date? I’m not sure who looks after Polish. (It might be a silly question, but it’s worth checking).

Hi Mark; they are appearing in English.