Skip to content
This repository has been archived by the owner on Mar 10, 2024. It is now read-only.

Login Error 1.0 #422

Open
kevingorman1000 opened this issue Jun 13, 2022 · 8 comments
Open

Login Error 1.0 #422

kevingorman1000 opened this issue Jun 13, 2022 · 8 comments

Comments

@kevingorman1000
Copy link
Contributor

Have noticed a bug that doens't allow login within the 1.0 milestone version (Latest canary).

Whenever you login after a session has expired, it still states your session has expired meaning you're unable to login. Possibly to do with the cookie not setting/unsetting?

@ItsAGeekThing
Copy link
Member

Have noticed a bug that doens't allow login within the 1.0 milestone version (Latest canary).

Whenever you login after a session has expired, it still states your session has expired meaning you're unable to login. Possibly to do with the cookie not setting/unsetting?

I'll deploy a test instance when I get a chance to attempt reproducing this.

What web server are you testing on and what version of PHP?

@kevingorman1000
Copy link
Contributor Author

Used XAMPP and WAMP, both producting this bug. PHP 8.0.13. Disabling the required API auth within oc-includes/apiAuth.php (Setting it to === False) seems to resolve the issue but obviously I know it's disabled the API Auth. I'd imagine there is an issue within that nested if statment somewhere.

@Cambridgeport90
Copy link
Contributor

Cambridgeport90 commented Jun 14, 2022 via email

@phillf
Copy link
Contributor

phillf commented Jun 14, 2022

@Cambridgeport90, I would be careful with what you are saying. It seems like you are insinuating that XAMP/WAMP aren't allowed at all. (Take not that I didn't use the word "supported").

I do think that if one is doing testing/development on Windows they should be using IIS with PHP instead just to avoid the weird shenanigans that default XAMP can pull which we saw with earlier versions of OC. I don't believe we have seen those issues with 1.0.0 as of yet.

@kevingorman1000
Copy link
Contributor Author

I have personally developed several web apps within PHP using xampp and haven't every expeirenced any problems when moving it over to a shared/dedicated hosting provider. If you wish, I can set up IIS and use it through that, but most people will use apache when they get shared hosting rather than IIS. I could however be wrong?

@phillf
Copy link
Contributor

phillf commented Jun 14, 2022

@kevingorman1000, like I said, I don't believe we haven't seen those issues from earlier versions of OC in the context of XAMP/LAMP.

Despite the fact XAMP/LAMP isn't recommended I think it's good to have at least one of us developing on top of it just to be sure that we aren't missing anything.

@kevingorman1000
Copy link
Contributor Author

I've found that WAMP provides a lot more error logs than XAMPP, I'm happy to carry on using WAMP as I believe the issues I have experienced (IE The API Auth) is related to the actual app rather than the environment. If I start noticing any odd behaviours, I'll be sure to log it.

@Cambridgeport90
Copy link
Contributor

Cambridgeport90 commented Oct 11, 2022 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants