Suddenly Front end blank. Admin fine.

[RodG]

Apologies. What is there is what I pulled from the root. The new directory does not have an htaccess.

Hmmm. The thot plickens... if this was from the root folder, there is nothing to perfom a redirect to the /new/ folder when the browser is pointed to http://yourdomain/ so, what happens when you point the broweser to http://yourdomain/new/ ?

Cheers
Rod

[Nepherael]

I'd be strongly tempted to delete/rename this file. With your current zen install it doesnt appear to be doing anything, and if the domain names did match (www vs no www) it looks like it will be asking for a password to access the site, and if the auth paths are wrong, or the auth files are unreadable you could possibly end up with the blank screen. ... just a thought.

Cheers
RodG

Hey I'll take any leads. I have backups of it so I'll just delete and report back

[Nepherael]

Hmmm. The thot plickens... if this was from the root folder, there is nothing to perfom a redirect to the /new/ folder when the browser is pointed to http://yourdomain/ so, what happens when you point the broweser to http://yourdomain/new/ ?

Cheers
Rod

There is a huge mess of redirects I left out. They were added after the issue and are working correctly. Sorry for the confusion.

Tested without the posted code. No change

Here's all the redirects.

rewriteengine on
rewritecond %{HTTP_HOST} ^www.lightsforholidays.com$ [OR]
rewritecond %{HTTP_HOST} ^lightsforholidays.com$
rewriterule ^$ "http\:\/\/lightsforholidays\.com\/new" [R=301,L] #577cf767e0212
rewritecond %{HTTP_HOST} ^www.lightsforholidays.com$ [OR]
rewritecond %{HTTP_HOST} ^lightsforholidays.com$
rewriterule ^pub(.*)$ "http\:\/\/lightsforholidays\.com\/new\/pub$1" [R=301,L] #577cedc587589
rewritecond %{HTTP_HOST} ^www.lightsforholidays.com$ [OR]
rewritecond %{HTTP_HOST} ^lightsforholidays.com$
rewriterule ^extras(.*)$ "http\:\/\/lightsforholidays\.com\/new\/extras$1" [R=301,L] #577cec60140a7
rewritecond %{HTTP_HOST} ^www.lightsforholidays.com$ [OR]
rewritecond %{HTTP_HOST} ^lightsforholidays.com$
rewriterule ^logs(.*)$ "http\:\/\/lightsforholidays\.com\/new\/logs$1" [R=301,L] #577ced99b5c4e
rewritecond %{HTTP_HOST} ^www.lightsforholidays.com$ [OR]
rewritecond %{HTTP_HOST} ^lightsforholidays.com$
rewriterule ^index\.php(.*)$ "http\:\/\/lightsforholidays\.com\/new\/index\.php$1" [R=301,L] #577cee609adc0
rewritecond %{HTTP_HOST} ^www.lightsforholidays.com$ [OR]
rewritecond %{HTTP_HOST} ^lightsforholidays.com$
rewriterule ^robots_example\.txt(.*)$ "http\:\/\/lightsforholidays\.com\/new\/robots_example\.txt$1" [R=301,L] #577cef5c941d6
rewritecond %{HTTP_HOST} ^www.lightsforholidays.com$ [OR]
rewritecond %{HTTP_HOST} ^lightsforholidays.com$
rewriterule ^images(.*)$ "http\:\/\/lightsforholidays\.com\/new\/images$1" [R=301,L] #577cecaa832a7
rewritecond %{HTTP_HOST} ^www.lightsforholidays.com$ [OR]
rewritecond %{HTTP_HOST} ^lightsforholidays.com$
rewriterule ^editors(.*)$ "http\:\/\/lightsforholidays\.com\/new\/editors$1" [R=301,L] #577cec1f3fe21
rewritecond %{HTTP_HOST} ^www.lightsforholidays.com$ [OR]
rewritecond %{HTTP_HOST} ^lightsforholidays.com$
rewriterule ^page_not_found\.php(.*)$ "http\:\/\/lightsforholidays\.com\/new\/page_not_found\.php$1" [R=301,L] #577cef2f95c1e
rewritecond %{HTTP_HOST} ^www.lightsforholidays.com$ [OR]
rewritecond %{HTTP_HOST} ^lightsforholidays.com$
rewriterule ^media(.*)$ "http\:\/\/lightsforholidays\.com\/new\/media$1" [R=301,L] #577cedb21ba65
rewritecond %{HTTP_HOST} ^www.lightsforholidays.com$ [OR]
rewritecond %{HTTP_HOST} ^lightsforholidays.com$
rewriterule ^download(.*)$ "http\:\/\/lightsforholidays\.com\/new\/download$1" [R=301,L] #577cebf307356
rewritecond %{HTTP_HOST} ^www.lightsforholidays.com$ [OR]
rewritecond %{HTTP_HOST} ^lightsforholidays.com$
rewriterule ^mcs_learn_more\.html(.*)$ "http\:\/\/lightsforholidays\.com\/new\/mcs_main_handler\.html$1" [R=301,L] #577ceeed4a9b6
rewritecond %{HTTP_HOST} ^www.lightsforholidays.com$ [OR]
rewritecond %{HTTP_HOST} ^lightsforholidays.com$
rewriterule ^email(.*)$ "http\:\/\/lightsforholidays\.com\/new\/email$1" [R=301,L] #577cec38a948d
rewritecond %{HTTP_HOST} ^www.lightsforholidays.com$ [OR]
rewritecond %{HTTP_HOST} ^lightsforholidays.com$
rewriterule ^ipn_main_handler\.php(.*)$ "http\:\/\/lightsforholidays\.com\/new\/ipn_main_handler\.php$1" [R=301,L] #577ceeb9ee787
rewritecond %{HTTP_HOST} ^www.lightsforholidays.com$ [OR]
rewritecond %{HTTP_HOST} ^lightsforholidays.com$
rewriterule ^cache(.*)$ "http\:\/\/lightsforholidays\.com\/new\/cache$1" [R=301,L] #577ceb7b360bf
rewritecond %{HTTP_HOST} ^www.lightsforholidays.com$ [OR]
rewritecond %{HTTP_HOST} ^lightsforholidays.com$
rewriterule ^includes(.*)$ "http\:\/\/lightsforholidays\.com\/new\/includes$1" [R=301,L] #577cecd23ff12
rewritecond %{HTTP_HOST} ^www.lightsforholidays.com$ [OR]
rewritecond %{HTTP_HOST} ^lightsforholidays.com$
rewriterule ^vbv_learn_more\.html(.*)$ "http\:\/\/lightsforholidays\.com\/new\/vbv_learn_more\.html$1" [R=301,L] #577cef8c07e18
rewritecond %{HTTP_HOST} ^www.lightsforholidays.com$ [OR]
rewritecond %{HTTP_HOST} ^lightsforholidays.com$
rewriterule ^nddbc\.html(.*)$ "http\:\/\/lightsforholidays\.com\/new\/nddbc\.html$1" [R=301,L] #577cef0c20ce5
rewritecond %{HTTP_HOST} ^www.lightsforholidays.com$ [OR]
rewritecond %{HTTP_HOST} ^lightsforholidays.com$
rewriterule ^docs(.*)$ "http\:\/\/lightsforholidays\.com\/new\/docs$1" [R=301,L] #577ceba077986
rewritecond %{HTTP_HOST} ^www.lightsforholidays.com$ [OR]
rewritecond %{HTTP_HOST} ^lightsforholidays.com$
rewriterule ^adminurrhtcqq(.*)$ "http\:\/\/lightsforholidays\.com\/new\/adminurrhtcqq$1" [R=301,L] #577ceb42175ff

[RodG]

Sheet, some people do like their needless redirects (a better way is to set the "document root" for the domain to be the folder where the files reside... no redirects needed.
Meanwhile, assuming you cant do that, please delete/rename that .htaccess file, then point your webbrowser to http://yourdomain.com/new/index.php
Report the results.
Thanjs
RodG

[mc12345678]

Also, please rename your admin directory. Those redirects are certainly an issue.

[RodG]

Also, how long has the site been located in the directory called "new"? ... im thinking (clutching at straws), is that godaddy may have recently(?) updated theiw mod_security rules, and "new" could be considered as a restricted keyword.. is so, I will have a hard time explaning why it doesnt trigger when accessing the admin area, so perhaps we should scub this idea, for now

[Nepherael]

Also, please rename your admin directory. Those redirects are certainly an issue.

OK the redirects have to be there. I don't know the details because I'm not a coder. I've built a lot of (crappy) sites but I survive on research. The redirects have always been there but they were in the root directory as some sort of file that could not be downloaded or opened and just said "target: /new/xxxx" when mouse over. They've been deleted and recreated using the redirects I posted.

Without the redirects the site just gives an error saying its coming soon and if I'm the owner I uploaded it wrong. That's why I didn't post them. They have been there for years and years. If I move the whole site to the root so that I can remove those redirects it will create more problems than it solves.

Now if I rename my admin directory I will not have access to the administration. I've tried it without the redirects already. Godaddy doesn't allow the "primary" domain in a subdirectory so if you're on a Godaddy server you have to find a way to make a subdirectory work. I wouldn't have used this way but as it's the way the site was built I can't try and fix it until the site is working again.

Remember the admin side of the site functions perfectly.

Also, it looks as if they have used the default template too. No additional modules. No transaction modules etc.

That's why I'm think this is either some form of corrupted data in the database or the website needs to be updated because if some sort of server update on Godaddy's end. But as there are no backups of anything prior to this error I can't restore the database and updating the site is a last resort until I know that is the solution.

[Nepherael]

Sheet, some people do like their needless redirects (a better way is to set the "document root" for the domain to be the folder where the files reside... no redirects needed.
Meanwhile, assuming you cant do that, please delete/rename that .htaccess file, then point your webbrowser to http://yourdomain.com/new/index.php
Report the results.
Thanjs
RodG

Tested. Nothing

[Nepherael]

Also, how long has the site been located in the directory called "new"? ... im thinking (clutching at straws), is that godaddy may have recently(?) updated theiw mod_security rules, and "new" could be considered as a restricted keyword.. is so, I will have a hard time explaning why it doesnt trigger when accessing the admin area, so perhaps we should scub this idea, for now

Maybe more than 5 years.

I was thinking it was something like this too I just don't know enough to know the specific things to try and fix.

Also, I've called Godaddy but they haven't been able to help me much. I asked if they did any updates but they said no (I doubt the average CSR would know though)

I've been leaning toward server side update since minute 1 because no one has accessed anything to do with the site in a long time. Just don't know what to fix on my end to get the compatibility back in line

[mc12345678]

Another "direction" is related to having a local directory and contents within it./home/content/l/i/g/lights4holiday/html/new/includes/local. Is it present? What files are present? is there a configure.php file?

OK the redirects have to be there. I don't know the details because I'm not a coder. I've built a lot of (crappy) sites but I survive on research. The redirects have always been there but they were in the root directory as some sort of file that could not be downloaded or opened and just said "target: /new/xxxx" when mouse over. They've been deleted and recreated using the redirects I posted.

Without the redirects the site just gives an error saying its coming soon and if I'm the owner I uploaded it wrong. That's why I didn't post them. They have been there for years and years. If I move the whole site to the root so that I can remove those redirects it will create more problems than it solves.

Now if I rename my admin directory I will not have access to the administration. I've tried it without the redirects already. Godaddy doesn't allow the "primary" domain in a subdirectory so if you're on a Godaddy server you have to find a way to make a subdirectory work. I wouldn't have used this way but as it's the way the site was built I can't try and fix it until the site is working again.

Remember the admin side of the site functions perfectly.

Also, it looks as if they have used the default template too. No additional modules. No transaction modules etc.

That's why I'm think this is either some form of corrupted data in the database or the website needs to be updated because if some sort of server update on Godaddy's end. But as there are no backups of anything prior to this error I can't restore the database and updating the site is a last resort until I know that is the solution.

Can rename the admin, but will have to also modify the htaccess to match if the redirects will stay.

Still have the question of the above attached post. Results?