22976 Posts in 11667 Topics by 2826 members
Page: 1 2
|Go to End||Next >|
1 September 2009 at 6:17pm Last edited: 2 September 2009 8:33pm
I'm not talking toilet trash.
I'm running SS 2.2.3 and recently installed the forum module (which I downloaded at the same time as SS2.2.3), I made a few updates to the forum CSS in the theme, and that went fine, then I made a few more edits to the CSS, tried a /?flush=1 and now it won't flush.
All the pages still display and I can update content and use the forum with no problem, I just can't flush on any page.
My CSS is now valid, but it never was before this error.
The standard yellow screen with red font error flashes on screen then I get a (firefox) "Content Encoding Error, The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression."
Any help would go down great!
2 September 2009 at 4:07am
you have to be logged in to flush. I can not imagine that itÂ´s the CSS changes fault that you canÂ´t flush. Anyways I would disable CSS by renaming the files and try again.
2 September 2009 at 8:32pm
Hi, I'm not trying to /db/build?flush=1 I'm just trying to /?flush=1
I tried to change the name of the file, this did disable the styling but still no success.
I uninstalled the Forum module and there was no trouble flushing the site. I installed the forum module again and i've got the same error.
2 September 2009 at 8:44pm
WhatÂ´s the exact name of the forum modules folder?
2 September 2009 at 8:53pm
forum. I have a forum theme as well (site is based on a template), perhaps i should try to delete this template see if that narrows it down?
2 September 2009 at 9:56pm
I you deinstall the forum module, itÂ´s tables will not be deleted. Before reinstalling the forum module I would delete them by hand. Maybe this will do it.
2 September 2009 at 10:16pm
so do I delete any tables that begin with forum. That probably sounds like a dumb question but I have to make sure
2 September 2009 at 11:20pm
Yes. If you delete a modules foulder and flush the db by "dev/build" all tables of that module will get an "_obsolete_" appended to the tables name as a prefix. Just delete all tables with that name. Be sure to make backups, in case the contain any valuable data.
Page: 1 2
|Go to Top||Next >|