Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
I
ISPConfig 3
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 509
    • Issues 509
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 33
    • Merge Requests 33
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #5198

Closed
Open
Created Dec 10, 2018 by Helmo@helmoReporter

Convert tform events from client domain edit to plugin

While working on the domains_domain_update api function in !845 (merged) I noticed that events didn't trigger like when updating a client domain via the webUI.

@tbrehm mentioned:

tform actions are not executed by the api. The api executes plugins but this code was written before the interface plugins were introduced in ispconfig. So basically the code needs to be migrated to a plugin. But we will have to be careful to not break existing API applications which do the changes on their own.

Another related issue:

  • #3997 - maildeliver plugin

the code in onAfterUpdate() in interface/web/client/domain_edit.php would have to go to I guess a new file interface/lib/plugins/client_domain_plugin.inc.php

An example for the structure could be in ./interface/lib/plugins/mail_mail_domain_plugin.inc.php

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None