wfy24

WFY24 Weather Widget lets you embed a free, fully-featured weather widget on any WordPress site — in any post, page, or sidebar — with a single shortcode, Gutenberg block, or built-in sidebar widget.
<h4>Zero-friction setup</h4>
On activation, a welcome wizard walks you through three clicks:
<ol>
<li>Activate — we auto-register your site with wfy24.com using your admin email. No external signup. No copy/paste.</li>
<li>Create Weather page — optionally publish a “Weather” page with the widget ready to go.</li>
<li>Add to sidebar — one-click inject a compact weather widget into your first sidebar.</li>
</ol>
<h4>Features</h4>
<ul>
<li>Free version with a small “Weather by WFY24” attribution link under each widget (disclosed and consented to during activation). No credit card, no hidden fees, no ads. <a href="https://www.wfy24.com/en/widgets/pro" rel="nofollow ugc">Upgrade to Pro</a> to remove the attribution</li>
<li>Lightweight — 6.6 KB gzipped</li>
<li>Real-time data — temperature, conditions, wind, humidity, 7-day forecast</li>
<li>50 languages — auto-detected from your site or set manually</li>
<li>Auto location — GPS (with consent) or IP-based geolocation, or pin a specific city</li>
<li>Light / Dark / Auto theme — matches your site automatically</li>
<li>5 layouts — Classic, Compact, Minimal, Badge, Forecast</li>
<li>Shadow DOM isolation — zero CSS conflicts with your theme</li>
<li>Zero dependencies — no jQuery, no React, no bloat</li>
<li>Multi-source data — ICON-D2/EU/Global NWP + GFS fallback, with ML post-processing</li>
</ul>
<h4>Usage</h4>
Shortcode:
<pre><code>[wfy24_weather]
</code></pre>
Override per instance:
<pre><code>[wfy24_weather city="paris-fr2988507" theme="dark" variant="forecast" lang="fr"]
</code></pre>
Or use the WFY24 Weather Widget block in the Gutenberg editor for a visual interface.
<h4>Attribution</h4>
The free version of this plugin displays a small “Weather by WFY24” link under each rendered widget. The onboarding wizard shows an explicit disclosure notice and asks for your consent before the “Activate now (free)” button; clicking that button is your explicit permission to enable the link. To remove the attribution, a Pro version is available at <a href="https://www.wfy24.com/en/widgets/pro" rel="nofollow ugc">wfy24.com/en/widgets/pro</a>.
<h4>External service</h4>
This plugin connects to the WFY24 weather service at <code>https://www.wfy24.com</code>:
<ul>
<li>Plugin activation: POSTs to <code>/api/widget/register-from-plugin</code> with the email you confirmed in the onboarding form (pre-filled from Settings → General; editable inline before activation), site name, site domain, WordPress version, and plugin version, in order to automatically provision your free API key. No activation happens without your explicit click on the “Activate now (free)” button.</li>
<li>City search (admin only, when typing in the Default City field): the plugin’s REST endpoint <code>/wp-json/wfy24/v1/cities</code> proxies your search query (e.g. “athens”) to <code>/api/places/search</code> server-side. Your search query is sent along with a User-Agent identifying the plugin. Results (slug + label + country flag) are cached for 5 minutes per query. The admin’s IP is never exposed cross-origin because the request is server-to-server.</li>
<li>Widget rendering (client-side on visitor browsers): loads <code>widget.js</code> and queries <code>/api/widget/data</code>. The widget sends the API key, optional city slug, language/units/theme preferences, and a <code>data-geolocation</code> flag (off by default — visitor location is not detected unless the admin explicitly opts in via the “Auto-detect visitor location” toggle). When the toggle is on AND the visitor grants permission, the visitor’s latitude/longitude is sent; when geolocation is denied, the visitor’s IP address is used for IP-based city detection (still gated by the toggle). No personal data is stored beyond standard anonymized request logs for rate limiting.</li>
<li>Pro upgrade flow (only if the user clicks “Upgrade to Pro” in Settings): GETs <code>/api/widget/pro/status</code> and POSTs to <code>/api/widget/pro/checkout</code> and <code>/api/widget/pro/portal</code> to provision a Stripe Checkout session and a Stripe Billing Portal session. No data is sent unless the admin clicks the relevant button.</li>
</ul>
Links:
<ul>
<li>WFY24 Terms of Service: <a href="https://www.wfy24.com/en/terms" rel="nofollow ugc">https://www.wfy24.com/en/terms</a></li>
<li>WFY24 Privacy Policy: <a href="https://www.wfy24.com/en/privacy-policy" rel="nofollow ugc">https://www.wfy24.com/en/privacy-policy</a></li>
</ul>
<h3>Multisite Support</h3>
The plugin is multisite-compatible. All settings (API key, defaults, page) are stored per-subsite using <code>get_option()</code>/<code>add_option()</code>, so each subsite operates independently.
<ul>
<li>Network Activation does not contact wfy24.com. It only loads the plugin code on every subsite. No <code>admin_email</code> is sent, no API key is created, no automatic phone-home occurs.</li>
<li>Each subsite admin completes onboarding individually. When the admin opens the welcome wizard on a subsite and clicks “Activate now (free)”, the plugin sends that subsite’s domain and <code>Settings → General → Email Address</code> to wfy24.com to obtain a domain-bound API key. The admin is shown a dynamic disclosure of the exact values that will be transmitted before clicking — no consent is collected on behalf of admins of other subsites.</li>
<li>New subsites added later remain inactive until their admin runs onboarding manually. The widget will not render on a subsite that has not been activated; no data leaves WordPress until an admin explicitly clicks Activate on that subsite.</li>
<li>No centralized network admin panel exists in this version — each subsite has its own settings page. A network-level overview is on the roadmap.</li>
<li>API keys are domain-bound. A key issued for <code>site-a.example.com</code> will not function on <code>site-b.example.com</code>, which means subdomain and domain-mapped multisite installs work correctly out of the box (each subsite gets its own key for its own domain).</li>
</ul>

WFY24 Weather Widget

Free, lightweight, embeddable weather widget for your WordPress site. One-click activation, 50 languages, auto location, light/dark theme.

CMEBOSS

在電商平台上，合理地拆分冷凍與常溫商品的訂單對於提升物流運營效率和控制成本至關重要。以下是一些具體的設計建議，能夠在結帳階段引導顧客拆單，並優化整體用戶體驗：
1.商品分類標籤：在商品頁面和購物車中，使用不同顏色或圖標清晰地標示冷凍商品和常溫商品。
2.購物車提醒：當購物車中同時存在冷凍和常溫商品時，顯示提示信息，告知顧客這些商品需要分開配送。
3.自動拆單建議：在結帳頁面自動將訂單拆分為冷凍商品和常溫商品的兩個訂單，並展示分開配送的優勢，如更快的配送速度和食品新鮮度的保證。
4.手動拆單選擇：提供顧客自行選擇是否拆單的選項，並清楚說明各選項的影響，例如不同的配送時間或費用。
5.配送費用透明化：分別顯示冷凍和常溫商品的配送費用，讓顧客清楚了解拆單的實際成本。明確告知顧客在達到一定金額時可以享受的免費配送政策，鼓勵合理拆單並增加銷售額。
6.簡化拆單流程：確保拆單操作簡單易懂，不增加顧客的購物負擔。對於拆單後的訂單，提供一鍵結帳功能，減少多次操作。
7.智能推薦系統：利用算法分析顧客的購買行為和偏好，自動推薦相關的常溫或冷凍商品，促使顧客一次性完成拆單購物。
8.後端系統整合：確保後端物流系統能夠高效處理拆單後的訂單，保持庫存更新、包裝和配送的流暢性。
這些設計策略不僅可以幫助電商平台提升運營效率，還能增強顧客的購物體驗，最終促進銷售和客戶滿意度。
This plugin allows customers to split their orders themselves at the checkout screen based on whether they prefer frozen or regular temperature shipping. Customers can divide the orders on their own, providing greater convenience for backend operators in managing inventory.

split order by different thermospheric transport 溫層拆單

在結帳時高效拆分冷凍和常溫商品，使用清晰標籤、自動和手動拆單選項、透明配送費用和智能推薦系統，以提升物流和顧客體驗。

WFY24 Weather Widget vs split order by different thermospheric transport 溫層拆單