Xavier Borderie

Thank you for your understanding.
Don’t hesitate to contact me directly, or via make.www.ads-software.com/polyglots, if you have more question issues.

Hey there,

fr_FR translation lead here. Thank you for your suggestion, John! And thank you Otto for being ever-so helping and insightful.

We’ve long chosen to translate “Upload” into “Mettre en ligne” (put online), because indeed, there is no other common way to put it.

As Otto says, “télécharger” supposedly should for both direction (upload and download), but in effect, people only ever use it to mean “download”. The OQLF indeed suggest “téléverser”, and Wikipedia even suggests “téléchargement montant”, “téléchargement vers l’amont”, or ttéléchargement vers le serveur”, but again, none of these are used in the wild.

Wanting to have a translation that works in all contexts, “Mettre en ligne is the one we chose to use.

You did suggest “remonter sur le serveur” (pull up on server), but I’m afraid that is the first time I ever see “remonter” being used in the context of an upload. I’m therefore afraid that I have to reject your suggestion, and keep using “Mettre en ligne” which, unlike what you imply in your first post, is not completely and 100% wrong.

We welcome debates about wording, so if you feel like it, don’t hesitate to discuss with the team of translators on the #traductions channel of the French WP Slack! Click here to get an invitation: https://boiteaweb.fr/slack-invitation

I’d like to suggest some things towards local communities.

– improve local codepoet (/europe is hard to read by country, really, and doesn’t bring a lot of information/verification it seems — yes, I know how hard this can be).
– have a local version of the job board on xx.wp.org.
– biggest request: make it possible for local communities to easily integrate xx.wp.org tools (download page, showcase, potential job-board, potential improved codepoet) on their own domain (such as in a sub-domain), so as to not have their community spread on many sites.

Ok then, fixed.
I went ballistic on the database using phpMyAdmin, successfully doing a check, an optimization and a repair on all tables, and there you go, every works again.
Still don’t know what might have provoke the problem, but I’m a happy camper.

Ok then, news…

I tried simply using the working third blog’s database prefix as the main blog’s prefix, and TADAM, it works. So the issue might not be with the files, but with the database itself.
Note that both blogs are on the same database, same hostname, same user, same password, etc.

Still digging.

Thanks for answering.

All files are at 664, folders are at 755.

Plugins: not sure it’s important since I don’t think it infuences the display of the admin, but who am I to judge? ??
1bit audioplayer, audio-player, google sitemap generator, spamkarma2, ultimate google analytics, simple-deezer, wp-shortstat2, xhtml-video-embed, wpdb backup, text-control.

Tried renaming /plugins to /__plugins so that none would be loaded, no dice.

I temporarily fixed it.

Fixed, because seeing that ticket 8533 blames wpautop, I tried installing the Jeff Minard’s Text Control plugin, which lets me choose which formatting option to use on a per-post basis. By default, the formatting uses “wpautop”, but thanks to Text Control, I was able to set it to the simpler “nl2br”. Worked like a charm! ??

Temporarily, because I was forced to go through the HTML code in order for the post to look good (misaligned image-text combo, twice-too-huge lists, etc.). I can’t use the visual editor on this post anymore because it would break my well-placed nl’s…

I truly hope this gets properly fixed in 2.8, so that I can 1) edit this post in Visual mode if I want to, and 2) remove the reliance on Text Control, which is handy but should not be used in such a cause.

Please hear me, core devs!

Update:
– I tested it on yet another host (llord.com), with WP 2.7.1: same result;
– a friend of mine tested it on 2.3.1 blog on 1&1, and according to him it worked;
– it doesn’t matter which part of the text is deleted to allow short size: start, finish, center, if I remove enough it works.

Hence, it sounds like it would be tied to this issue:
https://core.trac.www.ads-software.com/ticket/8553
…which is apparently fixed in 2.8-bleeding, but I tried copy/pasting my post into this trunk public demo blog:
https://demo-trunk.wordpress-fr.net
…and it didn’t work still.

Still digging…

Moshu : yup, I tried that one but indeed, it doesn’t make it “public”, it seems you really have to enter the category’s URL in order to read its content. It does display months that have verbotten-only posts, but once you click that month, it gives the 404-finger ??

I guess I’ll stick to it anyway for now, but I might have to apply my theme-editing idea, which is just what Gangleri said.

Thanks guys!

Also receiving spam promoting this plugin on my company’s punBB forum.

IP address: 59.92.65.211
User mail: [email protected]

Yet another link

Same issue here, tried everything, no luck.
Gabrielz solution did the trick for me. Thanks!

I have the very same problem. Comments go through without any problem, but, when comes the time to process the page, I get this, the URL being on /blog/wp-comments-post.php .

I didn’t make any change to my install (still using WP 1.5.2), and a frequent commenter just told me about it today…
Zoddo, did you solve it ?

Parse error: syntax error, unexpected T_STRING in /home/xibe/public_html/xavier/blog/wp-includes/gettext.php(307) : eval()’d code on line 2

Warning: Cannot modify header information – headers already sent by (output started at /home/xibe/public_html/xavier/blog/wp-includes/gettext.php(307) : eval()’d code:2) in /home/xibe/public_html/xavier/blog/wp-comments-post.php on line 51

Warning: Cannot modify header information – headers already sent by (output started at /home/xibe/public_html/xavier/blog/wp-includes/gettext.php(307) : eval()’d code:2) in /home/xibe/public_html/xavier/blog/wp-comments-post.php on line 52

Warning: Cannot modify header information – headers already sent by (output started at /home/xibe/public_html/xavier/blog/wp-includes/gettext.php(307) : eval()’d code:2) in /home/xibe/public_html/xavier/blog/wp-comments-post.php on line 53

Warning: Cannot modify header information – headers already sent by (output started at /home/xibe/public_html/xavier/blog/wp-includes/gettext.php(307) : eval()’d code:2) in /home/xibe/public_html/xavier/blog/wp-comments-post.php on line 55

Warning: Cannot modify header information – headers already sent by (output started at /home/xibe/public_html/xavier/blog/wp-includes/gettext.php(307) : eval()’d code:2) in /home/xibe/public_html/xavier/blog/wp-comments-post.php on line 56

Warning: Cannot modify header information – headers already sent by (output started at /home/xibe/public_html/xavier/blog/wp-includes/gettext.php(307) : eval()’d code:2) in /home/xibe/public_html/xavier/blog/wp-comments-post.php on line 57

Warning: Cannot modify header information – headers already sent by (output started at /home/xibe/public_html/xavier/blog/wp-includes/gettext.php(307) : eval()’d code:2) in /home/xibe/public_html/xavier/blog/wp-comments-post.php on line 58

Warning: Cannot modify header information – headers already sent by (output started at /home/xibe/public_html/xavier/blog/wp-includes/gettext.php(307) : eval()’d code:2) in /home/xibe/public_html/xavier/blog/wp-includes/pluggable-functions.php on line 129

Cool, thanks.

11.20 seconds to load it last time I checked. Every single time, the dashboard takes forever, for feeds I don’t really care for…

I’m in the process of fully revamping the PO file in order to get rid of such special characters and change them to HTML entities… Please bear with my lack of time ??