Welcome, Guest
Username: Password: Remember me

TOPIC: [FIXED] My Component 101 is now failing after migration

My Component 101 is now failing after migration 20 Aug 2015 08:05 #13388

  • jonathanbell
  • jonathanbell's Avatar
  • Offline
  • Premium Member
  • Posts: 147
  • Thank you received: 5
  • Karma: 1
Please help. My component Safety101 is now having trouble since the migration. Sandbox does not open it. I have downloaded the component and placed it on a trial site without my custom coding and some of the views now don't work. I had about six more minor changes to make after months of testing and should have completed this ready for final release this weekend.

My last post seems to have died as well.!

This is extremely bad timing. Can this be sorted as soon as possible. :(
The administrator has disabled public write access.

My Component 101 is now failing after migration 20 Aug 2015 08:24 #13389

  • admin
  • admin's Avatar
  • Offline
  • Administrator
  • Chef
  • Posts: 3711
  • Thank you received: 987
  • Karma: 140
I check it.
Coding is now a piece of cake
The administrator has disabled public write access.

My Component 101 is now failing after migration 20 Aug 2015 08:36 #13390

  • admin
  • admin's Avatar
  • Offline
  • Administrator
  • Chef
  • Posts: 3711
  • Thank you received: 987
  • Karma: 140
The default value you have inserted in Incident Actions > Incident is causing the problem.

Because of the unix type. I will fix it, but for the moment if you want to generate, just change this datetime default value.

Hope it helps
Coding is now a piece of cake
Last Edit: 20 Aug 2015 08:38 by admin.
The administrator has disabled public write access.

My Component 101 is now failing after migration 20 Aug 2015 16:50 #13395

  • jonathanbell
  • jonathanbell's Avatar
  • Offline
  • Premium Member
  • Posts: 147
  • Thank you received: 5
  • Karma: 1
Thanks. I'll have a look later in the day to have a look once you have sorted out the other stuff. Fingers crossed it all gets sorted.
The administrator has disabled public write access.

My Component 101 is now failing after migration 20 Aug 2015 16:55 #13396

  • admin
  • admin's Avatar
  • Offline
  • Administrator
  • Chef
  • Posts: 3711
  • Thank you received: 987
  • Karma: 140
For the moment I am still in the problem, it is really strange and long to fix.
For the rest, the migration went super good. All your datas are safe and even the builder even runs little bit faster.

In the coming hours I will put the builder in maintenance so better you come back tomorrow. Guess everything will be ok.

By the way, you still can download your creations and work anyways. Just the sandbox lacks.

Note: At the moment, when you force to pass with 'Retry' at 'uninstall', and then you stop at the install error, then your component IS now installed in sandbox.
It works I think.

They are only messages coming from I don't know wich (JFolder::) instance.
Coding is now a piece of cake
The administrator has disabled public write access.

My Component 101 is now failing after migration 20 Aug 2015 17:06 #13397

  • jonathanbell
  • jonathanbell's Avatar
  • Offline
  • Premium Member
  • Posts: 147
  • Thank you received: 5
  • Karma: 1
Thanks , I understand. The date autofill was on another action form as well.It didn't affect the component in the last build. I have removed and downloaded for testing. Appreciate you have a big job with the migration and see the server will be down shortly. I must go back to bed :)
The administrator has disabled public write access.

My Component 101 is now failing after migration 20 Aug 2015 18:04 #13398

  • admin
  • admin's Avatar
  • Offline
  • Administrator
  • Chef
  • Posts: 3711
  • Thank you received: 987
  • Karma: 140
Fixed.

Thank you for your patience
Coding is now a piece of cake
The administrator has disabled public write access.
Time to create page: 0.066 seconds

Get Started