[Opencart 4.0.2.3 Bitnami Google Cloud] Admin Cannot login & Bugs #1538
Labels
opencart
solved
tech-issues
The user has a technical issue about an application
triage
Triage is needed
Platform
Google Cloud Platform
bndiagnostic ID know more about bndiagnostic ID
e2f05f9d-ce5e-7d4d-3d15-6f03f61d1294
bndiagnostic output
No response
bndiagnostic was not useful. Could you please tell us why?
Only telling me what I know
Describe your issue as much as you can
I recently changed the currency from AUD to USD in Opencart because their currency module has calculation issues and does not calculate correctly unless it is based on USD as default.
Then I changed one item in the product to reflect a different price and the whole system crashed.
Now the admin login does not allow me in and does not report errors for incorrect passwords.
After attempting to login, the login page refreshes without any warnings.
Upon password reset, the first and confirmation passwords can be different without error.
In the Opencart forum they suggest version 4.0.2.3 has too many bugs that need to be ironed out and to use version 3.0.3.9.
Thinking Bitnami would choose a more stable release, I have purchased extensions and am now left with nothing at all.
Bitnami Opencart documentation online is for older versions which also does not help.
If it is as simple to get Opencart to tell me there are issues with this release, it just amazes me Bitnami would make this version their primary release.
From what I make out, it appears to be either a cookie session issue that I have tried everything to fix
or a duplicate database entry which appears to have been an issue through many versions.
I have tried clearing cache on browser, in VM, changing cookie settings in currency files, in framework
and other files as suggested for older version with similar issues.
If anyone has experienced this issue and may have advice, I would appreciate any feedback.
FYI, the cookie error listed in Developer tools
Cookies marked with SameSite=None must also be marked with Secure to allow setting them in a cross-site context. This behavior protects user data from being sent over an insecure connection.
Resolve this issue by updating the attributes of the cookie:
Specify SameSite=None and Secure if the cookie is intended to be set in cross-site contexts. Note that only cookies sent over HTTPS may use the Secure attribute.
Specify SameSite=Strict or SameSite=Lax if the cookie should not be set by cross-site requests.
The text was updated successfully, but these errors were encountered: