Contests by Rewards Fuel vs Hosted Content Importer (HCI)

Contests by Rewards Fuel connects your WordPress site to the Rewards Fuel platform. Use this plugin to embed live contests on any post or page. Create contests, entry methods, prizes, and rules in the Rewards Fuel web dashboard — the plugin handles connection and embedding. What this plugin does Connect your site with an API key from Account → WordPress Integration in the dashboard View your contests inside WordPress admin → Rewards Fuel Copy a shortcode or use the Rewards Fuel Contest Gutenberg block Embed the contest widget on posts, pages, and most themes Link out to the dashboard to edit contests, view stats, and pick winners What you build in Rewards Fuel (not inside WordPress) Contest schedule, rules, prizes, and appearance Entry methods (social actions, newsletter signup, questions, referrals, and more — by plan) Hosted contest page at r-f.page or embed on your own site Statistics, CSV export, winner selection, and prize claim flow Popular entry methods Available entry methods depend on your plan. Examples include: Click to enter — simple one-click entry Newsletter signup — collect email addresses (with optional confirmation for newsletter entries) Refer a friend — bonus entries when friends enter via a share link Answer a question — collect feedback or quiz answers Visit a URL — drive traffic to a landing page Code word — entrants enter a secret phrase Social actions — Instagram, Facebook, X/Twitter, YouTube, TikTok, Reddit, LinkedIn, Discord, Telegram, Twitch, and more (link-based actions; availability varies by plan) Email list member — allow pre-approved emails on your contest list to enter File upload — photo or document submissions Platform features (dashboard) Physical and digital prizes — upload digital prize files; winners claim online Geo restrictions — block selected countries from entering Bot protection — optional Cloudflare Turnstile per contest Custom appearance — colors, fonts, backgrounds, and widget wording 11 widget languages — English, Spanish, French, German, Portuguese, Italian, Dutch, Polish, Japanese, Korean, and Simplified Chinese Contest statistics — entries, methods, countries, traffic, referrers, device breakdown, and entrant summaries CSV export — download confirmed entrants from the dashboard Winner tools — random or manual winner selection; optional auto-pick and winner notification emails when the contest ends Scheduled draws — weekly, daily, or end-of-contest prize draws while live Copy a contest — duplicate setup for your next campaign Embed on WordPress After connecting your API key, embed any contest with: [rewardsfuel id="YOUR_CONTEST_REF"] Legacy shortcodes still work: [rf_contest id="123"] Or add the Rewards Fuel Contest block in the block editor. Pricing Rewards Fuel offers a free tier plus paid plans with more entry methods and stats. All paid plans include unlimited contests and entries. See current pricing at rewardsfuel.com/pricing. Get started Create a free account Create a contest in the dashboard Generate an API key under Account → WordPress Integration In WordPress: Rewards Fuel → Your account → paste your key Copy the shortcode from Rewards Fuel → Contests into any post or page Questions? Email [email protected]. Translations Widget copy supports 11 languages (configured per contest in the dashboard). The WordPress plugin admin UI is English.

It imports third party hosted contents within WordPress blog. You can define from which url/resource to fetch the content. The original source may be editable by anyone else whom you trust. Thus, it logically empowers you to allow other users to externally edit a particular section of your blogs. And, you do not have to give them any access credentials of your website. After installation, use shortcode tag [third] with few parameters as: [third source="markdown" id="https://goo.gl/UpclKH" section=""] source is a content processor type. id is a URL or ID given by the third parties. section is an optional parameter to access deeper content. cache is a boolean directive whether to reuse the cached content. It will then embed remote markdown content inside your blog. Additionally, it will convert the text into HTML using Parsedown. Parameters source: Where to seek the data (eg. Content Hosting Server). Examples: analytics: ✔ implemented (Google Analytics) file: ✔ implemented (Read from local file) gist: ✔ implemented (Embed Gist Snippets) jotform: ✔ implemented (Embed Web Forms) markdown: ✔ implemented (Parse remote markdown files) qr: ✔ implemented For Custom Data, For current page’s URL youtube: ✔ implemented (Embeds a YouTube Video) database: Partially implemented, and left for developers url, api: Work in progress wikipedia: Work in progress, Strategy: Content JSON to Data Section The list is not limited, you expand it. Join/Fork Development id: Content ID (unique identifier) of the data you want. Often: Full URLs Database IDs Resource IDs provided by Service Providers eg. YouTube Video ID, JotForm Form ID, … Full Path of a Local File section: Additional parameter to identify the specific section of the content. Example: Parsing a remote .md file [third source="markdown" id="https://goo.gl/UpclKH" section=""] Learn to write your .md file. Example: Embedding a gist code from GitHub [third source="gist" id="000000000000" section="filename.php"] Create your gists at GitHub. Example: Embedding a JotForm [third source="jotform" id="000000000000" section=""] Create your own web form at JotForm website. Example: Reading a server’s local file [third source="file" id="/tmp/readme.txt" section=""] It has to be a static file for security reasons. For example, if you read the .php file, it will NOT process it, rather read its contents only. Your can contain valid HTML data, css and javascripts. Example: Accessing database – Expand it yourself [third source="database" id="0" section="recent"] Detailed implementations are left for the developers because of the nature. It is a proof of concept work. Please feel free to modify/expand it. Example: Custom QR Code [third source="qr" id="YOUR DATA" section=""] Example: QR Code for Current Page (Full URL) [third source="qr" id="url" section="internal"] The above example is a full code. If you embed it anywhere, it lets your users copy that page’s URL into their mobile. Example: Embedding a YouTube Video [third source="youtube" id="v00000000000" section=""] Choose your video from YouTube. Personalized Content Processors You may often consider writing your own Content Processor. Refer to Custom Content Processor section in [Other Notes] tab. Custom Content Processors If you want to develop your own Content Processor, it is much easier now. Just create a tiny class file inside classes/processors as like one of the existing one. Simple examples are YouTube, JotForm and Gist processors. Minimum requirements File name: class.processor_YOURNAME.inc.php Method: public function fetch($form_id = null, $section = null). Process your content. Return HTML string. For references, see class.processor_none.inc.php Use as: [third source="YOURNAME" section=""] Click for real examples. Just that much easy drop-in replacement. Banner Image Used from unsplash.com Cable Cars and Rope: Represents contents coming from various sources.