Reviewed:  https://reviews.mahara.org/10264
Committed: 
https://git.mahara.org/mahara/mahara/commit/a8542d054e675a0869a917a1f357f0989399b205
Submitter: Robert Lyon (robe...@catalyst.net.nz)
Branch:    master

commit a8542d054e675a0869a917a1f357f0989399b205
Author: Lisa Seeto <lisase...@catalyst.net.nz>
Date:   Fri Aug 16 10:13:27 2019 +1200

Bug 1840368: Create page via tags not inserting all tagged artefacts
into DB

made the taggedblock dirty again so that it saves itself later with all
DB references.

Change-Id: I60d340b9a1924a43186a0f0a41cb632342c80a7d
Signed-off-by: Lisa Seeto <lisase...@catalyst.net.nz>

-- 
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/1840368

Title:
  Create page via tags not inserting all tagged artefacts into DB

Status in Mahara:
  Fix Committed

Bug description:
  It is possible to create a new page via tags.  When a journal entry is tagged 
and a new page is created via tags, the journal block will appear on the new 
page.  It will have a title that links back to the full journal entry, ie 
http://mahara/artefact/artefact.php?artefact=227&view=52  
  Clicking this link produces this error:
  Access denied
  You do not have access to view this page.

  Artefact 227 not in page 52

  It seems that when you create via tags, it is not inserting this
  journal entry artefact into the database.

  
  Mahara: 19.04.dev
  OS: Ubuntu 18.04.2
  DB: postgres
  Browser: Firefox 68.0.2

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

_______________________________________________
Mailing list: https://launchpad.net/~mahara-contributors
Post to     : mahara-contributors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mahara-contributors
More help   : https://help.launchpad.net/ListHelp

Reply via email to