|
Post by Ian on Dec 5, 2019 23:07:21 GMT -5
Chapter 16 seems to be delayed ?
Ian
|
|
|
Post by Not Wes on Dec 6, 2019 12:18:54 GMT -5
Chapter 16 seems to be delayed ? Ian Sorry about that. I wasn't watching for the chapter (seldom do) and didn't see your note here, Ian. I put the chapter up about 9 a.m. West Coast time Friday 6th. Wasn't sure it was working right at first because I'm on a new system and it's being flaky right now. Windoze 10 is weird (switching last minute from Windows 7). Dan usually lets me know if he can't get a new chapter up within a reasonable time period, but he may be stuck somewhere and can't for some reason. Anyway, it's up now. Again, sorry about that, but with Wes gone, all the volunteer labor can't always be quite as on the ball as he was. Thanks for your understanding. Not Wes
|
|
|
Post by Ian on Dec 6, 2019 14:32:11 GMT -5
Still not up, for me anyway
Ian
|
|
|
Post by Ian on Dec 6, 2019 15:15:54 GMT -5
OK now
Ian
|
|
|
Post by rick on Dec 6, 2019 16:13:19 GMT -5
Still don't have 16 here.. 15 is last chapter, and no 'go to next chapter' link at the end. Have reloaded a couple of times.
|
|
|
Post by Not Wes on Dec 6, 2019 16:36:18 GMT -5
Still don't have 16 here.. 15 is last chapter, and no 'go to next chapter' link at the end. Have reloaded a couple of times. Rick, all I can suggest is to clear your caches, or try holding down the left shift key and click reload/refresh. That sometimes will do it (often for me). Or right click inside the chapter frame and click "reload frame". Different things work in different operating systems and machines and different browsers. Too many combos to keep track of. It's working for too many people for it to be a fluke for just you. The different thingies out there in Webland may not have all caught up with the updates, too. Don't pretend to know how that stuff works (I wonder if it does, sometimes! <G>) Good luck. Not Wes
|
|
|
Post by rick on Dec 6, 2019 17:50:54 GMT -5
Typed the URL in manually and it came right up. Gremlins!!!!
|
|
|
Post by Not Wes on Dec 6, 2019 19:30:12 GMT -5
Typed the URL in manually and it came right up. Gremlins!!!! I decided long ago that computers are the ultimate invention for pissing people off. No clue as to what the problem is. Anonymous
|
|
|
Post by Not Wes on Dec 7, 2019 0:59:24 GMT -5
One lesson from all of this is that if at least a few people spread out all over Wes fan land can see the new chapter, everyone should be able to. It's just a matter of convincing your computers and software that it's possible. Just reloading the page can often do it. Hold the shift key down as you click reload tells the browser to reload from scratch, not use a cached page. Clearing caches can do it. Coming at it from another direction, like using the previous page if that now has the "next chapter" link in it. Or even typing in the web address manually like Rick had to do. Sometimes its a matter of waiting for all the root servers in your area to get updated.
Good luck.
Not Wes
|
|
|
Post by John Robert Mead on Dec 7, 2019 23:03:42 GMT -5
I'm reminded of the old joke concerning the mechanical engineer, electrical engineer, and the software engineer travelling together in a car.
The car breaks down. The mechanical and electrical engineers start tearing away at the innards, trying to figure out if its a mechanical or wiring problem. The software engineer looks at them in puzzlement, and says, "Why don't you just turn it off, let it sit a couple of minutes, and turn it back on and see if it works?"
|
|
|
Post by Leo Kerr on Jan 3, 2020 21:28:10 GMT -5
Depending on the issue, the software engineer might be on the right track. In my own experience, dissecting the car without the right tools and training is likely to just be asking for more problems.
On the website front, in my own experience, if I think the chapter should be there, hitting F5 a couple of times ([Refresh] on Firefox and Chrome) will usually work. And after 3 tries, it's probably not there yet.
Leo
|
|