On Wed, Aug 14, 2013 at 11:38 PM, Lakmali Baminiwatta wrote:
> Hi,
>
>
> On 14 August 2013 23:21, Lalaji Sureshika wrote:
>
>> Hi Vijitha,
>>
>> Sorry,I was referring to a different i18n related error from my previous
>> reply. Your getting error is due to i18n module is not available with
>> pac
Hi,
On 14 August 2013 23:21, Lalaji Sureshika wrote:
> Hi Vijitha,
>
> Sorry,I was referring to a different i18n related error from my previous
> reply. Your getting error is due to i18n module is not available with
> pack.Can you check whether a folder called i18n exists in location
> "{GREG_
Hi Vijitha,
Sorry,I was referring to a different i18n related error from my previous
reply. Your getting error is due to i18n module is not available with
pack.Can you check whether a folder called i18n exists in location
"{GREG_Home}/modules".
There was an issue on that jaggery related modules n
Hi Vijitha,
This is due to the changes done for APIM with i18n module is not sync with
latest jaggery git repo i18n module.We encountered this issue and I have
already committed the changes to jaggery git repo and hope this fix will be
available with next pack building cycle..
Thanks;
On W
This was a build with yesterday's updates.
Get an empty page for the store and the below for the publisher
(http://:9763/publisher).
Is this tested with recent jaggery changes etc...?
[2013-08-14 16:30:27,656] ERROR
{org.jaggeryjs.jaggery.core.manager.CommonManager} - A module cannot be
found
