Erwan

This Nginx (helper) plugin relies, like WP codex Nginx fastcgi_cache recommandation btw, on the free 3rd party ngx_cache_purge module and its fastcgi_cache_purge directive.

How can you claim this plugin’s purge method/feature does not work anymore, whatever your Nginx free version?

Thanks a lot for your responsiveness & accurate explanations.

I exported the .mo/.po files from the translation project (and renamed them: breadcrumb-navxt-fr_FR.mo/.po instead of breadcrumb-navxt-fr.mo/.po): it works fine.

I draw your attention to the facts that:

• among the translated strings (i.e. 149/184 – 81%), a LOT of crucial / basic ones are not correctly translated and/or are missing in the .pot (e.g. strings including “post” or “gallery”);
• among the not translated strings (i.e. 35/184 – 19%), some should be translated in order to have standard French “frontend – template” settings before further user settings / customizations (e.g. "<a title="Go to the %title% category archives." href="%link%">%htitle%</a>").

I of course could help you improving this translation & meet the threshold: quite simple (except for the missing strings in .pot of course), just tell me how to proceed.

Before editing my custom CSS: what are the current excerpt display type applied by default to cat / tag pages as far as featured images are concerned?

I thought it was the 1st / large image one i.e. 700×290 px, but it seems to be another one i.e. 630×290 px according to my Firebug… Am I right ?

My WPLANG is of course fr_FR in my wp-config.php. Running on 4 different sites (and configurations: server, PHP version, themes, etc.), Breadcrumb NavvXT is the only plugin with an available translation which won’t show.

I checked again the .po file: actually, the translation is really poor (73/184 strings not translated), but I could improve it with Poedit.

Instead, I have to modify most of the settings (mainly: NavXT “template” settings) on all sites, which is a real loss of time and rather frustrating.

Thanks a lot for your quick answer: trick works fine!

@atallos:

Apparently another Firefox (21.0 / Windows 8) bug… : works on Chrome!

Thanks for your responsiveness !

@attallos:

Actually, I ran again from scratch the BP Template Pack process with my Pagelines theme, and the birthday field shows all right now: no real idea why though ?? ! Unfortunately, the date picker appears as a plain text field.

Same issue here (for the birthdate; email etc. are OK), using Pagelines (framework : 2.4.3) + BuddyPress Template Pack + child theme (like another user in a related topic in this plugin support forum.

In my child theme members \ single \ profile \ edit.php, I already do have the hook <?php do_action( 'bp_custom_profile_edit_fields_pre_visibility' ); ?>, changed his location following @sundowner667 indications (i.e. line right after <?php while ( bp_profile_fields() ) : bp_the_profile_field(); ?>): no effect.

Where exactly must the hook be placed in the file, if it’s really the problem? Could someone maybe post the whole correct code?

FYI, this error still obviously shows up with BuddyPress 1.7 stable release (i.e. 1.7.2 atm) & Pagelines.

Maybe Pagelines developers could understand better than me this topic in the BuddyPress.org support forum adressing the “bp_setup_current_user was called incorrectly” notice and capitalise on it?

Same here (notice, not error / warning hence not critical!), probably due to BP 1.7 too.

If the strings were added or modified since the last Jetpack release, they are not included in the current version of Jetpack, indeed.

It’s the opposite: French strings were added or modified before last Jetpack releases and were obviously not added in the Jetpack installation package. For instance, the string “Tiled Mosaic” was translated 2013-03-29 in GlotPress and is not translated in current Jetpack 2.2.5 “package” .mo file.

Thanks for your .mo link anyway ??

@jeremy

All strings should be translated in the latest version of Jetpack, but if you find missing translations, you’re welcome to suggest new translations!

• Whatever their relevance, strings relating to galleries are translated in active GlotPress Jetpack 2.2. project but not in the .mo file delivered with Jetpack 2.2.5.
• Moreover, the original English strings of the current translation in GlotPress do not even match the Tiled Gallery feature description. For instance, “Tiled Mosaic” versus “Tiles”.
• Hence: a real mess, which would incidentally make useless and even risky any other translation suggestion from me.

@denis cc @jeremy

No matter what size are the images, i get the default 500 px width. I think Pagelines does not define the width somehow or i do not know.

I think the topic you opened in the Pagelines support forum eventually resolved this really tricky problem, isn’t it?

[EDIT – PHP 5.4. deprecated function?]

1. My bad: same settings on backend, don’t know what happened.

2. Clarification: bug occurs only when user tries to log whislt a required field is not completed yet.

3. Explanation? My first site is running under PHP 5.3., the second under PHP 5.4. I logged a deprecated attribute_escape() function used in this plugin bp-fp-admin.php file, tried to use esc_attr() instead but it did’nt work, though. Any coding help would be most welcomed ?? !

I probably misunderstood both of you, because I noticed weird / not steady backend column option behaviour for tiled galleries.

I unfortunately didn’t took screenshots and I don’t manage atm to replicate what I described (and I really saw, belive me ?? !), i.e. 0, 2, 5, or 9 columns proposed on backend (using for instance Pagelines framework or Clean Retina theme) when selecting “Tiles” or “Squared Tiles” type.

Atm, my frontend galleries are OK and do adapt to size of images, orientation, number of images, theme or specific page / article content width. And the column option does’nt appear anymore on my backend for tiled galleries : which is supposed to be the case with this last Jetpack update, if I enventually understood you correctly… ? Am I wrong or right ?

Moreover, confusing French translation of Jetpack gallery settings do not help: I have “Thumnail Grid” (yes, in English !) for “Default”, “Tiled Mosaic” (yes, in English !) for “Tiles”, and “Mosa?que d’image carrées” for “Square Tiles”… A real mess ?? !

Hi,

Are you sure this new feature is rock steady… ?

After pulling my hair out trying to understand why I had columns or not under various circumstances, I was glad to find this topic and Jeremy’s explanation.

Unfortunately, the number of columns is totally unpredictable, NOT always related to this method of calculation, and NOT steady.

If you take the same theme & exact configuration, and the same images, you can have 0 or 9 columns proposed when creating a “Jetpack gallery”. Or for instance 9 columns proposed for two or 40 images..

Could you confirm me there ARE bugs ? Many thanks in advance.

Best regards.