mahara-contributors team mailing list archive

[Don Presant <896890@xxxxxxxxxxxxxxxxxx>]

I haven't seen a mockup, so am visualizing this in my mind...

Are we hanging onto the collection name for a specific user reason, or
because it's easier to code?

To me, it's redundant to have the collection name in addition to the
page name, if you are using a collection block.

Will anything change for tabbed collections? Having the same solution
means the page titles are redundant.

That said, the suggested improvement is better than what we have now.

My 2 cents.

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
https://bugs.launchpad.net/bugs/896890

Title:
  Collection title overrides page title

Status in Mahara ePortfolio:
  In Progress

Bug description:
  When pages in a collection are displayed, the title that appears at
  the top of the pages is the title of the collection, not the title of
  the particular page.

  Is this a bug or a feature? I see it as a bug.

  In this case below, a page enttitled "Professional Page" looks like it's called "Site Index", which is just wrong:
  http://careerportfolio.mb.ca/view/view.php?id=1209

  Is there a reason to have it the other way? Could it be accommodated in other ways, such as optionally having:
   "CollectionTitle: PageTitle" ?

  Mahara 1.4 , LAMP
  FF and IE (at least)

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