Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: General JEM setting>User Control>Registration>Allow event Registration #1879

Closed
jojo12 opened this issue Jan 2, 2025 · 11 comments
Closed
Labels
fixed Have a commit with the solution.
Milestone

Comments

@jojo12
Copy link
Contributor

jojo12 commented Jan 2, 2025

Perhaps the following error is just older and only detected now! Sorry from my part.

The event registration in general JEM settings in Backend has 3 options: No, Yes and Allow Event Registration.

If I choose there "Yes", then the frontend edit shows only a yes which can't be changed "Yes".
When I create an event in frontend, there is (in the view) only the title "Registration" and a subtitle "Description". This is wrong!

If I create an event in backend, I have a box with the 3 possibilities and "Yes" is chosen.
In the view the "Registration"-part is full there, as it should be!

I see, the settings in backend and frontend are not congruent (=synchronised), this means on backend it can be "No" and on frontend it can be "Yes"

@jojo12 jojo12 added bug Something isn't working releaseblocker labels Jan 2, 2025
@jojo12 jojo12 added this to the JEM 4.3.2 milestone Jan 3, 2025
mckillo added a commit that referenced this issue Jan 8, 2025
When event is saving in frontend, if the 'registra' field does not exist or is null, set it to the value from jem settings
@mckillo mckillo added fixed Have a commit with the solution. and removed releaseblocker labels Jan 8, 2025
@mckillo
Copy link
Collaborator

mckillo commented Jan 8, 2025

Test it. Now you can register for the event if the JEM setting is set to 'yes'.

mckillo added a commit that referenced this issue Jan 8, 2025
When event is saving in frontend, if the 'registra' field does not exist or is null, set it to the value from jem settings
@jojo12
Copy link
Contributor Author

jojo12 commented Jan 8, 2025

it works, thanks
important to know: if general JEM setting is set to yes, then backend event setting shows the possibility to "limited", but this is only possible if in general JEM setting "use event setting" is choosen.
In frontend you only see this possibility, if JEM general setting is "use event setting"

@jojo12 jojo12 added change and removed fixed Have a commit with the solution. labels Jan 8, 2025
@jojo12
Copy link
Contributor Author

jojo12 commented Jan 8, 2025

I tested more and I am not yet satisfied, sorry.
I made the following test (to reproduce):
The general JEM setting is NO, I change to YES and save and clean the cache
I open new event in backend, there is a dropdown field: where I can choose: NO, YES or LIMITED,
But the visible setting is NO as defautl!
I can change, but it should be YES as default because the general JEM says YES.
It's good that I can change to NO or to LIMITED.

In Frontend edit, there is no dropdown field, there is only YES. and I can't choose or NO or LIMITED.
It would be good to choose.

When the general JEM setting is USE EVENT SETTINGS, then frontend and backend is ok.

@mckillo
Copy link
Collaborator

mckillo commented Jan 12, 2025

OK, this was set up in the previous design, but it can be modified (coming soon).

mckillo added a commit that referenced this issue Jan 12, 2025
Now the registration option displays YES, NO, and LIMITED in the event edit view (Frontend), for both responsive and legacy layouts.
@mckillo
Copy link
Collaborator

mckillo commented Jan 12, 2025

Here you are. Now the registration option displays YES, NO, and LIMITED in the event edit view (Frontend), for both responsive and legacy layouts. Check it.

@mckillo mckillo added the fixed Have a commit with the solution. label Jan 12, 2025
@jojo12
Copy link
Contributor Author

jojo12 commented Jan 12, 2025

  1. BUT the only thing which rests: when JEM general =YES and you change in Backend or Frontend to NO, then there is in event view something visible
    grafik

If I see right, then "Description" is title of Venue Description --> nonsense

EDIT: the solution is easy: delete the line echo Text::_('COM_JEM_VENUE_DESCRIPTION');
AND move the <h2 class="register"><?php echo Text::_('COM_JEM_REGISTRATION'); ?></h2>
into the case 1 and case 2

@jojo12
Copy link
Contributor Author

jojo12 commented Jan 12, 2025

  1. When JEM general =NO, then you can change in Frontend editevent to YES.
    This should not be: if the administrator decides to disable event registration, this decision must be fix! NO can't be changed in FE!
    The only decision event creator should be able to do, is: YES or LIMITED
    (Because in Backend there are only admins, there is not the problem!)

mckillo added a commit that referenced this issue Jan 12, 2025
Now the registration option displays YES, NO, and LIMITED in the event edit view (Frontend), for both responsive and legacy layouts.
@mckillo
Copy link
Collaborator

mckillo commented Jan 12, 2025

Now I think I understand everything. Please check it, and I hope to resolve everything.

@jojo12 jojo12 removed bug Something isn't working change releaseblocker labels Jan 12, 2025
@jojo12
Copy link
Contributor Author

jojo12 commented Jan 12, 2025

Excellent! Sorry, sometimes my trials to explain are very complicated. Thank you for understanding!

The only thing, you forgot to adapt is the legacy view: the views/event/tmpl/default.php

EDIT: After that this can be closed.

@jojo12 jojo12 added the change label Jan 12, 2025
mckillo added a commit that referenced this issue Jan 12, 2025
Now the registration option displays YES, NO, and LIMITED in the event edit view (Frontend), for both responsive and legacy layouts.
@mckillo
Copy link
Collaborator

mckillo commented Jan 12, 2025

Here you are the update in the legacy view.

@jojo12 jojo12 removed the change label Jan 12, 2025
@jojo12
Copy link
Contributor Author

jojo12 commented Jan 12, 2025

thanks, This will be closed! Ready for 4.3.2

@jojo12 jojo12 closed this as completed Jan 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixed Have a commit with the solution.
Projects
None yet
Development

No branches or pull requests

2 participants