[Building Sakai] Creating HTML Document in Resource Too Sakai 10.x

[Mustansar Mehmood]

Well I set the property /content.useMimeMagic=false and did not help/

Applying the patch did not help either.
I went to truck QA server over the weekend  and somehow my browser 
attempts to download the file instead of displaying it
As far as Sakai 10 QA serverrs concerned it is hard to tell which one is 
the latest. I tried the indiana QA server had the same download effect.
http://qa3-us.sakaiproject.org:8086/portal/site/83596984-e77b-4288-ac90-61fcea9212c1/page/009bdc27-7fbc-4fee-8a4c-6a8db76bcd4f

On 08/08/2014 10:15 PM, Matthew Jones wrote:
> Yeah, I think we'd need some more info though it sounds like the issue 
> is filed as
> https://jira.sakaiproject.org/browse/SAK-27758
>
> But it looks like it's working on trunk.
>
> It's likely it's something with content type interpretation. This 
> should have been fixed by
> https://jira.sakaiproject.org/browse/KNL-1235 right before 10.0 was 
> out in a very late breaking RC.
>
> I feel like there was probably an edge case it missed. This patch 
> below contributed by Jacques is planned for 10.x (10.1) as soon as 
> it's it's QA'd in trunk (blocker for 10.1) and fixes this check and 
> improves the performance. I've tested locally and it passes the unit 
> test so I think it's good to go.
> https://jira.sakaiproject.org/browse/KNL-1281
>
> If you set
> /content.useMimeMagic=false /
> does it work any better for now? (Or apply the patch on KNL-1281)
>
>
>
> On Fri, Aug 8, 2014 at 8:22 PM, Sam Ottenhoff <ottenhoff at longsight.com 
> <mailto:ottenhoff at longsight.com>> wrote:
>
>     Are you able to replicate on a QA instance? If yes, can you file a
>     JIRA with exact steps to replicate?
>
>     On Aug 7, 2014 10:01 PM, "Mustansar Mehmood" <mustansar at rice.edu
>     <mailto:mustansar at rice.edu>> wrote:
>
>         Hi,
>           It seems, creating HTML page in resource tool  using a
>         WYSIWYG editor
>         leads to raw HTML being displayed unless we edit the source
>         and enclose
>         the 'page' in div or html tag as a work around.
>         I am trying to locate a simpler solution/workaround for end users.
>         Any ideas?
>         Thanks
>           Mustansar
>         _______________________________________________
>         sakai-dev mailing list
>         sakai-dev at collab.sakaiproject.org
>         <mailto:sakai-dev at collab.sakaiproject.org>
>         http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
>         TO UNSUBSCRIBE: send email to
>         sakai-dev-unsubscribe at collab.sakaiproject.org
>         <mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a
>         subject of "unsubscribe"
>
>
>     _______________________________________________
>     sakai-dev mailing list
>     sakai-dev at collab.sakaiproject.org
>     <mailto:sakai-dev at collab.sakaiproject.org>
>     http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
>     TO UNSUBSCRIBE: send email to
>     sakai-dev-unsubscribe at collab.sakaiproject.org
>     <mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a
>     subject of "unsubscribe"
>
>


-- 
Mustansar Mehmood
Educational System Developer& Integrator

Information Technology
6100 Main St. MS 119
Houston Texas 77005

Phone:(713)348-2523
Fax  :(713)348 6099
email:mustansar at rice.edu





I have yet to see any problem, however complicated, which, when,you  looked at it in the right way, did not become still more complicated.
     -- Poul Anderson

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140811/67c1fcb1/attachment.html