We Found The Cache Issue. So Things Should Be Back To Normal. Whatever Normal Is?
Well, Woody Boater should all be working again, we had some small cache settings that were wonky and Bill went in and reset stuff back to the original settings. So all should????? be normal again.
I am glad something is working correctly!
Not sure on your fix….Standard browser firefox…still get may 13 story..private browser got today’s headline
when I go to woody boater in the normal browser mode not the private browser mode. it still comes up with the may 13 story…if I change to private browser mode I get today’s story…..(private is hide all your browser history…I’m sure no one here has ever done that LOL) …and btw…I was getting a little worried about you after sniffing all the fiberglass fumes, my stories didn’t update for days..
Ahhhh…cache got me…never mind….
Not sure what that means?
Seems to be working on IPad and Android phone. WoodyBoater is cruising again!
Actually, it looks like my Android phone will not update beyond three comments, even with multiple refreshes. WoodyBoater not there yet.
Have another cheesy steak and cheese!
Graflex cameras and projectors made here in Rochester, NY. Eastman Kodak in the same town. More questions to ask yourself.
Good to see things working again.
I was concerned that WB was going to go the way of Boat Buzz with “upgrade” challenges.
I had to hit “reload” in Google Chrome to see today’s story.
Had to refresh to see using Safari just now; Love what you do Matt !
Had to refresh just now ; using Safari browser
Love what you do Matt; thank you for sharing your passion
UGH! Just shoot me. I am hoping it will all work its way out. Like eating a cheesy steak and cheese. It is getting better though, and as far as private settings, thats on you! HA, It may also have something to do with the PHP 8 stuff, which is all sensitive to cookies and so on. And yes the Boat Buzz and other forums are what happens if you are not on it. Hold on.. I feel.. The steak and… nope, just gas!
Whether things are going as they should on the WoodyBoater site, or if it is a little off, it is still my go to happy place first thing in the morning!!! It always brings a smile to my face.
I ALWAYS get a little (?) concerned when I see nothing on WoodyBoater. Glad to have you back!
Through this whole issue, I’ve not had a problem seeing the day’s story. It’s always popped right up. For me, it’s been that my comments & those of some others, don’t show up until the following day – even if I hit “refresh” or come back hours later. Didn’t try to comment yesterday, as we were enjoying this view of the mighty Ohio, while visiting my dad & his wife.
9:19am Trying comment without photo. Commented with photo attached a minute ago. Not displayed, even after refresh. Currently see comments from Dan Overbeek, Mahogany Madness, Matt, Greg Lewandowski, Bilge Rat, Troy, rjtipple & james steele.
Normal?!?!??!??
WTH fun is that anyway?!?!???
We’re WoodyBoaters after all and we always put the “fun” in “dysfunctional”.
Makes us a fun lot to be with and compare maladies.
(Sorry Matt, I used a big word there…..)
It looks like the little guy in the 1st picture has something big those girls want. Thongs are working here.
Giving it a try, along with a pic.
Funny, working from my phone but not my laptop.
Now seeing it from my laptop.
Cache. We shouldn’t really care much about it, so, if you are not interested, ignore please! In the web server world where Woodyboater is hosted, cache is somewhat complicated with many, many settings. To make matters a bit more complicated, there is actually a two-tier system of caching…one with the primary host and one with a secondary CDN (Content Delivery Network) which is CloudFlare. All involved here are the best of the best. Caching is good….really it is…it makes sites like this load quicker, perform better. But, though the array of settings, things can hiccup. I think that is what is happening here. I disabled a setting which could very well be the issue. From this point on (after this comment), my hope is that things are fixed. Many of these settings will succeed or fail, based on an Operating System’s (iOS, Android, Apple Desktop OS, etc.) ability to deal with the technology—as some of these settings introduce more “bleeding edge” features. That is why you are all seeing different results. Carry on! I hope this is resolved.
Now working on my Android phone. Woohoo!
Thank you Bill Basler.
Took a look at 3:20pm & both of my comments are there now. Thank you, Bill Basler!
I have some cash issues as well. Can your crack team help me out too?
Lol, John. I feel your pain. Things were much simpler back in the ‘80’s on IBM’s mainframe and their SNA network with dumb terminals as they were called. I developed the first statewide application with a development staff of 5 and network support staff of 3. Twenty years later to implement a similar PC based network application costs $52 million going from 200 dumb terminals to about 1500 PC’s ($26 million in hardware) to track Georgia’s child abuse cases and their subsequent placement in foster care homes and case management. That cost didn’t include the network infrastructure to support statewide data transmission and help desk support that was already in place for other application support. My hats off to Bill, et al, to keep WB up and running. 20 years ago the standard PC helpdesk problem response was turn your PC off wait 20 seconds and turn it back on. Now you’ve got multiple phone manufacturers, touchpad manufacturers, and PCs, all with different operating systems requiring different data and screen manipulation and presentation. Brings me back to days of chasing problems and that doesn’t even address security from hacking attacks. So now people, just hit refresh, that will actually help in most cases.
Took a look at 3:20pm & both my comments from this morning were there. Thank you, Bill Basler!
bravo!!