Skip to content

Works with your stack

Cookie consent for the JNews theme on WordPress

9 keys of its own

← Cookie Rocks for your stack

The JNews theme by Jegtheme and its bundled plugins can set 9 cookies and browser-storage keys of their own for visitors, 3 of them as the page loads, without a click. With the theme active, Cookie Rocks recognises them and gives each the category shown below.

By Jegtheme · jnews.io

Is this your product? Tell us if anything here is out of date. Write to us

What matters for consent with JNews

What it stores

5 necessary, 3 preferences and 1 statistics, by the category our legal watch gives each key. The table below lists each one: what it is for, how long it lasts and when it is set.

A location from the IP address

With the weather widget’s automatic location on, JNews looks up the visitor’s approximate place from the IP address and sends it in the weather_location cookie with the first page, from the server. A location kept for a widget is a preference: in countries that ask for consent first, it must wait for the visitor’s yes.

Before the choice

We reproduced 9 keys with the same name, duration and logic as the theme’s code, on a test site. Without a consent tool that knows them, 9 were set before the choice, 9 kept after Reject all.

Cookie Rocks today

With the theme active, Cookie Rocks recognises these keys and gives each the category in the table. Keys in a refused category are erased after the page loads, and those the server sets are held until the visitor accepts. The weather_location cookie is held this way, and the banner shows the Preferences category from the next page, so a visitor who accepts gets the weather.

What you can do now

The weather widget’s automatic location waits for the visitor to accept preferences. A fixed city shows the weather to everyone without that cookie. Leave JNews’s own cookie notice off: next to a consent plugin, visitors would see two bars.

Cookies and storage JNews sets

NameKindLastsCategoryWhy
<sanitised-site-name>-jnews-player TestedLocal storageabout 12 hoursPreferencesKeeps the podcast track, position and volume for 12 hours, beyond the visit: a convenience, not strictly needed; consent in prior-consent countries.
When and what for

When: after the visitor plays or pauses audio in the podcast player (JNews Podcast active).

What it is for: Keeps the podcast player state (track, position, volume, playlist) across pages and tabs. Lasts: persistent (internal expiry 12 hours, removed on next load after that).

darkmode TestedCookiesessionNecessaryDark or light mode for the visit only, chosen by the visitor or following their own device setting: session display customisation, exempt (WP29 04/2012, 3.6).
When and what for

When: after a click on the dark mode toggle (default option jeg_toggle_light); first page for every visitor with option Night Time Only (jeg_timed_dark) or Use Device Theme (jeg_device_dark), default off.

What it is for: Remembers whether the visitor uses the light or dark colour scheme.

jnews_view_counter_visits[N] (multisite: jnews_view_counter_visits_<blog_id>[N]) TestedCookieset by the siteStatisticsRecords which articles the visitor read so a view is not counted twice: audience measurement. Not set with the default setting (0 hours); when the owner sets a delay, it waits for consent in prior-consent countries, except where the country's analytics exemption applies.
When and what for

When: on a single post view (AJAX count); kept only when option time_between_counts is above 0 (default 0); skipped when Cookie Notice says cookies are not accepted.

What it is for: Lists the posts the visitor already viewed so a repeat view is not counted twice. Lasts: time_between_counts setting (default 0 hours: expires at once, so not kept).

jnews-webstories TestedCookiesessionPreferencesRemembers which stories the visitor already opened: a convenience based on what they read, not needed for the page; consent in prior-consent countries (as Soledad's pc_webstories_seen).
When and what for

When: after the visitor opens a story (JNews Web Stories active).

What it is for: Remembers which web stories the visitor has already seen.

paywall_product TestedCookiesessionNecessaryCarries a choice the visitor just made (scroll target, page to return to after login, paywall package) to the next page, short-lived: needed for the service requested.
When and what for

When: first page for every visitor when JNews Paywall is active (value "false"), then the product ID after a click on a package button.

What it is for: Remembers which paywall package the visitor picked so that checkout opens with that product; reset to "false" on each page load.

urllogin TestedCookie1 hourNecessaryCarries a choice the visitor just made (scroll target, page to return to after login, paywall package) to the next page, short-lived: needed for the service requested.
When and what for

When: after a click on a social login button (JNews Social Login active).

What it is for: Remembers the page to return to after a social network login.

weather_location TestedCookieset by the site (30 days)PreferencesA place derived from the visitor's IP address, kept for a weather widget: location data used for a convenience, not needed for the page. In prior-consent countries it must not be set before consent; since JNews sets it with Set-Cookie on the first response, Cookie Rocks must hold it on the server (or remove it from the response) until preferences are accepted. If that is not possible, erase it at once and warn the owner on the dashboard to turn off the widget's location feature.
When and what for

When: first page for every visitor, server side on init; only with option top_bar_weather_location_auto (default off).

What it is for: Stores the visitor's approximate location, looked up from the IP address, to show local weather in the top bar. Lasts: until option cookie_timeout, else 30 days.

zoom_position TestedCookiesessionNecessaryText zoom the visitor just chose, kept for the visit only: session display customisation, exempt (WP29 04/2012, 3.6).
When and what for

When: after a click on the zoom buttons; only with option jnews_single_zoom_button (default off).

What it is for: Remembers the text zoom level the visitor chose on articles.

What our tests found on JNews

  • Good to know · JNewsCookie Rocks holds the JNews view counter cookie set through admin-ajax

    jnews_view_counter_visits is held until statistics are accepted; views are still counted.

    Seen in our tests, 13 November 2026, JNews 11.2.1.

    Full detail

    With a time between counts above 0, JNews sets jnews_view_counter_visits[N] (HttpOnly) on an admin-ajax response. Cookie Rocks removes that header until the visitor accepts statistics, and expires a copy already in the browser after a refusal. Views are still counted.

  • Good to know · JNewsCookie Rocks also holds JNews weather_location on REST responses

    weather_location is held on pages and REST, and an old copy is expired after a refusal.

    Seen in our tests, 13 November 2026, JNews 11.2.1.

    Full detail

    With JNews active, Cookie Rocks removes the Set-Cookie header of weather_location from pages and from REST responses until the visitor accepts preferences. After a refusal, a copy already in the browser is expired by the server on its own path, HttpOnly copy included. From the next page, the banner shows the Preferences category, so the visitor can accept it and get the weather back.

  • A setting to know · JNewsJNews View Counter keeps viewed posts in an HttpOnly cookie

    setting “time_between_counts” · by default: 0

    With a time between counts above 0, viewed posts go to an HttpOnly cookie that page scripts cannot erase. Default: expires at once.

    Read in the code of JNews 11.2.1, 13 November 2026.

    Full detail

    When the time between counts is above 0, JNews View Counter lists the posts a visitor has viewed in jnews_view_counter_visits[N], set by the server with HttpOnly, so scripts in the page cannot read or erase it. With the default setting, 0 hours, it expires at once. JNews skips it only when the Cookie Notice plugin reports a refusal. Our legal watch classes it as statistics.

  • A setting to know · JNewsJNews weather finds the visitor's place from the IP address

    setting “top_bar_weather_location_auto” · by default: off

    With automatic location on, the server sends a place found from the IP address in weather_location (30 days) with the first page.

    What to do: In countries that ask for consent first, turn off the automatic location and set a fixed city for the weather widget.

    Read in the code of JNews 11.2.1, 13 November 2026.

    Full detail

    With the weather widget's automatic location on, JNews looks up the visitor's approximate place from the IP address and sends it in the weather_location cookie (30 days by default) with the first page, from the server, for every visitor. A browser can only erase it after it has arrived. Our legal watch classes it as preferences: consent first.

WordPress themes

Other plugins of the same kind.

AstraNo cookie of its own, Google Fonts once you choose one.tested 4.14.3BlocksyIts own Analytics field and notice: leave both off with a consent plugin.tested 2.1.62Hello ElementorA bare theme: no cookie, no outside request.tested 3.5.2KadenceBackground videos held, Google Fonts to host yourself.tested 1.6.0NeveNo cookie of its own, an extra notice to avoid.tested 4.2.19OceanWPGoogle Fonts on by default, widgets that load other sites.tested 4.2.8WordPress themesFonts, videos, widgets and extra notices, theme by theme.Avada3 keys of its own; 3 need consent first.BeTheme7 keys of its own; 5 need consent first.The71 key of its own; 0 need consent first.Bridge1 key of its own; 1 needs consent first.Enfold4 keys of its own; 3 need consent first.Salient2 keys of its own; 2 need consent first.WoodMart28 keys of its own; 21 need consent first.Porto5 keys of its own; 3 need consent first.Newspaper6 keys of its own; 4 need consent first.Uncode5 keys of its own; 3 need consent first.XStore9 keys of its own; 6 need consent first.Impreza5 keys of its own; 3 need consent first.Soledad20 keys of its own; 12 need consent first.JupiterX3 keys of its own; 1 needs consent first.Kallyas3 keys of its own; 3 need consent first.CocoonClick analytics and a Pinterest button, both held until consent.FlatsomeVideo backgrounds held, lightbox cookies removed until consent.FoxizA visitor ID and a dark mode choice in the browser.DiviContact forms with reCAPTCHA, videos and maps in modules.tested 5.15.0

Every plugin and theme we test →

Questions

Does JNews need a cookie banner?

Its own keys are listed below with their category. The tools you add through it, such as videos, maps or analytics, are held by Cookie Rocks like everywhere else.

Can a cookie set by the server be erased in the browser?

Only after it has arrived. That is why a key sent with the first response, such as weather_location, is better held on the server, or switched off in the theme, than erased afterwards.

What happens after the 30-day trial?

The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.

For JNews sites

See what your theme stores, held or cleared.

tested keys

Every feature of the complete plugin for 30 days, no card.

  • During the trial: everything, including the full settings and the scans
  • After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
  • What waits for a key: most settings, updates and support

How the trial works, in detail

Cookie Rocks

Get your trial key

Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.

One trial per domain. Local and staging sites never use up your key.

We keep your e-mail address to send your key and help you with it, as explained in our privacy policy. No newsletter, nothing else.