22-01-2016, 04:59 AMZenith Wrote: 22-01-2016, 04:57 AMAsa Wrote: 22-01-2016, 04:56 AMZenith Wrote: 22-01-2016, 04:53 AMAoki Wrote: Seems like you broke your JS. I don't remember touching the JS which one would I need to replace? and again it seems to be a problem with the template and not the XML itself :/ The same thing happened to me once. Found that a plugin or something had fucked up my headerinclude. Might want to start there. Maybe replace your current with a fresh copy of the headerinclude template? I did that before. It didn't work. I looked at the templatemultiple times and I saw no differences. :/
22-01-2016, 04:57 AMAsa Wrote: 22-01-2016, 04:56 AMZenith Wrote: 22-01-2016, 04:53 AMAoki Wrote: Seems like you broke your JS. I don't remember touching the JS which one would I need to replace? and again it seems to be a problem with the template and not the XML itself :/ The same thing happened to me once. Found that a plugin or something had fucked up my headerinclude. Might want to start there. Maybe replace your current with a fresh copy of the headerinclude template?
22-01-2016, 04:56 AMZenith Wrote: 22-01-2016, 04:53 AMAoki Wrote: Seems like you broke your JS. I don't remember touching the JS which one would I need to replace? and again it seems to be a problem with the template and not the XML itself :/
22-01-2016, 04:53 AMAoki Wrote: Seems like you broke your JS.
Loading Info...