← Back to team overview

mahara-contributors team mailing list archive

[Bug 1758181] A change has been merged

 

Reviewed:  https://reviews.mahara.org/8857
Committed: https://git.mahara.org/mahara/mahara/commit/1bf98911e8639efbdcbff3de4868d47d0c3ec81d
Submitter: Robert Lyon (robertl@xxxxxxxxxxxxxxx)
Branch:    master

commit 1bf98911e8639efbdcbff3de4868d47d0c3ec81d
Author: Sarah Kirby <sarahkirby@xxxxxxxxxxxxxxx>
Date:   Wed Apr 4 16:30:51 2018 +1200

Bug 1758181: Hide comment-container div if comments

are not present or enabled

behatnotneeded

Change-Id: Ie47a4e8735a8cc4fb13640a6c991b8af0c32171c

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1758181

Title:
  Extra div field when comments are turned off on page or artefact
  details page

Status in Mahara:
  Fix Committed

Bug description:
  Environment tested: Master
  Browser tested: MS Edge (Virtualbox)

  ===================
  Manual Test Script
  ===================

  1) user has a portfolio page with one resume field block that is set to retract on it 
  2) user views Page displayed 
  3) user clicks the details link just below the one resume field block
  4) user is redirected to a page only showing the one resume field block

  Actual result: Page is displayed with the one resume field block and
  is retracted.✔ Just under the block area is a very light grey
  background section on the page ✘

  
  Expected result: Light grey background section should not be displayed because this artefact cannot have a comment.

  NOTE: 
  - this also happens when you have a page that does not allow comments. (could be any page without comments)
  - this is visible in themes that have a background for the comment area 

  Catalyst QA

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1758181/+subscriptions


References