Page 2 of 2

Custom component issues

Posted: Mon Dec 01, 2014 2:40 pm
by Evgene Karachevtsev

Hello Simon,

Unfortunately this is the bug. We reported it and will get back to you with the update, when we have any info from our development team. Sorry for the inconveniences.


Custom component issues

Posted: Tue Dec 02, 2014 2:17 pm
by Simon McGinnes

Thanks Evgene.

I don't know if it is connected, but now my app (the same one, 'adaptive') is getting many errors. For example, the login page no longer works - after clicking the login button, a javascript error occurs: "Uncaught Error: c15r: component not found" in component-manager.js. I haven't made any changes on the login page, as far as I know.

Regards,
Simon


Custom component issues

Posted: Wed Dec 03, 2014 12:21 pm
by Alena Prykhodko

Hello Simon,

Uncaught Error: c15r: component not found should be fixed in the nearest release.

As to component breaking apart - no ETA unfortunately.
As workaround please try to recreate identical component and break it apart, this works for us.


Custom component issues

Posted: Wed Dec 03, 2014 1:47 pm
by Simon McGinnes

Hi Alena,

Can you offer any workaround for the 'uncaught error' problem, or suggest how I can track down what is causing it? At present my app does not work and I'm unsure how to proceed, short of abandoning the whole thing and starting again.

I suppose I could try deleting pages one at a time until the problem goes away!

Regards,
Simon


Custom component issues

Posted: Thu Dec 04, 2014 1:55 pm
by Evgene Karachevtsev

Hello Simon,

Unfortunately there isn't any workaround. We do our best to fix this bug. For now you may consider using old builder. We are sorry for inconvenience


Custom component issues

Posted: Thu Dec 11, 2014 7:32 am
by Evgene Karachevtsev

Hello Simon,

There is information about one of your bugs (c15r)
Please do the following:

  1. Go to Custom components - conceptList. Open Data tab, there is the service without a name. Please fill in the name, so it would be not empty.
  2. Open Success mapping for this service and make at least one mapping (for examle from body.$. to conceptListItem). Click Save and return, then click Save at the top. Then reopen this Success mapping and remove this mapping (the one that from body.$. to conceptListItem) or you can make the correct mapping from the drist try and save all. This is necessary in order to rewrite the wrong mapping.

Custom component issues

Posted: Thu Dec 25, 2014 7:18 pm
by Alena Prykhodko

Hello,

c15r: component not found is fixed now.