Ticket #36 (assigned defect)

Opened 1 year ago

Last modified 2 weeks ago

Asgard: Things breaking

Reported by: adrenalin Assigned to: tarjei (accepted)
Priority: critical Milestone: 9.03 Vinland
Component: Asgard Version: 3.0
Keywords: Cc:

Description

At the moment these thingies break other thingies:

Parse error in ROOT style of the current site

Breaking a configuration snippet of the component under which Asgard is run. This includes cases when pointing e.g. net.nehmer.static to use an broken/non-existing schema as default.

Change History

06/02/07 13:19:36 changed by adrenalin

  • component changed from MidCOM component to Asgard.

06/03/07 16:36:04 changed by bergie

We discussed this with Tarjei a bit, and it is not trivial. An idea for how to fix this:

Reflect what properties of what objects contain executable PHP code, and "test-eval" them before saving so we can catch errors and alert user of them (this would be a nice service regardless of the actual issue at hand)

There is some interesting discussion in PHP eval documentation

07/24/07 13:34:27 changed by bergie

(In [11332]) Codepress for editing typical PHP fields, try validating the code before saving. refs #36

09/17/07 21:48:35 changed by tarjei

  • owner changed from bergie to tarjei.
  • status changed from new to assigned.
  • milestone changed from MidCOM 2.8 to MidCOM 3.0.

Moving to 3.0 as the changes needed require Midgard 2.0

The main fix for 2.8 is running test-evals on the code submitted.

It will always be possible to brake midcom somehow if the startupfile is changed.

The best way to make this happen as little as possible is to move the midcom startup into a separate snippet from code-init and also read all config variables from yaml instead of setting them in php code.

=> Clearly 3.0 stuff.

09/17/07 21:48:40 changed by tarjei

  • version changed from 2.8 to 3.0.

09/30/08 14:34:15 changed by bergie

  • milestone changed from MidCOM 3.0 to 9.03 Vinland.