RebelMouse Talk to Us

You can always control the posts displayed from A .xml file. by using the following attributes with <posts> tag;

P.S : If you use <posts> tag without the source attribute, it will use the frontpage source as default.


<posts ... /> 

Here is a list of the attributes that you can use to control pulled out posts source

  • "limit" : Controls the number of posts pulled from source with these Attributes
<posts limit="10" ... /> 

In the example above, it only displays only 10 posts from the source

  • source_unique="true" :Excludes duplicates found in blocks .
<posts source_unique="true" ... /> 
  • source="current_page" :is converts into one of the following sources: tag, search_result or frontpage
<posts source="current_page" ... />
  • source="search_result" : When you use "search_result" attribute , it will display posts found by a search phrase from the request
<posts source="search_result" ... /> 
  • source="frontpage" : Displays posts from Home section
<posts source="frontpage"> 
  • source="frontpage" seciton_url="politics" Using "section_url" attribute along with "source" attribute it would show posts from the section URL added , like example below :
<posts source="frontpage" seciton_url="politics" ... />

Displays posts from Politics section on front page

  • source="frontpage" section_url="{{post.section}}" : displays posts from current post's primary section (or one of the secondary sections if not primary section defined).
<posts source="frontpage" section_url="{{post.section}}" ... />
  • source="saved" :Displays posts from those that user saved/liked (should have been liked but whatever)
<posts source="saved" ... />
  • source="tag" : displays posts with one of the tags matching tag from the request
<posts source="tag" ... /> 
  • source="tag" tag_name="example_tag" : displays posts with one of the tags matching "example_tag" tag
<posts source="tag" tag_name="example_tag" ... /> 
  • source="tag" order="primary" :displays posts with primary tag matching tag from the request Falls back to matching secondary tags.
<posts source="tag" order="primacy" ... /> 
  • source="popular" : displays posts ordered by pageviews from the last 1 hour.
<posts source="popular" ... /> 
  • source="popular" interval="6" unit="hour" : displays posts ordered by page-views from the last 6 hours
<posts source="popular" interval="6" unit="hour" ... /> 

-- (soon deprecated)

  • source="popular" period="6h" : displays posts ordered by page-views from the last 6 hours.
<posts source="popular" period="6h" ... /> 

-- (soon introduced)

  • source="popular" period="lifetime" : displays posts ordered by page-views from all time.
<posts source="popular" period="lifetime" ... /> 

-- (soon introduced)

  • source="popular" [sections_filter] : displays posts ordered by pageviews from the last 1 hour and filtered by sections (see below)
<posts source="popular" [sections_filter] ... />
  • source="related" : displays posts which tags match one of the tags of the current post. it falls back to posts which sections match primary section of current post.
<posts source="related" ... />

if you need to Disable the fallback

<posts source="related" no_fallback="true" />
  • source="related" [sections_filter] : displays posts which tags match one of the tags of the current post filtered by sections
<posts source="related" [sections_filter] ... /> 
  • source="related" from_tags_of_current_post="false" [sections_filter] : displays posts filtered by sections
<posts source="related" from_tags_of_current_post="false" [sections_filter] ... /> 
  • source="related" [tags_filter] : displays posts filtered by tags (see below)
<posts source="related" [tags_filter] ... />
  • source="related" [period_filter] : displays posts filtered by publishing date
<posts source="related" [period_filter] ... />
  • source="related" post_per_section="true" from_sections="politics,health-care" :

displays at most 2 posts -- one from Politics and one from Health Care

<posts source="related" post_per_section="true" from_sections="politics,health-care" ... />

Sections Filter:

  • from_sections_of_current_post="true" : keeps posts which sections match one of the current post's sections
<posts ... from_sections_of_current_post="true" ... />
  • from_sections_of_current_post_other_than="section_name"

keeps posts which sections match one of the current post's sections excluding those that are in section_name mentioned.

<posts ... from_sections_of_current_post_other_than="section_name" ... />
  • from_sections="section1, section2" : keeps posts from section1 and section2 sections
<posts ... from_sections="section1, section2" ... /> 
  • from_sections_other_than="section1, section2" : ignores posts from section1 and section2 sections
<posts ... from_sections_other_than="section1,section2" ... />
  • from_sections="section1" from_sections_other_than="section2" : keeps posts that are in section1 but not in section2
<posts ... from_sections="section1" from_sections_other_than="section2" ... />

Tags Filter:

  • from_tags_of_current_post="true" displays posts which tags match one of the tags of the current post (default behavior of related source)
<posts ... from_tags_of_current_post="true" ... /> 
  • from_tags="section1" displays posts which tags include "section1" tag

<posts ... from_tags="section1" ... />

  • from_tags_other_than="section1" : displays posts which tags do not include "section1" tag
<posts ... from_tags_other_than="section1" .../>

Period Filter:

  • interval="12" unit="day" : (soon deprecated) either used to define page-views period for popular source or publishing date for related source
<posts ... interval="12" unit="day" ... />
  • period="12d" : (soon introduced) either used to define PVs period for popular source or publishing date for related source
<posts ... period="12d" ... /> 
  • published_before_current_post="true" : Used in related source to keep only posts that are older than the current one.
<posts ... published_before_current_post="true" ... />
Build on a Better PlatformReady to See More?
Request a Proposal
People on a train station
Rebel Insights

RebelMouse Q1 2021 Platform Updates

Speed, performance, and Core Web Vitals enhancements

Click here to read our Q2 2021 platform performance updates!

At RebelMouse, we pour our souls into making sure that our platform is always the most modern, high-performance CMS on the market. In fact, we invested over $100,000 worth of hours into our platform in Q1 2021 alone. This has resulted in updates and performance enhancements that publishers would have to pay for on their own to make happen on any other platform, such as WordPress. We're proud to be at a level of scale where we can invest this way into our platform, and we will continue to invest at this rate every quarter moving forward just as we have in the past.

Here are the major updates that we've added to the platform in Q1.

Keep reading... Show less
Build on a Better PlatformReady to See More?
Request a Proposal
An Important Note on Site Quality From Google’s Search Expert
Rebel Insights

An Important Note on Site Quality From Google’s Search Expert

Do you ever wonder if a few typos can impact your site’s search performance? According to Google’s Search Advocate John Mueller, it takes more than just a few grammatical missteps for Google’s crawler to determine your site’s quality.

During a New Year’s Eve Office Hours hangout, Mueller said that if certain portions of a website are deemed low quality, it can negatively impact the site’s search ranking overall. A good example of this is a site that has different language versions within the same domain. If the site has a French-language version that is made up of quality content, but the English translation isn’t up to the same standard, the ranking of the French version of the site could be negatively impacted.

Keep reading... Show less
Build on a Better PlatformReady to See More?
Request a Proposal