My comic won't update even after I deleted the old file

For requests for help from CG administrators, Wranglers, and experienced CG members. Please read the FAQ before posting. Also look at CG Wiki for tutorials and how-tos written by other CG webtoonists.
Post Reply
User avatar
Reactor
Regular Poster
Posts: 59
Joined: Mon Jul 04, 2005 4:06 am

My comic won't update even after I deleted the old file

Post by Reactor »

I often post a new comic, then notice some flaws in it, make some changes and replace it with the newer version. I do this by simply replacing the old file in Public HTML - Comics with a new one with the same name. It's always worked before, and I could see the new version instantly by reloading the page in my browser.

Two days ago I did this for my latest comic, and the old comic still appeared, even though the file was no longer there! Now, two days later, it's still the old comic I see, not the revision.

I've tried doing a full update and regular update, numerous times, to no avail. I am not seeing my browser's cache, I've already checked that.

Any suggestions? Why is the old comic still there when its file has been deleted and replaced? D:
Image

User avatar
Oualawouzou
Cartoon Cop (Moderator)
Cartoon Cop (Moderator)
Posts: 1548
Joined: Fri Jan 10, 2003 7:47 am
Contact:

Post by Oualawouzou »

Try deleting the comic from public_html/comics, upload the new one to workspace/comics and trigger a regular manual update. Don't use full updates unless it's the only thing that can fix your problem.

User avatar
Reactor
Regular Poster
Posts: 59
Joined: Mon Jul 04, 2005 4:06 am

Post by Reactor »

Thanks! That worked. So why did i have this problem in the first place?
Image

User avatar
JTorch
Regular Poster
Posts: 520
Joined: Mon Jun 19, 2006 7:51 pm
Location: Canada
Contact:

Post by JTorch »

I'm not sure what caused the problem, but just don't upload things to public_html. It's tedious, but if you want to test pages it would likely be safer to just upload to workspace/comics/ and then trigger an update. I personally think someone should come up with a CG page viewer for viewing html pages with ***tags*** on your computer without having to update to see what it looks like.
Image
There's a Civilization on my Fork - Updates Sometimes

User avatar
Lando
Regular Poster
Posts: 255
Joined: Thu Apr 27, 2006 11:50 am
Location: Roxboro
Contact:

Post by Lando »

portable autokeen? brilliant!
Lando

"My spelling and grammar come with a disclaimer."

www.back2roxboro.com

User avatar
JTorch
Regular Poster
Posts: 520
Joined: Mon Jun 19, 2006 7:51 pm
Location: Canada
Contact:

Post by JTorch »

Something like that. It wouldn't update your site, just allow you to see what the page would look like after the ***tags*** have been converted. I'd make it, but I'm afraid I have no idea how, if it's even possible.
Image
There's a Civilization on my Fork - Updates Sometimes

User avatar
Reactor
Regular Poster
Posts: 59
Joined: Mon Jul 04, 2005 4:06 am

Post by Reactor »

JTorch wrote:I'm not sure what caused the problem, but just don't upload things to public_html. It's tedious, but if you want to test pages it would likely be safer to just upload to workspace/comics/ and then trigger an update.
Actually, it's not tedious, it's the easiest thing in the world. Or was until a few days ago. I've replaced files in Public Html-Comics with revised versions many many times with no problem at all. I still don't understand why it didn't work this time.

Normally, you just replace the file with one of the same name, and no updates are needed, you just refresh your browser and, presto, there it is. :-?
Image

User avatar
Kisai
Goddess of Light
Goddess of Light
Posts: 3276
Joined: Fri Jan 01, 1999 4:00 pm
Location: The Past, the Present, The future
Contact:

Post by Kisai »

You shouldn't change the files in public_html since they will be overwritten by the templates when the comic updates.

Yes, any live change should be reflected instantly, but CG sends out no-expire headers, so you literately have to do a forced-refresh to update (shift-f5) to force the browser to check the page again, otherwise it will still use the cached state.

Whenever you update your templates, especially with new images that have the same file names, do a shift-f5 refresh

Post Reply