1
I have currently 4 sites using XOOPS 2.0.15 all with same modules. One in particular has less modules than the other but the modules it has are indeed on the other sites.
Suddenly in the last few days and no major changes the client can not access the site.
What occurs is this: They go to the sites url which is presently the site closed page. They have access to enter while we are working on it and have until a week or so ago. They login and it takes them to a blank white page.
I set them up and gave them access to two other sites running the XOOPS 2.0.15 and closed each one so as to emulate the same atmosphere for the site as theirs.
They were able to login and access those sites with no problems.
For their site which they can not access is basically says it can't find it. Their site is currently a sub-domain for testing purposes. If they go to the www.x x x.-----.com addy they get zilch, no can find, white blank page. If they go to the directory addy where XOOPS is loaded as the sub-directory eg;
http://www.--------.com/----- they get the Site Closed page just fine. They login and it takes them to a white page. Doesn't happen on any of the other 2.0.15 sites.
Sorry if I repeated myself along the way but this has me totally stumped.
I don't have a problem accessing it, my better half who at her work PC on a seriously networked and secure system has no problems accessing it either.
Going Bonkers in Georgia,
Quest