Register page changed after login

Technical assistance
1

Infos:

  • Used Zammad version: 3.0.X
  • Used Zammad installation source: Cent OS via RPM
  • Operating system: Cent OS 7
  • Browser + version: Google Chrome 75.0.3770.100

Expected behavior:

  • Register page have field for set customer password and create account work normally.

Actual behavior:

  • Register page have weird behavior

Steps to reproduce the behavior:

But after any login and logout , now register page will look like this ->

image
image.png1920Ă—1080 64.2 KB

then even though user enter the right information, the “Wrong Username or Password combination.” will appear… also the user’s info will be registered with no password…

if I need to provide any more information , please tell me
With Respect,
Nangi

2

Can you please provide a step by step what you’re doing?
URLs would be interesting, too (without domain.tld-part).

Is this a clean Zammad-Version from our Github or did you fiddle in the code?

3

I’m not really sure what info should I provide more… but first I will add the url part :sweat_smile:

First enter

image
image1920Ă—1080 199 KB

Then click register as a new customer
image
image1920Ă—1080 178 KB

After login and logout and then click register as a new customer again
image
image1920Ă—1080 177 KB

No, I didn’t went into any of those (Even if I want to do it :joy:)
I follow the installation instruction : install on Cent OS via RPM
Didn’t do anything on rails console (Can’t run rails :sweat_smile:)
so I think, Yes it’s exactly a clean version of Zammad. (except I change the domain from local host to ip…)

If I need to provide any log or code or any more specific info please tell me.
Thank you for your attention.
With Respect
Nangi

4

Hey,

thank you very much!
I could verify this (your step by step helped a lot).

This is a bug and no feature, I already created a bug report for you:

1 Like
5

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.

6

Hi @nangi158,
this issue got fixed and will be released with version 3.4. Thanks for your support!

1 Like