Close

Copyright © RebelMouse 2019

Follow Us:

How to Fix: “Most Read” Module Displays Incorrect Content

Make sure your best-performing stories are visible

RebelMouse's powerful tools give you the ability to filter and display your site's posts in many ways.

A popular use case demonstrating this is a post element on your site's home page that displays the "Most Read" or "Trending" articles from a given period of time. These elements pull posts that are filtered from a specific section, like news, to show readers the most current and popular articles at that moment.

An important thing to keep in mind when setting up post elements with filtering in this way is to ensure that they do not have the same source_id as any other element on the page that also uses filtering. If not, unpredictable behavior may occur.


For example, let's say you have a "Trending" element that is filled with content from your news section, and filtered for the most read articles in that section. Unfortunately, you see that some articles appearing in the section are not actually trending, which you can verify by checking the respective articles' page views.

How to Verify and Solve

The first thing that should be checked is if the filtered element uses the same source_id as another filtered element on the page.

  • Go to the element where one of the problem posts appear.
  • Get the post's post ID. This can be taken from the end of the URL if your site includes it, or can be accessed in Entry Editor.

  • Type in your site's main address and append the following to the end of the URL: ?skeleton_logging=display
  • Search for the post ID using CTRL/CMD + F.
  • Confirm where it appears twice (the sources), as well as the names of those sources (the source_ids).

    For example, here you can see that the source Frontpage appears twice. One instance of Frontpage has been explicitly named news, while the other has been named current_page (this was done automatically).

  • In our Layout & Design tool, go to the element and view the code for the source_id that was explicitly set to news.

  • Here we can see that there are two elements with the same source_id, which is news in this case. Both elements have source="filtered" to filter the news posts. These filter attributes are ignored for the following reasons:
    1. One of the elements has source_url="current_page", while the other one has source_url="_most-read". The first one is processed by Skeleton as source="current_page", while the second is processed as source="popular".
    2. When the same source_id (news, in this case) is used twice on the same page, it can cause conflicts which are resolved by Skeleton overwriting attributes. In our example, the source attribute is overwritten so that the posts are no longer filtered as expected, causing non-trending posts to populate the trending page element.

In order to fix the issue in this example, the source_id needs to be changed to something other than news so it can serve the same purpose as filtering for the most popular posts. This will give the same desired result while avoiding the need to pull posts from the same source_id when using different filters for two post elements on the same page.

If, for whatever reason, it's necessary for two elements on the same page to use the same source_id, the filters must be the same for both elements. Otherwise, unpredictable behavior may occur.

If you have questions about this, email support@rebelmouse.com or talk to your account manager today.

Publishers No Longer Have to Submit Their Site to Google News

Google's Publisher Center creates new opportunities for audience growth

Just before the start of the next decade, Google announced an important change to its Google News offering with the launch of Google Publisher Center. The new interface merges Google News Producer and Google News Publisher into one to streamline the partnership process for publishers.

Overall, the change should make it easier for publishers to manage their Google News settings, including updating themes, directing URLs to section pages, and configuring user permissions. Read the full list of features here.

Keep reading... Show less

How to Find Work-Life Balance as a Remote Employee

Tips from our CEO on making the most of an office-free lifestyle

Working from home is becoming increasingly popular, with an estimated 66% of companies now allowing remote work and 16% operating completely office-free. RebelMouse is one of those fully remote companies, and over the years we've mastered how to stay close to each other despite being spread across more than a dozen countries. We believe working remotely is good for both our personal lives and our productivity. Read more about this here.

Still, working free from the shackles of an office environment doesn't mean every day is a dance party in your pajamas from 9 to 5. Working from home comes with its own set of challenges just like any other job.

Keep reading... Show less

Inside RebelMouse’s Quality Assurance Operations

How We've Perfected Stress-Free Publishing

At RebelMouse, we like to refer to our enterprise publishing platform as "lean tech." Most publishers have a natural inclination to start doubling down on teams of developers who try to build unique experiences to help stand out above the noise. But they should actually be doing the opposite: Lean tech is the preferred way to cut through content saturation. By allowing RebelMouse to obsess over your product, content producers, editors, managers, and everyone in between can focus on creating quality content and taking advantage of opportunities to leverage distributive publishing strategies that create real revenue growth.

One of the major reasons we're able to maintain a lean tech environment is thanks to our approach to quality assurance (QA). We make updates to our platform daily to ensure our clients always have access to the most robust, high-performing, and secure version of our platform. Behind the scenes, this means having a solid QA structure that's efficient, creates less bugs, and catches the ones that do pop up before they go live. It's a system of checks and balances that's hard and costly to replicate on a custom CMS. Here's a glimpse into how it works.

Our Tech Stack Toolbox

  • Cucumber
  • Java
  • Junit
  • Maven
  • Selenium WebDriver
  • TeamCity
  • Zalenium (Selenium Grid)

Our Checks and Balances Workflow

Automated Regression Testing Cycle

The Lifecycle of a Product Update

When an update is first made to RebelMouse, TeamCity immediately triggers the start of automated tests to review integrity.

TeamCity Build

TeamCity Agent

The tests run in parallel on TeamCity's Build Agent. Next, Zalenium creates docker containers with browsers that matches the count of parallel threads. An Allure report is then generated from the test results, which shows the state of the application after the update.

Allure Report Pass

If a test doesn't complete successfully, the testing framework receives a video with a failed test and attaches it to the Allure report.

Allure Report Issue

Based on the report analysis, a QA specialist will create a "bug" ticket in our product management software to address the issue if needed. Then, information about the bug is immediately sent to the project manager and we begin the process of correcting the problem.

The media powerhouses we power can publish with confidence knowing that any product issues that arise are met with a tried-and-true process to fix the problem with little-to-no disturbance to their workflow. If you have any questions about this process, please email support@rebelmouse.com.

Related Articles

Subscribe to Our Newsletter