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 489
    • Issues 489
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 25
    • Merge Requests 25
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ISPConfig
  • ISPConfig 3
  • Merge Requests
  • !640

Merged
Opened Sep 12, 2017 by Ispcomm@ispcomm

Primary ID force for remoting api on insertion of new objects

  • Overview 0
  • Commits 6
  • Changes 3

Patch based on the thread here: https://www.howtoforge.com/community/threads/add-site-with-specified-system_user-via-remoting-api.77236/

Basically, when a new object (primarily site) is added via remoting, this patch allows to specify the primary domain_id of the site and following sys_userid and resulting path.

If a _primary_id is passed in the $params array, then this is used on the SQL insert operation. If a same id exists on the system, an error will be returned (mysql error for duplicate primary key value).

_primary_id is only available in the remoting api and is not found in the standard $forms of the app.

Based on implementation idea by @tbrehm

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Reference: ispconfig/ispconfig3!640
Source branch: till_primary_force

Revert this merge request

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.