pitbully
Senior Member
- Aug 14, 2013
- 854
- 729
I am a marketer and somewhat of a designer, but when it comes to servers, programming or any of the complicated stuff, I suck. I just got somebody to migrate my Wordpress site from shared hosting to a VPS, all on the same GoDaddy account.
For some reason, now all of the inner pages/posts have a slash( / ) at the end of the URL, and this is the only way these URLs will load. Without the / these URLs return a warning like this:
Warning: Cannot modify header information - headers already sent by (output started at /home/wwwshops/public_html/wp-content/themes/****/admin/options-init.php:31) in /home/wwwshops/public_html/wp-includes/pluggable.php on line 896
Note: I replaced my theme name with the **** in the file path, just to be clear
This guy is pretty knowledgeable, but had no idea why this was happening after he migrated the site for me. I'm not sure if the server is forcing the trailing slash, or if there's some kind of Wordpress problem on the new server. But either way I'm lost here and this is a big problem. Any guidance you guys can give me here would be greatly appreciated. I can't even log into the back end to figure it out because the login page calls for the dashboard URL without the / so it brings up that warning.
For some reason, now all of the inner pages/posts have a slash( / ) at the end of the URL, and this is the only way these URLs will load. Without the / these URLs return a warning like this:
Warning: Cannot modify header information - headers already sent by (output started at /home/wwwshops/public_html/wp-content/themes/****/admin/options-init.php:31) in /home/wwwshops/public_html/wp-includes/pluggable.php on line 896
Note: I replaced my theme name with the **** in the file path, just to be clear
This guy is pretty knowledgeable, but had no idea why this was happening after he migrated the site for me. I'm not sure if the server is forcing the trailing slash, or if there's some kind of Wordpress problem on the new server. But either way I'm lost here and this is a big problem. Any guidance you guys can give me here would be greatly appreciated. I can't even log into the back end to figure it out because the login page calls for the dashboard URL without the / so it brings up that warning.