כפתור "שמור שינויים" נמוך מאוד בדף ממשק העדפות המשתמש שלי

סיכום מבוסס בינה מלאכותית

The user debryc reports that the “Save Changes” button is positioned too low on their user preferences page, a bug not present on Discourse Meta. Falco suggests it’s likely a theme issue and recommends testing in Safe Mode. debryc identifies the issue occurs when two unofficial plugins—discourse-events and discourse-layouts—are active. angus explains the conflict arises between discourse-events and the official discourse-calendar plugin, as both use the .calendar class with conflicting styles. He advises using discourse-calendar for event management and uninstalling discourse-events unless specific needs require it, as the latter is maintained only for niche use cases.

I’m experiencing this odd bug where my “Save Changes” is very low on my user preferences interface page. The button is in the right place in every other preferences category.

I am not experiencing this on Discourse Meta.

If it doesn’t happen on Meta this is most likely a theme issue. Can you reproduce on Safe Mode?

The bug occurs when I do not disable unofficial plugins.

My two unofficial plug-ins are

https://github.com/paviliondev/discourse-events

and

https://github.com/paviliondev/discourse-layouts

@angus What do you think? Have you seen this bug before?

Try rebuilding with one disabled to isolate the culprit. After finding which one, please report in the plugin topic.

@debryc This one is caused by a conflict between the discourse-events plugin (Pavilion’s) and the discourse-calendar (Discourse’s) plugin on your instance. The discourse-calendar plugin gives the class .calendar a set height (645px), and the discourse-events plugin uses that same class in the settings view.

Unless you have specific needs served by the discourse-events plugin (i.e. Pavilion’s) I would suggest you use the discourse-calendar plugin to manage your events and uninstall discourse-events. We actually use discourse-calendar ourselves to manage internal Pavilion events. We only maintain discourse-events for specific use cases we’re supporting, otherwise we’d deprecate it entirely.