#55217 closed enhancement (invalid)
welcome balloons
Reported by: | in2info | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | Administration | Keywords: | |
Focuses: | ui, css, administration | Cc: |
Description
hi there,
i use the Booking Ultra Pro CORE plugin
and since wordpress 5.9 it shows the welcome ballons in
the appointment view (see screenshot).
i can't get rid of this
Attachments (1)
Change History (5)
#1
@
3 years ago
- Milestone Awaiting Review deleted
- Resolution set to invalid
- Severity changed from minor to normal
- Status changed from new to closed
#2
@
3 years ago
- Component changed from General to Administration
- Focuses ui css administration added
Hi there, welcome to WordPress Trac! Thanks for the ticket.
Just noting that the balloons are attached to the .welcome-panel::before
CSS class, and should only be displayed on the Dashboard screen. It's weird for them to appear on a plugin screen like that. As noted above, I would suggest contacting the plugin developers. Feel free to reopen if this turns out to be a bug in WordPress core.
For reference, the new Dashboard Welcome panel was introduced in [52442] / #54489.
As a workaround, you should be able to remove the balloons with this code:
function wp55217_remove_welcome_balloons() { ?> <style> .welcome-panel::before { display: none; } </style> <? } add_action( 'admin_head', 'wp55217_remove_welcome_balloons' );
#3
@
3 years ago
Is there any reason for not being able to remove the balloons with just using this CSS?
.welcome-panel::before { display: none !important; }
I was able to add the function to remove the balloons from the welcome panel.
I bring up these things as I am these days reworking various WordPress tutorials that I have created. One of them is about removing and adding Dashboard widgets.
Hello and welcome to WordPress Trac,
This is occurring because of a poor implementation of specific widgets on WordPress dashboard and can't be fixed on WordPress Core side. Please contact the plugin author so they can fix the issue on their side.
I'm closing this ticket as it doesn't occurs on a fresh installation of WordPress (= without any plugin activated), but feel free to reopen it if needed.