Developer edition mashlets not working

burnsj1
User offline. Last seen 1 year 47 weeks ago. Offline
Joined: 01/14/2010
Points: 10

I am new to Presto.  Is there an issue with Mashlets in the developer edition?  I have Presto 2.7.0 running on another host than the host I am loading the mashet from.  I can see the mashlet in the standalone page, however when I embed the script tag in a new HTML document then nothing is displayed.  I see all of the javascript and css includes loading, but the display is blank.  This worked during development when I had Presto 2.7.0 on the same host machine as the requesting HTML document.  I also noticed that when I go to share the mashlet, all of the links are releative links (no http://...) so I prepend with the correct host so it works over the network.

 

Is this an issue that can be resolved with a production license (which we have, just haven't upgraded yet).

 

Thanks,

Josh Burns

0
Your rating: None
jeremy.pitten
jeremy.pitten's picture
User offline. Last seen 2 weeks 6 days ago. Offline
Joined: 09/22/2008
Points: 275

There is a known issue that mashlet share panel icons fail to display if the mashlet web page is not hosted on teh same box as presto, but the share links should work, for example if you get the share script tag it shoul dcorrecly include the full mashlet script url.

From what you describe, the mashlet script tag mashlet url is ok, allowing the mashlet to reach back to presto to load the mashlet scripts/css, but then the mashlet fails to render. I dont know if this is a custom mashlet implementation or a standard Presto.ServiceMashlet (created in mashlet maker), if it is a service mashlet then I see no reason why it isnt working but if it is a custom mashlet then it sounds like teh mashlet is failing to retrieve service data prior to rendering. It may be that the mashlet is using a Presto.Connection which isnt initialised to connect back to Presto rather than the server the web page is hosted on. If a mashlet needs to connect back to presto to invoke a published service then it should be using the connection owned by the mashlet (and can be accessed as a property of the mashlet).

If you can share the mashlet implementation with us, either here or contact JackBe directly, then we can check the above.

Thanks