Usually I add a section to the theme's CSS rather than editing any core files in CiviCRM.
Note that there is also a "Custom CSS URL" that you can add, and you can also disable the core CiviCRM CSS if you want to. (Administer > System Settings > Resource URLs)
Here we check what form we're ...
you need to enable the civicrm theme module, that allows you to to set specific themes for backend and frontend pages. You don't need to download it, it's already there, you just need to enable it.
By default, it's the same theme that the other "normal" drupal pages and you need to have enabled the themes you want to assign to civi
There has been some work going on to support shoreditch for CiviCRM 5.13. The temporary solution(until a new release is available) is to make the Menu colour to white by navigating to CiviCRM >> Administer >> Customize Data and Screens >> Display Preferences. Update the form by changing the 'Menu Color' to white
One consideration is to use different themes for the front office and the back office.
The front office are the profile pages used to gather information from the constituents (or maybe you are using webforms in combination with webform_civicrm). These should be themed according to the official stylebook of your organization. They are part of the marketing ...
Bright and clean: I use Seven (ships with Drupal 7 Core - so well supported) as CiviCRM Administration theme - for nearly all of our projects. Easy to subtheme as well - making it a MySeven - if/when required.
In Drupal 7 at /admin/appearance you can specify what Drupal theme to use for front-facing civicrm pages, and separately which one to use for back-end civicrm interface.
Hope that helps. Not sure I quite understood your question but thought this might be what you need.
you can override (not recommended):
or set your custom error template here:
You can also specify a different error handler in that setting
Watch out for themes or plugins that use Backbone.JS calls. They seem to be causing some issues right now. One such theme is Salient.
The JetPack plugin also seems to be suffering from the same problems. (Search the StackExchange for backbone and you'll see a few different threads.)
The Virtue theme has styling issues.
Twenty Fourteen provides good ...
Assuming the file you want to load is the one located in the CiviCRM plugin folder at 'civicrm/packages/backbone/backbone-min.js', then you'd use:
wp_enqueue_script( 'your_backbone_handle', CIVICRM_PLUGIN_URL . 'civicrm/packages/backbone/backbone-min.js', array(), CIVICRM_PLUGIN_VERSION );
Do you see &snippet=1 in your contribute page URL?
That parameter can be used to deactivate the theme on a CiviCRM page.
CiviCRM demo donate page as per normal & then without theme
CiviCRM profile page as normal & same without theme
If that parameter is present in the link to your contribution page, remove it and see if this restores the ...
Another (simpler) option that comes from a slightly different angle -- set up a Page Redirect using Eileen's extension so the user doesn't see the error message at all. This extension redirects all traffic from disabled contribution pages to a default contribution page (which you specify). So if you have a disabled customized donate page that you used ...
After inserting some debug code per recommendation at chat.civicrm.org, I discovered an even more focused repair is to just change a single line in civicrm_in_wordpress_set() within civicrm.php.
$page = get_query_var( 'page' );
$page = $_GET['page'];
and all problems we have noted disappear. The get_query_var call involves calls to our ...
Karl has already posted my solution to this issue, but for those who want to update their CiviCRM install with immediate effect, the patch can be found on the GitHub repo for the CiviCRM-WordPress plugin.
Eventually I found out what the problem is and it is caused by the child theme that I had created. Another problem elsewhere that had an extra blank line at the start of a news feed and Demerit's comment above suggested this as a solution. When I changed to the base theme all was fine. Going back to functions.php for the child theme I found a blank line ...
We have been using CiviCRM shoreditch theme for quite a long time until we switched to Kindly Theme by artfulrobot for some of our clients recently. Both are good in their own aspects. Around 2.4k sites in this universe are using CiviCRM shoreditch theme. We also have custom theme inheriting Drupal bootstrap3 theme for some clients to match their screens.
As of 4.7 there is no more 'Fatal Error Template' setting. See https://issues.civicrm.org/jira/browse/CRM-16478
You can instead use the standard approach to overriding template files as described here: http://wiki.civicrm.org/confluence/display/CRMDOC/Theming+CiviCRM
The custom template directory can be set in: CiviCRM > Administer > System settings > ...
Personally I often like https://www.drupal.org/project/liquid_coolness
Simple, clean theme, that is still pleasing to see. Has liquid width, so if you have a big screen you can make use of it for CiviCRM screens.
Not really maintained though.
FWIW, if you want to extend an analogy from the jQuery.noConflict(), you might try patching js/noconflict.js. The theory is to load files in this order:
Civi's version of each upstream library (jquery, backbone)
Civi's *.js files (which reference the upstream library)
noconflict.js (which obscures Civi's version)
Avada, Divi, X theme, Genesis, Virtue and in general most well-developed WordPress themes work fine. I think BeTheme is OK too.
The Slider Revolution plugin causes JS problems and can be disabled and replaced easily. A lot of commercial themes bundle this plugin.
You can still expect to do some work making CiviCRM pages display nicely because CiviCRM uses ...
Render all CiviCRM public pages in a responsive CMS theme (eg a bootstrap one) and then add some css for the labels - I typically position the labels above the input boxes (on form) and above the answers (on confirm and thank you) for small screen sizes.
I did not work on the site, but looking at the source code from View Source in the browser, it looks like the Bootstrap theme was the main theme, and then they created a subtheme called "civicrm_bootstrap" off of that.
This is a core issue (not specific to Shoreditch) and there is an issue with some discussion related to it here:
To tag on to your specific point about Shoreditch's CSS, I have found this to be problematic for the display reasons you mention (conflicts with CSS from the front end theme) but also for performance ...