• This community needs YOUR help today. We rely 100% on Supporting Memberships to fund our efforts. With the ever increasing fees of everything, we need help. We need more Supporting Members, today. Please invest back into this community. I will ship a few decals too in addition to all the account perks you get.



    Sign up here: https://www.muzzleloadingforum.com/account/upgrades
  • Friends, our 2nd Amendment rights are always under attack and the NRA has been a constant for decades in helping fight that fight.

    We have partnered with the NRA to offer you a discount on membership and Muzzleloading Forum gets a small percentage too of each membership, so you are supporting both the NRA and us.

    Use this link to sign up please; https://membership.nra.org/recruiters/join/XR045103

Log Cabin Shop website

Muzzleloading Forum

Help Support Muzzleloading Forum:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
Status
Not open for further replies.
No its that all carry on and on about what is a problem its just like are government on and on no solutions
Yeah, but that's mostly because most of the people involved have no understanding of the technology and what and how things can go wrong (even though some of them can spell "Javascript" but don't know the difference between that and "Java," "Java scripts" and "Javascript scripts"). They're just hoping to get some clue -- and to be sure the problem isn't theirs. No one likes to try to fix a problem that isn't theirs, even if they want the problem to be fixed -- and especially if they have no clue how to fix it.

You can call that "carry on" if you like, but it's pretty understandable and definitely not BS. It's really just an attempt at getting some sort of reassurance and not wasting time. When people (who don't really know what they're talking about) suggest that the problem is in an individual's browser installation or version or configuration because "I don't have a problem" -- when in fact clearly it's not (from the perspective of people who do have experience and know what they're talking about), that's not helpful and only confuses things. But I guess that's just an endearing feature of social media.

There is a problem here. A number of people have the problem and a lot don't have the problem. In this case the cause of the problem isn't on the side of the customers just trying to use the web site to buy stuff. It's on the side of the web site.

While I suppose it's comforting to view everything from an ideological perspective, in this case any analogy to government escapes me -- except that the result of frustration is the same.
 
Nice comeback doubleset.
However, yes, if some have the problem and some don't then the problem is in deed on the site's side; that is, in compatibility with those few who experience the problem.
As a System Analyst the first thing we do is gather the User's data (browser, version, OS, other apps in particular security and settings). We would then build the system in lab and confirm. It gets more detailed then this post is going to go into (log files etc) and if still necessary then systematically disable setting...that is if no version compatibility is found.
I simply verified on my system that it was not a hard stop that could or would effect all; as some posted they had no issue, I could find no issue, then any further troubleshooting from my end is futile. It is now between you, the OP, and the seller to discover your issue.

I could open up their page's code and run through it but that would most likely find nothing on my end unless it's an obvious code break. Yes some apps will 'guess' the errors meaning where others will fail or refuse to go further (or outright lock up - IE was horrible with that).
Anyway, I enjoyed your slice at my attempt to offer a little troubleshooting before heading out the other day.

My conclusion; the problem is only effecting a few out there and can only be resolved between the effected customers and the site. If was effected however, I could have picked apart their code and called the shop - but since I don't see what the effected folk do then perhaps you can assist them further.
 
My conclusion; the problem is only effecting a few out there and can only be resolved between the effected customers and the site. If was effected however, I could have picked apart their code and called the shop - but since I don't see what the effected folk do then perhaps you can assist them further.
As a "system analyst" (whatever that means -- your profile lists you as a "field service technician") who hasn't actually identified the cause, you probably don't want to conclude much of anything about the scope of the problem and how many people it's affecting. Just viewing a particular page's code isn't anything like the type of dynamic web debugging that needs to be done in this sort of situation, and I guess a "system analyst" wouldn't do that. So what you mean by "system analyst" (which I thought was an antiquated term at this point) sounds like just first-level tech support information-gathering -- which you might then turn over to the actual developers for diagnosis and correction. Fair enough. That's exactly what needs to be done.

I'm not interested in doing that sort of debugging for the company myself, and they wouldn't want to pay my consulting fees on that anyway.

But the way to pursue this is for all those having the problem to continue pressing the company that runs the site for a solution. This should be done by using their Contact Us link, reporting as many details of the problem as they can, and then following this up with a phone call in which you reference the report(s) you've made. If enough people do this, it may get a response. It's especially important to do the phone follow-up since those report submissions may go directly to the people (system analysts?) responsible for the problem -- and who are doing their best to cover it up because they don't know how to fix it. So CALL CUSTOMER SERVICE about it and tell CUSTOMER SERVICE you submitted a problem report and that this is making it difficult to BUY THEIR PRODUCTS. Otherwise, just wait and hope they fix it in the fullness of time. :rolleyes:
 
doubleset; I will not even read your long story there.
I have worn many hats along the way in life, including that of Instructor where I have produced several Microsoft Engineers under my training. I have taught classes for two manufacturers and a trade school, I have served as a Regional Specialist for one, not to mention I have also been a welder and a skydive coach; that don't mention web building either. And I have done plenty more on the side with Networking and web development.
If you know how to use Google then look us 'System Analyst' if you don't know what one is.
I only offered a quick check to see if the site had trouble with FireFox: it don't.
I would offer further assistance to anyone wishing it; but you appear to be the Master with Java, so go fix it :thumb:
 
I would offer further assistance to anyone wishing it; but you appear to be the Master with Java, so go fix it :thumb:
What a silly and nutty thing to say. If you know anything about this, you should know that you can't "fix it" without access to the server code. It isn't a browser config problem. The fix needs to be done on the server side because that's where the problem is. Exactly what type of further assistance would you offer? I mean -- really -- if you have the solution to this, please just post it.
 
To everyone on this forum I apologize. My intention wasn't to create any problems or friction. I was seeking input from someone that had encountered this issue and had fixed it. Buying online is my usual way of doing business with many companies. First time ever with a problem with a website purchase. I have used the "contact us" form and told the person when I called in an order. Tried Windows 10, Windows 11, Apple OS (iPad) and Android phone and none worked. Only thing in common to all those is my broadband service which is supplied by Spectrum. Sometimes my IP address says I am in Kentucky when I actually am in Ohio If the issue never gets resolved I will survive.
 
Only thing in common to all those is my broadband service which is supplied by Spectrum.
That's not the problem. People with different ISPs are having the same problems. I'm seeing the problems myself on four different browsers (to varying degrees), and I don't have these problems at all on any other sites: Chrome, Firefox, Internet Explorer, and Microsoft Edge. All configured differently, and the MS browsers have the default configurations.
 
The second "contact us" got a reply which she said that they would contact the web company and she was sorry for the trouble.
Ah ... Well, that makes perfect sense. As expected for a small company like that, they don't do their own on-site web maintenance and support, but pay someone else to do it. With any luck at some point "the web company" will discover the browser-dependent bug(s) they introduced when they "upgraded" something. And poof! The problem will magically disappear. :)
 
At this point I can't get any of my four browsers to even connect to the login page:

"The requested URL was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request."

I even tried it on my wife's computer and got the same result. The results are symptomatic at least of bugs in their error-handling code. It may be a while before this stuff gets fixed. :confused:
 
Last edited:
I could have told you yesterday that Log Cabin doesn't maintain their own server, just look at the bottom of the page and it says so.
Works fine from my Android using Chrome.
 
Status
Not open for further replies.

Latest posts

Back
Top