From Calldoctoday

Reply to From Calldoctoday on Fri, 14 Jan 2022 20:36:46 GMT

julian — Fri, 14 Jan 2022 20:36:46 GMT

calldoctoday Would you believe me if I said it was solar flares?

Reply to From Calldoctoday on Fri, 14 Jan 2022 20:35:06 GMT

calldoctoday — Fri, 14 Jan 2022 20:35:06 GMT

Jonathon Seems to be working right now. Thank you. What exactly was the problem, do you know?

Reply to From Calldoctoday on Fri, 14 Jan 2022 20:08:58 GMT

Jonathon — Fri, 14 Jan 2022 20:08:58 GMT

nodebbtest Thanks guys! Hopefully, this fixes it. Everyone, please let us know if you keep seeing it.

Reply to From Calldoctoday on Fri, 14 Jan 2022 18:51:51 GMT

nodebbtest — Fri, 14 Jan 2022 18:51:51 GMT

Hello,
We pushed a fix for the forbidden issue, if you are still getting it please clear your browser cookies and refresh the forum. Let us know if you still experience the issue after doing that.

Reply to From Calldoctoday on Thu, 13 Jan 2022 19:35:32 GMT

calldoctoday — Thu, 13 Jan 2022 19:35:32 GMT

Jonathon No Problem, you are very welcome.
Definitely still doing it as when I just logged in to see this message & initially tried to respond it did it again. Recycled & immediately cleared up. All this was well within one minute of login in, but I was not logging the seconds.

Reply to From Calldoctoday on Thu, 13 Jan 2022 15:33:41 GMT

johnsbrewhouse — Thu, 13 Jan 2022 15:33:41 GMT

It is still happening. It is like the site times out. I just hit refresh and it allow the reply to be posted. Somewhere in their script they have something that limits the amount of time for replies.

Reply to From Calldoctoday on Thu, 13 Jan 2022 15:13:12 GMT

Jonathon — Thu, 13 Jan 2022 15:13:12 GMT

calldoctoday Thank you! I will pass this on! @DennyO Hopefully what Doc gave us will be enough but if anyone does see it please let us know and follow same procedure that he did with he F12 and the screen shot.

Reply to From Calldoctoday on Thu, 13 Jan 2022 08:46:57 GMT

Denny O — Thu, 13 Jan 2022 08:46:57 GMT

Jonathon OH -ELL YES!!! for at least the last 2 days now.
It seems to go away only if I reboot the computer.

I’ll keep your request in mine but it seems I’m the one that is in the tail end of this group. You will have it solved by the time I’m back.

Reply to From Calldoctoday on Wed, 12 Jan 2022 23:48:55 GMT

calldoctoday — Wed, 12 Jan 2022 23:48:55 GMT

Jonathon No problem, it should happen now when I try to submit this.
Well, I am not sure what to say about myself. 40 years ago when few folks knew much of anything about a lot of this computerized stuff, I could do a whole lot, very well. Now, everyone seems to know a whole lot about it & I seem to know nothing. That my friend is embarrassing & humiliating.
Here goes.
I think this is it;
[Intervention] Images loaded lazily and replaced with placeholders. Load events are deferred. See https://go.microsoft.com/fwlink/?linkid=2048113
app.js:360 ServiceWorker registration succeeded.
stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j96&tid=UA-1727082-7&cid=1756617139.1575052261&jid=692688200&gjid=1538958226&_gid=1185677325.1641675375&_u=ACCAgEABAAAAAE~&z=1438324046:1

   Failed to load resource: net::ERR_BLOCKED_BY_CLIENT

app.js:145

   [deprecated] app.removeAlert is deprecated, please use alerts.remove

app.removeAlert @ app.js:145
4main.js:37

   Uncaught TypeError: Cannot read properties of undefined (reading 'test')
at HTMLAnchorElement.u (main.js:37:41)
at HTMLAnchorElement.handle (jquery.js:5895:29)
at HTMLBodyElement.dispatch (jquery.js:5430:27)
at HTMLBodyElement.m.handle (jquery.js:5234:28)

app.js:145

   [deprecated] app.removeAlert is deprecated, please use alerts.remove

app.removeAlert @ app.js:145
2main.js:37

   Uncaught TypeError: Cannot read properties of undefined (reading 'test')
at HTMLAnchorElement.u (main.js:37:41)
at HTMLAnchorElement.handle (jquery.js:5895:29)
at HTMLBodyElement.dispatch (jquery.js:5430:27)
at HTMLBodyElement.m.handle (jquery.js:5234:28)

4app.js:145

   [deprecated] app.removeAlert is deprecated, please use alerts.remove

app.removeAlert @ app.js:145
/api/v3/topics/4884:1

   Failed to load resource: the server responded with a status of 403 (Forbidden)

app.js:138

   [deprecated] app.alert is deprecated, please use alerts.alert

app.alert @ app.js:138
DevTools failed to load source map: Could not load content for https://meatgistics.waltonsinc.com/assets/src/modules/pulling-drawer.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for https://meatgistics.waltonsinc.com/assets/src/modules/jquery.form.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

Reply to From Calldoctoday on Wed, 12 Jan 2022 22:59:01 GMT

Jonathon — Wed, 12 Jan 2022 22:59:01 GMT

calldoctoday Thank you for that, and since it just happened I can tell them it is still happening. The next time it happens, can you hit f12 to bring up the code on the right hand of the screen and screen shot that? That is what will give the nodeBB people what they need. Obviously, not just him, anyone please do that.

Tex_77 The funny thing is I am basically as smart as Allen about all this stuff, which is to say not very smart! Austin is the really good one and Rachel is picking it up but I just try to keep up…and usually dont

Reply to From Calldoctoday on Wed, 12 Jan 2022 21:30:36 GMT

calldoctoday — Wed, 12 Jan 2022 21:30:36 GMT

calldoctoday Well, this time when I tried it again it deleted my post response too when I was trying it again & using Jonathon Jonathon’s tip. It is a snipping tool, I can deal with that. Here it is.

Reply to From Calldoctoday on Wed, 12 Jan 2022 21:22:39 GMT

calldoctoday — Wed, 12 Jan 2022 21:22:39 GMT

Jonathon OK, here is exactly what happens.
I get on to Meatgistics, completely logged in.
I go to respond to a post, give a thumbs up, anything.
When I hit submit I get the “Forbidden” error & cannot post.
I hit refresh & then hit submit again.
Everything then works fine from there on out.
Until I close the page & open it again, then, REPEAT, no Pete.

Reply to From Calldoctoday on Wed, 12 Jan 2022 19:51:13 GMT

PapaSop — Wed, 12 Jan 2022 19:51:13 GMT

Tex_77
LOL

Reply to From Calldoctoday on Wed, 12 Jan 2022 15:44:11 GMT

Grimpuppy — Wed, 12 Jan 2022 15:44:11 GMT

I get this message with safari on my iphone. I always have megistics tab open in the back ground. When I come back to it after a period of time and try to post, I get that message. I just hit refresh and then am able to post again.

Reply to From Calldoctoday on Wed, 12 Jan 2022 15:28:44 GMT

Tex_77 — Wed, 12 Jan 2022 15:28:44 GMT

Jonathon mind blown…what it must look like in your head…

Reply to From Calldoctoday on Wed, 12 Jan 2022 15:10:50 GMT

Jonathon — Wed, 12 Jan 2022 15:10:50 GMT

If anyone does see this, and can do this, please just post the red text here. Also, and this is an amazing tip, if you are on Windows, hit the windows key, the shift key and the S key. That will open up a snapshot tool that will allow you take a “screenshot” by drawing a box around what you want to record. It automatically puts it in your clipboard so you can just come to meatgistics, hits Reply (the one up top, not the Post Quick Reply) and hit Ctrl and the V button and it will paste it right in as a pic

Reply to From Calldoctoday on Wed, 12 Jan 2022 15:06:08 GMT

Jonathon — Wed, 12 Jan 2022 15:06:08 GMT

FYI, below is the response from NodeBB. They have applied a fix for it
I have applied a fix that might fix the forbidden issue. When this happens to someone again can you ask them to check the value of config.csrf_token in their browser console. I have attached a sample screenshot show it in chrome.

They can also check their network tab in the browser to find the request that failed and send us that too.

So, what they are asking you to do is when you see this issue, please hit f12, which will open up the website coding on the right side, then get that part that is in red.