Page 1 of 1

Wordpress App "Blocky"

Posted: Thu Jul 10, 2014 6:05 pm
by rdagijones
Installed Wordpress on an Amahi server by the app. If I go to it on the browser of the HDA everything is fine. If I go to wordpress.home.com on a client computer the page that comes up is "blocky," simple text that is left justified and no other links resolve correctly. Could it be something in the /etc/http.d/1000.wordpress.conf file that is causing that behavior or what?


System Specs:
Amahi 7
Fedora 19

Re: Wordpress App "Blocky"

Posted: Thu Jul 10, 2014 6:38 pm
by bigfoot65
Did you make the domain home.com? Amahi 7 does not use that domain by default but rather home.net.

There may be an issue on your end as Wordpress works fine on my test machine.

Re: Wordpress App "Blocky"

Posted: Thu Jul 10, 2014 6:46 pm
by rdagijones
Sorry, I posted "home.com" just as a generic instead of posting my actual domain. Other apps resolve just fine. It is only wordpress that does this strange behavior. What can I test to narrow down the problem?

Re: Wordpress App "Blocky"

Posted: Thu Jul 10, 2014 6:50 pm
by bigfoot65
Ensure the browser cache is cleared. Have you tried from other clients or using other browsers?

You can also modify the URL in the wordpress database, table wp_options. I have not heard of anyone having problems.

Re: Wordpress App "Blocky"

Posted: Fri Jul 11, 2014 4:09 am
by rdagijones
I have tried multiple clients and have the same issue on each client. I will check out the url mod but how would I need to modify it to help this kind of problem?

Re: Wordpress App "Blocky"

Posted: Fri Jul 11, 2014 6:54 am
by bigfoot65
You would fully qualify it. i.e. wordpress.home.net or whatever your domain is called.

[ Post made via Android ] Image

Re: Wordpress App "Blocky"

Posted: Thu Jul 17, 2014 4:59 pm
by rdagijones
Fully qualifying the domain is the fix. I had to use PHPMyAdmin and change it to http://wordpress with my full local domain but now it is working well.

Re: Wordpress App "Blocky"

Posted: Thu Jul 17, 2014 5:06 pm
by bigfoot65
Must be the way you have the systems set up. Normally the FQDN is not needed for apps. Often when you select the app from the Dashboard, it automatically uses the FQDN.

When things such as this arise, it typically points to a failure in DNS. Most that have encountered this issue were not using the HDA for DHCP and DNS server.