We are operating a subdirectory-based multisite.
Every time we push from devkinsta to remote, and transfer from remote staging to Live, the ‘DOMAIN_CURRENT_SITE’ in wp-config.php becomes ‘undefined’.
define(‘DOMAIN_CURRENT_SITE’, ‘undefined’);
We want ‘DOMAIN_CURRENT_SITE’ to automatically replace itself with the appropriate value for Live, staging (with subdirectory changes each time), and devkinsta.
We are also operating a single site on another site, and it automatically replaces itself.
Hello Keisuke 
This seems to be a bug and out developers are checking it. I found the same when you first reported an issue with the Multisite and DevKinsta.
It’s under review, but there’s no ETA so I’m not sure when is this going to be fixed. However, we are aware of the issue and intend to fix it.
@VladimirM
Thank you for your message. I understand that the issue is a bug. Could you please let me know if there are any measures or solutions currently available to address this issue?
Hello @keisuke 
At this moment, the only workaround is to change the line manually in wp-config on staging site before pulling to DevKinsta.
Until the bug is resolved, there’s no other workaround, I’m afraid.
I just wanted to add that we’re having the exact same issue as well and it would be great to get it fixed.
Hello @landyman
This should be resolved in DevKinsta version 2.3.15. which was released recently.
Can you please tell me what operating system, Docker version and DevKinsta are you using? If you still have DevKinsta 2.3.14, I would suggest backing up your local sites’ files and database and attempting update.
Kind regards!
Thanks @VladimirM ! I fired up DevKinsta, and I am using 2.3.14 (Ubuntu version, but running on Fedora); but when I check for updates, it claims there is no update. I’ll try again later, then re-install it clean if it still says there’s no update.
Hi, @VladimirM
I’m having the same issue.
I tried pushing again with this version:
・Docker Version 4.45.0
・DevKinsta Version 2.13.5
・multisite
But the staging config still shows DOMAIN_CURRENT_SITE as undefined.
Is there a specific version I should be using?
Can you tell me if this is occurring when pulling to DevKinsta, pushing to Staging or both?
Also, are you on Windows, Mac or other?
Kind regards!
Hi @VladimirM,
This issue occurs only when pushing to Staging.
When pulling to DevKinsta, there is no problem.
I’m using a Mac with macOS Sequoia 15.5.
After pushing, I can manually replace the staging config to fix the domain undefined issue,
but if this is resolved in a newer version of DevKinsta, that would be great.
Kind regards,
Hello @Makiko
I have tested again, and both pull and push don’t set ‘undefined’ on DOMAIN_CURRENT_SITE.
Can you please check that;
Kind regards