By ryanmnly on

I moved a client's website from my server to their ATT hosting platform. When I moved it, the dynamic loading of content stopped working. I am assuming it is an AJAX issue.

1. On my server, the banner image would load once and never have to reload again. On their server, it reloads everytime they change pages.

2. On my server, the file attachment uploading (via editing the node) worked. On their server, it does not complete and does not return any error.

I may be phrasing it wrong or troubleshooting in the wrong spot. I am also assuming the 2 errors are related. So here it is:

http://paragon.ryanmanley.com (this is my server and it works.)
http://www.theparagongroup-inc.com (this is their ATT hosted site and it doesn't work.)

Would anyone mind taking a look at it and seeing if they recognize the issue? I am baffled and ATT is no help.

Thanks in advance,
Ryan

Comments

pobster’s picture

pobster commented

For 1, I would say that there probably isn't an issue here? All it probably is, is that on your server the 330Kb banner is being 'served' straight in front of you and coming directly from your own filesystem (i.e. it's FAST) whereas when it's on a remote server - you're actually noticing the delay with the rotating script 'executing' the image file? TBH the way the rotator script 'executes' an image is fairly bad practise, especially when it's done on every page like that - makes it hard for caching as the image isn't an image, it's a script... Is it absolutely necessary? Will the image actually need to be different at any point or is that just how the theme is?

For 2, it's likely permissions on the /tmp folder.

Pobster

ryanmnly’s picture

ryanmnly commented

That's great feedback, thanks. I went ahead and removed the rotating script since it isn't necessary. It does load a bit faster, but the same problem persists. My own server is still remotely hosted, so in theory, I should still see the delay regardless.

Also, I went ahead and fixed the permissions in the /tmp folder. It turns out there was not write access. However, it still did not fix the problem. I'm fairly confident it has something to do with the way it generates the page, and I think it has to do with ATT's services. I just can't pinpoint it. And without pinpointing the issue, they refuse to help.

Any other ideas on what I should try next?

Thanks,
Ryan