Craft CMS  

• This site just recently moved from Continuum/ePub to Craft on 2/22/23

• Admin login: https://www.reliasmedia.com/admin/login  

  • FCME shares the Craft CMS Instance with Relias Media

  • Reach out to Kenny Joa if you help logging in, resetting password, or creating an admin account for you.

• When you select an item from the left hand navigation menu in the admin panel, be sure to click on “relias media” and change to “free cme” on the drop down menu.

...

To override general settings: Entries > FreeCME - Specialities - Template > Asthma & Allergies >

Redirects

 All redirects are currently run through a plugin called Retour. Retour allows you to implement individual and bulk URL redirects on multiple domains through a simple interface.

Individual Redirects

• Best for a small number of redirect requests and is more user-friendly.

• Retour: How-to Guide

Individual Redirects - How-to:

In the Craft CMS side-menu, select the following:

Retour >>> Redirects >>> New Static Redirect (red button)

The screen should look like this:

...

Once here, you’ll follow the following steps to successfully implement a redirect:

• Enabled: Make sure this button is green

• Sites: Select your particular domain, here we’ll use “Relias Media”. This redirect will only process for the selected domain.

• Legacy URL Pattern: Here you have 2 options, you can either put in the full URL pattern or the URL path after the domain. I prefer using the URL path (in the case of internal links) in case the domain name is ever updated.

  • For this example we’ll use “/testBrokenPage”

• Legacy URL Match Type: You can choose between Path Only or Full URL. Since we chose to use a URL path for this example, we’ll select “Path Only”.

• Destination URL: Here you will paste in the URL you’d like the old URL to route to. Since the Legacy URL was put in as a path, this URL will also need to be a Path Only URL.

  • For this example, we’ll use “/testWorkingPage”

• Match Type: For mostly all cases, choose Exact Match. If you are replacing bulk URLs through RegEx, you will select RegEx Match (consult with engineering or a teammate to validate your Regex before submitting this)

• Redirect Type: For most cases, you’ll choose 301 for links that are permanently moved. For other types of redirects, see the following codes to determine whether they are applicable:

  • 302 - Found. This is an older protocol for a temporary redirect that would redirect to a new URL but search engines would not update their links to the resource. There are very few use cases for using this response code.

  • 307 - Moved Temporarily. Useful for a link that will be updated to a new destination shortly. This is the current response code for temporary redirects.

  • 308 - Moved Permanently. This method indicates that a resource has been definitively moved to a new URL indicated by the Location header. Link juice is passed on to the new link, but the request method and body are not altered.

  • 410 - Gone. A link is permanently removed. This should be used if a link is never to be used again and needs to be removed. This differs from a 404 in that the broken link tells search engines that it is permanently removed, not that it may potentially restored (404).

Bulk Redirects - How-to:

Navigation: Retour >>> Redirects >>> Import CSV File

Before getting to this step, you’ll want to prepare your file. Name your headings as follows:

• Legacy URL Pattern - URL that needs to be redirected

• Redirect To - New destination URL

• Match Type - use “exactmatch”. This is case sensitive.

• Site ID - “ReliasMedia” or “Free CME”. If it is for both sites, this column can be omitted or the variable “All Sites” can be used.

• HTTP Status - your status code, for most redirects you will use “301”

Export this file to a .csv file, UTF-8 works perfectly.

Once in the field mapping menu, you’ll prompted to match up any fields that aren’t automatically matched up. Several file fields will be left blank, which is fine.

...

Once these are matched up select “Import” and your redirects should go through successfully. QA these changes on the live site, as these should push live instantly. If you do not see the changes, clear your cache and view the page again. Report any issues to your manager or site admin.

How to Update Overall Site Settings & Schema Markup Data:

...