By catweazle on
My site is working 100% on my local test machine. After transferring it to my host (fatcow.com), a few very strange things start to happen:
- I frequently see 'old' versions of pages (i.e. pages I've seen before, but new content doesn't show up)
- About 50% of the time, I get "500 Internal Server Error". Clicking refresh loads the page eventually.
- Sometimes, logging in as user A gives me user B's permissions !!
I use Drupal 6.8.
Any ideas ?
Comments
Site
For those who want to have a look for themselves, the site is at:
http://bordermadness.org
I don't know what the
I don't know what the problem is but you should make sure you start with a level playing field by clearing your cache admin/settings/performance and I would try rebuilding the permissions admin/content/node-settings
Cache
Before reporting this problem, I:
- turned off all optimisations
- cleared the cache manually
Did you rebuild the
Did you rebuild the permissions?
I did rebuild them. Does not
I did rebuild them. Does not make a difference...
Also, make sure you loaded
Also, make sure you loaded Drupal's .htaccess file to your site.
Yes, I transferred
Yes, I transferred *everything* ...
One thing to note:I
One thing to note:
I developed the site on http://localhost/bordermadness/
(a subdirectory of the apache htdocs directory)
Then I copied that subdirectory to the host, and configured the domain:
http://bordermadness.org -> ~home/bordermadness
Could this have anything to do with my problems ??
Can anyone see
Can anyone see http://bordermadness.org without getting "500 Internal Server Error" ??
I'm not getting any errors
I'm not getting any errors at all. Can you share the solution?
Thanks for trying it
Thanks for trying it out!
Unfortunately I don't have a solution yet. It works fine from my home internet connection (and yours).
But I get the 500 errors with my work internet connection. All other sites work fine there !!
I was able to load the site
I was able to load the site fine also. Remember that we're accessing as Anonymous and not authenticated as you might be. Test it as anon and if it works then the problem is limited to authenticated or super user access. Perhaps a specific module...