Folders in views don't allow access to subfolders and subfolder content until full parent cache rebuild

[Nigel-catalyst]

Steps:

1. Put a folder in a View
2. Add a subfolder to the folder in My Files, put a file in it
3. Try to access that new file through the View (you can click on the folder block's title to go browsing through it, or on the subfolder name itself)

Expected: You can access and download the folder (in fact, anyone who can see the view should be able to do this

Actual: The file isn't available until the full parent cache rebuild happens in cron.

This rebuild only happens once a day, so this isn't desirable.

There's actually a mechanism to mark rows in the artefact parent cache (APC) as dirty so that things like this don't happen, so I wonder why that mechanism isn't working?

From http://mahara.org/interaction/forum/topic.php?id=1062 as reported by Olaf Perlick.

This bug was imported from eduforge.org, see:
https://eduforge.org/tracker/index.php?func=detail&aid=3395&group_id=176&atid=739

[Richard Mansfield (richard-mansfield)]

Files in subfolders should now be accessible after the partial (dirty) parent cache rebuild every minute.

[Craig Eves (ceves)]

I just had someone describe the same problem accessing a subfolder in their view.

I logged in as them Shelley Lock and couldn't access the standard 5a subfolder in their view.

http://myportfolio.ac.nz/view/artefact.php?artefact=109081&view=12351

This was resolved by deleting and creating the folder in the view.

Craig

[Richard Mansfield (richard-mansfield)]

Hi Craig,

This fix is in Mahara 1.1.7 and will be available when you next upgrade.

R.

[Craig Eves (ceves)]

Thanks Richard

It looks like we are using Mahara version 1.1.7testing (2009022620)
Do we need to request an upgrade or does a minor upgrade just happen?

Craig

[Richard Mansfield (richard-mansfield)]

Hi Craig,

That 1.1.7testing probably would have been created just after the 1.1.6 release, so it's a little bit older than the latest which is currently 1.1.8testing (2009022623).

I'm not sure what the normal process is for you guys with minor upgrades, I suspect they happened when Nigel got around to it. Unfortunately they can't be automated for customised sites. A real human needs to actually merge the latest 1.1.7 in to your branch, build a package and deploy it to the server, but it's not too painful for minor upgrades.