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

Translation of Development Readme (trunk): Spanish (Spain)

Filter ↓ • Sort ↓ • All (169) • Translated (32) • Untranslated (137) • Waiting (0) • Changes requested (0) • Fuzzy (0) • Warnings (0)
← 1 2 3 … 12
Prio Original string Translation —
↑ Adds an AJAX poll system to your WordPress blog. You can also easily add a poll into your WordPress's blog post/page.
Priority: high
Añade un sistema de encuestas AJAX a tu sitio WordPress. También puedes añadir fácilmente una encuesta en tu entrada/página del sitio. Details
Adds an AJAX poll system to your WordPress blog. You can also easily add a poll into your WordPress's blog post/page.
Comment

Short description.

You have to log in to edit this translation.

↑ WP-Polls
Priority: high
WP-Polls Details
WP-Polls
Comment

Plugin name.

You have to log in to edit this translation.

Anywhere the poll can be predicted this early will do. Code that already runs later↵ in the page — a <code>the_content</code> filter inserting a placeholder, say — can call↵ WP_Polls_Display::request_assets() instead, which is the same request the render↵ paths make and is picked up by the footer pass. You have to log in to add a translation. Details
Anywhere the poll can be predicted this early will do. Code that already runs later↵ in the page — a <code>the_content</code> filter inserting a placeholder, say — can call↵ WP_Polls_Display::request_assets() instead, which is the same request the render↵ paths make and is picked up by the footer pass.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Say so from the page that will hold the poll: You have to log in to add a translation. Details
Say so from the page that will hold the poll:
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Neither reaches poll markup fetched over <code>admin-ajax.php</code> or the REST API into a page↵ that itself shows no poll: the fetch has no footer to enqueue into, and the page↵ carried nothing for the head to find. The symptom is a poll that will not vote, under↵ a "Loading ..." that never goes away. You have to log in to add a translation. Details
Neither reaches poll markup fetched over <code>admin-ajax.php</code> or the REST API into a page↵ that itself shows no poll: the fetch has no footer to enqueue into, and the page↵ carried nothing for the head to find. The symptom is a poll that will not vote, under↵ a "Loading ..." that never goes away.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

The head pass looks for the poll widget, a <code>[poll]</code> or <code>[page_polls]</code> shortcode and↵ the two blocks, and anything rendering after it — a template tag, a poll in a loop↵ page — asks for the assets as it renders and gets them from the footer. You have to log in to add a translation. Details
The head pass looks for the poll widget, a <code>[poll]</code> or <code>[page_polls]</code> shortcode and↵ the two blocks, and anything rendering after it — a template tag, a poll in a loop↵ page — asks for the assets as it renders and gets them from the footer.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

My own code renders a poll and the page loads no stylesheet or script You have to log in to add a translation. Details
My own code renders a poll and the page loads no stylesheet or script
Comment

Found in faq header.

You have to log in to edit this translation.

The stylesheet and the voting script load only on pages that show a poll, a polls archive or the poll widget; a page without one carries neither. You have to log in to add a translation. Details
The stylesheet and the voting script load only on pages that show a poll, a polls archive or the poll widget; a page without one carries neither.
Comment

Found in faq list item.

You have to log in to edit this translation.

Before 3.0.0 this was written against <code>.pollbar</code>, the single element the bar used to↵ be. That class no longer exists, so the old snippet colours nothing. You have to log in to add a translation. Details
Before 3.0.0 this was written against <code>.pollbar</code>, the single element the bar used to↵ be. That class no longer exists, so the old snippet colours nothing.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

If your theme ships its own <code>wp-polls.css</code>, the bar rules are not in it — they used to↵ be generated by PHP into an inline <code>&lt;style&gt;</code> block, and they now live in the plugin's↵ stylesheet. Either copy the <code>.wp-polls-bar</code> rules across, or delete your copy and↵ override these instead, which is the supported way now: You have to log in to add a translation. Details
If your theme ships its own <code>wp-polls.css</code>, the bar rules are not in it — they used to↵ be generated by PHP into an inline <code>&lt;style&gt;</code> block, and they now live in the plugin's↵ stylesheet. Either copy the <code>.wp-polls-bar</code> rules across, or delete your copy and↵ override these instead, which is the supported way now:
Comment

Found in faq paragraph.

You have to log in to edit this translation.

If you re-add a bar by hand, use <code>%POLL_ANSWER_PERCENTAGE%</code> for the width.↵ %POLL_ANSWER_IMAGEWIDTH% was removed in 3.0.0 and is no longer substituted, so a↵ template still containing it emits the literal token into the <code>style</code> attribute and↵ the bar renders with no width at all. You have to log in to add a translation. Details
If you re-add a bar by hand, use <code>%POLL_ANSWER_PERCENTAGE%</code> for the width.↵ %POLL_ANSWER_IMAGEWIDTH% was removed in 3.0.0 and is no longer substituted, so a↵ template still containing it emits the literal token into the <code>style</code> attribute and↵ the bar renders with no width at all.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

The <strong>Result Body</strong> and <strong>Result Body (Voted)</strong> templates are rewritten to that markup↵ on upgrade, <em>including customised ones</em>. There was no way to keep them: the class names↵ and the stylesheet changed with the markup, so a customised copy of the old template↵ would have rendered a bar with no rules left to match it. Re-apply your changes on↵ the <strong>Templates</strong> tab, keeping the two <code>wp-polls-bar</code> elements. You have to log in to add a translation. Details
The <strong>Result Body</strong> and <strong>Result Body (Voted)</strong> templates are rewritten to that markup↵ on upgrade, <em>including customised ones</em>. There was no way to keep them: the class names↵ and the stylesheet changed with the markup, so a customised copy of the old template↵ would have rendered a bar with no rules left to match it. Re-apply your changes on↵ the <strong>Templates</strong> tab, keeping the two <code>wp-polls-bar</code> elements.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

3.0.0 rebuilt the poll bar. It used to be one <code>&lt;div class="pollbar"&gt;</code> sized by an↵ inline width; it is now a track holding a fill: You have to log in to add a translation. Details
3.0.0 rebuilt the poll bar. It used to be one <code>&lt;div class="pollbar"&gt;</code> sized by an↵ inline width; it is now a track holding a fill:
Comment

Found in faq paragraph.

You have to log in to edit this translation.

That is deliberate and unchanged: WP-Polls stores <code>wp_hash()</code> of the address, so the↵ logs can tell two voters apart without keeping their IP addresses. You have to log in to add a translation. Details
That is deliberate and unchanged: WP-Polls stores <code>wp_hash()</code> of the address, so the↵ logs can tell two voters apart without keeping their IP addresses.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Sites that need to decide per request can use the <code>wp_polls_trust_proxy</code> filter, which↵ defaults to that constant. You have to log in to add a translation. Details
Sites that need to decide per request can use the <code>wp_polls_trust_proxy</code> filter, which↵ defaults to that constant.
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 … 12

Export as