Loading...
 
Skip to main content

Features / Usability


Unable to log in - TikiWiki update from 24.11 to 24.13

I wanted to update our Tiki instances to 24.13. Unfortunately, I can no longer log in with this version.

Message when logging in correctly (tiki-login.php) – STATUS_CODE 500
Image

If you enter invalid login details, you can access tiki-login.php without any problems.
Image

Does anyone have any ideas as to why this is happening?

Christoph wrote:

I wanted to update our Tiki instances to 24.13. Unfortunately, I can no longer log in with this version.

Does anyone have any ideas as to why this is happening?


Hi,

Your 500 response look like PHP throwing a fatal exception before rendering the page.
Look at your web‑server php‑error.log (name and path depends) right after you try to log in.

That should give a first hint.

You can contact me in private if you prefer.

Bsfez | Tiki Express TutorialsQuestion | bsfez-at-opensourcesolutions-dot-pro | https://opensourcesolutions.proQuestion
Bernard Sfez / Tiki Specialist wrote:

Hi,

Your 500 response look like PHP throwing a fatal exception before rendering the page.
Look at your web‑server php‑error.log (name and path depends) right after you try to log in.

That should give a first hint.

You can contact me in private if you prefer.

Bsfez | Tiki Express TutorialsQuestion | bsfez-at-opensourcesolutions-dot-pro | https://opensourcesolutions.proQuestion


Hi. No entry is created in the php-error-log.
I’m not yet sure which of our settings is causing this issue.
Our wiki is multilingual and 2FA is enabled. However, these settings alone do not cause the problem in the demo system.
In our Tiki, however, I can disable the 2FA option under login, and after that, users can log in again:
Image

Christoph wrote:

Hi. No entry is created in the php-error-log.
I’m not yet sure which of our settings is causing this issue.
Our wiki is multilingual and 2FA is enabled. However, these settings alone do not cause the problem in the demo system.
In our Tiki, however, I can disable the 2FA option under login, and after that, users can log in again:
Image


Hi,

Good you got access back.

If the PHP error log is empty it usually means that PHP isn’t configured to write fatal errors (or the file you’re looking at isn’t the one PHP uses). I won't go too deep here, but you could:

  • Verify which error log PHP actually writes to
  • Create a tiny test page (``) and visit it.


If you see “test” on screen, `display_errors` is enabled, else...
log_errors = On, display_startup_errors = Off, error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT

Knowing what is going on will help you to understand what you can do.
This said, Tiki24 is back to the future version ? 😉
lifecycle