New to Translating WordPress? Read through our Translator Handbook to get started. Hide

Translation of Development Readme (trunk): Greek

Filter ↓ • Sort ↓ • All (120) • Translated (0) • Untranslated (120) • Waiting (0) • Changes requested (0) • Fuzzy (0) • Warnings (0)
← 1 2 3 … 8
Prio Original string Translation —
↑ Allows people to recommend/send your WordPress blog's post/page to a friend.
Priority: high
You have to log in to add a translation. Details
Allows people to recommend/send your WordPress blog's post/page to a friend.
Comment

Short description.

You have to log in to edit this translation.

↑ WP-EMail
Priority: high
You have to log in to add a translation. Details
WP-EMail
Comment

Plugin name.

You have to log in to edit this translation.

Two option rows — <code>wp_email_options</code> for the settings and <code>wp_email_version</code> for the version it last ran — and one table holding the log. Deleting the plugin from the Plugins screen removes all three, along with every pre-3.0.0 row. You have to log in to add a translation. Details
Two option rows — <code>wp_email_options</code> for the settings and <code>wp_email_version</code> for the version it last ran — and one table holding the log. Deleting the plugin from the Plugins screen removes all three, along with every pre-3.0.0 row.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Add a custom field with the key <code>wp-email-remark</code>, and it will be placed in the remarks field on the E-Mail form. You have to log in to add a translation. Details
Add a custom field with the key <code>wp-email-remark</code>, and it will be placed in the remarks field on the E-Mail form.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Add a custom field with the key <code>wp-email-title</code>, and it will be used as the E-Mail title. You have to log in to add a translation. Details
Add a custom field with the key <code>wp-email-title</code>, and it will be used as the E-Mail title.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Before 3.0.0 the plugin looked for a copy of <code>email-css.css</code> in your theme directory and loaded that instead of its own. That is gone: it meant a theme had to reproduce the whole file to change one rule, and every upgrade that added a rule silently skipped those themes. You have to log in to add a translation. Details
Before 3.0.0 the plugin looked for a copy of <code>email-css.css</code> in your theme directory and loaded that instead of its own. That is gone: it meant a theme had to reproduce the whole file to change one rule, and every upgrade that added a rule silently skipped those themes.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Put them in your theme's own stylesheet. Everything the plugin styles sits under the <code>.wp-email</code> class, so <code>.wp-email label { ... }</code> in your theme is enough to override a rule, and your changes are never touched by an upgrade. You have to log in to add a translation. Details
Put them in your theme's own stylesheet. Everything the plugin styles sits under the <code>.wp-email</code> class, so <code>.wp-email label { ... }</code> in your theme is enough to override a rule, and your changes are never touched by an upgrade.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

The text inside will not appear in the message, but it will still show on the post or page as normal. Note that if you also run WP-Print, text inside <code>[donotemail]</code> will not be printed either. You have to log in to add a translation. Details
The text inside will not appear in the message, but it will still show on the post or page as normal. Note that if you also run WP-Print, text inside <code>[donotemail]</code> will not be printed either.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Wrap it: You have to log in to add a translation. Details
Wrap it:
Comment

Found in faq paragraph.

You have to log in to edit this translation.

The constant was called <code>EMAIL_SHOW_REMARKS</code> before 3.0.0. The plugin only defines it if you have not, so your setting survives upgrades. You have to log in to add a translation. Details
The constant was called <code>EMAIL_SHOW_REMARKS</code> before 3.0.0. The plugin only defines it if you have not, so your setting survives upgrades.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Add this to your <code>wp-config.php</code>: You have to log in to add a translation. Details
Add this to your <code>wp-config.php</code>:
Comment

Found in faq paragraph.

You have to log in to edit this translation.

With none of the three set, the plugin uses <code>REMOTE_ADDR</code> — correct on a plain host, and the proxy's address behind one. You have to log in to add a translation. Details
With none of the three set, the plugin uses <code>REMOTE_ADDR</code> — correct on a plain host, and the proxy's address behind one.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

If you need to decide per request — say, only trust the header when the request arrives from your load balancer — use the filter instead: You have to log in to add a translation. Details
If you need to decide per request — say, only trust the header when the request arrives from your load balancer — use the filter instead:
Comment

Found in faq paragraph.

You have to log in to edit this translation.

To trust the usual set instead (<code>X-Forwarded-For</code>, <code>CF-Connecting-IP</code> and friends), add this to <code>wp-config.php</code> above the <code>/* That's all, stop editing! */</code> line: You have to log in to add a translation. Details
To trust the usual set instead (<code>X-Forwarded-For</code>, <code>CF-Connecting-IP</code> and friends), add this to <code>wp-config.php</code> above the <code>/* That's all, stop editing! */</code> line:
Comment

Found in faq paragraph.

You have to log in to edit this translation.

If you know which header it is, name it under <code>WP-Admin -&gt; E-Mail -&gt; Settings</code> in the <code>Header That Contains The IP</code> field — for example <code>HTTP_CF_CONNECTING_IP</code> for Cloudflare. That is the narrowest option, and the one to prefer. You have to log in to add a translation. Details
If you know which header it is, name it under <code>WP-Admin -&gt; E-Mail -&gt; Settings</code> in the <code>Header That Contains The IP</code> field — for example <code>HTTP_CF_CONNECTING_IP</code> for Cloudflare. That is the narrowest option, and the one to prefer.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Legend:
Current
Waiting
Rejected
Fuzzy
Old
Changes requested
With warnings
← 1 2 3 … 8

Export as