-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Plugin conflict: The Events Calendar #2284
Comments
I took a peek at this tonight, but I don't seem to be able to reproduce the issue you're seeing. This is the plugin I tested with: https://wordpress.org/plugins/the-events-calendar/ When I scale the window narrower and wider it seems to respond appropriately, but let me know if there are any more specifics to try to reproduce the issue– I tried in a few browsers. I did also try logged in and logged out as well as going extra wide. Screen.Recording.2024-04-05.at.10.54.02.PM.movIf you are familiar with the browser inspector, if you can provide any additional context related to the classes/CSS that may be conflicting that can also help narrow this down. Also, any screenshots you can provide would also be great– is the entire monthly calendar disappearing or only partially? |
Thanks for the clarification– can you also provide a screenshot of what it should look like at desktop size? I can look around myself as well, but if you happen to have that as a reference that would be great, thanks. Also, you mentioned it may use a JavaScript function to trigger the swap– any chance you know that function name? I can see if there are any conflicts in there too. |
Version information can be found in the lower right of most WP admin screens
WordPress Version: 6.5
Nebula Version: 11.8.10.395
Describe the Problem
There seems to be a plugin conflict between Nebula and The Events Calendar that causes the calendar to only ever display the mobile version.
Steps to Reproduce
Expected Behavior
The plugin should be able to switch to desktop view on larger screens.
Additional Information
Strangely, the problem doesn't seem to happen if you're logged in to WordPress.
The text was updated successfully, but these errors were encountered: