Hi Steve, Allowing views to be in multiple collections introduces a lot of view access issues that were unfortunately outside the scope of the 1.3 release. It's definitely on the wishlist for future iterations though.
Thanks, Stacey -- Allow views to exist in multiple collections https://bugs.launchpad.net/bugs/658396 You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. Status in Mahara ePortfolio: New Bug description: The new collection feature is a great one. However, when a view is added to a collection it can't be reused; either in a collection or on its own. As an example, I may have created a CV view which I plan to use for all my job applications. I plan to create a new collection for each application as the jobs I'm applying for are in different areas. I therefore need to have a CV in each collection, and having to create a new CV view for each collection doesn't fit with Mahara's concept of reuse of content. In addition, I may wish to share just my CV with someone, and presently when they visit it they will see the navigation bar for the collection. It makes sense for views to exist separately to collections, rather than as part of them. (Mahara 1.3.1) _______________________________________________ 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
