Greenpoint seeds!!

greenpointseeds

greenpointseeds

Well-Known Member
The last of the Secret Society Seed Co. stock is gone for the moment...

But there are still 3 strains up at Reverse Auction

Chickasaw Cooler - Purple Badlands - Orange Blossom Special​
 
Rivendell

Rivendell

Well-Known Member
greenpointseeds said:
Here ya go!

Bad Request (400) Errors

This is a cache/cookies related issue.

I am forwarding this bug to the developer.

I have seen this happen on a few different sites (not many) and it seems to be having issues with some specific browsers and the new GDPR integrations they are using with our platform. I read the changes are not 100% compatible yet. This is effecting auctions when someone else beats you to the sale and the cache is still showing them as available to you.

They should work themselves out when the platform updates.

Right now, the best thing to do is to clear your cache and cookies. Not with a plugin or extension, but the old-fashioned way using the instructions in the link above (following the instructions fully).
Click to expand...
Thanks, but that was the first thing I did and it had zero effect. What I am seeing is that after getting to any page, either a bookmark or from a google search, clicking on anything else returns that error. It has been going on all day and has nothing to do with the auction page, as it does this no matter where i am on the site. For example, clicking the forum button while on the home page.
 
greenpointseeds

greenpointseeds

Well-Known Member
Rivendell said:
Thanks, but that was the first thing I did and it had zero effect. What I am seeing is that after getting to any page, either a bookmark or from a google search, clicking on anything else returns that error.
Click to expand...
I will ask them again. This is what Google, Mozilla, and Apple are all telling me to do. They are telling me it is an issue with the cache on the browsers and that this is the only way to fix it until they update again. It is the personal caches that the platform and the browsers connect with each other (depending on settings chosen by the user and/or outdated defaults). The platform and the browsers have not been able to give me any other information but that.

This is their last response:

...I cannot say this enough: please push your users to clean their browsers and caches completely. 99% of the time it is because a user doesn't know how to clear their caches and cookies properly. They just clean one or the other, or they don't know how to. Keep this in mind before you explore other options. And if you can, please get access to their screen so you can properly clean their caches and cookies ("All Time", NOT "Past 24 Hours" or "Past Week"), close the browser completely (most browsers still run in the background even after closing them down), restart the browser and refresh any bookmarks that may be old or outdated.

This is not an issue with your site, but with the connection between caches. The 400 error IS NOT a Server-Side Error. It is a Client-Side Error. And users do not like hearing that there is something wrong with their browsers or their configurations. This bug is browser based on the client side and has nothing to do with the website. Therefore, it is a client and browser problem:

"All HTTP response status codes that are in the 4xx category are considered client error responses..."

"Since a Bad Request Error indicates that the request sent by the client was invalid for one reason or another, it’s entirely possible the issue stems from the clients settings. Your client may be trying to send a file that’s too big, the request could be malformed in some way (viruses, malware, browser extensions or plugins, ad-blockers, etc), the request HTTP headers could be invalid, and so forth. There are literally hundreds of things that could be the culprit at this point."

"If these errors are only occuring with one or two users (and nobody else is having similar issues), this just goes to prove that it is most likely a browser-related issue."​
 
Last edited:
Rivendell

Rivendell

Well-Known Member
greenpointseeds said:
I will ask them again. This is what Google, Mozilla, and Apple are all telling me to do. They are telling me it is an issue with the cache on the browsers and that this is the only way to fix it until they update again. It is the personal caches that the platform and the browsers connect with each other (depending on settings chosen by the user and/or outdated defaults). The platform and the browsers have not been able to give me any other information but that.
Click to expand...
I wasn't trying to put you on the spot, just wanted you to have as much info as I could provide. Thanks for looking into it.
 
greenpointseeds

greenpointseeds

Well-Known Member
Rivendell said:
I wasn't trying to put you on the spot, just wanted you to have as much info as I could provide. Thanks for looking into it.
Click to expand...
Of course. I didn't think that at all. I just didn't want you to think I was being lazy about it and so I wanted to give you everything they gave me :-)

I am checking out their last changelogs as we speak and will message you as soon as I get any further information. Promise.
 
Chunky Stool

Chunky Stool

Well-Known Member
greenpointseeds said:
This is a conflict between two plugins where the only choice is to disable one or the other. The developer has refused to update the plugin's code and it is a proprietary. I can remove the waitlists, but that's about it.

I have answered a few emails regarding this cross-code error already and the answer remains the same. Sorry there isn't a fair solution at this time (to anyone else reading this who has emailed me about this in the past).

We have sent 47 emails to date requesting they update their code and have opened over 100 tickets. Not much more I can do. I have exhausted all resources. They want $$$. Period.

Please send things like this to webmaster@greenpointseeds.com
(creating support tickets for website issues takes about 5000x-times longer when taking them from RIU or any other place because they have to be re-written from scratch - our email system has this integrated and it takes less than a second to start the process)

It only affects customers utilizing the waitlist functions. Without them, it works fine. Either way, it is a secondary UX blemish not worth their asking price to access their code. They only have one option: Developer/Multi-API-Access. And it is $5,500. Ridiculous. Lol.

View attachment 4163609
No Waitlists Active​
Click to expand...
This bug has nothing to do with waitlists.

REPRO:
  1. Log in.
  2. Left-Click "My Account" to go to the account information screen.
There you go. It repros every time from here.

It would seem there are actually two "My Account" drop-down menus that are very similar -- and the one that's displayed on the user account page is broken.

This is what happens when you use canned software.
Customization is a bitch and now they've got you by the short hairs... :roll:
 
greenpointseeds

greenpointseeds

Well-Known Member
Chunky Stool said:
This bug has nothing to do with waitlists.

REPRO:
  1. Log in.
  2. Left-Click "My Account" to go to the account information screen.
There you go. It repros every time from here.

It would seem there are actually two "My Account" drop-down menus that are very similar -- and the one that's displayed on the user account page is broken.

This is what happens when you use canned software.
Customization is a bitch and now they've got you by the short hairs... :roll:
Click to expand...
Thank you for the feedback. It is very helpful.

Unfortunately, like I said, the only quick way to get rid of it is by fixing the Waitlist integration. When removing it, it goes away forever and completely solves the problem. Me adding the part about how it doesn't show unless you have items in your Waitlist was merely an observation I included.

When I said:

"It only affects customers utilizing the waitlist functions. Without them, it works fine..."​

I should've been more specific and wrote:

"It only visually affects customers utilizing the waitlist functions during normal use. When not utilizing the Waitlist functions and when navigating the site normally, there are no visible blemishes..."​

Our situation and environment are different (as I am sure you know) than other base configurations. The only way to give you a complete understanding of this situation would be to give you admin access to the site because not everything is visible from the front-end. You also understand this isn't something we can do.

We have the best developers available to us and we trust what they do and what information they give us. We have to.
  1. One is a current WC developer who has been with them for years.
  2. The second one is a great guy I met at a WC conference in Italy a few years back and is also the author of some of the best-selling WP/WC books. He also teaches WP/WC for a living.
  3. The third one is a developer we found through integrations (he builds integrations for our platform for a living and he offered us paid extra assistance whenever we needed him).

These 3 different developers have tried to fix it and it's still the same outcome.

What you posted is just showing how it can be reproduced without items in the Waitlist. But the Waitlist is always there, just not visible. It loads with every account page just like WC and the other integrations (whether or not an action you perform calls them for visual content). The problem is always there, just not visible in the menu when there are no items in the Waitlist for a logged in user.

Opening it in another tab brings it back, yes, but that is not the issue we are having. If it was, you would be spot on. The issue causing this to display has nothing to do with visible items on the front-end, it has to do with a conflicting piece of code that is not visible from the front-end and is improperly using an override from another integration causing not only this issue (that we have been discussing), but one other that has nothing to do with the front-end.

We also only have one menu.

I have this same integration on 4 other sites and it has never been a problem except when it is installed with this other integration. But this other integration has no issues with any others.

I have gone through this a zillion times with them and have had our 3 different WP/WC devs go through and try it from all the other angles that I might have missed.

The Waitlist integration causes this.

The only other way I could explain it would be to reference ionCube. This is basically what we are dealing with and trying to pull conflictions from, but from within the encrypted code that is proprietary.

Either way, all suggestions and theories are helpful and welcome. They force me to go back through the details and sometimes I find stuff that I could have missed otherwise.

So thank you. Just please email about this so I can keep better track of it. I have a whole system taking care of website changes, updates and fixes and it is extremely helpful in getting things done faster.

EDIT: I just tested your theory, but the same thing: Waitlist. Sent your notes to WP/WC developers and they'll get back soon and I can update you by email or here. Email is better for me and is less confusing to the others who might not understand. And it doesn't muck up the forum with this type of information so there is more room for GPS growing and images :-)

UPDATE: Sorry Brother. They said the same thing I did. If you think of anything else, PLEASE email me so I can keep track of your notes easily so that we can use them to help in the future.

These things will not be an issue soon. That's all I can really say ;-)
 
Last edited:
mistermagoo

mistermagoo

Well-Known Member
The Blizzard Bush, Im just chopping it today, it really looks to be a great yielder , this was in a one gallon soil bucket, I also main lined it, for the most part , the Sativa side branching still took over but nugs are all fat , not much in smell but as others said after chop and even just a couple days funky smells start to mature from the Stardawg gear, time will tell in the taste and smells, old school smells for sure

I flipped her at around 16 inches , topped out around 40 inches , shoots up fast after 12/12

I hate estimating trichs on finishers like this with so many white hairs, but I’m saying around 70 %cloudy 20 %clear , 5 to 10 % amber , the ambers are very sporadic


... yes this is 91 DAYS FROM FLIP ...

grown under 400w vero cob LEDs
 
You must log in or register to reply here.
Top