CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Installing CiviCRM »
  • WordPress Installations (Moderators: Kurund Jalmi, Coleman Watts) »
  • Incompatibility with Genesis theme framework
Pages: [1]

Author Topic: Incompatibility with Genesis theme framework  (Read 1801 times)

nicolas

  • I post occasionally
  • **
  • Posts: 92
  • Karma: 6
    • cividesk
  • CiviCRM version: 4.4 LTS
  • CMS version: Standalone (yep)
  • MySQL version: 5.1
  • PHP version: 5.3
Incompatibility with Genesis theme framework
March 15, 2013, 11:11:19 am
I just installed CiviCRM on a Wordpress site using the Platinum child theme (based on Genesis theme framework). While the back-end is mostly OK (a few issues with the menu bar sometimes being incomplete or not displayed at all), I cannot get a single front-end page to display. By 'front-page' I mean CiviCRM content embedded in the main website, such as event information and registration pages, contribution pages, etc.

What happens is that instead of the CiviCRM content, there just is the frontpage content. This happens whether this is a direct link to the page (ie. 'Manage event', 'Event Links', 'Live page'), or when the page is embedded in a post with shortcodes ('Add New Post', 'Add CiviCRM Public Pages'). When switching back to the default WordPress theme everything works as expected.

I have traced this to the fact that CiviCRM insert content on front-end pages using the 'the_content' filter (ie. add_filter('the_content', 'civicrm_wp_invoke'); ), but for some reason this filter is not called by the Genesis theme.

Would this be considered a CiviCRM bug (ie. we're using the wrong filter, or a filter instead of an action) or a Genesis framework bug? Is there a workaround for this situation?
cividesk -- CiviCRM delivered ... your way!

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Incompatibility with Genesis theme framework
March 15, 2013, 11:26:14 am

In general, for all the CMS, with regard to development and testing, we use the default theme supplied by the CMS and implement the protocol that theme assumes

Dont know anything about genesis / platinum to say if 'the_content' filter should not be used. We will make fixes that will support other themes, if they also support the default theme and is not  a hack etc

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

nicolas

  • I post occasionally
  • **
  • Posts: 92
  • Karma: 6
    • cividesk
  • CiviCRM version: 4.4 LTS
  • CMS version: Standalone (yep)
  • MySQL version: 5.1
  • PHP version: 5.3
Re: Incompatibility with Genesis theme framework
March 16, 2013, 06:20:15 pm
I have tracked this issue down and resolved it. See: http://issues.civicrm.org/jira/browse/CRM-12131.

This is due to the fact that the WordPress integration assumes that the homepage for a website will contain at least one post. This was not true for my customer's website, which only contained a gallery slider.

The proposed change suggests a different filter to insert CiviCRM content in WordPress pages, with the added benefit of providing more flexibility for the end-user in controlling how the CiviCRM content is displayed through the use of a WordPress template.
cividesk -- CiviCRM delivered ... your way!

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Installing CiviCRM »
  • WordPress Installations (Moderators: Kurund Jalmi, Coleman Watts) »
  • Incompatibility with Genesis theme framework

This forum was archived on 2017-11-26.