Not all form caches will drop at central site

Bug #795022 reported by Carl Leitner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Human Resource Information System for Tanzania
Confirmed
Low
Sovello Hildebrand

Bug Description

Dropping all forms from the form cache produces the message below. It is likely because the form storage is misconfigured

    Unable to setup cached form employee_status:Cannot instantiate employee_status
    Unable to setup cached form employer:Cannot instantiate employer
    Unable to setup cached form isco_88_major:Cannot instantiate isco_88_major
    Unable to setup cached form isco_88_minor:Cannot instantiate isco_88_minor
    Unable to setup cached form isco_88_sub_major:Cannot instantiate isco_88_sub_major
    Unable to setup cached form isco_88_unit:Cannot instantiate isco_88_unit
    Unable to setup cached form leave:Cannot instantiate leave
    Unable to setup cached form notes:Cannot instantiate notes
    Unable to setup cached form title:Cannot instantiate title
    Unable to setup cached form tribe:Cannot instantiate tribe
    Unable to setup cached form ward:Cannot instantiate ward
    Dropped all tables

Carl Leitner (litlfred)
Changed in pmoralg:
importance: Undecided → Medium
Revision history for this message
Carl Leitner (litlfred) wrote :

We are getting these errors because the form factory (I2CE_FormFactory) cannot determine the form class associated to the form. I think that the problem is that the forms are defined in the form storage modules but not properly defined in magic data.

There are two types of problems here:
1) There is form storage defined for something that is not a form. For example, tribe has it's form storage set, but in the Demographic module, the tribe form field is STRING_LINE and not a MAP, so it means that there probable should not be a form called "tribe". You should probably do something like <erase path="/modules/forms/forms/tribe"> in the ihris-manage-pmoralg module

2) There is form storage defined for a form, but the module defining that form is not turned on. For example this is the case with the ISCO codes. (As an aside, I would use the ISCO 08 codes and not the ISCO 88 codes -- the numbering is the year that the codes were released)

Problem 1) should be fixed. Problem 2) can be ignored as long as you don't mind those warning messages.

Changed in pmoralg:
assignee: nobody → Sovello Hildebrand (sovellohpmgani)
importance: Medium → Low
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.