[Portfolio] access to images, etc.

Charles Hedrick hedrick at rutgers.edu
Wed Feb 10 10:52:29 PST 2010

OK, so it looks like this won't work. The security advisor mechanism is more abstruse than I realized.

On Feb 10, 2010, at 11:35 AM, Charles Hedrick wrote:

> We have a continuing stream of problems with people not able to see things in public images. I can fix it for attachments that we process. But the moment we let students do things in FCK, the ability to do any kind of systematic fixup seems to go away.
> For the moment I'm thinking strongly of doing a replacement of /access/content/ in any fck-generated content with h /access/ospPresentation/SITE/PORTFOLIOID/content/   This could trigger falsely, but I think the number of times we are burned by it is going to be a lot less than the troubles we're currently seeing. Unfortunately XSL is such a dreadful language that it's hard for me to do better tests than that. 
> Another approach would be to do the replacement in the code that calls FCK. Then I'd have Java available and could do an HTML parse.
> Any better suggestions?
> _______________________________________________
> portfolio mailing list
> portfolio at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/portfolio
> TO UNSUBSCRIBE: send email to portfolio-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2669 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/portfolio/attachments/20100210/557d9914/attachment.bin 

More information about the portfolio mailing list