That IS really strange. Also the fonts are different.
How is the alias created ?
I did not notice the font. Thank you for pointing it out.
Additionally modifying the Virtual Host in Apache did not make a difference. My thought had been that with the document root being /var/www/html and the content being in /var/www/html/blogs the wrong URL was being served up causing the browser to look in the wrong spot for the images. Such does not the case.
The alias was created in AWS Route 53. Admittedly it was only set up around 6 PM Central US time. For testing purposes the blog is hosted on EC2 with the OS being Amazon Linux (haven’t decided on a production host). But since the user arrives at the correct page, I don’t see how the DNS could be an issue.
I think the apache virtual host should be just /var/www/html
Try it with a hosts file entry in your local workstation?
# local linux workstation /etc/hosts
# ec2-52-4-19-122.compute-1.amazonaws.com =
test.michaelpaulmeno.com 52.4.19.122
Would rule out improper dns which would be typically A record…
Edit: Well, I tried that to no avail.
And noticed another strange difference with alias site. Where the search magnifier glas image should be, in firefox it appears like ’88’ led display, in chromium it appears text ‘fl’
??
restart httpd?
Yeah that didn’t help me either. Restarting did not do much good.
I feel like this must be a theme issue. Some script is not pulling images from the right spot. Perhaps the FQDN is buried somewhere in the theme file where the images are called up? Problem is I can’t seem to find any suspicious looking code in the php files so far.
FQDN should never be in the theme, it’s pulled from the db options table:
https://codex.wordpress.org/Changing_The_Site_URL
Double check you have this right?
Caching can confound the issues, though.
To test theme
- Clear every cache you can find, like caching plugin
- Deactivate all plugins
- try your theme
- switch to the default theme Twenty Fifteen, try both urls
- Switch back to your theme
Fixed *dances around the room* ! The key was to put test.michaelpaulmeno.com/blogs as both the site address and the WordPress address URL. Now if you go to the first link, the problem appears. However since that is not one I plan on giving out, it is of little concern. I still have to fiddle with Apache so that one can access the blog by simply typing test.michaelpaulmeno.com without needing the /blogs (and get rid of the default Apache test page in the process), but that can wait for another time.
Thank you for your help Martin. I am very new to WordPress administration and am still learning the ropes.
Good job, even though it works around instead solve the issue.
To solve it outright with no apache mods, I should have thought earlier to try the following:
site_url: http://test.michaelpaulmeno.com
home: http://ec2-52-4-19-122.compute-1.amazonaws.com
Both must be and are FQDN ! … One is displayed, the other hidden…
