I recently updated the logo of our store to a Valentine's Day themed logo, and tried to update the site. Actinic proceeded to completely erase all the HTML files on our server, then crash (by crash, I mean a completely unhelpful Windows Vista "Actinic Catalog has caused an error" crash with a "debug" button that attempts to launch Visual Basic then crashes once more). Obviously this left me very angry, and nobody can purchase from our site because EVERY HTML file in /acatalog/ has gone. This is a LIVE SITE. This is the message in the browser:
The requested URL /acatalog/********.html was not found on this server.
This applies to the entire catalogue. We are losing sales as we speak. What on earth is going on with Actinic? I am now onto my tenth attempt at updating the site, but each time it crashes after about 5 minutes as above. Not a word of helpful information as to why this is happening. Actinic takes almost 30 minutes just to load (?!) on a Core 2 Quad Q6600. The whole thing is a complete joke.
I've tried purge and refresh, compact databases and deleting FileList from the MDB file. Nothing is working. Please, someone suggest something quick and I would be most grateful. My suspicion is that yet again the resolution will be crude and hacky, with no real solution to the root of the problem, but as long as it puts our site back live again that's fine for now.
Thanks,
Matt
The requested URL /acatalog/********.html was not found on this server.
This applies to the entire catalogue. We are losing sales as we speak. What on earth is going on with Actinic? I am now onto my tenth attempt at updating the site, but each time it crashes after about 5 minutes as above. Not a word of helpful information as to why this is happening. Actinic takes almost 30 minutes just to load (?!) on a Core 2 Quad Q6600. The whole thing is a complete joke.
I've tried purge and refresh, compact databases and deleting FileList from the MDB file. Nothing is working. Please, someone suggest something quick and I would be most grateful. My suspicion is that yet again the resolution will be crude and hacky, with no real solution to the root of the problem, but as long as it puts our site back live again that's fine for now.
Thanks,
Matt
Comment