search

tuankhac / share-extras

Automatically exported from code.google.com/p/share-extras
0 stars 0 forks source link

Site-geotagged-content-dashlet not working under Alfresco Share 4.0a CE #50

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. install the Site-geotagged-content-dashlet
2. add dashlet to the user dashboard
3.

I expect to see the Google maps dashlet, instead I get:

An error has occured in the Share component: 
/share/service/components/dashlets/site-geo-content.
It responded with a status of 500 - Internal Error.
Error Code Information: 500 - An error inside the HTTP server which prevented 
it from fulfilling the request.
Error Message: 09260000 Failed to process template 
org/alfresco/components/dashlets/site-geotagged-content.get.html.ftl
Server: Alfresco Spring WebScripts - v1.0.0 (Final 905) schema 1.000
Time: 26-okt-2011 11:19:12
Click here to view full technical information on the error.

Version 0.2 of the Dashlet

What version of Alfresco are you using? On what application server?

Version 4.0a CE on Windows server 2008 64 bit with Tomcat 6

Safari (Lion) and Firefox

Please provide any additional information below.

Original issue reported on code.google.com by rge.hann...@gmail.com on 26 Oct 2011 at 9:24

Attachments:

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
If the Browser in US English the dashlet works under 4.0a CE. If the browser as 
Dutch language, the Alfresco uses the Dutch language files and we get the error 
described above.

I added a Dutch translation file for site-geotagged-content.get.properties, but 
still the same error.
The GPS information is international with a . ( 54.113) But the error say it 
expects a number and gets 54,113.

Any idea how I can fix this? If the Browser in US English the dashlet works 
under 4.0a CE however.

Original comment by rge.hann...@gmail.com on 26 Oct 2011 at 11:06

GoogleCodeExporter commented 8 years ago 
This should be fixed in the 0.2.1 release I've just added to the downloads 
page. Please could you re-test and let me know if this works OK for you?

Original comment by will.abson on 7 Nov 2011 at 2:57

GoogleCodeExporter commented 8 years ago 
Reported notified as Fixed

Original comment by will.abson on 11 Nov 2011 at 5:21