Content Mask vs WFY24 Weather Widget

Read More & View Demos Here Embed Any Content†‡ Into Your WordPress Website Content Mask allows you to embed any external content onto your own WordPress Pages, Posts, and Custom Post Types. The end result is fairly similar to setting up a Domain Mask, but the content is embedded into the front end of your website and is fully contained inside your WordPress permalink ecosystem. Example: If you built a landing page on landing-page-builder.com/your-landing-page/, you can simply create a new Page on your website at your-site.com/landing-page/ and paste in the URL of your landing page. The Content Mask plugin will then download and cache of copy of your landing page directly on your website, so any visitors that come to your-site.com/landing-page/ will see the landing page you built. This allows you to keep all of your links integrated into your WordPress Website. † Do not use Content Mask to embed any content that you do not own or do not otherwise have license to share, embed, frame, or distribute. Simple 2-Step UI With a simple 2-Step UI, you can embed any external content into your website without any complicated URL Forwarding, DNS Records, or .htaccess rules to mess with. Just enable the Content Mask on any Page, Post, or Custom Post type by clicking on the check mark. Then put in the URL that contains the content you want to embed. It’s that simple! Powerful Embedding and Redirect Options Using the Download method (default) will fetch the content from the Content Mask URL, cache it on your website, and replace the current page request with that content. By default, this cache lasts 4 hours – but it can be changed anywhere from “Never Cache” all the way up to “Cache for 4 Weeks”. Caching prevents the need for additional requests that slow down your site. Using the Iframe method will replace the current page request with a full width/height, frameless iframe containing the host URL. This method is ideal if the URL you want to embed won’t serve scripts, styles, or images to other URLs or IP Addresses. If you use the Download Method, and links or images look broken, you can try the Iframe method instead. Using the Redirect (301) method will simply redirect the visitor to the host URL. Simple Integrated Vistor Tracking In the Content Mask admin panel, you can enable tracking for Content Masked pages. This will allow you to see how many visitors are viewing these links. This is ideal for when you need to track acquisition, such as on a Landing Page. [Views] shows how many times that Content Mask page has been viewed by anybody (even logged in users) [Non-User] shows how many times it’s been viewed by visitors that are not logged in to the website. [Unique] shows how many times it’s been viewed by unique IP addresses. Note: IP addresses are one-way hashed and are not identifiable in any way. Creating a Content Masked Page Using the Content Mask Admin Panel Notes: Do NOT use Content Mask on any content you aren’t explicitly authorized to share or use. Please confirm you’re allowed to utilize and embed the content before embedding any particular URL. Content embedded using the Download method is cached using the WordPress Transients API for 4 hours by default. If the content on the external URL is updated and you would like a fresh copy, you may just click the “Update” button on the Page, Post, or Custom Post Type to refresh the transient, or click the “Refresh” link in the Content Mask Admin panel. You may also change the cache expiration timer per page anywhere from “Never” to “4 weeks”. You may use the Transients Manager plugin to manage transients stored with the Download method. All Content Mask related transients contain the prefix “content_mask-” plus a stripped version of the Content Mask URL, such as “content_mask-httpxhynkcom”. ‡ Your site may be prevented from processing page requests for any reason; Reasons include, but are not limited to: masking unauthorized content, at the request of the masked URL site owner, masking hateful content, masking illegal content, circumventing IP bans, etc. A dual one-way encrypted hash of your masking URL may be used to check for infraction. No identifying information will be used for this check, and no information is saved other than as a transient to prevent unnecessary duplicate checks per site Read More About Content Mask

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. Zero-friction setup On activation, a welcome wizard walks you through three clicks: Activate — we auto-register your site with wfy24.com using your admin email. No external signup. No copy/paste. Create Weather page — optionally publish a “Weather” page with the widget ready to go. Add to sidebar — one-click inject a compact weather widget into your first sidebar. Features 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. Upgrade to Pro to remove the attribution Lightweight — 6.6 KB gzipped Real-time data — temperature, conditions, wind, humidity, 5-day forecast 50 languages — auto-detected from your site or set manually Admin interface in 15 locales — the settings screen and setup wizard are fully translated into Bulgarian, Czech, Dutch, French, German (de_DE / de_AT / de_CH), Greek, Hungarian, Italian, Polish, Portuguese (pt_PT / pt_BR), Spanish and Swedish, and the activation link opens wfy24.com in your own language Auto location — GPS (with consent) or IP-based geolocation, or pin a specific city Light / Dark / Auto theme — matches your site automatically 7 layouts — Classic, Compact, Minimal, Badge, Forecast, Air Quality, Air Quality + Weather (wide) Shadow DOM isolation — zero CSS conflicts with your theme Zero dependencies — no jQuery, no React, no bloat Multi-source data — ICON-D2/EU/Global NWP + GFS fallback, with ML post-processing Usage Shortcode: [wfy24_weather] Override per instance: [wfy24_weather city="paris-fr2988507" theme="dark" variant="forecast" lang="fr"] Or use the WFY24 Weather Widget block in the Gutenberg editor for a visual interface. Attribution 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 wfy24.com/en/widgets/pro. External service This plugin connects to the WFY24 weather service at https://www.wfy24.com: Plugin activation: POSTs to /api/widget/register-from-plugin 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. City search (admin only, when typing in the Default City field): the plugin’s REST endpoint /wp-json/wfy24/v1/cities proxies your search query (e.g. “athens”) to /api/places/search 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. Widget rendering (client-side on visitor browsers): loads widget.js and queries /api/widget/data. The widget sends the API key, optional city slug, language/units/theme preferences, and a data-geolocation 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. Pro upgrade flow (only if the user clicks “Upgrade to Pro” in Settings): GETs /api/widget/pro/status and POSTs to /api/widget/pro/checkout and /api/widget/pro/portal to provision a Stripe Checkout session and a Stripe Billing Portal session. No data is sent unless the admin clicks the relevant button. Links: WFY24 Terms of Service: https://www.wfy24.com/en/terms WFY24 Privacy Policy: https://www.wfy24.com/en/privacy-policy Multisite Support The plugin is multisite-compatible. All settings (API key, defaults, page) are stored per-subsite using get_option()/add_option(), so each subsite operates independently. Network Activation does not contact wfy24.com. It only loads the plugin code on every subsite. No admin_email is sent, no API key is created, no automatic phone-home occurs. 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 Settings → General → Email Address 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. 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. No centralized network admin panel exists in this version — each subsite has its own settings page. A network-level overview is on the roadmap. API keys are domain-bound. A key issued for site-a.example.com will not function on site-b.example.com, which means subdomain and domain-mapped multisite installs work correctly out of the box (each subsite gets its own key for its own domain).