Uploaded image for project: 'Planet4'
  1. Planet4
  2. PLANET-1863

Investigate: Remove the need for both Categories AND PageTypes of pagetypes

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Should have Should have
    • None
    • None
    • 8
    • Pages
    • Sprint #31, Sprint #32

      Currently we have in the GPI website both Categories and a custom taxonomy field PageType, that have the same data: Story/Publication/Pressrelease.

      This creates inconsistencies, and it creates the need for extra functionality (that was described at PLANET-1642).

      After an initial investigation, we have both of these for the following reasons:

      a) Categories

      Assigning a post to a category gives it the relevant permalink url. Example:

      https://www.greenpeace.org/international/*story*/14967/when-will-samsung-announce-something-that-actually-matters/

      Also, it makes it easier to filter them on the backend (using the category filter).

       

      b) Page type:

      It is used in the plugin-blocks , in "Content four column" (so that editors can select what to show), and in the articles block (appearing in the front end).

       

      In order to drop one of the two, the functionality mentioned above, would need to be trasnfered.

       

      Notes: At first it seemed like a solution could be to create a new parent category "pagetype", move the three categories we have under them, and rewrite the functionality in the blocks.

      But if we follow this solution, then the url's get rewritten to /international/pagetype/story

      If we follow this, then we need to ensure that only the last part of the url is used for the permalink.

      (Currently this is not possible, we would need to overide the default functionality).

       

       

       

            kkokkoro Konstantinos Kokkorogiannis (Inactive)
            kkokkoro Konstantinos Kokkorogiannis (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: