Feature #661

Saving default configuration

Added by Magoni Bruno over 5 years ago. Updated over 3 years ago.

Status:RejectedStart date:
Priority:HighDue date:
Assignee:-% Done:

0%

Category:CORE
Target version:Unplanned
Sponsor: Ergonomic impact:
Functional impact:

Description

After installation process, default configuration values should be automatically setted during postflight process with setParams method
i.e.

if ($type == 'install') {
            require_once JPATH_ADMINISTRATOR . '/components/com_easysdi_core/helpers/easysdi_core.php';
            $params['infrastructureID'] = Easysdi_coreHelper::uuid();
            $this->setParams($params);
        }

To prevent managing such default value in multiple location inside easySDI, XML configuration of backoffice options must not contains anymore default values. These default values must be only driven by postflights processes.


Related issues

Related to easySDI - Defect #676: Error when creating a catalog Rejected

History

#1 Updated by Magoni Bruno over 5 years ago

  • Target version changed from 4.0.0 to 4.0.1

#2 Updated by Magoni Bruno over 5 years ago

  • Target version changed from 4.0.1 to Unplanned

#3 Updated by Magoni Bruno over 5 years ago

  • Priority changed from Normal to High

#4 Updated by Magoni Bruno about 5 years ago

  • Target version deleted (Unplanned)

#5 Updated by Magoni Bruno about 5 years ago

  • Status changed from New to Request For Comments

#6 Updated by Magoni Bruno about 5 years ago

  • Description updated (diff)

#7 Updated by Magoni Bruno about 5 years ago

  • Status changed from Request For Comments to Request For Votes

I think it's time to vote on such important feature...

#8 Updated by Magoni Bruno about 5 years ago

+1

#9 Updated by Mérour Xavier about 5 years ago

+1

#10 Updated by Magoni Bruno about 5 years ago

  • Assignee set to Steering Committee

#13 Updated by Magoni Bruno almost 5 years ago

  • Status changed from Request For Votes to Accepted
  • Assignee deleted (Steering Committee)

#14 Updated by Magoni Bruno over 4 years ago

  • Target version set to Unplanned

#15 Updated by Magoni Bruno over 4 years ago

  • Target version deleted (Unplanned)

#16 Updated by Magoni Bruno over 4 years ago

  • Target version set to Unplanned

#17 Updated by Blatti Yves over 3 years ago

  • Status changed from Accepted to Affected
  • Assignee set to Technical Committee

I think this is correctly done now...
... and the problem with infrastructure is solved.
Can we close this ?

#18 Updated by Van Hoecke Hélène over 3 years ago

  • Status changed from Affected to Rejected
  • Assignee deleted (Technical Committee)

This had be done in a previous 4.x.x version.

So this ticket is rejected by the TC.

Also available in: Atom PDF