Title: &quot;No Theme&quot; CSS issue
Last modified: August 24, 2016

---

# "No Theme" CSS issue

 *  Resolved [keygrip](https://wordpress.org/support/users/keygrip/)
 * (@keygrip)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/no-theme-css-issue/)
 * I have No theme selected and am getting 2 errors in the console. The No Theme
   option is trying to link to 2 css files that don’t exist:
 * /wp-content/plugins/wp-fullcalendar/includes/css/jquery-ui/NoTheme/jquery-ui.
   min.css?ver=1.0.2
    and /wp-content/plugins/wp-fullcalendar/includes/css/jquery-
   ui/NoTheme/theme.css?ver=1.0.2
 * [https://wordpress.org/plugins/wp-fullcalendar/](https://wordpress.org/plugins/wp-fullcalendar/)

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Support [angelo_nwl](https://wordpress.org/support/users/angelo_nwl/)
 * (@angelo_nwl)
 * [11 years ago](https://wordpress.org/support/topic/no-theme-css-issue/#post-6110127)
 * I get this too, I’ve let the devs know about it.
 *  Plugin Author [Marcus (aka @msykes)](https://wordpress.org/support/users/netweblogic/)
 * (@netweblogic)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/no-theme-css-issue/#post-6110245)
 * Sorry for the delay, this is fixed in the latest update 0.9.1

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘"No Theme" CSS issue’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wp-fullcalendar.svg)
 * [WP FullCalendar](https://wordpress.org/plugins/wp-fullcalendar/)
 * [Support Threads](https://wordpress.org/support/plugin/wp-fullcalendar/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-fullcalendar/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-fullcalendar/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-fullcalendar/reviews/)

 * 2 replies
 * 3 participants
 * Last reply from: [Marcus (aka @msykes)](https://wordpress.org/support/users/netweblogic/)
 * Last activity: [10 years, 9 months ago](https://wordpress.org/support/topic/no-theme-css-issue/#post-6110245)
 * Status: resolved