Your web server doesn’t know what to do with that subdomain…
You need to tell your control panel about the subdomain and then to send requests for that domain to your WordPress install.
I think you are on Hostgator and I think that would be CPanel but it’s been a while since I’ve worked with any sites on Hostgator.
Look for an add subdomain feature and do check that it ‘maps’ the subdomain to the public_html directory exactly as the root domain does.
Thread Starter
soygisse
(@gisegalaburri)
Hi @jnashhawkins !
Yes I have HostGator and Cpanel.
I did what you said. Nothing changed. Then I deleted subdomain *.elevatupotencial.com and created it again in Document Root public_html, then created again the subdomain cursos.elevatupotencial.com
And now I saw this warnings when go to the subdomain URL:
Warning: strpos(): Empty needle in /xxxxxxx/xxxxxxx/public_html/wp-content/plugins/bloom/core/functions.php on line 647
And when I try to go to the wp-admin it says:
Warning: strpos(): Empty needle in /xxxxxxx/xxxxxxx/public_html/wp-content/plugins/bloom/core/functions.php on line 647
Warning: Cannot modify header information – headers already sent by (output started at /xxxxxxx/xxxxxxx/public_html/wp-content/plugins/bloom/core/functions.php:647) in /xxxxxxx/xxxxxxx/public_html/wp-includes/pluggable.php on line 1281
Warning: Cannot modify header information – headers already sent by (output started at /xxxxxxx/xxxxxxx/public_html/wp-content/plugins/bloom/core/functions.php:647) in /xxxxxxx/xxxxxxx/public_html/wp-includes/pluggable.php on line 1284
Can you help to fix it?
-
This reply was modified 6 years ago by
soygisse.
Thread Starter
soygisse
(@gisegalaburri)
I fix it!
After doing what you recommended, try to open the subdomain again throug WP Super Admin and I saw a new message before the warning. It said: Theme Twenty Twenty wasn’t found.
Installed it and now it works fine the subdomain URL and the wp-admin.
Close the topic. Hope it helps somebodody in the future.
Yes, I see that it’s working fine now… When I saw the error you reported I thought it was a plugin problem.
Glad that worked for you!
Let us know if you need anything else.