David Stone

Can you look for log files in /wp-admin/network/admin.php?page=wp-ultimo-view-logs on your site? It’s Network dashboard -> Events -> View Logs. Then in the right widget select the log to view. Look for logs like domain-creation.log and domain-domain-nameX.log. And anything with cpanel. You can paste the relevant parts of the logs here or use https://ultimatemultisite.com/support/

What hosting integration are you using? Where do you expect the subdomain to be created automatically?

There is a log file created for each domain. In Ultimate Multisite -> Events -> View Logs or this path on your main domain /wp-admin/network/admin.php?page=wp-ultimo-view-logs will let you review all the log files and may give a clue why the subdomain is not being created.

If you can setup a wildcard *.domain.com in your host provider it will give the best experience for your customers but not all hosts will support wildcard subdomains.

2.6.0 has a bug fix for site selection in some context. Please update and try again.

Here’s a draft response:

Thanks for reaching out.

The “My Sites” dropdown in the admin bar behaves differently depending on the user’s role:

Super admins / network administrators — Ultimate Multisite intentionally hides customer-owned sites from this dropdown. On a network with many customer sites the list would become unmanageable, so it only shows non-customer sites (main site, templates, etc.). All customer sites remain accessible through the Ultimate Multisite > Sites page in the network admin.

Regular customers / site owners — The plugin doesn’t modify the dropdown for these users at all. WordPress handles it natively and lists every site the user has a role on, regardless of how it was created.

Could you help us narrow this down with a few details:

1. Are the affected users super admins or regular customers?
2. What status do the missing sites show under Ultimate Multisite > Sites — Customer-Owned, Pending, or something else?
3. On one of the missing sites, if you go to Network Admin > Sites > Edit > Users tab, is the affected user listed with a role?

If the users are super admins, this is expected behaviour. If they’re regular customers with active Customer-Owned sites and a role assigned, that would indicate a bug we’d want to investigate.

Thanks for reporting this problem. We’ll look at it and get a fix ready for next release.

Hi @mirshadrahman ,

Thanks for reporting this — we’ve tracked down the issue and it turns out there were actually three related bugs in our site duplication code that were causing URLs in Elementor elements (buttons, links, etc.) to not get updated when creating a new site from a template.

Here’s what was happening in simple terms:

1. Replacement was getting skipped prematurely. When we duplicate a site, we replace URLs in a specific order — upload folder URLs first, then the main site URL. On subdirectory installs like yours, once the upload URL was updated (e.g. /mirshad/wp-content/uploads → /mysite2/wp-content/uploads), our code saw that the new site name already existed in the data and incorrectly assumed the job was done — skipping the
   replacement for all remaining URLs like button links.
2. Elementor’s data format wasn’t fully accounted for. Elementor stores its page data as JSON, which escapes forward slashes (/ becomes \/). Our search-and-replace was looking for normal slashes and never matched the escaped versions, so Elementor URLs were silently skipped.
3. Deeply nested data wasn’t being processed. Some URL references buried inside nested data structures were also being missed.

Would you be able to test the fix on your site? You can install the branch version by downloading it from the PR page. Or directly https://nightly.link/Ultimate-Multisite/ultimate-multisite/actions/runs/21490680774/ultimate-multisite.zip After installing, try creating a new site from your template and check whether the button and element URLs are now correctly pointing to the new site. Let us know how it goes!